Egregoros

Signal feed

API Docs
Timeline

Post

Remote status

Context

3
silverpill

silverpill

@silverpill@mitra.social remote
Open link

@hongminhee

>There's no going back.

We absolutely must go back. Either we have a vibrant ecosystem where building stuff is a pleasant experience, or fediverse slowly dies while linked data cultists harass developers about nonresolvable URLs in @context.

JSON-LD adds nothing to ActivityPub, it only creates problems. Time to move on.

Phantasm

Phantasm

@phnt@fluffytail.org remote
Open link
@lutindiscret @silverpill @hongminhee It was supposed to bring document schema validation (you shouldn't be able to fool a JSON-LD consumer into accepting invalid documents) and instead it added complexity that few know how to deal with and subtle vulnerabilities with plain JSON consumers due to the ability of overriding types.

Also it was supposed to be entirely optional, but the current spec editors would like you to believe otherwise.
Replying to @phnt@fluffytail.org
arcanicanis

arcanicanis

@arcanicanis@were.social remote
Open link

Also it was supposed to be entirely optional, but the current spec editors would like you to believe otherwise.

The part I love about the authors to the spec, is that as far as I'm aware, none of them have even made their own complete implementation in any way, and only one of them has made some contributions to Mastodon and Pleroma.

Meanwhile, one of the authors had their own federated microblogging application from the OStatus days (that OStatus was defined from), that they abandoned entirely, and had no interest to even attempt a remake or a fork with ActivityPub at all, despite both being their project.

I don't trust people that can't even follow through implementing their own suggestions/ideas.

Replies

0
No replies yet.