Fediverse stuff

0 readers

1 users here now

This is a magazine dedicated to posts about the Fediverse and things related to it. This is a MBin magazine, but you can follow it from Lemmy or Piefed as well. If you want to post specifically about Mbin feel free to post into !mbinmeta@gehirneimer.de

Recommended magazines

Rules

Please stay on topic, if it's off-topic please write [META] in the title. Please report off-topic posts if you see them.
Try to avoid drama related posts, for this type of content you can go to !fediverselore@lemmy.ca

founded 2 years ago

MODERATORS

Fitik@fedia.io

submitted 1 year ago by trwnh@mastodon.social to c/fediverse@fedia.io

96 comments fedilink hide all child comments

idk where to really put this (might turn into a blog post later or something). it's what you might call a "hot take", certainly a heterodox one to some parts of the broader #fediverse community. this is in response to recent discussion on "what do you want to see from AP/AS2 specs" (in context of wg rechartering) mostly devolving into people complaining about JSON-LD and extensibility, some even about namespacing in general (there was a suggestion to use UUID vocab terms. i'm not joking)

1/?

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

[–] trwnh@mastodon.social 1 points 1 year ago (2 children)

this is the fundamental divide between #fediverse thinking and #Web thinking, where #ActivityPub straddles the line between both.

i've seen it said that the "open-world assumption" at the foundation of the Web is actually an undesirable thing for a "social networking protocol", and as a consequence, specs built on that open-world assumption are "completely unsuitable" for that "protocol".

but do we need a "social networking protocol"? do we even need "social networks" in the first place?

9/?

[–] trwnh@mastodon.social 1 points 1 year ago (61 children)

to build the #fediverse as its own "social networking protocol" then seemingly requires that we instead go with the closed-world assumption, contrary to the #Web

it requires ahead-of-time communication and coordination, where implementers need to be willing and available to talk to any other implementer, and this load grows with every new implementer.

it requires you to be aware of other extensions, present and future, because your extension might conflict with someone else's extension.

10/?

load more comments (61 replies)

[–] MichaelTBacon@social.coop 1 points 1 year ago (13 children)

@trwnh@mastodon.social

https://social.coop/@MichaelTBacon/110634358031380559

Non-corporate/non-VC social media really needs to stop hating on "walled gardens" and start thinking about how you mind the gate that lets you into the garden and who gets in and who gets out.

If this exclusion still seems bad, start with "fascists" and then work outward from there.

load more comments (13 replies)