rather unfortunate that AP didn't leave any protocol signaling mechanisms for itself, so "upgrading" to a different/future version of AP is kinda fraught, since there is no concept or awareness of multiple protocols potentially using the same vocabulary

by "AP" here i mean the Follow/Like/Announce bits and how they affect the followers/likes/shares collections. since that's the only part that has any sort of consistency

even then, i do kind of think that WebSub was/is/remains better for handling subscriptions. also they should have kept calling it pubsubhubbub

not-so-fun fact: it is possible for a topic manager to destroy a websub subscription after-the-fact. it is however not specified how to remove a follower in activitypub

i don't wanna be too much of a crank but i do think that the way that a lot of things have gone over the past decade or so have been more or less a mistake from which we might not ever be able to repay the technical debt

@trwnh hard fork with versioning!

Also I vaguely remember some talks about AP2 coming?

i don't particularly like feed technologies like RSS and Atom (and Atom is probably easier to work with although RSS might be more prevalent)

but you do kind of have to admit that feeds + a pubsub hub (as in ostatus) was actually in a lot of ways better for the web than whatever we have currently going on. in that sense, activitypub is honestly a **lot** of overhead for what it gets used for -- following feeds and syndicating articles.

you could layer on the social notifications with an inbox?

@jalcine those have become AP 1.1 instead, i think

@trwnh no.

@evan

1. how do you notify someone that you've replied to them?

2. how do you manage side effects?

@thisismissem @jalcine i am very unsure if a v2 is even possible due to term conflicts between versions and no way to detect versions. minting an activitystreams/v2 context doesn't actually do anything for existing usage

@trwnh @jalcine AS is already v2..? I'm assuming you meant AP?

@thisismissem @jalcine i mean w3.org/ns/activitystreams/v2 which would be like an "AS2 v2", whereas right now we are on i think AS2 v1.11? might be a v1.12 in the pipeline? https://www.w3.org/ns/activitystreams-history/

@trwnh

Great questions. You should read my book!

https://evanp.me/activitypub-book/

@trwnh if your questions are an attempt to engage in Socratic dialogue, I withhold consent!

https://cosocial.ca/@evan/112400367303688503

@evan evan, not only did i read your book, i also reviewed it for o'reilly at your request. the topic at hand is about reply notifications and reply acknowledgements, two things which are not specified in the activitypub TR. we have Like+likes and Announce+shares, and to some extent we have Follow+followers, but everything else is left as an afterthought perhaps stuffed in a Create. i'm very confused what this kind of response is supposed to mean.

@evan it's a genuine question, which you may ignore.

@trwnh so, the way you let someone know you replied to them is that you include the original object as the `inReplyTo` property of your reply object. You then send them the `Create` activity that creates your reply by including them in the addressing properties of the `Create` activity. The OP adds the reply object to the original object's `replies` collection. Many servers do this automatically, but it's possible to let the recipient approve or reject replies they receive.

@trwnh they can send an `Add` or `Approve` activity to let the other recipients of the original object know that a new reply has been added.

@trwnh the original author can also add the object to the `thread`, which contains the full reply tree.