Wormhole will use /user/ instead of /users/

idk why its called /users/ when its just a link to a user

@alex @hj discuss is this good idea?

@ne @alex @hj Makes sense tbh, the user with specific nickname is a subset of users group. Either way, it doesn't matter that much, honk even uses /u/.

@mint @alex @ne @hj using singular terms is pretty common in db and api design. if you have a list of notes and you index into it, you would expect user[0] to return the user at index 0. if it's users[0] it looks like a nested array structure. similarly with api design, if you're already doing /users/:id then what are you supposed to use if you want to show a list of registered users? you have to use /users/ or rename it /all-users/ or something dumb

@mint @alex @hj @ne I use /ap/{actor,following,followers,inbox,outbox}/:id for activity stuff so I can easily just redirect nginx to forward /ap/* and then for the frontend I use /user/:id /followers/:id /thread/:id

@e @alex @mint @hj for what backend?

@ne @alex @mint @hj huh?

@e @alex @mint @hj the /ap/{act...} stuff? idk anything that works with that.

That's also not portable if you want to add another backend beyond activitypub, like litepub.

@ne @alex @e @mint @hj there's a project to port pleroma-fe to gnusocial btw

@PhenomX6 @alex @e @mint @hj But why though? PleromaFE is a fork of Qvitter? and Qvitter is MUCH faster at least

@ne @alex @e @mint @hj https://gnusocial.jp/pleroma
I mean. Someone wants it. And an instance runs it.

@PhenomX6 @alex @e @mint @hj oh wait, this isn't a fork, just an old PleromaFE version