I cut the sleeves off of mine, that was probably my crime. Sleeves are like pants; the fewer you wear the better your day is.
Dran_Arcana
joined 2 years ago
I think you've convinced me that it's a slightly more complicated problem than I initially gave it credit for; thank you for that!
I think you could solve for the disparate community theme problem by also requiring title match for mergers. You could probably also solve for it by having a 2-way merger whitelist on links. E.g community A and B both maintain lists of "similar" communities and then if A's list contains B and vice-versa they would merge.
Comment moderation I got nothing though. That's a tough one.
Oh weird, I would not have expected to be in the minority there
It's about halfway there I think, they still show up separately in clients and have separate comments threads.
Lemmy needs some sort of built-in way to merge them. That'd be the best solution I think. Then you could just pick a list of relevant communities and it'd be pretty seamless
It's a little deeper than that, a lot of advertising works on engagement -based heuristics. Today, most people would call it "AI" but it's fundamentally just a reinforcement learning network that trains itself constantly on user interactions. It's difficult-to-impossible to determine why input X is associated with output Y, but we can measure in aggregate how subtle changes propagate across engagement metrics.
It is absolutely truthful to say we don't know how a modern reinforcement learning network got to the state it's in today, because transactions on the network usually aren't journaled, just periodically snapshot for A/B testing.
To be clear, that's not an excuse for undesirable heuristic behavior. Somebody somewhere made the choice to do this, and they should be liable for the output of their code.