Bug 484474 - Failed to contact server: Error transferring https://.../api/v1/accounts/.../featured_tags - server replied: . Please check your settings.
Summary: Failed to contact server: Error transferring https://.../api/v1/accounts/.../...
Status: RESOLVED DUPLICATE of bug 484475
Alias: None
Product: Tokodon
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified All
: NOR minor
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-25 20:35 UTC by tbqdrn
Modified: 2024-03-25 20:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Error screenshot (26.17 KB, image/png)
2024-03-25 20:35 UTC, tbqdrn 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description tbqdrn 2024-03-25 20:35:38 UTC 
Created attachment 167757 [details]
Error screenshot

SUMMARY
Some alternative fediverse software like e.g. Akkoma does not implement Mastodons featured_tags API methods.
See https://docs.joinmastodon.org/methods/featured_tags/ and https://docs.akkoma.dev/stable-docs/development/API/differences_in_mastoapi_responses/#featured-tags

Because of that, visiting a profile when connected to an Akkoma instance shows this ugly error message at the top:

Failed to contact server: Error transferring https://.../api/v1/accounts/.../featured_tags - server replied: . Please check your settings.

Visiting the specified URL in a browser gets me a {"error":"Not implemented"} JSON response, so I would suggest to silently fail instead of showing this error every time.

STEPS TO REPRODUCE
1. Connect Tokodon with an account hosted on any Akkoma instance
2. Visit a profile

OBSERVED RESULT
See error message at the top

EXPECTED RESULT
Silently fail

SOFTWARE/OS VERSIONS
OS: Arch Linux
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Comment 1 tbqdrn 2024-03-25 20:38:22 UTC 

*** This bug has been marked as a duplicate of bug 484475 ***