Have you been successful in obtaining ownership or moderation to any abandoned mags? I've requested to a couple that I occasionally participate in just in case they get targeted for spam, but I haven't heard yea or nay either way.
Preventing this issue doesn't seem like a userscript issue (though that's definitely a good start).I think the auto report function is severely needed; it's happening everywhere. If the script can automatically block any user whose post it suppresses, it would be awesome.
But I think the issue is that we need to get support top-down on this.
If the script can automatically block any user whose post it suppresses, it would be awesome.
It does! I've reworded the OP to hopefully make that clearer. After using this approach for a few days, my blocklist (generated entirely programmatically) is ten pages long, and there is nary a bad post in sight. I'm expanding the filters on a daily basis.
I think the auto report function is severely needed; it's happening everywhere.
The idea is that it takes the burden off of myriad (N) users having to manually do this themselves, and lets a single user (the KES custodian) prepare the filters, which then propagate out to any user of KES. Instead of 1,000 people manually blocking, one person builds the heuristics, and everyone benefits.
Preventing this issue doesn't seem like a userscript issue...but I think the issue is that we need to get support top-down on this.
I understand, but the stated goal of KES is addressing issues that can't, or won't (due to some design conflict), be addressed, or which fall through the cracks. At the moment I'm seeing a lot of people voicing frustration, but due to the skeleton crew situation with administration of the site, it seems like screaming into the void. Not that there's anything wrong with that, and hopefully it gets some traction. But my job with KES is just to provide fixes for the end-user, albeit of a third-party nature.
This is a good discussion here. I'm sure I am not the only person to have other accounts (an mbin and a lemmy) but I am pretty invested here. But your #1 option has some relavent points.
Edit to add I have been digging the microblogs and miss that from what I can see on mbin. Maybe my error. I can't even find them.
Mbin does support microblogs. I believe there's a "Microblog" button in the navigation bar for desktop, and the same button found in the side drawer on mobile.
Actually, it would really help if the "Block" button was right next to the username on the spam post. Having to hover over the name and wait for the modal to appear and then go click on "Block" makes it more of a nuisance. I wonder also if in the future you could choose not to display posts by user accounts less than a month old with only downvotes or who have been blocked by hundreds of people.
I've been curious about trying out mbin, and this seems like a good instance to do it on. So I absolutely like option 2 the best.
That said, I tried to sign up earlier today, and never received the registration email. Tried to sign up with an old Gmail account. Might be worth looking into. :)
Sorry about that, and thanks for letting me know. I had no idea the email system was down. I'll probably try to look into it after the migration to Mbin. I've gone ahead and manually verified each user from the past week, so you should be able to sign in now.
Sounds good! Migration probably won't happen today, but maybe tomorrow or the day after if we get lucky. Unfortunately, I ran into a problem while trying to set up Mbin due to one of the mbin/kbin dependencies suddenly disappearing out of the blue (see here).
I understand if you don't want to add yet another third-party tool just to browse the site, but if you feel at all inclined, give it a try. For me 99% of magazines went from unusable to essentially clean.
I don't use a smartphone. im a smartphone luddite. Heck I don't even have a cell phone on me often unless I know I need it (expecting a call or oncall)
Is there a way to leverage down votes to limit content, at the magazine or instance level? I think I know the answer, but it would be dandy to put in place
I mean this is because of a technical issue likely on Kbin's side. Which is not a shock.
Also I posted 2 threads to kbin communities recently, 1 got most of its activity from LW and the other got 4 favorites from different instances and no comments (and it did not federate to LW, though I don't think that was related to the temporary block). LW could be too big but kbin seems kind of dead for the communities that aren't constantly in the feed (likely because of the same people posting, in many cases). Though technical issues always could be part of it in one way or another.
except it doesn’t work well for the rest of lemmy/the fediverse.
many other instances seem to be getting hit by this, but they don’t have as many activities generated locally for this to become much of a problem. additionally, this is mostly affecting instances with high latency to the instance that is being flooded by kbin, as lemmy currently has an issue where activity throughput between instances with high latency can’t keep up with too many activities being sent. the impact of this is can be a bit less on smaller instances with smaller communities often not having as many subscribers on remote instances, although we’ve seen problems reported by some other admins as well. this includes e.g. kbin.earth, which i suspect to have been hit by responses from a lemmy instance, while the lemmy instance was actually only answering the requests sent from that kbin instance.
during the last peak, when we decided to pull the plug for now, kbin.social was sending us more than 20 activities per second for 7 hours straight. lemmy.world can easily handle this amount of activities, but the problem arises when this impacts our federation towards other (lemmy) instances, as e.g. votes will get relayed by the community (magazine) instance, which means, depending on the type of activity being sent, we might have to be sending out the same 20 requests per second to up to 4,000+ other fediverse instances that are subscribed/following the community this is happening in. trying to send 20 requests per second, which lemmy does not do in parallel, requires us to use at most 50ms per activity total sending time to avoid creating lag. when the instance is in australia, with 200ms+ latency, this is simply not possible.
ps: if you’re wondering how i’m seeing this post, you can search for a post url and comment urls on lemmy to make lemmy fetch them, even if they haven’t been directly submitted through normal federation processes. this requires a logged in user on lemmy’s end.
Honestly, no. Kbin has been barely usable for a long time and I'm starting to consider giving up.
I have a notification waiting for me, but I get a 404 on the page to check it out. /sub also didn't work yesterday. I spent a few minutes trying to edit a comment just an hour ago.
Nothing against Ernest, a page of this size is hard to manage alone or almost alone, but it's still a pain as a user.
This is an absurd thread. By collecting together critical comments, and picking back up a loud fight that previously died down over a week ago, you are absolutely adding to any pressure towards our lad in charge.
kbinMeta
Ważne
Magazyn ze zdalnego serwera może być niekompletny. Zobacz więcej na oryginalnej instancji.