search

mastodon / mastodon

Your self-hosted, globally interconnected microblogging community
https://joinmastodon.org
GNU Affero General Public License v3.0
47.1k stars 6.98k forks source link

Include metadata in API object if a toot comes from a hashtag subscription. #22540

Open timdmackey opened 1 year ago

timdmackey commented 1 year ago

19895 currently exists in part to request the addition of a “you’re following this hashtag” notice for hashtag subscriptions in the home timeline.

I’d like to request that this information also be added to the API so that apps can provide the same information to users.

Pitch

When someone boosts a post into your timeline, it's helpful context that a label is applied letting you know who boosted it, so you know why the post is in your timeline. The ability for apps to show a similar label for hashtag subscriptions would be equally useful. This information would need to be included in the API so that an app is aware that a particular post came from a subscription.

This is what a boosted post looks like in the Mastodon web UI:

Screen Shot 2022-12-20 at 1 09 58 AM

And this is how a hashtag subscription post might look:

Screen Shot 2022-12-20 at 1 06 19 AM

Motivation

I often find myself reading a post in my timeline and wondering "who is this person, why am I seeing their posts? Do I have the federated timeline open?" I then realize that the person has randomly decided to include a hashtag in their post that I'm subscribed to, and the hashtag isn't relevant to the post (or I just didn't realize it was relevant).

Having the ability to label posts that originate from a hashtag subscription would be a helpful context clue for managing one's home timeline. I'm hoping that this can be added to the data available to all apps so that this kind of labelling is an option.

DagAgren commented 1 year ago

This originally came as a feature request for Toot!, but I don't think the current API gives enough data to do it. However, it seems like a very obvious user experience improvement.

rbairwell commented 1 year ago

I think this is a duplicate of #22444 which itself is a duplicate of #19895

timdmackey commented 1 year ago

I think this is a duplicate of #22444 which itself is a duplicate of #19895

You're right, I didn't see those before posting this. Since my original intention was for this to be available in the API, I'm going to rewrite the post to reflect that.