mariusor (@mariusor@metalhead.club)
I am becoming more and more frustrated with how Mastodon behaves towards the #ActivityPub ecosystem.
After I finish with the current plans I have for GoActivityPub I have to push into making #ONI good enough to be used as a daily driver fediverse profile and switch to that.
I'm not entirely sure the inbox model of social consumption is good enough for others, but I think for me it'll have to be enough.
Show Original Post
smallcircles (@smallcircles@social.coop)
Today we see a big uptake in interest in the #ActivityPub C2S part of the specs, to implement the Social API, and there is again an opportunity to reboot and give the ecosystem a big boost.
I'd say the most important projects in the #ActivityPub ecosystem are the ones where people focus on building reusable libraries, SDK's and developer tools that honor the original promise of the AS/AP specs: to allow heterogeneous decentralized social networking. The conceptual architecture of fedi of "addressible actors exchange activities with object payload" is ultra-powerful, a universal distributed message bus of sorts. And the easier it gets to model services on top of this model, the more excitement and new entrants we'll see in the ecosystem.
I am highly in favor that we not dogmatically focus on keeping compatibility at all cost to the existing installed base, where somehow this powerful architecture has devolved into "social media microblogging" galore.
Show Original Post
smallcircles (@smallcircles@social.coop)
The fediverse has been weirdly stuck for many years, driven by app developers who attended first and foremost to their own app projects and only secondary to the technology base the entire app is built upon. There was also hardly funding to do anything else. It may be pragmatic approach, but its not smart, eventually weakening the entire ecosystem. And here we are today, with a mountain of protocol decay and tech debt holding us back.
For many years people, me included, have argued that we should focus on getting robust extensibility mechanisms in place, fill the #ActivityPub holes, and not handwave it to say "yeah it is #LinkedData this and that sorta kinda". #Interoperability requires way more rigour at the protocol level.
Nice effect that #ATProto had, was it opened people's eyes to the benefits of having a sound technology base. The ATProto ecosystems excites newcomers, whereas fedi only frustrates with its high barrier to entry and whack-a-mole dev.
Show Original Post
heinz (@heinz@graz.social)
@LianaBrooks I am using only Mastodon and Wordpress with #ActivityPub. Works perfectly for me except for monitoring trends. I rely on lists for organizing information. What I have lost in quantity since leaving LinkedIn, X and the Meta platforms completely I have won in quality. Strangely LinkedIn seems to have become so autoreferential that I don't even remark missing it.
Show Original Post
smallcircles (@smallcircles@social.coop)
It would be even better if on #fediverse as a whole the developer ecosystem were able to move beyond the app-centric development model that dominates. Basically the app-centric approach constitutes a "poor man's TAM", facilitating technology uptake on the basis of how #FOSS projects are typically developed where the individual devs are in charge and there's hardly need to coordinate and collaborate at ecosystem levels. Here the grassroots environment within our ecosystem failed miserably. Apparently we are too fiercely independent to be able collaborate at scale. When a big player joins you get app-by-app competition, and their product development process is likely to easily blow the FOSS project out of the water.
If we had a more service-oriented #ActivityPub fediverse, a fedi of apps and services, then - depending how this is designed - it might be much harder to 'win' the market, as the competition becomes more on quality of service than feature sets.
Show Original Post
eyeinthesky (@eyeinthesky@mastodon.social)
Why did #ActivityPub create special behaviors such as Like, Announce and Block (and the Undo variants) instead of using Add to or Remove from the associated Collection objects? I have a similar question for outbox and inbox POST, which is an implicit Add to those collections. 
When adding support for extended collections, is an new collection-specific Activity preferred over Add/Remove? FWIW, I see Mastodon uses Add/Remove for pinned and featured posts.
Show Original Post
archipielago (@archipielago@bonito.cafe)
Mi curiosidad por las conversaciones entre los dos @flan me llevó a enterarme que se puede tener un servidor con funcionalidad #ActivityPub en un celular.
Show Original Post
mapache (@mapache@hachyderm.io)
@ocdtrekkie @badgefed and hey, if we can help to do that backpack badgefed compatible (which is really #activitypub + #openbadges) lmk
Show Original Post
notes (@notes@not-brain.d.on-t.work)
"how to not regret c2s"
w.on-t.work/activitypub/c2s
my opinions about how activitypub c2s ought to be implemented, probably with way too much snark for anyone to take it seriously. wrote pretty much all of it at like 1 am so expect the writing to not be great. will prolly regret it tomorrow but eh. whatever
#activityPub #fediDevs
Show Original Post
objects (@objects@mitra.social)
In previous years, I published two "fediverse tech roadmap" posts:
- Fediverse tech roadmap 2024
- Fediverse tech roadmap 2025
However, I didn't publish such post this year because not much has happened in 2025. Many problems I talked about require complex solutions, but unfortunately proposed solutions are often very limited or lead to centralization. Or worse, there is no solution but only an imitation of work. I don't want to write about that.
I saw a thread today where ATProto ecosystem was compared to #ActivityPub. Things are happening in the Atmosphere, but not in Fediverse. MAU graphs are flat. What's going on?
There are multiple factors at play, but I think fake activity may be the biggest contributor. Trivial developments presented as breakthroughs. Features that already exist somewhere in Fediverse presented as new inventions. Vaporware. Specs written by people who have no idea how to implement them. Working groups that do nothing but meetings.
Real work is ignored, competent developers see that and quit.
We need to fix this.
For my part, I will continue to document #Fediverse development at @weekinfediverse. But this newsletter doesn't have much impact.
Show Original Post
Flipboard (@Flipboard@flipboard.social)
What does a Discord replacement look like, and how might the open social web play a part? @laurenshof looks at what needs to happen — different apps built on the same protocols, active collaboration to make sure it all fits together — and how that's already fundamental to the Atmosphere and fediverse.
flip.it/QdL.F…
#ActivityPub #Mastodon #ATProtocol #Bluesky #Blacksky #Discord #Technology #Tech
Show Original Post
Flipboard (@Flipboard@flipboard.social)
Mastodon has announced plans to make its app more approachable for newcomers, and developed new features for creators. Here's @Sarahp's story for @Techcrunch. Find the full blogpost by @renchap and @imanijoy at the second link.
https://flip.it/TKKQZS
https://flip.it/RQRRnp
#ActivityPub #Mastodon #OpenSocial #Technology #Tech
Show Original Post