submitted 1 week 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 week ago

@oblomov@sociale.network yeah, there's the old "it's like email but for websites!" which isn't terribly inaccurate, but that's honestly more a consequence of "HTTP POST to ldp:inbox" than anything else in AP. the side effects for each activity kinda stray from that model and go into almost RPC-like territory. there's also some potential redundancy with HTTP verbs, but that's because HTTP verbs don't notify arbitrary audiences (although i guess they could do that with a header!)

[-] oblomov@sociale.network 1 points 1 week ago

@trwnh@mastodon.social actually what made me think of “extensions of email and newsgroups” was more the object structure, but on second thought that's more an ActivityStream characteristic than an ActivityPub one, although an actual implementation of the C2S part of AP would still fit the bill in some sense.

(Yeah, the lack of usage of DELETE and PATCH surprised me initially, but the fact it would have needed to also define how to propagate them partially explains it.)

this post was submitted on 24 Sep 2024

1 points (100.0% liked)

News from fediverse

0 readers

26 users here now

founded 9 months ago