Hi, sorry for late answer. Yes, the anti-bot workaround is currently unstable

You only need a single account to interact with different lemmy servers (given they are federated), you can’t log in with your programming.dev account credentials on other lemmy servers, but you can interact with them via your programming.dev account.

Frequency of allowed self-promotion may vary depending on each individual community, there is no universal rule on our instance, but try to interact with communities beyond just self-promotion.

It’s perfectly fine and you’re not alone in having multiple accounts. We have no rules against it on our instance. People are more than welcome to use different accounts on different instances as long as it’s not used for ban evasion.

No, you haven’t done anything wrong. It’s an automated system that temporarily removes posts and comments that include image uploads from new accounts as we have had issues with trolls making new accounts to post abuse. Once the posts/images are manually reviewed by the admin team, they are restored.

With that said, please pace out the self promotion, you got 4 self promotion posts in 2 hours.

Edit: I’ve whitelisted your account from the system, so you shouldn’t receive any new removals from the auto mod.

I’m not sure if you’re masterfully trolling, or genuinely asking for help. But if you’re making a post asking for help, you should be open to feedback and willing to learn from the help provided.

I’m locking the post as there’s seems to be nothing but arguing with no learning involved. Feel free to send a DM if you want to discuss the decision.

@c0dezer0@programming.dev @remington@beehaw.org @CombatWombat@feddit.online

Bot is online. ESPN has implemented cloudflare/captcha protection to block bot activity, the current workaround is of degraded performance and slightly more fragile than directly querying data from ESPN. Bot update still work-in-progress, it should work fine for the most part. Check the Norway - Iraq post for current format.

Died a few months ago when ESPN stopped responding to the queries the bot made. I probably got some time to maybe fix it next week

Seems like everything is up to date on lemmy.dbzer0 now, just minor federation quirks it seems like. Thanks for notifying about a potential issue.

It’s an open issue on github from 2024, it doesn’t seem to be a priority. This tool allows us to react faster than reports though, and hopefully remove some problematic content before it’s seen by others.

From the PR standpoint, I don’t think it’s worth it, and it’d be better to just leave it on reports.

The problem is that we can’t rely on reports of DMs since lemmy doesn’t federate them to us.

E.g.
-> troll@programming.dev makes a new account and sends harassment to victim@lemmy.instance
-> victim@lemmy.instance reports the DMs from troll@programming.dev
-> We, the admins of programming.dev, do not see this report because lemmy does not federate the DM report and troll@programming.dev can continue harassing others because we never find out about it.

This isn’t just a theoretical, it happened just last month that one of our users (1 day old account) sent rape and death threats (which were reported), and we found out about it by pure chance when talking to admins from the other instance.

And just to clarify, the tool only automatically monitors new accounts, i.e. accounts that are being registered today. If you account is more than a few weeks old, the tool doesn’t monitor any of your activity.

We’ll take the fact that you haven’t noticed much spam as a compliment.

The most recent spam that we have seen is harassment/doxxing campaigns that target specific users. It’s not something the average user would notice as the harassment is often DMs or pings on random posts. That, and a ban evader with a recognisable writing style.

As you pointed out, there is no monetary interest on our end. We are just volunteers looking to fix the blindpots in the moderation tools. We have no interest in needlessly censoring speech, and if you ever feel we moderate the instance too harshly, we are open to taking feedback. You can always check the modlog to see our activity. The guidelines for our moderation can be seen here.

Please avoid insulting users in your comments

Good point, I think I misunderstood OPs post

c/die_reklame has been set to hidden by an admin due to being a community primarily driven by a bot, but it seems like it wasn’t added to the public hidden communities list. That’s our mistake, we will update the list to show it as hidden.

Hiding communities isn’t something done by moderators, it’s something we do at an admin level according to our instance’s policy.

I haven’t hidden the community yet and the post is visible both on the standard frontend and the tesseract frontend. Not quite sure what’s going on in OP’s picture, checking the database, all the recent posts seem normal.

https://programming.dev/c/britishtelly@feddit.uk is currently visible and not hidden.

However, as it seems to be a bot community, it should be hidden on our instance, so we will hide it and update https://legal.programming.dev/docs/hidden-communities to reflect that.

Bot is online again

Yes, I get an error whenever trying to log in