Oh, what an interesting idea! I like this, on Monday I'll test out switching to this as my main search engine for work and try to report back how it goes!
Hazzard
Honestly, I like this idea, just because it means I could block your instance in my app and instantly filter out that kind of content, just like how someone can block lemmynsfw to get rid of almost all porn.
Yeah, nothing but respect for Lego here. Tried it, proved it wasn't viable, chose not to do it just for the PR, and set back out to continue looking for something that actually works.
Not much of an addition, but you're absolutely right, in most systems that are expected to be highly available, there's standard maintenance times, an agreement in place, and no critical use of the system is permitted to be scheduled in that regular time period. Any deployments are limited to that window, in case a rollback is necessary, data sync, etc.
All of that is in addition to the type of high availability stuff you're describing.
Very true. As someone who likes the all feed as a decent way to find new communities and just generally see more content, it's been a lot of using the "Block Instance" button, and I have NSFW turned off, there's still an abundance of Lemmynsfw celeb type content. I won't even consider enabling NSFW until we get that functionality.
Agreed. The upload schedule has been a holy grail within LTT for a long time, and I truly believe it's the root of all of this, yes, even the sexual harassment. Or at least how that harassment was handled so poorly. When do you have time to make good HR policies? Pull people into HR for reprimanding? Have opportunities for others to second guess decisions? Do training? Or heck, even just have less tired and irritable people making in-the-moment stupid decisions?
This uncompromising maximum velocity hurts everyone, and I hope they keep never bring it back to this pace, even after the process improvements they have planned.
I'm not sure I understand your position here, because voting is such a minor part of the system. A troll that only trolls by upvoting and downvoting isn't much of a threat, unless they've got a dozen alt accounts or a botnet, both of which are different situations that should be handled differently. "The definition of a troll" is ridiculous hyperbole.
And as far as bans are concerned, that's a moderation problem, not your role as an individual. I've never suggested votes should be completely untraceable, that'd be patently ridiculous and remove the ability to actually handle vote manipulation. Moderators and admins should obviously have that access, as I've asserted in this thread.
I'm also not advocating my votes be anonymous, I'm fine with having them public on my page. That alone gives you the complete ability to make a judgement about me as a person, or whatever it is you want to do with that. What I'm suggesting is that a user who's just been downvoted shouldn't have a trivial way of linking it to the individual who downvoted them in order to harass them.
Frankly, the impression I'm getting is that you're not actually paying much attention to the case I've made, and are instead just using my comments as a platform to have a completely different argument that you're passionate about. That's the ONLY way that you could have missed my point so entirely, and come to the conclusion that I could ONLY be a troll or a moron.
It's not being a troll, downvotes are part of the system for a reason: suppressing toxicity. If you downvote a toxic comment to push it down in the algorithm, there shouldn't be a risk of that toxic person deciding they have a grudge and attacking you personally. Otherwise you risk downvotes not being used for their intended purpose, and an overall more toxic environment.
Yeah, having it on your user page is much less dangerous, imo. Still a possibility of getting called out if you downvote someone you're arguing with, but you're already in the comments there.
The only way I see a problem is if someone writes a bot or extension that reads the user profile into something "per comment", and if that gets enough traction and use to build up a strong database. However, in that case, I'd imagine the Lemmy devs would build a feature to let instance admins hide that information from regular users.
Oooh, good point. As an admin/moderator feature, that's a much better idea.
Hmmm, tbh, I don't think that's a feature I'd want. Every now and again you see "that guy" furious that he's getting downvotes, doubling down and trying to start an argument or something. I don't need that guy showing up in my DMs.
Legally responsible, for one.
I.E. If a federated instance hosted pedophilia, that content would be copied to, and served by, your instance's infrastructure, which is obviously legally problematic.