Fediverse

12 readers

1 users here now

This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.

founded 2 years ago

120

If ActivityPub can't survive Meta, it was never going to succeed in the first place (kbin.social)

submitted 1 year ago* (last edited 1 year ago) by anthoniix@kbin.social to c/fediverse@kbin.social

91 comments fedilink hide all child comments

Corporations don't just sit out on new technologies, and no matter how hard you try you can't force them to. Defederating from Meta's new project preemptively is naive, and will not do much of anything.

Protocols are going to be adopted by corporations, whether we like it or not. SMTP, LDAP, HTTP, IP and 802.11 are all examples of that. If it ends up that meta is able to destroy the fediverse simply by joining it, that is a design flaw on OUR end. Something would then clearly need to be different in order to prevent future abuse of the protocol.

FOSS is propped up by corporations. By for profit corporations. If you want to stop those corporations from killing projects, you put safety guards up to make sure that doesn't happen. You don't just shut them out and put your head in the sand.

you are viewing a single comment's thread
view the rest of the comments

[–] FaceDeer@kbin.social 8 points 1 year ago (1 children)

the EEE strategy (embrace, extend, extinguish) is well known by this point and it always ended up with the open standard not being used anymore and falling into irrelevance.

This isn't even remotely true, there are plenty of counterexamples. TCP/IP, HTTP, HTML, XML, SMTP, PNG, SVG, OpenDocument, OGG, PDF, FLAC, WebM, Vorbis, I could go on at great length. There are a vast number of open standards that are still open and are used extensively as fundamental parts of our everyday lives. Eg, the IEEE standards and RFCs.

[–] 00@kbin.social 3 points 1 year ago (2 children)

OpenDocument

How compatible is microsoft office with it?

And how many PDFs are broken by Adobes bs?

[–] FaceDeer@kbin.social 3 points 1 year ago (1 children)

I don't use Microsoft Office, so I don't know. Same with PDFs, I don't use Adobe.

There are plenty of programs that handle those formats other than Office and Adobe and I've never had significant problems with any of them.

Regardless, OP said "it always ended up with the open standard not being used anymore." Both of those standards are being used, and even if OpenDocument and PDF had been extinguished it still wouldn't matter because any open standard still being used is sufficient to disprove OP's position.

Emrace-Extend-Extinguish is something worth paying some concern to, but it's not some kind of unstoppable boogeyman. It's failed far more often than it's succeeded.

[–] 00@kbin.social 2 points 1 year ago

I don't use Microsoft Office, so I don't know. Same with PDFs, I don't use Adobe.

Same, and neither of us is having a particularly fun time when we get sent a .docx or a strange PDF that refuses to be opened and correctly edited without Adobe Acrobat (not joking, this happened to me once).

Regardless, OP said "it always ended up with the open standard not being used anymore." Both of those standards are being used, and even if OpenDocument and PDF had been extinguished it still wouldn't matter because any open standard still being used is sufficient to disprove OP's position.

Fair point. But both of them suffer from being adopted and then maligned by the corporate entities that picked them up, which is a part of the cycle. First it gets adopted, then "slightly tweaked for features" and then its (usually) unusable on other platforms that dont want to adapt to the corporate vision. Granted, OpenDocument has a different history and both it and PDF are old enough to not actually fear that they will be replaced be corporate "alternatives", but that they did generally follow the cycle but didnt finish it doesnt necessarily disprove it imo.

Emrace-Extend-Extinguish is something worth paying some concern to, but it's not some kind of unstoppable boogeyman.

Absolutely. But that doesnt mean we have to attempt giving it a fair fight. They dont intend to either, its antithetical to the point of EEE.

[–] Bloonface@kbin.social 1 points 1 year ago (1 children)

ODF has been supported natively by Office for years now, and LibreOffice is able to open .docx files just fine.

I've never found a PDF "broken by Adobes bs".

[–] 00@kbin.social 1 points 1 year ago

ODF has been supported natively by Office for years now, and LibreOffice is able to open .docx files just fine.

Open, yes, but the formatting will be terrible in my experience.

I've never found a PDF "broken by Adobes bs".

It has happened to me. Wasnt impossible to solve in the end, but still.