Please express disagreement in a less hostile manner when commenting in our communities.
Hi, sorry for late answer. Yes, the anti-bot workaround is currently unstable
It's currently offline due to instability, I'll let you know once it's fixed
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.
This is the wrong community for these kind of posts, if you have issues you want to discuss regarding this instance, please use !meta@programming.dev. As for your complaint about DMs from our admin team, I would recommend you to send any complaints about admin behaviour as explained on our legal site
On a different note, you have been given multiple warnings for your use of slurs, which have no place on an instance about programming. You will be given a second (and final) temporary ban of 14 days, any repeated offences will result in a permanent ban on our instance.
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.
1
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.
I'll copy the answer I provided in the main thread over on !meta@programming.dev, but to also add, the tool does not monitor all users. It only monitors newly created user accounts on programming.dev for x amount of time so that we know that the account isn't being made to abuse or spam. We do not want to have this tool monitoring regular users.
Copied reply about why DM monitoring is needed:
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.
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.
[Announcement] A list of hidden communities on programming.dev is now public
(legal.programming.dev)
view more:
next ›