Feature request: show why a message is shown in web UI about mastodon HOT 4 OPEN

Phanpy's behaviour for followed hashtags should be similar to Ivory; only show hashtag indicator for posts from non-following accounts (not including boosted posts, group posts, own posts, etc). These are the steps:

1. Pull in and store all followed hashtags (locally).
2. When loading posts in the timeline, find all posts that contain followed hashtags, grab the posts' accounts, (batch-)check their relationships (following or not).
3. Add hashtag indicator for posts from non-following accounts.

Unlike Ivory showing 1 hashtag, Phanpy shows max 3 hashtags (unordered, magic number), as a post could contain more than 1 followed hashtags.

Nevertheless, this (including any form of contextual indicators) is better done in the backend API in my opinion. On the client-side (Phanpy, and all other clients), the above implementation is honestly quite hacky and tedious just to show one indicator on the post.

from mastodon.

There's a long standing ticket for this, which I know the team knows about, because it was part of my interview with Mastodon gGmbH last June.

it's just really difficult to fix without requiring an extremely expensive complete rebuild of everyone's timelines (on larger instances this could take days or weeks).

it's gonna need a really interesting solution to solve it in a live/rolling migration way, that doesn't wipe out everyone's feeds.

the place to start looking is in app/lib/feed_manager.rb

from mastodon.

Plenty of apps do this client side. Here’s Phanpy.social showing a post from a followed hashtag, a post from a follow, and a bunch of boosts from my follows. Note the subtle colouring also denoting which is which.

from mastodon.

I'm gunna ask @cheeaun to explain phanpy's behaviour, but basically the timelines returned from the mastodon API do not include why something is in the timeline.

Apps like phanpy just try to guess why, by pulling in all your followed hashtags & hoping that's why the post was inserted into the timeline feed or ranked where it was.

To properly implement this with the timeline API returning back context for "why" is a major engineering lift because it has to be done extremely carefully.

from mastodon.