Excited to share our community vision for @Mastodon today: we are for the people.
Fediverso
13
Posts
4
Posters
3
Views
-
Excited to share our community vision for @Mastodon today: we are for the people.
This year our focus is on ensuring everyone can have a safe and fun experience on #MastodonSocial and #MastodonOnline, and doing more to support and celebrate the diverse servers running #Mastodon, its forks, and every #Fediverse application out there.
https://blog.joinmastodon.org/2026/02/mastodon-is-for-the-people/
-
Excited to share our community vision for @Mastodon today: we are for the people.
This year our focus is on ensuring everyone can have a safe and fun experience on #MastodonSocial and #MastodonOnline, and doing more to support and celebrate the diverse servers running #Mastodon, its forks, and every #Fediverse application out there.
https://blog.joinmastodon.org/2026/02/mastodon-is-for-the-people/
First, weโre sharing a couple of new resources for the #MastodonSocial and #MastodonOnline communities. They are part of our new Help Centre. These are living resources! If you have feedback or questions about them, let us know.
-
First, weโre sharing a couple of new resources for the #MastodonSocial and #MastodonOnline communities. They are part of our new Help Centre. These are living resources! If you have feedback or questions about them, let us know.
In particular, Iโm excited about our new library of tutorials, which weโre building to help anyone get up to speed on how to use #Mastodon.
What things do you find confusing on here? Let me know, and weโll see about getting a tutorial added :)
https://help.joinmastodon.org/collection/1-support-tutorials
-
In particular, Iโm excited about our new library of tutorials, which weโre building to help anyone get up to speed on how to use #Mastodon.
What things do you find confusing on here? Let me know, and weโll see about getting a tutorial added :)
https://help.joinmastodon.org/collection/1-support-tutorials
I'm also thrilled to share an important resource for our community: Community Standards.
This resource expands on the #MastodonSocial and #MastodonOnline server rules, to help clarify what is and isn't allowed on our servers. Let us know what you think.
https://help.joinmastodon.org/article/12-community-standards
-
I'm also thrilled to share an important resource for our community: Community Standards.
This resource expands on the #MastodonSocial and #MastodonOnline server rules, to help clarify what is and isn't allowed on our servers. Let us know what you think.
https://help.joinmastodon.org/article/12-community-standards
I'm equallyโmaybe even moreโexcited about another resource in our Help Centre.
#Fediquette: A Community Etiquette Guide
Our community is full of passionate people who care deeply about improving accessibility and respecting consent. This resource will help newcomers to understand our cultural norms here in the #fediverse and #SocialWeb.
https://help.joinmastodon.org/article/13-fediquette-community-etiquette-guide
-
I'm equallyโmaybe even moreโexcited about another resource in our Help Centre.
#Fediquette: A Community Etiquette Guide
Our community is full of passionate people who care deeply about improving accessibility and respecting consent. This resource will help newcomers to understand our cultural norms here in the #fediverse and #SocialWeb.
https://help.joinmastodon.org/article/13-fediquette-community-etiquette-guide
Looking beyond Mastodon.social and Mastodon.online, our big project to support the Mastodon network of #fediverse servers this year is a series of experiments to replace the `join mastodon.social` button with a button that recommends a server running default Mastodon from an opt-in pool that we will be hand-selecting to start.
-
Looking beyond Mastodon.social and Mastodon.online, our big project to support the Mastodon network of #fediverse servers this year is a series of experiments to replace the `join mastodon.social` button with a button that recommends a server running default Mastodon from an opt-in pool that we will be hand-selecting to start.
We're also going to work on the #ServerDirectory this year.
This starts with moving the directory to a new pull-request-based system so admins can submit, update, or remove entries themselves.
Another change we want to make is to add more and new ways to โclassifyโ different types of servers including demographics, interests, and geographic regions.
Once we have that kind of information, we can start to explore new ways to incorporate it into the onboarding process. Stay tuned...
-
We're also going to work on the #ServerDirectory this year.
This starts with moving the directory to a new pull-request-based system so admins can submit, update, or remove entries themselves.
Another change we want to make is to add more and new ways to โclassifyโ different types of servers including demographics, interests, and geographic regions.
Once we have that kind of information, we can start to explore new ways to incorporate it into the onboarding process. Stay tuned...
In other news, we're moving off #Discord to @zulip.
Our first step will be to migrate the people on our existing Discord servers to Zulip. Then we also want to extend access to more and different kinds of people who are deeply engaged and actively contributing to Mastodon and the #fediverse.
We're going to move slowly and carefully because we want to be thoughtful about how we build out this space. Running this community space is important, but it does add coordination and moderation overhead to our small team.
How would a space like this be useful to you? Let me know in the comments :)
-
In other news, we're moving off #Discord to @zulip.
Our first step will be to migrate the people on our existing Discord servers to Zulip. Then we also want to extend access to more and different kinds of people who are deeply engaged and actively contributing to Mastodon and the #fediverse.
We're going to move slowly and carefully because we want to be thoughtful about how we build out this space. Running this community space is important, but it does add coordination and moderation overhead to our small team.
How would a space like this be useful to you? Let me know in the comments :)
And coming soon! I'm restarting a blog series that's near and dear to my heart: Community Spotlights.
The first person we're featuring is @Yehuda of #TurtleIsland. I can't wait to share his story with you. It's beautiful.
And that's a wrap โย now let's go build the good web together ๐
-
undefined gina@fosstodon.org shared this topic
-
And coming soon! I'm restarting a blog series that's near and dear to my heart: Community Spotlights.
The first person we're featuring is @Yehuda of #TurtleIsland. I can't wait to share his story with you. It's beautiful.
And that's a wrap โย now let's go build the good web together ๐
-
undefined haubles@hachyderm.io shared this topic
undefined _elena@mastodon.social shared this topic
-
Excited to share our community vision for @Mastodon today: we are for the people.
This year our focus is on ensuring everyone can have a safe and fun experience on #MastodonSocial and #MastodonOnline, and doing more to support and celebrate the diverse servers running #Mastodon, its forks, and every #Fediverse application out there.
https://blog.joinmastodon.org/2026/02/mastodon-is-for-the-people/
-
First, weโre sharing a couple of new resources for the #MastodonSocial and #MastodonOnline communities. They are part of our new Help Centre. These are living resources! If you have feedback or questions about them, let us know.
@haubles Good on you for taking on such a task. Writing documentation for newcomers must be quite a daunting mountain to look at. Every step forward is a step towards the top!
-
@haubles Good on you for taking on such a task. Writing documentation for newcomers must be quite a daunting mountain to look at. Every step forward is a step towards the top!
@wordsmith onward, together ๐
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@smallcircles@social.coop I feel personally called out for this ๐
-
#ActivityPub builds on top of #ActivityStreams in the sense that it adopted a number of its 'social primitives' defined in its vocabulary, and Collection being among those. These particular uses become 'protocol space', but other than that AS from the perspective of AP solution development is purely a set of social primitives, granular building blocks that one *may* use in a solution. AS is a utility library of sorts then. Or is that a wrong perception?
A 'feed' is something that lives in solution space, and I would only choose Collection to model it, if it offers a perfect fit in functionality. And aboveall.. does not assign some new app-specific use along the way.
I tooted today that I feel the biggest folly of the fedi is that everyone tries to cram their domain into the AS namespace. The AS primitives should not be Swiss army knives and have only singular well-defined meaning and purpose, yet they have become that along the way.
-
I haven't seen anyone use Add and Remove activities to notify updates to the `outbox`. I don't think it would work; it's too recursive.
I've done it for other feeds, like `replies` or `followers`, and it works pretty well.
-
I might not understand what we're talking about.
@smallcircles said that AP doesn't mention "timelines" or "feeds". We use a different term, collections. They are ordered in reverse chronological order, like what most people expect a "feed" to look like.
-
@evan@cosocial.ca gosh I can't imagine assigning Add and Remove activities for a "popular" collection. It changes so often that it seems a waste of resources to try to track it.
Dynamic Collection?
Or as @smallcircles@social.coop said, even just light algorithmic ordering in a timeline makes stuffing it into a collection unwieldy.
-
Except when they are called other names instead ;p
A timeline is a different thing than a collection imho. And an AS collection has some very particular functionality, which if I model a timeline in my app may not supported (e.g. reverse ordering).
Collection / 'timeline' is one of those words where sometimes they indicate an app domain, and sometimes a core protocol mechanism. Same is true with 'follow' which is sometimes a user action, sometimes indicates low-level publish/subscribe.
For core capabilities that must be part of the specs, in 'protocol space' it may be better to use terminology that is more common in messaging architectures and all the various architecture patterns that are involved. Perhaps idk we deal with a time-ordered event log or something like that.
-
@smallcircles @julian @deadsuperhero we call them collections.
-
Can't help but wonder about terminology use and abstractions they indicate. Nowhere in the specs is there mention of 'timeline' and neither of 'feed' (except as example use in AS).
I feel we started with powerful specs to be able to model *any* social networking use case. But where the specs had blanks gradually the impls filled these in with leaky abstractions such that fedi is now hammered into a very narrow social media microblogging domain.
If an app needs "Timeline" and "Feed" concepts, then it should model them. Given the actor-based nature of AP they might be actors, or whatever is best. These concept are about solution development, i.e. what is built on top of the protocol, and not indicative of core protocol capabilities.
There's so much confusion on "where does the protocol end vs. where does my app design start".
SDK's should offer "Addressable actors exchanging msgs with object payload", and hide all impl details for the solution developer.
