In a similar vein, I’ve seen a lot of auto moderator implementations created. If instead of creating yet another project, people started contributing to existing ones we’d have a good core set of functionality that could be shared across instances. Competing implementations are fine, but at some point the efforts get spread so thin that progress is limited.

I also only use rounded handles. For some reason flat ones drive my crazy! 😅

I’m not sure what’s worse. The engineer that thought this would work or the company that doesn’t do code reviews.

Squirt me some tunes, bro!

I’m just not confident that I’d be able to pass an interview with either of them. No issue with rules or ratios, I simply don’t have enough time to study up on the technicals. I used to be on a decent tracker years ago, but didn’t pay enough attention when they shut down and missed out on the open invites.

I’ve tried RuTracker in the past but it hasn’t worked very well for me so far. Soulseek sounds interesting, especially if they get a Lidarr integration working.

You’re assigning rmdec to the output of sed. It should work if you wrap it as you did with i1xmr.

From what I understand, this is an issue with using different timestamp formats between implementations. In this case, it’s with kbin and Lemmy.

I think the concerns about smaller instances are valid (as I post from lemmus.org). Some additional data points to consider when evaluating an instance would be whether they’re running a recent version and the uptime of the instance.

It’d probably be a good idea to have a page that promotes these smaller instances that ‘score’ well to help distribute some of the load.