![Last Week in Fediverse – ep 69\70 | fediversereport.com [Blog Article]](https://lemmy.world/pictrs/image/69f49260-8a5b-4736-85b2-1eba6f1941c7.jpeg){kind=link}
https://fediversereport.com/last-week-in-fediverse-ep-69/
-
Celebrating the 16th birthday of the fediverse
-
The European Commission sets up a new fediverse instance
-
bridge between the fediverse and Bluesky has been used to spam Bluesky with pro-Trump messaging
-
Three new products for the ATmosphere by Japanese developers: Video platform Bluemotion, Blogging with WhiteWind, and audio spaces with Bluecast.
-
Fediverse share button - https://stefanbohacek.com/project/fediverse-sharing-button/
UPDATE:
EPISODE 70 - https://fediversereport.com/last-week-in-fediverse-ep-70/
deleted by creator
There are some provisions in the Digital Markets Act that go in that direction. It only took effect roughly 3 months ago though, so remains to be seen if it works out as intended.
deleted by creator
No, the DMA has nothing to do with RCS, at least not directly.
Yes, WhatsApp and Facebook Messenger were initially just XMPP servers, but have since had proprietary expansions.
In the context of the DMA both of them will be forced to make interoperability with other third-party messengers possible, since Meta has been designated a “gatekeeper” under the new regulation. Meta has announced they plan on doing so via an implementation of the Signal protocol.
deleted by creator
Signal protocol ≠ Signal messenger
AFAIK you could always have selfhosted a Signal server, you just can’t interact with the “normal” Signal messenger and its network.
deleted by creator
Not with Signal messenger, the company running it hasn’t been designated as a gatekeeper under the DMA rules. You can see which services will be affected on the Wiki page (only WhatsApp and Facebook Messenger currently).
deleted by creator