Comment by Teever

Open in a window
Comment

Comment by Teever

One of my biggest criticisms of social media in general is that the algorithm that determines how things are scored and ranked is intentionally obfuscated under the auspices of preventing 3rd parties from gaming it in such way that results in an outcome where it is impossible for users to determine if the platform owners are gaming it themselves.

I'm not aware of a social media site that does it but I think that I'd very strongly prefer a site where I could view a transparent log of who voted for what and when and what moderator took what action and when and why and how that all factors into how a comment / post / thread is ranked on the feed at any particular moment than one that hides all that stuff.

Reproducible builds but for social media.

Less 'pay no attention to that man behind the curtain' and more 'Exactly what it says on the tin"

The more that I interact with moderators on social media the more I've come to realize that as much as they're burnt out from answering the same questions from not-bad actors over and over as they are dealing with organic bad actors or automated content generators and that a great deal of those questions stem from the opaque nature of the algorithm.

All too often I find that moderators on social media are exasperated and burnt out not just from the endless janitorial work but also from users reaching out to them for understanding about the opaque nature of their actions and the outcomes that they have in the system.

So a lot of moderators gravitate towards a 'don't rock the boat' sort of mentality and over time adopt this sort of mentality: https://youtu.be/hNuu9CpdjIo?t=56

IMHO we're well past the point where any sort of security by obscurity with regards to the algorithm prevents any sort of automated influence on social media and the negative impacts of this kind of moderating technique only causes more damage than it prevents / mitigates.

Replies Teever · 2d
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. The list is kept in this browser only.

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
]
Read the next story in the same article-reader applet. Back returns to the previous story.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or a story row's Open in new reader window button to compare articles. Docked and minimized readers keep their articles when you select another story from the sidebar. A window's Next story link reads on down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.