I feel like having to do moderation on the instance level is just not a good idea, because it just leads to scenarios like this. Unless an instance was just set up to send spam, in which case blocking it site-wide is obviously the best thing to do, you’re always going to cut off actual people who post from there.
At least on Lemmy, moderation can also be done on the community level, which actually have a topic they can enforce.
Also reading through the post linked at the end that has more details, this proposal actually seems pretty well-designed. Most importantly, it’s very easy to use, and that’s important for accessibility features (otherwise no one will put these attributes on their websites).
Looking forward to being able to use this, but it’s probably going to take a while for it to be accepted and implemented across browsers. Not sure what the process for that actually looks like.
“Following the recent discussion, we have strengthened our safeguards,” [OKA’s] Zimmerman told me. “We are now rolling out a second, independent LLM review step. Translators must run the completed draft through a separate model using a dedicated comparison prompt designed to identify potential discrepancies, omissions, or inaccuracies relative to the source text. Initial findings suggest this is highly effective at detecting potential issues.”
Ah yes; when LLMs don’t work, just add more LLMs. Genius.
They say it’s been “highly effective” but somehow, I doubt that.
Oh that’s true, I didn’t consider that. I do usually copy the URL directly, because share buttons tend to add tracking parameters I’d have to remove manually. But I know many people don’t even bother (or know about) that. Still, that’s only the “share as link” button. Who knows how much the social share buttons actually get used.
I wonder if anyone actually uses any of these. I just can’t imagine finding an article or something and wanting to share it this way, but I’m also not on Mastodon or other similar networks.
Now that I think about it, this might make the most sense for link aggregators, as that’s just the kind of post you’d frequently share. Hm.
The information returned by whois depends on the registry. For example, most registries for European TLDs basically just show whether the domain is registered (I say “most” because I’m not sure whether it’s actually all or if there are exceptions, but I know .de is like this). In that case, there aren’t even “whois privacy” services available from registrars. For TLDs from other countries or gTLDs, this might vary.
In either case, do note what the other comment says. Whois is not the only way to identify who runs a service.
If you didn’t pay for whois privacy, it would most likely return your actual name, email address, phone number, and home address instead. “Whois privacy” just means your registrar inserts their information into these fields instead, and forwards any mail they might get to you.