Egregoros

Signal feed

Timeline

Post

Remote status

Context

6

@i @sun You don't understand, spending a year discussing why https://www.w3.org/ns/activitystreams#Public should actually be banned, that the spec is completely wrong and everyone must switch to as:Public is important to the whole network.

@i @phnt the same crticisms of ostatus apply to activitypub. that a bunch of standards all standing on each others shoulders in a trenchcoat to make this one use-case work (microblogging) won't magically create interoperability with other services that leverage one or more of those open-web standards.

you use rss--but you can't consume some other rss feeds, and rss readers can't read your rss feed.
you use webmention--but you can't interoperate with blogs
you use websub--but you can't interop with aggregators

instead of a tight and targeted spec for use cases you drag in a shitload of baggage to be "spec-compliant" with a spec you were only using out of design convenience, but then you have extra work and mismatch with functionality so you end up cutting corners and you're not compatible anyway (see: json-ld)

AP sometimes can do these things partially because it has enough traction that people just...implement AP instead of just the minimal standard. At which point it could have been anything else, even ostatus to some extent (ostatus had no private messages admittedly)

Replies

0

Fetching replies…