[Feature] Redirect remote user to internal ID

Resolve remote user's host name and user name into internal ID, and redirect to that.

• /remote-users/:username@:hostname -> /users/:id
• /remote-users/@:username@:hostname -> /users/:id
• /remote-users/:hostname/:username -> /users/:id

Usecase

Some implementations of decentralized social network, such as Misskey, have no explicit remote follow feature on their standard web UI. In case of following from Pleroma (e. g. pleroma.example.com) to Misskey (e. g. exampleuser@misskey.io), first we can open the URL https://pleroma.example.com/remote-user/@exampleuser@misskey.io, redirected into https://pleroma.example.com/users/INTERNAL_ID, and we can push the follow button.

added 1 commit

• 29bcb3a7 - use vue's router instead of window.location

Compare with previous version

added 1 commit

• d11fb4c8 - redirect /users/acct/:username@:hostname -> /users/:id

Compare with previous version

changed title from WIP: [Feature] Redirect external user to internal ID to WIP: Redirect external user to internal ID

changed the description

unmarked as a Work In Progress

changed title from Redirect external user to internal ID to [Feature] Redirect external user to internal ID

added 1 commit

• c5f4d6a5 - redirect /remote-users/:username@:hostname -> /users/:id,...

Compare with previous version

changed title from [Feature] Redirect external user to internal ID to [Feature] Redirect remote user to internal ID

changed the description

added 1 commit

• 6893e4f5 - remove redundant redirect

Compare with previous version

added 1 commit

• 26b38975 - show message in remote user profile page

Compare with previous version

added 1 commit

• 3325fa1d - accept redirect from /remote-users/@example@example.com

Compare with previous version

changed the description

changed the description

I believe that this MR is ready to merge.

Not sure why, you can just use user search to find remote user.

On top of that we shouldn't redirect internal users, and whole thing is buggy enough already, this will need intense testing before merge.

I think this is a good idea, search can be fiddly sometimes. This doesn't seem to change how internal users work either.

plz don't depend on qvitterapi for new features

????

I guess this.$store.state.api.backendInteractor.externalProfile(acct) is qvitterApi?

can we have something similar of our own if qvitterapi is not ok?

I guess this.$store.state.api.backendInteractor.externalProfile(acct) is qvitterApi?

Yes

can we have something similar of our own if qvitterapi is not ok?

Yes, filed pleroma#1222 (closed)

oh yeah, that unmaintained bit of code. I thought there's already mastoapi analogue for it?

We extended /api/v1/accounts/:id to support nicknames, but remote nicknames don't work because of a bug