So, we're going to talk about what we're going to talk about, what we're going to talk about is what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about
what we're going to talk about, what we're going to talk about, what we're going to talk about, thoughts about what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to sit in there, what we're going to talk about, what they're going to talked about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we just talking about, what we're going to talk about, what we're going to talk about, what we were going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we should talk about, what we should talk about,
What do you think you're going to miss here over to make one of it?
Also, when you took about ten minutes, there's a big problem.
On the other hand, there's a lot of trouble.
You can tell if that you make the first thing,
and you're going to miss it.
It's not green, but you can do it.
Okay.
So, here we go.
You're on this side, the right side should do it.
Okay.
Sorry for people who have only the lips.
But what I'm seeing is that, sometimes that's on my own.
Not that good.
I'm explaining why.
And you will see why.
Maybe it's a good alternative.
So, I was speaking about the ergonomic of those platforms.
Most of the time, they are done for posting, posting contents.
They are not made for events.
And events are very particular.
They are days.
There is location.
There are also audience on who can attend and not.
And the searchability is really bad.
So, I don't know how you manage, but you have to follow a very specific people.
And it's crude for events at your local access message or something.
So, you have to be very careful.
You can really search.
You can bookmark.
So, you can't really sense what you have found to your friends.
And they have to go to the platform again and search again.
And also, it's also, again, also there's a lot of fragmentation.
So, if you are on a social network, you are not on another.
And by that, you turn share contents.
And also, they like a lot of interoperability.
They don't play anything for it.
And it's very easy to add the content to, for example, to have a agenda.
So, last year, from a self-step aside from the project.
And we offered them to take over the maintenance.
And we've been financially supported by an internet for this challenging transition.
So, we sense them a lot.
Now, after a year, we are here in front of you.
What?
It's still the same.
The next one will come.
Thank you.
So, we are very glad to be there in front of the first day to speak about mobility.
To share with you all our ambition for the future.
And we really want to build this roadmap with the community.
We have a lot of users, we have a lot of instance owners.
And we want to build the next steps with them along with all the diverse ecosystem.
And so first of all, Alex is going to present to you what is mobility zone for the users.
And then I'll take over to explain our works.
And then finally, we'll share with you our ambition for the future.
So, I will drive you through the main features of mobility zone that you might not know.
So, it's a web site.
Basically, on the homepage, you find local agenda.
And then you can search and dive for more contents.
You will find, so you can search for events based on lots of criteria.
But date, location, location is quite a key feature.
And you can also search for activities.
Like for instance, if you look for yoga class or anything that lasts all year long,
you can find it there as well and local books.
So, events, so you can publish them.
You can share them on social measures and email them.
You can also publish activities, as I said, that lasts all year long.
You can search by location, by keywords, by dates, and also by categories.
You can manage box situation to events.
Users will get notified by email, for instance, if there is a change.
And also there are possibilities that events get automatically published that stuff will explain a bit more.
Then you have groups.
So, you can create groups for several things.
So, first groups have a public page where they can post content.
So, you can post events or activities from a group.
And you can also create posts like news or information related to the group.
You can manage group members.
And they will have access to some private content, like something like a small forum.
You can share links to documents and also have private events.
And the groups have their own ICS feed and RSS feed.
So, you can follow whoop news like that.
So, if you understood some of these websites that we call instance.
So, instance administrator, they can create their own website with their own visual identity.
They will also define who's terms and conditions and who can register.
So, it can be open for anybody to register and post or it can be a little bit more private.
Where they choose which users can join.
They are responsible for moderation of users and contents.
And there are also the one that we choose which instance to federate with.
Which one to follow or which ones can follow them.
So, there are quite some dozens of instances.
You have the full list of the ones that self registers themselves on the website.
As an example, I listed a few.
So, there is one case called one for family and kids.
There are some from activism, activist movements.
We have some in various countries.
For instance, there is a mobilized Italy.
We have a university that chose to have a mobilized website for their events.
Some local agenda for a city or an area.
And there is quite a great variety of them.
In other words, it is available in 20 languages.
And they can federate with the users.
So, what it means is that one instance will follow another one.
And it will retrieve automatically all its contents.
So, all the groups and events posted on one instance will be also visible on the other instance that follows.
And you need to accept, of course, that other instance will follow you.
That's it.
We'll have a little bit more, maybe.
So, how it works.
So, I will probably explain activity people for the 10th time in the day.
Maybe the best one, but I will try to do my best.
And so, if you want to build a federated distributed service,
you need a protocol to agree on.
So, everyone knows email, SMTP for email, and GSM for mobile.
For the Fedivers, we mainly have activity pub.
So, this schema is taken from activity pub.
The drugs, probably, be all of them to you.
Nobody knows about it.
But the main concepts are that an actor, as an inbox, and an outlet box.
So, every time you subscribe to something, you receive new content on the inbox.
And every time you want to put something to others, you push it to the outbox.
So, pretty simple, like explain before it's a mailbox.
And what it means that it's validated, it's that we first of all,
we enable those kinds of use case where people can total together,
even if they belong to different service providers.
So, you can think about two instance of mobile reasons,
but also one instance of mobile reasons, and one instance of most of, for example.
And also that we accept, on one instance, the content,
and the identity of someone coming from another instance.
So, those two aspects, on sharing content,
and federated identity, is key to our Fedivers service,
and distributed platform.
So, when you want to provide the service in the open,
it's key to our interoperability.
And for example, on mobile reasons, so, the main obvious one is activity people.
So, what is interoperability?
It's enabling service to talk together and to understand themselves.
So, activity people, it allows mobile reasons to be able to interoperable with all the Fedivers.
So, Mastodon, Pleroma, PixelFed, Piatuben, so on.
But also, with tools that have done been built for the Fedivers,
explicitly, but are now adopting this protocol to share content.
So, there are some plugins for WordPress, also for next cloud,
and those are open source projects.
For mobile reasons, we have a private API that is in GraphQL.
So, for people not familiar with this technology, it's a bit more,
let's say, elaborated than rest.
So, you can query the world graph of objects that we have in our model.
So, for example, a Mactor and OLED school.
It's events, an event, and all its comments, et cetera, et cetera.
So, this is very art implement, and we haven't done it ourselves,
and there are frameworks to do that.
But on the other side, it's very easy to develop new clients.
So, for example, so, mobile reasons, it's a progressive web app,
that is also provided with the project.
But there are also tools that we can plug on it.
For example, you can write some script in Python,
and importing it automatically, some events in the platform.
That's what we do with some open data information.
We also have a side project, which is the mobile zone importer,
that will allow you to make a bridge between Facebook.
I think, Eventbrite is managed, so private platform.
You can take the content and put it on a mobile instance,
and also you can import like an SS, that is published by any website,
and regularly, all the new events will be pushed to your mobile instance.
So, yeah.
And I'm pretty sure that most of the language
have the client side implementation of GraphQL.
So, it's very easy.
We have also some minor interoperability,
thanks to a calendar you can have the event,
push to your, to your calendar application, like on the bird.
And for all the posts, there are published as an SS feed,
so you can have it in any new feed.
So, on the left you are more the red and right,
and on the right you have riddenly protocols.
So, what do you use to do all of that?
So, we have a bunch of protocol to implement.
I did open ID Connect for the authentication,
all the others I've been mentioned before.
And so we have, we've based our codebase on Playorma,
like five years ago, so maybe it has diverge a lot,
but it was a great accelerator to take start the project.
And the technology are, so we need a framework.
So, it's not Django, it's not really a noise, but it's Phoenix.
It's based on the go-in-ice language, which is Elixir,
looks a lot like Ruby, but it's on top of the air-long open telecom platform.
So, the open telecom platform, if you don't know it,
it's what is used in the telecom, like it says,
and also on what's up.
And each time you want billions of people talking together,
you have the open telecom platform behind.
For the persistence, we use post-gray, and for the front end,
we use UGS and TypeScript.
We glue with this thing with a lot of libraries,
and then everything is working, so you can come and contribute.
It will be easy.
Since we want people to be able to self-host,
we have prepared, we try to make things easy for people
at least running on Linux, and you have some package for Docker,
for Debian Fedora.
You have package, I don't know, it fits well,
but you have a package for Unhost.
Thank you very much.
And if you have something more exotic,
you can still be from source, but at least you have all those package,
like we'll help you to go fast.
This one I will be very quick, but like I said,
we don't just confate to be empty when you come on the platform,
so we use the open data from our governments.
It's mainly in France, but we have probably 200,000 events
in the France at any time, so if you will,
to a small village, you will have at least some events
for your next weekend.
So that's it for the technical part,
and I end over Alex for the future.
So we're done with icons.
So as I've said, we have been granted a phone
by NLNet last year.
It was for this year, right, 2024,
which was great, so we could transition from
from our self to maintaining ourselves.
And what we did is that we abstrained
what had been developed aside of the main branch,
and that was really great to have that support,
and also skill developers that jumped in.
And now we can look forward,
and think of what we want to do next,
develop new features, so in 2025 and beyond.
We'd like everybody to be able to use mobilization
and create local and thematic instances.
So our dream would be that anywhere in the world,
when there's a local initiative, it's on mobilization,
because it's created there or built there by interoperability.
But if we just start with our neighborhood or
our nearby streets, that's good.
So we'd like to offer hosting services
and develop the community of users and contributors.
And also to define what to do with the new branch,
we got from NLNet to go forward,
we'd like to involve mostly instance administrator,
but also end users to give their ideas and help together
to define what's the most meaningful to deliver to the community,
basically refine and prioritize the backlog,
and finally a little bit because we know we cannot do
at once everything we'd like to do.
So there are two things we'd like to do
is to improve the quality.
So as quality, I think of UX accessibility,
performance, fixing bugs, improving the tests and the security.
And then there are the features we would like to develop as well.
And we'll see also what comes from the other people
that we'll have on the change advisory board
that we're trying to build.
So we have an open call for that.
So what we've been thinking of and also we
received a feedback from the community that
would be nice to have, would be to be able to link groups
with one another.
So they can kind of federate groups with one another
and also display events that come from other groups
not only from your own.
Improved participation management,
so take multiple places to an event and manage a weighting list.
And there are a group members to see who participates
to group events that's not there yet.
Have a new search dimension that would be for the audience
for a group is events.
Annable instance administrator to moderate user account
creation for spam and also in case you don't want to open
registration to everybody.
Annable instance admin also to manage a bit more
the homepage and be able to pin posts and events
or groups on the homepage.
Have some kind of instance ball.
So not all of people but all of the instance with everything
that is new like a news feed for the instance,
new posts, new events, new groups created.
Small one have mobile apps available on stalls.
And also we would like to have auto generated newsletter
either at instance level, like here are the upcoming events
for the two coming weeks for instance.
Or maybe at group level.
If we can make that we can make that a group
event and it comes in somebody's mailbox.
And we would like to info federation so that we can so
for now if one instance for follow another one
it receives all the contents.
Sometimes it's relevant sometimes not.
So we would like to enable instance to only share
a selection of events.
So maybe for we should have the instance administrator
that decides which instances he federates with
that are open to communicate with each other.
And then it could be like users that push
content on those other instance.
Or on those that were on that pools.
What's interesting for them.
So we would love to have this kind of organic growth
of instance content.
But that's quite a big change.
There are lots of use cases to consider.
And also we need users and instance administrators
to keep in control.
We really think it would be like.
Or you valuable thing to have in mobilization
that makes it maybe more interesting than mainstream websites
that exist today.
So I hope you have a good feeling now about mobilization.
If you want to support it there are two things you can do
that are very easy.
It's communicate about it and use it.
So you can think of what you can do.
Maybe talk to one person about mobilization after you live.
And maybe find an instance.
You would like to you can post on there are many available.
And post on events just to try out.
Thanks.
Thank you.
So we have one question online.
And I know there's people in the audience at one
to ask questions as well.
So I'm going to ask you to find the somewhere else
because we'll want to move on after this.
So the question I have from Matrix is,
what about attendance information for the event?
If I sign up to an event, will that be public information?
No, go and leave.
But you say you want to participate in trial events.
It's not the public information.
Okay.
So that's not public.
So thank you so much for coming and talking about mobilization.
That was something that I wanted to know about as well.
So this great.
Thank you all for your patience.
I know that we've had very tight scheduling.
We honestly had so much great content.
The event and I were really struggling to figure out how we could
fit the talks together.
So we really appreciate everybody moving in and out.
And bearing with us that we haven't had really as great time for
questions that we would have liked.
But do come along to the birth of a feather.
Group session tomorrow.
Do come along to the social out.
I'm already evening if you can.
Find folks in the around fuzz dam.
And look them up on the fettie verse.
Ask questions.
This is great.
Thank you very much.