@evan how come Mastodon does not implement it already ???
@evan Thank you, that means a lot!!
@evan Oh!
> Instead, they often implement platform-specific APIs, with a narrow range of functionality. Mastodon, for example, implements the Mastodon API, which focuses primarily on microblogging. Threads implements the Threads API. Many other ActivityPub implementers have APIs that clone the Mastodon API, to make it easier for users to adapt third-party Mastodon clients to their platforms.
That's really cool. Thank you so much for working on stuff like this, it makes a difference (you know :)
Rankings from fedidb.com which skips Flipboard and Threads.
@mariusor @silverpill @hongminhee thank you 🙏🏼
Naru, the Korean version of #Neocities, reportedly added an #ActivityPub implementation in just an hour using #Fedify. If you also want to implement ActivityPub quickly, give Fedify a try!
https://hackers.pub/@jihyeok/019da3d9-45b8-7629-96a8-b26bd62867c2
@reiver I use .jsonld which GitHub serves correctly.
@reiver can you post this on https://github.com/w3c/activitypub/issues ?
In the video in the post I just boosted, @anildash says #Substack is now boiling the frog in a slow move from email towards lock-in. And of course they work with Nazis etc.
What we need is an effort between newsletter publishers like #Ghost #WordPress etc and reader apps like @wallabag to build an ecosystem like podcasting. To make it smooth while remaining totally open. I'd argue for using #ActivityPub in addition to RSS to support boosts. Then we need decentralized money.
@golemwire ActivityPub has two main parts; a social API and a federation protocol. All of these platforms support the protocol but not the API (at least, not in read-write form).