@Jan Well, it is possible to use the Mastodon client API for features that Mastodon itself doesn't have like text formatting. But, for example, many mobile apps don't support text formatting because Mastodon doesn't, although everything that isn't Mastodon does. They're built only against Mastodon.
And there are things, mostly Web services, that either do the same, use the client API, implement only Mastodon features and depend hard on features that only Mastodon has. Or they skip APIs and build directly against Mastodon, again, requiring the presence of features only available on Mastodon in the required way.
Then they have the audacity to have "Fedi" in their names while being completely incompatible with Pleroma, Misskey, Iceshrimp, Friendica, Hubzilla etc., essentially everything that isn't Mastodon or maybe a Mastodon fork.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #MastodonAPI #FediverseDevelopment
#FediverseDevelopment
@CartyBoston I guess people who only know Mastodon see this differently from people who actively use something in the Fediverse that is not Mastodon.
The difference is:
If you "implement ActivityPub", it will work with, for example, Mastodon and its forks, Pleroma and its forks, Misskey and its forks, GoToSocial, Friendica, Hubzilla and (streams). As long as they have a reasonable ActivityPub implementation itself.
If you "implement Mastodon", it's only guaranteed to work with Mastodon.
It may or may not work with Mastodon forks, Pleroma and its forks, Misskey and its forks, GoToSocial and Friendica. If it doesn't, it never will because the non-Mastodon Fediverse is not officially supported. In fact, the devs may not even know that there's something in the Fediverse that's federated with Mastodon, but that isn't Mastodon.
It will most likely not work with Hubzilla, which is what I use, and (streams). They, too, are federated with Mastodon, by the way.
But this is the way a whole lot of things in or for the Fediverse are developed.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ActivityPub #FediverseDevelopment
The difference is:
If you "implement ActivityPub", it will work with, for example, Mastodon and its forks, Pleroma and its forks, Misskey and its forks, GoToSocial, Friendica, Hubzilla and (streams). As long as they have a reasonable ActivityPub implementation itself.
If you "implement Mastodon", it's only guaranteed to work with Mastodon.
It may or may not work with Mastodon forks, Pleroma and its forks, Misskey and its forks, GoToSocial and Friendica. If it doesn't, it never will because the non-Mastodon Fediverse is not officially supported. In fact, the devs may not even know that there's something in the Fediverse that's federated with Mastodon, but that isn't Mastodon.
It will most likely not work with Hubzilla, which is what I use, and (streams). They, too, are federated with Mastodon, by the way.
But this is the way a whole lot of things in or for the Fediverse are developed.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ActivityPub #FediverseDevelopment
As @Dennis Schubert said on (and about) diaspora* three years ago:
"Nobody implements ActivityPub. People implement Mastodon."
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ActivityPub #FediverseDevelopment
"Nobody implements ActivityPub. People implement Mastodon."
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ActivityPub #FediverseDevelopment
A Developer's Guide to ActivityPub and the Fediverse
Topics covered:
➡️ importance of mapping software aspects to the Activity Streams format,
➡️ creating RESTful API endpoints,
➡️ handling HTTP signatures,
➡️ planning for evolving standards and potential server incompatibilities
➡️ event handlers and retries for reliable operation.
#ActivityPub #ActivityStreams #REST #FediverseDevelopment #Fediverse #DecentralizedNetworking
Privacy and Consent for Fediverse Developers: A Guide
About the importance of privacy and consent for developers in the #Fediverse.
The article highlights:
➡️the need for clear communication
➡️best practices
➡️mechanisms that empower users
➡️principles of consent
➡️the challenges of opt-in and opt-out mechanisms
➡️the significance of user feedback and competitive advantages in creating a user-friendly environment.
#Privacy #FediverseDevelopment #BestPractices #UserConsent
https://wedistribute.org/2024/07/fediverse-privacy-and-consent/
I am thinking about trying to implement #fediverse application similar to @bookwyrm but for rating/reviewing/tracking other than book objects. And I wonder how that object is decentralized, if it is part of the instance itself.
I imagine you can implement auto alias addition once you somehow identified it on another instance, but it means in most chances it would have its own review/rating per instance instead of in fediverse itself, right?
@4ioskd@misskey.io Maybe the @NGIZero@mastodon.xyz #funding program (Hi! 👋 ) could help Syuilo ? 🤔
#FediverseDevelopment
RE: https://mastodon.xyz/users/NGIZero/statuses/104590424297126162
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst