I'm pretty certain I know how this algorithm is generating its order. And it's bullshit.
It has recency bias.
@lina An improved version would probably need database access to be performant enough to work.
I'm pretty sure this thing just "walks" your profile for the last 50 or so interactions and just scores based on that.
A complete ranking would take forever, but if you just fed it postgres it could do it pretty fast.
@dcc @lina This is the smallest circle I've ever seen this thing make. (I'm antisocial and only post) And it 100% is interactions and not something more meaningful like replies (it might be both). Install Gentoo commonly stars my posts but I don't think I've ever talked to him.
This is also the first time I've ever used this thing I never bothered asking what it was.
@SuperSnekFriend @dcc @lina
Yeah that's what I was thinking. It would have to be instance specific (only users on that instance can gen).
I'd do it but having a publicly facing web app attached to my database is kind of spooky even if it's just read only I'd be concerned with SQL injections cause idk what I'd be doing for security.
Factoring in this would be extremely easy but would require API keys for the user.
The easiest way to go about all of this would be to just use the REST API to pull all this information since pleroma and mastodon both can use Mastodon API. However I'm like the only person that hates REST API
The way I'm imagining is more intimate... and by intimate I mean some dickhead is literally going to rape/ddos your database and exfiltrate your DMs or something.
You literally just give the application psql access and run tabulations off queries with an internal application and abstract the dangerous functionality away from the end user. It's still extremely dangerous I think somehow if you don't set up your hooks or access controls right.
push button, SELECT id FROM known_users, if match block/mute list remove, count and tally interaction count, sort by id DESC ASEC or something, build visualization.
It'd need to be custom to each instance type because pleroma and mastodon structure data differently and potentially each instance since admins might have setup their databases differently.