#drogiblipie#drogiefedi
Mam grupę znajomych, w której dzielimy się na bieżąco informacjami o koncertach, meczach i różnych wydarzeniach. Obecnie wygląda to tak, że gdy ktoś znajdzie coś ciekawego wrzuca to na Whatsapp i chętni wpisują sobie do kalendarza. Pomyślałem, że #mobilizon się do tego nada lepiej, w związku z tym mam pytania do obecnych użytkowników:
Czy można stworzyć w tym własną grupę?
Czy można ustawić powiadomienia o wszystkich wydarzeniach z grupy?
Czy mobilizon synchronizuje się z kalendarzem?
Czy można importować wydarzenia z FB i różnych stron internetowych?
Dzięki Waszym dobrowolnym wpłatom możemy finansować wiele projektów oraz utrzymywać serwerownię KRK-DC, w której prowadzimy dla Was paletę usług, by wymienić m. in.:
Oferujemy tę infrastrukturę również dla takich serwisów jak: NoEvil.pl, WriteFreely.pl, Kbin.social, FOSSGralnia, Polesie.Pol.social, TePeWu.pl, SVMetaSearch, CesarstwoKwadratowe, OZZIP, SKK, Plony.org, Parasol.coop, KO-OP.pl i kilku innych.
Więc jeśli wygodnie Wam wspierać te serwisy finansowane przez społeczność na Patronite, oraz uznacie, że nasza wspólna praca jest warta waszych dotacji, to serdecznie zapraszamy ❤️
Venez découvrir ou partager vos connaissances,
y rencontrer les groupes locaux qui se développent sur ces réseaux,
Y FAIRE GRANDIR ENSEMBLE LA COMMUNAUTÉ NANTAISE.
Ça fait quelques temps qu'on prépare ça et maintenant c'est officiel : avec @Julie_ en partenariat avec @2i2l, nous proposons maintenant des formations sur #mastodon#Mobilizon et #PeerTube ! À chaque fois, les participant⋅es ressortiront de la formation équipé⋅es pour faire vivre le #Fediverse, dans un cadre perso ou pro.
Profitez-en aussi pour découvrir tout le catalogue de 2I2L, qui forme depuis 2007 au logiciel libre et aux formats ouverts. Scribus, MediaWiki ou Dolibarr, y'en a pour tous les goûts et ce sont des formations de qualité, construites sur mesure par des expert⋅es passionné⋅es.
Last weekend FOSDEM took place in Brussels, Belgium. However it was O₄FFDEM that provided the space for about 20 people to meet and discuss the future of events in the Fediverse for the whole Saturday. Among them developers like @lesion (developer of Gancio), setop (upcoming coordinator of Mobilizon), @dreirik (foss.events), @laurin (contributor to ActivityPods) and community members, (h)activists and event organizers like @becha or @eest9, just to name a few, and myself. Eventually, there were people from half of Europe: Montpellier, Strasbourg, Graz, Amsterdam, Italy, Vienna, Ljubljana, and Rotterdam.
Expectations
It was impressive how, despite the number of people present, it was possible for the group to de facto moderate itself, in particular through the experienced careful intervention of a few at the right moments. We began with a short round of introductions, in which expectations for the day were also clarified. We first decided to talk about values, to clarify what needs and concerns are generally present. We were all united by the desire to become independent of Big Tech, although there were several completely different concepts of how this would be achieved from a single point of view in the mix.
Dilemmas
It has become evident that in the case of events, from of a software developer’s point of view, one cannot simply speak of users, but must distinguish between organizers and participants, although the distinction can also be blurred in the case of a small community. Following dilemmas were identified:
regional vs global calendars
topical vs mixed calendars
aggregation vs autonomy
moderation vs censorship
Advantages of a physical meeting
The discussion about these aspects was extensive and, admittedly, did not always seem to me to be very target-oriented. However, it was necessary to balance our different backgrounds and bring us up to the same level of knowledge and it became more concrete after the lunch break when we decided to compare and work out the intentions and use cases of the existing applications and developments in more detail. I could recap this in detail here, but I think it is best to write a stand-alone follow-up article. Each project has its own approach: some focus on local communities, some focus on private events an another wants to provide a way to organize larger political movements with as few social features as possible. On top of that, people have come up with use cases that no developer ever seemed to think of before.
One activist’s question, “What’s the difference between federation and interoperability?“, which had been floating around the room all day, was finally addressed in a satisfying way with examples. Even if all applications can successfully aggregate and display events of others, it does not mean that they respect all mechanisms that control how the event is listed, whether the event is joinable via ActivityPub, whether these joins have to be manually approved, whether some event details visibility have a certain scope, etc.
Calendiverse
Perhaps one of the most important points was to enable the creation of event calendars, which are also aimed at people who do not want to have an account anywhere, but are simply looking for events. From the point of view of people looking for events, regional or topic-specific calendars are particularly important. Which events are aggregated and shown on an individual platform would be in the hands of the platform operators, which would then automatically play a major role in moderation.
Why use ActivityPub?
ActivityPub covers most of the features iCal offers for creating calendars by aggregating multiple sources, but adds a few more:
Follow relationships become tangible
Social media like features:
Boosting
Liking
Replies
Push, not pull based
Joining (Participants management)
Use moderation and governance tools from the Fediverse
Getting to a Common Ground
Mobilizon has already introduced a huge set of custom properties and ways to manage event objects in the ActivityPub world. We decided on a process to re-evaluate their choices and draft a Fediverse Extension Proposal (FEP) for the least common set of them. What makes an event:
Private locations which may be disclosed on participant’s acceptance
From Whom
To Whom: Public, Private, Unlisted
Why if not want to get listed just not “send” the event: e.g., Mobilizon -> federated groups -> federated private events
Let the sender of an event set the discoverability : the recipient might mistreat that
We decided to deal with advanced mechanisms such as sub-events, recurring events, irregularly rescheduled events in the future.
Summary
All in all, it was simply nice to get to know each other and exchange ideas with other people who pursue common or similar goals. Especially the exchange between developers and non-developers, who were in the majority, was of great importance from my point of view. Unfortunately, it is almost impossible to capture all the aspects in such a short recap. If you are missing something important, please have a comment. Many thanks to all of you, especially the organizers and those who were taking the meeting minutes.
There's barely 1 week to fund @Framasoft to develop @peertube@mobilizon and all the amazing projects they've brought you.
They're almost two thirds of the way. If you've been thinking about helping, NOW IS THE TIME.
Do you want an official #Peertube app? Do you want to see more content more easily discovered? To you want better #accessibility? Do you want a better #UX?
When writing the initial version of our project plan as signed and agreed with by NlNet we didn’t know yet about the dynamics of the community, specifically about how the cooperation between the maintainers of the #WordPress#ActivityPub plugin and #Mobilizon would be like. The level of collaboration with other #Fediverse developers would determine whether our project goals could only be achieved through a series of workarounds, or whether we could work together to strengthen interoperability and compatibility in the Fediverse.
Mobilizon was the first Fediverse application with true event federation. #Gancio has very limited ActivityPub capabilities, partly by design, but is working on an enhanced federation, and other services like #Friendica have a very different approach to events: their implementation focuses on sending invitations rather than publishing events. #Pleroma might get initial event support soon and it’s fork #Rebase already implemented it. As is usual with any software, you will find a lot of small bugs if you have not done any tests beforehand. In the case of Mobilizon, this was not possible since there were no alternative platforms to do the tests with in the past, especially if it comes to the instance-to-instance federation, so the only option was to test the Federation with other Mobilizon servers. We seem to be the first and we are fascinated and incredibly grateful for the willingness and prioritization that such issues have among the other developers (thanks to tcit and les). The issues may seem small, but they have a big impact: 304, 33, 321, 1509, 1507, 1392, 1385, 1388, 1387, 1378, 1376.
The other deciding factor for us was that we didn’t know how close the interaction with the upstream WordPress AktivityPub project would be. The exchange of ideas and the desire for a joint solution is strong. We would like to thank @pfefferle again for the regular exchange, his ideas and inspiration, without his commitment to the community our project would be less sustainable.
Tasks done (almost)
We published a repository that aims to make it easy for other developers, including ourselves to start developing and debugging WordPress along with Mobilizon.
We have created a pull request to add management of various ActivityPub transformers to the admin interface. The current implementation basically works, but we have a lot to polish and improve on our roadmap.
Using that patched ActivityPub plugin we explored writing transformers for two popular event plugins, this gave us a lot insight on what is important. These transformers already have fundamental compatibility with Moblizon.
Updating our About us page showing some information who we are.
Implement the followers list of the application actor in the admin UI along with the ability to reject, approve, and remove followers. We are very inspired by how #PeerTube has solved this in the admin UI. This of course includes a an option as:manuallyApprovesFollowers that can be set for an ActivityPub actor within WordPress.
Write an initial draft of the user documentation informing about custom ActivityPub transformers and instance-to-instance federation with Mobilizon. The target audience will be non-tech people. Parts of this will also be used as a non-tech description of our project.
Improve the admin UI and propose a solution to handle the settings for each transformer, if there are any.
Write more transformers for other popular event plugins to discover common pitfalls.
If you have any questions, ideas, or would like to help us, for example by testing our progress in case your are running a WordPress site with events yourself, please don’t hesitate to contact us. We don’t care if you have technical experience or what your background is: any kind of involvement is valuable to us.
#Mobilizon, the federated social events system by Framasoft, is pulling in some big new features. It's also moving out from under the Framasoft umbrella!
Framasoft, the French non-profit organisation for open source software such as PeerTube, says that after 5 years, Mobilizon has reached maturity. In December 2018 the organisation announced their plans to develop Mobilizon, with the goal of creating an alternative to Facebook Groups and events.
Over the years, they have added multiple updates, such as federation in 2020 and searching across Mobilizon instances in 2020. This month, they are releasing their final update, v4, with a variety of new features.
Event administrators can now send private announcements to attendees, allowing them to contact all people who have registered for an event directly. This announcement is a one-way communications channel, intended for organisers to broadcast information. Besides that, a chat system for attendees is also implemented, which federates with the rest of the fediverse.
Another new feature is the ability to import and synchronise events from other platforms, such as Meetup and EventBrite. Framasoft created an import tool that allows you to import and synchronise event information from these platforms into Mobilizon. iCal event feeds are support too, so this even works with most calendar tools.
The big platform for importing events from is Facebook. Here, Framasoft has done the work to get it to work, and the ball is now in Facebook’s court to approve and validate. Framasoft is clear that they do not have a timeline how long this will take, and that they are unsure if Facebook will do so.
While Framasoft sees Mobilizon has having completed their vision, it is far from over for the project. Framasoft will hand over the keys to the French association Kaihuri, who has been maintaining a Mobilizon presence for a while. Kaihuri recently got funding from NLnet to continue development work on Mobilizon, focusing on the user experience and improving interoperability. Meanwhile, Framasoft is betting big on PeerTube for next year, and is currently organising their yearly donation drive.
Events import and synchronization, announcements, conversations... with Mobilizon v4 releasing today, we're reaching our goals (and are ready to pass the ball!).
Import et synchronisation des événements, annonces des orgas, conversations... avec la v4 de #Mobilizon qui sort aujourd'hui nous atteignons nos buts (et sommes prêtes à faire la passe !)
Five Years Later, Mobilizon "Reaches Maturity" ( wedistribute.org )
With a new release under its belt, Mobilizon's developer Framasoft is stepping back from the project.