@sanity Almost all AP implementations have an internal database with a fixed schema.

[mat@friendica.exon.name]

@sanity Almost all AP implementations have an internal database with a fixed schema. When JSON-LD arrives, they take pieces they recognise and force them into that schema. They throw away anything they don't recognise. It's not really a case of "supporting" RDF. They support it just fine, provided you only use exactly the structure they expect. This is definitely not how AP was conceived, and I would be very interested in an implementation that stored and forwarded JSON-LD as it was intended.

[mat@friendica.exon.name]

@julian Well, that's good to know 😀 That said, the other aspect: I believe the biggest thing ActivityPub brings to the world is networking existing communities using existing platforms. They're not "legacy", they're first class. It's completely normal to build a platform with a specific schema for your own needs, and then hook up to AP later. To the rest of the network, it looks like you're extending JSON-LD in exciting innovative ways, while to you it just looks like dumping rows into JSON with a weird @context element.