-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] V1 search API used, but deprecated and removed in Mastodon 3.0.0 and later #526
Comments
This also happens if you click a notification in the Notifications pane:
|
I think i might have a idea about this bug. https://digipres.club/nodeinfo/2.0 says its hometown and version number is hometown version. superseriousbusiness/gotosocial#1069 gotosocial suffers from a simmilar issue where sengi looks for v1 coz it assumes version less the 2 is using v1 api. Hope this RCA is right and is helpful here. |
This is also an issue with pleroma/akkoma instances it seems. |
What version of pleroma? |
The instance I tested it on is running Akkoma 3.5.0-0-gd9508474b |
I figured I would ask this here to clutter up the issue list less, unless I absolutely need to open one for what I'm experiencing. It appears that this issue is preventing me from joining certain Mastodon servers. I was wondering if there's an ETA on this fix or if there's any further information I could provide in a bug report to help |
Didn't realized before, but this issue is already fixed in the current version of Sengi. |
I tried to run a search for a hashtag in Sengi earlier. A "404" error appeared at the bottom of the search window, from my Mastodon instance.
From the endpoint URL it appears that Sengi is using the v1 search API, which has been deprecated and removed in Mastodon 3.0.0 and later:
https://docs.joinmastodon.org/methods/search/#v1
Sadly this won't work on most current Mastodon deployments, and needs to be updated to use the v2 search API.
The text was updated successfully, but these errors were encountered: