Search: Handle Mastodon v4 remote post URLs #300

Closed
opened 2022-11-23 00:50:50 +00:00 by nninja · 3 comments

Mastodon v4 frontend has some UX tricks to display remote posts without having the user "leave" the instance. Nifty trick, but breaks the search bar in Akkoma/Pleroma

Would be very convenient if Akkoma search function can follow the Mastodon redirects and fetch the remote post.

Example: User browsing masto.nu and find a funny post, User right-clicks the timestamp and copy the URL, and get this:

https://masto.nu/@charlotte@akko.chir.rs/109387908449143493

Suggest Akkoma search function to fetch this URL, follow Mastodon's HTTP 302 redirect and fetch https://akko.chir.rs/notice/APrew44Zg0zn1z2xyi

Mastodon v4 frontend has some UX tricks to display remote posts without having the user "leave" the instance. Nifty trick, but breaks the search bar in Akkoma/Pleroma Would be very convenient if Akkoma search function can follow the Mastodon redirects and fetch the remote post. Example: User browsing `masto.nu` and find a funny post, User right-clicks the timestamp and copy the URL, and get this: `https://masto.nu/@charlotte@akko.chir.rs/109387908449143493` Suggest Akkoma search function to fetch this URL, follow Mastodon's HTTP 302 redirect and fetch `https://akko.chir.rs/notice/APrew44Zg0zn1z2xyi`

this isn't new to mastodon, we've had this problem for a while with misskey (which doesn't even redirect, it just shows the post in the remote instance and makes it unclear in the URL)
that would be a bit harder to figure out because Misskey™ but yes it would be very useful

this isn't new to mastodon, we've had this problem for a while with misskey (which doesn't even redirect, it just shows the post in the remote instance and makes it unclear in the URL) that would be a bit harder to figure out because Misskey™ but yes it would be very useful
Owner

Adding special parsing for however all the frontends out their create remote-post URLs isn’t feasible imho.
It’s up to the remote to behave sensibly here and e.g. prominently display an option to copy the canonical URI or at least redirect incoming AP-type requests to the original source

Your description sounds like Mastodon, does already redirect in which case fetching unknown posts from it should work fine in recent’ish versions of Akkoma

Adding special parsing for however all the frontends out their create remote-post URLs isn’t feasible imho. It’s up to the remote to behave sensibly here and e.g. prominently display an option to copy the canonical URI or at least redirect incoming AP-type requests to the original source Your description sounds like Mastodon, _does_ already redirect in which case fetching unknown posts from it should work fine in recent’ish versions of Akkoma
Owner

One catch though: it will only work if the source server doesn’t require authfetch, else it runs into #731

One catch though: it will only work if the source server doesn’t require authfetch, else it runs into #731
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AkkomaGang/akkoma#300
No description provided.