Search: Handle Mastodon v4 remote post URLs #300
Labels
No labels
approved, awaiting change
bug
cannot reproduce
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs change/feedback
needs docs
needs tests
not a bug
not our bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AkkomaGang/akkoma#300
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.nuand find a funny post, User right-clicks the timestamp and copy the URL, and get this:https://masto.nu/@charlotte@akko.chir.rs/109387908449143493Suggest Akkoma search function to fetch this URL, follow Mastodon's HTTP 302 redirect and fetch
https://akko.chir.rs/notice/APrew44Zg0zn1z2xyithis 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
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
One catch though: it will only work if the source server doesn’t require authfetch, else it runs into #731