Are Accounts/Actors and Statuses URIs intentionally different?

[diligiant]

I just noticed that the first follow this template https://%s/u/%s (here) whereas the second => https://%s/users/%s/%d (here) and I was wondering if this was intentional or just an oversight when you decided to use /u/ instead of /users/? Some code out there might want to infer the account URI from a status'… ;)

[davecheney]

Hmm, yes this is probably a bug. Keeping the activitypub representation of an actor or status separate from its mastodon version always confuses me

I like the way that wilderbeast does it, /ap/o for objects, /ap/u for actors.

[diligiant]

Indeed, I like their /ap/users and /ap/o prefixes as it very explicitly (different root, different sub-root lengths) breaks bad players. I'm willing to try if you're game.

[davecheney]

I realised tonight that all the id's that I'm storing in the statuses table are wrong :( -- they shouldn't have the /activity suffix.

I've been thinking a lot about making pub less mastodon specific, perhaps not quite as activity pub generic like wildebeest, I think there will be some problems with their approach, but never the less, they have some good ideas that I'd like to copy.

[diligiant]

CreateNote is fine (using atomUri). Announce is not (using activity.ID instead of act.Object [like in Follow]) [superficial check]