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/
I really hope the eu gets addicted to the openness and starts forcing it on other companies to ensure competition
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.
Thats the whole rcs thing tho. Isnt signal WhatsApp and all Facebook messenger things use xmpp? Can we bridge them to rcs or have the alphabet bois locked that down.
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.
This sounds like i can finally self host signal and its going to be interoperable? Or is it gatekept for only the big bois?
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.
Yeah exactly but will the bill allow me to interoperate?
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).
Right so WhatsApp and messenger are gatekeepers and they must allow interoperation with who anyone who wants to ie me running my own signal instance? They also need to interoperate with signal hence if a works with b and c works with a why wouldn't b work with c? Cos if thats hoe it works or if im not allowed to interoperate with WhatsApp or messenger in the first place then this juat seems like its handing the monopoly away from the companies to the government and giving the people fuck all.
There are several stipulations on interoperability in the new regulation (Ctrl+F "interop"). To my understanding it is stipulated that they have to make interoperability possible for certain third parties, but how to go about this is not exactly specified on a technical level - meaning the specific way to implement this is left to the gatekeeper. So your Signal server may or may not be able to depending on how exactly they go about this.
No they need to enable interoperability period. Says nothing about Signal (the software) per se. Meta has announced they plan on implementing it based on the Signal protocol (not Signal messenger software, not Signal server software).
To my knowledge the aim of the regulation is exactly that, to allow anybody interoperability with these "core platform services". The status quo is that the regulations has been announced by the EU, it has gone into effect, and Meta has announced how they will implement interoperability to comply. Once the implementation is available and then found lacking in regard to the regulation it would be up to the affected third party to sue Meta over it.
So long story short can i or can i not run some software that will interoperate with all platforms stipulated in the document.
Not yet, but you probably will be able to in the future.