If Mozilla open sourced it years ago like they promised, it could be picked up by someone else.
If Mozilla open sourced it years ago like they promised, it could be picked up by someone else.
But #1 is predicated on #2. If developers are aware of the risk of EEE, then they won’t try to remain compatible with Meta extensions, which means development of the open AP ecosystem will continue at the same pace.
Yes I read that and explained why I don’t think its relevant. Facebook can’t slow down progress on the fediverse because:
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?
They abuse the subject
field which I think lemmy ignores. name
is a separate field that is used for the title
It’s not as common to push users to apps on desktop, but its a tried-and-true practice on mobile. I’m sure companies would do it if they could, but app stores and app lockin aren’t as strong on desktop as on mobile
Users can block those with extensions so the data isn’t as reliable
nodebb and discourse are working on activitypub support. See https://crag.social/@devnull/111732273308478221