nodebb and discourse are working on activitypub support. See https://crag.social/@devnull/111732273308478221
nodebb and discourse are working on activitypub support. See https://crag.social/@devnull/111732273308478221
This is exciting. I think code forges are one of the biggest opportunities for ActivityPub to really go mainstream and change the internet. Not only because it’ll make working with open source way easier since you can work with any compatible forge, but developers will be more exposed to ActivityPub just by working with the software and so more likely to participate in AP dev. It will be interesting to see what effect this has on the fediverse. There’s been a lot of talk from various organizations/companies but this will be the first large project adopting AP. I’m interested to see how development goes for them and for other fediverse projects.
I wonder what changes it will force on Mastodon. Masto won’t be the biggest project anymore and won’t be able to throw its weight around as much. Just like the recent influx of users forced the implementation of full text search and has reenergized conversations about quote posts, I think federated gitlab would force masto to rethink some things.
I’ve never really understood the EEE argument here. XMPP was an open proptocol, Google embraced it and attracted users, then extended it and took those users away. But according to this article, Google didn’t extinguish XMPP. It’s still around and serving its niche community.
That’s already the situation the fediverse is in. This is a niche community and there are already existing social media companies that the majority of internet users are on. If Facebook joins the fediverse, it brings billions of new users to the fediverse. If they then leave the fediverse, ActivityPub will still be here and all of us on the real fediverse will still be here, in a niche community. Everyone here has already chosen the fediverse despite it being a clunky, unpolished, niche network. How is EEE a relevant fear for the fediverse?
Users can block those with extensions so the data isn’t as reliable
Apple’s implementation of other PWA standards requires an app to be opened from the home screen. A user can’t access features of the app if they can’t add it to the homescreen.