Mastodon normalizer

Revision as of 19:57, 15 July 2024 by Adamw (talk | contribs) (focused row)

Problem statement: Social media amplifies the loudest voices more than is necessary. In real life, we know that a person who speaks often and loudly might be full of good insights, or they might just suffer from an excess of hot air. Either way, we aren't obliged to give this person all of our attention just because they're loud.

There is rarely any way to deal with this, no alternative between full volume and blocked, to allow us to better hear the quieter voices.

Experimenting with normalization

 
Preferences pane

When @futurebird@sauropods.win mentioned the fun idea of a customizable timeline allowing us to check in on our friends' latest posts, I was excited to see how it might be applied. I'm happy with the results so far! You can login to the demo service using your own Mastodon account and instance. Preferences currently look this this. Expect to see many more options here, since customizability is the main point.

 
Equal height for each author

The default view is called the "orthogonal" view, which gives each author equal vertical space in your timeline regardless of how many posts they write.

A more extreme version of this view is the "Check in" mode which shows exactly one recent post from each account you've subscribed to, in other words normalizing both the vertical and horizontal space to a single square for each person.

 
Focused and expanded row

Since the messages might be any length, it's necessary to make them expandable. Focused (clicked) rows are expanded, and you can expand every row at once using by using the "natural" row height preference.

Time dimension

 
Time axis

It's possible to reintroduce time, but at 90 degrees running left to right. We're showing all the same cards as a regular timeline view, but rearranged on a grid.

Development

So far, this software is the labor of one unpaid person acting on friendly suggestions. Contributions, suggestions or other resources are welcome!

Its architecture is a server-side, Elixir Phoenix Live View application authenticated temporarily to act as the user. Posts and tokens are kept in server memory for each session, then forgotten.

In the long term, the algorithm should be fully flexible and visually-programmable, and there would be a library for sharing your algorithms with others, by local code, coprocess, or remotely-hosted.

Resources

Get involved

Similar projects

Reporting related to the topic