Tuba
Tuba copied to clipboard
[Request]: Show followed hashtags
Describe the request
Phanpy does this neat little thing when showing a post because of a followed hashtag (only from non-followed accounts), where it displays the hashtag (as a clickable link) it so you can see why that post is on your timeline.
Can Tuba do something similar? You can reuse the part with boost info and only replace the icon with the hashtag one and booster's name with a #hashtag.
Implementation Details
- [X] This follows the GNOME HIG.
TBH, I'd rather the API improved on that than do it myself. Here's how it works:
Every post has a tags
property that includes are the tags found in the post, e.g.
{
"tags": [
{
"name": "gnome",
"url": "https://tech.lgbt/tags/gnome"
},
{
"name": "test",
"url": "https://tech.lgbt/tags/test"
}
]
}
What Mastodon and other software that have API compat should do is to provide another property on each tag, following : Bool
, so it would become, for my account at least:
{
"tags": [
{
"name": "gnome",
"url": "https://tech.lgbt/tags/gnome",
"following": true
},
{
"name": "test",
"url": "https://tech.lgbt/tags/test"
}
]
}
This is being tracked on Mastodon's issue tracker FWIW https://github.com/mastodon/mastodon/issues/19528 and a working patch in the comments does exactly what I described above
The way some clients do it right now is by keeping track of followed hashtags themselves. My issue with that is mainly syncing. Both the initial sync between app restarts AND while the app is running. Picture this, you have Tuba running on your desktop and you decide to open Mastodon on your mobile phone. You follow a hashtag from there and suddenly when you get back to your desktop, there's a new post at the top of your timeline by someone using the hashtag you just followed and you are left confused as to why it's in your timeline and why Tuba doesn't show that it's because of the hashtag you are following - which is something you know it does
A solution would be to GET the user's hashtags every so often so they sync but honestly idk if it's worth it
Waiting for the fix in Mastodon's API seems reasonable, thanks for explaining!
Hi, I saw that my patch was mentioned here.
I have submitted a pull request for the patch now at the following link.
https://github.com/mastodon/mastodon/pull/28874
I have no idea if the pull request will be accepted or not, though, as I am not a part of the core team.