Eh, that’s a mixed bag. Absolutely, one could setup shared delete requests, to federate a delete request, but it would be a bit of a lie as anyone could simply… update their instance to simply ignore delete requests.
For now, simply not having a delete feature is a more honest to the realities of the fediverse. There’ll never be a “true” delete, even if they do eventually support one that’s “good enough”.
I’d be very surprised if anything functional actually comes out of this. Far more likely they get scammed out of the money by garbage like the current “AI writing detection” methods, with terrible success rates that cause more societal problems than they solve.
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.
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!
So true, I have to do this with some predatory mobile game or another every year or two. Sometimes one of them just gets you.
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.
Seems like a sensible overhaul, hitting the major issues with the fee, but still going ahead with a version of it. Big points for me:
Still not sure I love charging per install as a concept, and they’ve already overplayed their hand and burnt many bridges, but at least this implementation isn’t insanely hostile. Guess we’ll see how this plays out from here.
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.
Having used tailwind a little bit, I have nothing but praise for it. Effortless copy/pasting of components with confidence, really nice look by default, easy tweaking, absolutely no management or planning required to organize your CSS, and it’s all right there, directly on your html, never anywhere you have to hunt for it. Feels very freeing to just… not think about CSS at all.
And the “clutter” really is fine, modern IDEs with good syntax highlighting, plus a tailwind extension to help complete the class names and clean up accidental duplicates or conflicting properties, and you’re good.
Exactly the mistake threads just made, trying to capitalize on twitter’s rate limiting fiasco. The “general public” is extremely fickle, and Reddit will give us more opportunities.
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.
I also feel like a lot of the value of chronological is lost if I think it’s algorithmic recommendations. If I don’t know I’m browsing the latest? I’ll likely just think the algorithm is serving up some garbage. Especially somewhere like Facebook, where people haven’t really been curating their feed for years, just… following whoever to be polite and letting the algorithm take care of it.
Yeah man, same boat. I actually do have NSFW disabled, but I’ve still blocked at least a dozen or two lemmynsfw communities for actresses, celebs, gentlemenboners, ladyboners, ladyladyboners, just a metric ton of SFW porn communities.
Would make things so much easier if I could outright block the instance, and heck, maybe I’d even turn on NSFW in that case.
Eh, I’d assume the comparison isn’t flattering. I think the point of this article is to argue you don’t need ElasticSearch to implement a competent Full Text Search for most applications. Splitting hairs over a few milliseconds would just distract from that point, when most applications should be prioritizing simplicity and maintainability over such tiny gains in a reasonable dataset.
Might be interesting to try to analyze at exactly what point elasticsearch becomes significantly useful, however. Maybe at the point where it saves a full tenth of a second? Or where it’s returning in half the time? Could be an interesting follow up article.
I don’t necessarily disagree that we may figure out AGI, and even that LLM research may help us get there, but frankly, I don’t think an LLM will actually be any part of an AGI system.
Because fundamentally it doesn’t understand the words it’s writing. The more I play with and learn about it, the more it feels like a glorified autocomplete/autocorrect. I suspect issues like hallucination and “Waluigis” or “jailbreaks” are fundamental issues for a language model trying to complete a story, compared to an actual intelligence with a purpose.