Technology

34789 readers

419 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.

Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.

Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago

MODERATORS

MinutePhrase@lemmy.ml

107

As the open social web grows, a new nonprofit looks to expand the 'fediverse' (techcrunch.com)

submitted 1 month ago by JRepin@lemmy.ml to c/technology@lemmy.ml

19 comments fedilink hide all child comments

A new project launching today aims to capitalize on the momentum seen within the fediverse, also known as the open social web, which describes interconnected social networking services powered by the ActivityPub protocol. Co-founded by the co-author and current editor of ActivityPub, Evan Prodromou, a new nonprofit organization called the Social Web Foundation will focus on expanding the fediverse, improving ActivityPub and the user experience, informing policymakers, and educating people about the fediverse and how they can participate.

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

[–] BriarTalker@lemmy.ml 1 points 1 month ago (1 children)

Can you extinguish a protocol nobody owns?

[–] drwho@beehaw.org 1 points 1 month ago

Google pulled it off with GChat. All told, those of us who run our own XMPP servers aren't even a rounding error when compared to everybody who uses Google Chat, FB Chat, Slack...

Interoperate with it. Add proprietary extensions faster than other implementations can keep up with (at least two orders of mag). Render software that isn't yours unusable by suddenly cutting over to something else internally; let connection attempts continue for a while to frustrate users while simultaneously releasing your own. Then cut away all points where legacy connection attempts could be done.