So weird that is not the default behavior.

Know an iOS client which implements this?

Yeah, but talking about GDPR is burying the lede.

Just another guy who thinks he’s Gods gift to open source because he found a bug, and thinks the volunteer developers fail to show proper gratitude by not dropping everything to work on your pet bug.

Inflicting lawyers on an open source project is a great way to drive off the developers.

If I hear Lemmy has a GDPR problem I assume it’s lawyer BS only European instance admins have to worry about.

If I hear Lemmy has bugs in basic CRUD functionality, that’s a real issue.

Bit of a red herring to put GDPR in the title when the article is about Lemmy missing key admin functions, and only tangentially how this runs afoul of GDPR.

TL;DR Lemmy hasn’t implemented image deletion for users or admins, so don’t upload your government ID.

A sort should not by any means be slow to implement.

Sure, if the sort key is something readily available. But for scaled sort they have to compute relative size/activity of the communities the specific user is in. The cost isn’t the sort, it’s computing the metric.

Is it really a lot of work for an experienced dev? I can pick up most new languages in a day or 2 unless it’s a total paradigm shift.

I’m a Java developer and I would much rather pick up Rust to join an active project than try to rebuild something that already works using a less-marketable language.

I have a hard time believing that rewriting the backend from scratch would be faster than getting PRs approved on the main project.

Forks like this with one guy who “knows best” usually die a slow quiet death as they get left behind by the main project.

I agree, the Israeli government only commits some of the atrocities on that list. It’s anti-semitic to say rape when only sexual assault and murder are well-documented. /s

A self selected list of nerds publishing their interests is a flashback to the 1990’s.

Anyone remember the Geek Code?

Sorry but Threads is read-only to the Fediverse.

I couldn’t find a MAU count either, but the largest, default community is Discuit with current 4,594 members, which I suspect is not too far below lifetime active users.

As a point of comparison, the largest Lemmy instance, lemmy.world has 12k MAUs out of 143k lifetime users. If this ratio is the same on Discuit, would imply about 400 MAUs.

You don’t seem to cover voting and feed ranking at all.

TL; Don’t Read German

The difference is the server doesn’t need to scan the giant vote table for ordinary polling or ranked posts.

Unless there was significant optimization work done on the DB schema, this approach would require joining the large posts table to the very large user-post-ranking table for each request for sorted posts.

This will kill DB performance without some sort of clustering or sharding.

If the server sends posts, and the client computes the ordering, the client has to do the sorting.

The “hot” thing is just server side caching of scores for a server side sort.

What you seem to be suggesting is that the server support storing post scores sent from clients so it can feed that sort back to the client. I don’t think that would scale for millions of users storing their preferred post sorting order on the server.

Sorting algorithms run on the server.

No way a server can allow arbitrary remote code execution.

You could implement something that uses a server sort and has the client do custom sorting on the results the server told it about.