@sir#GitTorrent is one attempt to solve the decentralized GH problem, your #sr.ht is another, #GitPub is another, #Git-SSB is another (https://github.com/noffle/git-ssb-intro). Each one tries using a different standardized of protocols (#BitTorrent, email, #ActivityPub, #SSB). Ideally it would be possible to bridge them all, so users and projects could hosted anywhere, and users could contribute anywhere
You've ever wonderd how or why to build a social network based on #xmpp? Maybe not. But in case you're a dev. you might enjoy reading Timothée Jaussoin blog post, with experience of years developing a such a network.
It will also present reasons why xmpp was choosen and what the advantage/disadvantage over #activityPub are.
Be it for curiosity or inspiration, I highly recoment reading this blogpost:
The blogging platform #Plume aims to be a federated open source alternative to #Medium, and is under active development.
It's still at a pre-Alpha stage, but you can get regular updates from the lead developer at @BaptisteGelez (the account is on a Plume instance but it federates through #ActivityPub, so you can follow it on Mastodon etc).
The ethical Instagram alternative @pixelfed is launching soon, but did you know that there's another federated photo sharing site in development?
It's called #Anfora (previously known as Zinat) and it's been developed in co-operation with #PixelFed so that they will be as compatible as possible (and they both use #ActivityPub).
Anfora is asking for help and feedback, links below:
hi @gergely I've noticed you're working on federating events nice! As I understood the federation of events won't be done through #iCal. What is the reason for that? Will it be compatible with ical?
In #hubzilla, events are federated via ical. Would be great having it compatible with the way #ActivityPub does it. Meaning also, if there are compelling arguments for doing it as in ActivityPub, to switch to this aproach cc @macgirvin @mhall119 @rhiaro
0x1C3B00DA (0x1c3b00da@edolas.world)'s status on Monday, 09-Jul-2018 10:48:01 EDT
0x1C3B00DAI think #mastodon growing so quickly may have held back the #fediverse. It's considered a de facto reference implementation for #activitypub, but it's a limited implementation. It doesn't support most Actor and Object types, it's client and server are tightly coupled, and it was designed specifically for microblogging. ActivityPub was an afterthought for it and it doesn't use it anywhere near its full potential.
Now every new AP project is following suit, developing a client/sever combination specifically to handle a single Object type, any enabling federation support on a project by project basis. We need a full AP server that's not tied to a specific client. It should support AP C2S API so a user can login to any client using oauth and handle different types. A user could use one client to create events, one to manage photos, and another to write notes or articles, and they'd all be tied to the same account.
Hopefully, people will get past thinking of Mastodon, Pleroma, PixelFed, etc and just think of the ActivityPub network. I don't think the fediverse will continue to grow without this change in philosophy.
@stigatle you're not going to move to another #fediverse instance? Hopefully #Diaspora can eventually be convinced to support #ActivityPub, since it addresses most of the shortcomings of #OStatus that led them to create their own standardized set of protocols.
''If after I implement AP in the library someone wants to contribute the Ostatus/DFRN/Zot or something else, I'd be happy to help pull it through.'' - Jason Robinson (#socialhome dev)
@feonixrift@puellavulnerata FWIU both Mastodon and Pleroma use the same custom variant of the #ActivityPub server > client API. Any desktop or mobile client that works with one will work with the other, and there are also some web clients like #Pinafore and #Halcyon that work with both.