db0

Follow-up from https://lemmy.dbzer0.com/post/15792108

I've spent a ton of hours trying to troubleshoot why lemmy.dbzer0.com is falling behind lemmy.world in federation. We have a good idea where it's going wrong, but we have no idea why.

The problem is that once I receive an apub sync from l.w and send the request to the lemmy backend, it takes about 1 second to process an apub sync, which is way too long (is should typically be < 100ms).

We had a look at the DB and it was somewhat slow due to syncing commits to disk. OK we disabled that, and now it's much faster (and less safe but whatever) but the sync times have not improved at all.

I've also made a lot of tests to ensure the problem is not coming from my loadbalancers and I am certain I've removed them from the equation. The issue is somewhere within the lemmy docker stuff and/or the postgresql DB.

Unfortunately I'm relying solely on other admins help on matrix, and at this point I'm being asked to recompile lemmy from scratch or deploy my own docker container with more debug instructions. Neither of these is within my skillset, so I'm struggling to make progress on this.

In the meantime we're falling further and further behind in the lemmy.world federation queue, (along with a lot of other instances). To clarify, the problem is not lemmy.world. It takes my instance the same time to receive apub syncs from every other server. It's just that the other servers don't have as much traffic so 1/s is enough to keep up. But lemmy.world has so much constant changes, 1/s is not nearly fast enough.

I'm continuing to dig on this as much as I can. But I won't lie that I could use some help.

I'll keep you all updated in this thread.

Found via: https://hackers.town/@CyberpunkLibrarian/112046696080448828

Okay, I found this on Reddit and I had to share it.

A guy shows up in r/bbs, a subreddit dedicated to classic and new computer bulletin board systems. I'm a big fan. Anyway, this guy shows up and says: Hey, does anyone remember the BBS game my dad wrote? It was called Buccaneer, and it was a pirate game you played on BBSes. Dad died six and a half years ago and I just wonder if anyone heard of his game?

Turns out... people have heard of Buccaneer.

One person has it running on their board. Another person was able to share the ZIP file for others to put it on their boards. Oh no! It was software you had to buy if you wanted the full version of it. But Dad is gone, and the kiddo has no idea how to open up the software to everyone.

No problem, someone posted a quick C programme that will generate keys for you. The kid might be crying because now even more people can play his dad’s game.

There’s some kinda lesson here in abandonware, but also in humanity. This kid may or may not own the copyrights to his dad’s stuff. Who knows? But one thing he certainly doesn’t have is the ability to make it work.

But because of a few folks on the Internet, running some old software, and someone who took a few minutes to write a keygen? Well, his dad is still out there somewhere, and he’s playing pirates.

https://www.reddit.com/r/bbs/comments/1b626zo/curious_if_anyone_remember_my_fathers_door_game/

Testen

Editing to avoid confusion

Do not confuse Open Collective Foundation with Open Source Collective: https://opencollective.com/opensource/updates/regarding-the-announcement-to-dissolve-open-collective-foundation

This is even more confusing because the org behind Open Collective (opencollective.com) is called " Open Source Collective" whereas the org behind Open Source Collective (oscollective.org) is called Open Collective Foundation.

I believe the author here is confused as well

EDIT: I'm even more confused. Links from oscollective.org point back to opencollective.com. 😵‍💫

cross-posted from: https://lemmy.dbzer0.com/post/15238521

Yet another "brilliant" scheme from a cryptobro. Naturally this caused a gold-rush for scammers who outsourced random people via the gig economy to open PRs for this yml file (example)

Yet another "brilliant" scheme from a cryptobro. Naturally this caused a gold-rush for scammers who outsourced random people via the gig economy to open PRs for this yml file (example)

cross-posted from: https://lemmy.ml/post/12426588

There's now a swagger documentation for the Lemmy API.

See also https://mv-gh.github.io/lemmy_openapi_spec/

cross-posted from: https://lemmy.dbzer0.com/post/15112791

Hey y'all. I've been working on this little project ever since the recent spam wave started. This is a very basic Python automoderator bot which will monitor the comments and posts federated into your instance for specific regex instances and then automatically report, delete, ban etc.

The Bot setup is very simple, as you can just chuck its docker-compose entry into your existing lemmy one. You just need to fill in the relevant environment variables.

The bot works by constantly polling your incoming reports, posts and comments, and matching them against provided regex.

I wanted to keep things simple for admins, so the bot configuration happens via a simple PM syntax. The README goes into details on this. But you basically send a message like this to the Bot to add a new filter

threativore add comment filter: `trial period`
reason: `Spam comment`
action: `REMOVE`
description: `Known spam string`

All bot controls work the same way. Eventually I want to add a UI to it.

The bot is built with collaboration in mind. So you can add more people to help you maintain your filters (even if they're not admins), you can add users whose reports will be treated more seriously, and you can even mark users as "ham" (i.e. known not spammers) to prevent them ever being filtered.

This is just the very first release and I have a lot of ideas to improve it in the future. Here's some stuff in my roadmap which should make the threativore a much more collaborative/crowdsourced process between multiple instance admins and the larger userbase. Stay tuned.

PRs and suggestion are welcome.

PS: The bot is already active on https://lemmy.dbzer0.com, so you can check the modlog for its actions.

Hey y'all. I've been working on this little project ever since the recent spam wave started. This is a very basic Python automoderator bot which will monitor the comments and posts federated into your instance for specific regex instances and then automatically report, delete, ban etc.

The Bot setup is very simple, as you can just chuck its docker-compose entry into your existing lemmy one. You just need to fill in the relevant environment variables.

The bot works by constantly polling your incoming reports, posts and comments, and matching them against provided regex.

I wanted to keep things simple for admins, so the bot configuration happens via a simple PM syntax. The README goes into details on this. But you basically send a message like this to the Bot to add a new filter

threativore add comment filter: `trial period`
reason: `Spam comment`
action: `REMOVE`
description: `Known spam string`

All bot controls work the same way. Eventually I want to add a UI to it.

The bot is built with collaboration in mind. So you can add more people to help you maintain your filters (even if they're not admins), you can add users whose reports will be treated more seriously, and you can even mark users as "ham" (i.e. known not spammers) to prevent them ever being filtered.

This is just the very first release and I have a lot of ideas to improve it in the future. Here's some stuff in my roadmap which should make the threativore a much more collaborative/crowdsourced process between multiple instance admins and the larger userbase. Stay tuned.

PRs and suggestion are welcome.

PS: The bot is already active on https://lemmy.dbzer0.com, so you can check the modlog for its actions.