You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From local feed: As a person wanting to see who reposted my post, I click on the repost icon underneath my post, expecting to see a list of the people who reposted. However, doing so opens a section enabling me to actually repost.
from the post URL: doing the same action shows a list of folks who reposted the toot
These two different behaviors with a component looking the same way are inconsistent and make it hard to build habits around reposting or seeing who's interacting with you.
Expected behavior suggestion
apply same UI and behavior as what can be seen from individual post's URL in the feed view
Clicking on buttons triggers reposting actions, clicking on social icons with numbers shows list of reposters
The text was updated successfully, but these errors were encountered:
The thing is we have a different UI for focused post (like on their own URL) and posts in a feed. We have that extra line with more accurate counters of reactions and boosts. Those "new" counters are clickable to get details on who reacted or boosted.
If we want to have the option to see who reacted / boosted on each post of the feeds, we should have that extra line on every posts. Which would overload the timelines.
If we were mobile only i would go for something like
"tap" → reacts / boosts
"long press" → see details on who reacted / boosted
But i'm not sure how to deal with this on desktop.. Ctrl + Click ? not that intuitive.
Maybe we could have the icon+label which would trigger the action to react/boost and the number which would display the details? But the click zone might end up pretty small even on desktop.
Issue
These two different behaviors with a component looking the same way are inconsistent and make it hard to build habits around reposting or seeing who's interacting with you.
Expected behavior suggestion
The text was updated successfully, but these errors were encountered: