According to the interviews there is a shared interest in #federated technologies but several things are slowing down the adoption of #decentralized tools such as: lack of awareness about these tools, strong dependency from popular platforms, perceived complexity of use ("lack of familiar features"). Our mission is to help partner organizations successfully migrate to the #Fediverse while analyzing and documenting the whole process to understand main blockers and affordances of the #federation

Indieweb Social states its "a home for those who build, study, promote - or are just fascinated by - #openweb, #indieweb, #federated & #humanetech practices & tech"

I'll add to that. It's also a place for 80s style nerds like @tchambers
#PledgeDrive 13/ to sit in the back of the class and giggle until you stare at them

Donate: patreon.com/c/indiewebsocial

#PledgeDrive 13/

I'm not sure that your reply is directly related to my comment. The full sentence I quoted is "Under these definitions, Bluesky and ATProto are not meaningfully decentralized, and are not federated either." by Christine Lemmer-Webber, but Daniel Holmgren talked more directly about "decentralised distribution of data".

Because of what I quoted, I don't think that "Bluesky" or "ATProto" are decentralized or federated, so it's extremely unlikely that I'll interact with them anytime soon. The particular reason that they are not decentralized or federated is not really interesting to me.

To get specific: it is a significant issue for me if "everyone can access the data but before it reaches the end users it goes through centralised applications". A "centralised application" is able to restrict my ability to contact other people, whereas with a federated and/or decentralized/distributed system, it's more likely that I will be able to contact someone that I want to communicate with. For comparison, consider how people would feel if using the United States Postal Service meant that all physical mail had to pass through the District of Columbia or if sending an email message required interacting with BBN-TENEXA just because that was the first machine to be capable of sending networked electronic mail. In the ideal case, the recipient of a message I send would not have to coordinate with me at all before they receive the message: "The first use of network email announced its own existence."

@harld Could we please add
@element
For instant Messaging apps, as an alternative to Whatsapp, Signal etc..

It should have a Non-US ( #Element is based in UK), and a Privacy label.
Also, it is #opensource and #federated

Although many people are flocking to #signal now (which is a lot better then Whatsapp), Signal can not be controlled by US government, it can be taken down by them. At this point, even that should be taken into account.
Element uses the #Matrix protocol. It is awsum

@elduvelle #Signal is #centralized - just like #Twitter, #WhatsApp, #Telegram, #Threema, etc - and therefore exactly as vulnerable to #enshittification. Its popularity also makes it a tempting target for backdoors.

I urge people to use #XMPP instead, which is #federated like the Fediverse and has no single point of failure. It uses the same end-to-end encryption algorithm as Signal.

1/