this post was submitted on 09 Dec 2022
20 points (100.0% liked)

Fediverse

757 readers
2 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
deadsuperhero@lemmy.ml
wakest@lemmy.ml
20
On Mastodon and Algorithms - Jayeless.net (www.jayeless.net)
submitted 2 years ago by anova to c/fediverse@lemmy.ml
19 comments fedilink hide all child comments
 

Is this sort of thing inevitable? The fact we feel compelled to bring algorithmic content sorting into the fediverse says something about the way we use social media. The author mentions that reverse-chronological timelines make you feel like you need to spend hours scrolling through much of the same thing to make sure you're not falling behind on the internet. The other side of that is, why is it that we're all spending so much time dumping the same thing into each other's timelines? (I'm at least a little aware that I'm probably the nth person you've seen posting about this or a similar problem in the last week)

My solution to the timeline getting too fast has always been to unfollow/mute people, but maybe that's getting impractical.

you are viewing a single comment's thread
view the rest of the comments
[–] jonny@social.coop 1 points 2 years ago (1 children)

@f00fc7c8 @anova
I got kind of stalled on this bc helping start a new instance (and part of that instance will be explicitly to support hacking on masto), but I have some notes on modifying Lists to give an API endpoint that accepts posts, rather than accounts here:
https://wiki.jon-e.net/Masto_Forks/DIY_Algorithms
As far as the actual algorithm part, some initial ideas I had were making paired "inverse algo" lists that show you what's being downranked ...

[–] jonny@social.coop 1 points 2 years ago (1 children)

@f00fc7c8 @anova
... but I also am much more interested in a parametric algorithm that lets you rank based on an explicit set of derived features, rather than any sort of ML model. The implementation of "lists that also accept posts" is extremely general, so you could plug in anything to that, and so I'm dissociating the literal algorithm part from the masto fork that supports arbitrary algorithms.

[–] jonny@social.coop 1 points 2 years ago (1 children)

@f00fc7c8 @anova the much touchier side of this imo is opting out of having your posts ranked/scraped/etc. like imo I think a bot that caches your home/local feed for some short period is basically the same as what any mobile app would do, but ideally it would be possible for people to opt out of even that - which points to a need for richer metadata at the account/post level, which is also something I'll be exploring by trying to expose arbitrary JSON-LD in posts

[–] jonny@social.coop 1 points 2 years ago (1 children)

@f00fc7c8 @anova and something I had been thinking about with @axz recently was how to make/use shortnames in posts/accounts, so it would be nice to be able to, eg. make a schema/etc. in something like JSON-LD that describes your account's disposition towards bots, or your particular set of algo params like @jonny:rules:bots, or @jonny:algo:timezoneCorrection so they could be reused/swapped/modified/etc.

[–] jonny@social.coop 1 points 2 years ago

@f00fc7c8 @anova @axz ideally long-term I would like to generalize this so you can declare any sort of post formatting/field structure/as a schema and then be able to use it s.t. other clients could consume it with reference to your schema (as opposed to the way eg. glitch-soc can do markdown but base masto just renders as plaintext). those ideas are over here, but still need work: https://jon-e.net/infrastructure/#documents--notebooks