Max-P

Dude’s got some balls downvoting all your comments on a thread calling them out for doing that. Gonna make the LW admin’s job easy.

Real user with many comments close to a hundred upvotes, although also a decent chunk of removed comments as well.

The one user went way further back than 12h, I’m seeing it well into 3 weeks. That user hasn’t downvoted this thread yet.

In the last 12 hours, this whole thread is the only thing on your profile that doesn’t have at least 3 downvotes, most much more than that. There’s only one repeat user across your entire profile, although you do have all your comments generally downvoted by the same users within a thread which isn’t super unexpected.

Yes, admins can see all the votes.

You’re kind of a downvote collector so it wasn’t easy, but I didn’t actually see all that much brigading. Seeing some repeat usernames and one occurrence that looks like someone did go through your profile and downvote most comments about a certain topic once, but that’s all I could find. Most set of downvotes are confined to a given post.

You’re really just getting downvoted a lot by a lot of different people. Your downvotes on this post have nothing in common with your other downvotes.

EDIT: Nevermind, there is indeed 2 people downvoting every comment from OP.

I think we’re still deeply into the “shove it everywhere we can” hype era of AI and it’ll eventually die down a bit, as it with any new major technological leap. The same fears and thoughts were present when computers came along, then affordable home computers, and affordable Internet access.

AI can be useful it used correctly but right now we’re trying to put it everywhere for rather dubious gains. I’ve seen coworkers mess with AI until it generates the right code for much longer than it would take to hand write it.

I’ve seen it being used quite successfully in the tech support field, because an AI is perfectly good at asking the customer if they’ve tried turning it off and then back on again, and make sure it’s plugged in. People would hate it I’m sure on principle, but the amount of repetitive “the user can’t figure out something super basic” is very common in tech support and would let them focus a lot of their time on actual problems. It’s actually smarter than many T1 techs I’ve worked with, because at least the AI won’t sent the Windows instructions to a Mac user and then accuse them of not wanting to try the troubleshooting steps (yes, I’ve actually seen that happen). But you’ll still need humans for anything that’s not a canned answer or known issue.

One big problem is when the AI won’t work can be somewhat unpredictable especially if you’re not yourself fairly knowledgeable of how the AIs actually work. So something you think would normally take you say 4 hours and you expect done in 2 with AI might end up being an 8h task anyway. It’s the eternal layoff/hires cycle in tech: oh we have React Native now, we can just have the web team do the mobile apps and fire the iOS and Android teams. And then they end up hiring another iOS and Android team because it’s a pain in the ass to maintain and make work anyway and you still need the special knowledge.

We’re still quite some ways out from being able to remove the human pilot in front. It’s easy to miss how much an experienced worker implicitly guides the AI the right direction. “Rewrite this with the XYZ algorithm” still needs the human worker to have experience with it and enough knowledge to know it’s the better solution. Putting inexperienced people at the helm with AI works for a while but eventually it’s gonna be a massive clusterfuck only the best will be able to undo. It’s still just going to be a useful tool to have for a while.

Then use Voyager, or Tesseract, or Photon. All 3 are usable as plain webapps and have decent mobile experience.

A computer can never be held accountable, therefore a computer must never make a management decision.

IBM, in 1979.

This is wide open to send a nuke on allies and blame the AI.

but I’m curious if it’s hitting the server, then going the router, only to be routed back to the same machine again. 10.0.0.3 is the same machine as 192.168.1.14

No, when you talk to yourself you talk to yourself it doesn’t go out over the network. But you can always check using utilities like tracepath, traceroute and mtr. It’ll show you the exact path taken.

Technically you could make the 172.18.0.0/16 subnet accessible directly to the VPS over WireGuard and skip the double DNAT on the game server’s side but that’s about it. The extra DNAT really won’t matter at that scale though.

It’s possible to do without any connection tracking or NAT, but at the expense of significantly more complicated routing for the containers. I would do that on a busy 10Gbit router or if somehow I really need to public IP of the connecting client to not get mangled. The biggest downside of your setup is, the game server will see every player as coming from 192.168.1.14 or 172.18.0.1. With the subnet routed over WireGuard it would appear to come from VPN IP of the VPS (guessing 10.0.0.2). It’s possible to get the real IP forwarded but then the routing needs to be adjusted so that it doesn’t go Client -> VPS -> VPN -> Game Server -> Home router -> Client.

• https://lemmy.fediverse.observer/stats
• https://fedidb.org/

Not seeing much, but given the subreddit deletions were attributed to an automated system error and stuff it’s not nearly as big of an event as the apicalypse was. The bigger bump I see seems to be linked to the TikTok ban and Pixelfed and Loops climbing to the top of the app store charts.

No idea, never used it, I just happen to know it exists.

You probably want something like Aether instead of the fediverse: https://getaether.net/

It’s peer to peer, encrypted, anonymous, ephemeral and all that.

The fediverse is plainly just not appropriate for this. The ActivityPub makes too many assumptions that the data is fully public.

End-to-end encryption: Encrypt all user communications, private messages, and sensitive data

That could work probably, it’s a lot of work and will break interoperability but could be done. You’d still have to vet your users very well though, which might contradict the next point. It takes one user to leak everything.

Anonymous accounts: Allow users to create accounts without requiring personally identifiable information (PII), such as email or phone numbers. How can we balance this with the need to combat spam?

There’s a fair amount of instances already that will let you sign up with a disposable email

Tor and VPN Integration: Ensure compatibility with privacy tools like Tor, and provide guidance on using VPNs.

A fair chunk of instances already allow VPN/Tor traffic. The bigger ones don’t because of spam and CSAM and all that crap, but even Reddit is fully functional over a VPN.

Remove or minimize data collection, including IP addresses, geolocation, and device information. No web server logs.

That’d be very hard to enforce, and the instance owners have to do some collection for the sake of being able to handle lawsuits and pass the blame. But you can protect yourself using a VPN or Tor.

Ephemeral content: auto-deleting posts, messages, etc after a set period.

As an admin, I can literally just restore last month’s backup and undelete everything that got deleted. If someone’s seen it, you must assume it can at minimum have been screenshot.

Instance chooser that flags which instances are in unsafe countries.

Anyone can get a VPS in just about any country, so you’d have to personally verify the owner which is PII and probably one of the most vulnerable part of the group. You take down the owner you take down the whole thing.

Once again however users have plenty of choices already for that, if you trust your instance’s admins.

Defederate from instances in unsafe countries?

Same as previous point. Plus, one can still use the API to fetch the content anyway.

Better opsec around instance owners, admins and moderators

Also pretty hard to enforce.

And then he’s gonna whine about a “refugee problem”

Lemmy is decentralized, there is no singular Lemmy as a whole unless you’re talking specifically about the server software. As a user you interact with your home instance, in your case lemmy.world.

Most connectivity problems and slowdowns are instance-specific unless you’re talking about a federation problem specifically, for example you posted but it doesn’t show up on other instances, that’s a problem between your instance and the community’s instance.

In your case you most likely just hit something on lemmy.world’s side. Lemmy as a whole is way too small for them to even care about it.

I’ve been having sub second response times consistently on mine. This post submitted instantly.

It makes the fediverse look about as bad as Lemmy did when the Reddit apicalypse happened.

I think we mostly need to communicate the state of things well and frequently to keep users aware this is super alpha preview software and that the the technology is sound but just needs time to mature properly. It’s the cost of freedom: patience. As long as the fixes and improvements keeps coming, buggy shouldn’t be that much of a problem.

So we spent like what, 20 years saying China censorship bad and finding sneaky ways to get them in the global Internet via VPNs and Tor and Tor bridges, and now we want to make our own?

That’ll go well.

Our cured FIP boy

As someone that admins hundreds of MySQL at work, I’d go with PostgreSQL.

Legal content that violates community rules or instance rules but is otherwise harmless like spam, is kept in the modlog just fine. People don’t generally browse the modlogs as you generally can’t interact with the stuff anyway. No upvotes (more likely, tons of downvotes), no commenting. Not much better than going to the internet archive to undelete a post elsewhere.

More extreme content like CSAM usually gets deleted then purged instead, which is a feature that properly goes in and wipes the content permanently.

If you look at it from a different angle and ask: who might be interested by a user being reported, given that each instance operate independently? The answer is all of them.

• The instance you’re on could be interested because it might violate the local instance’s rules, and the admin might want to delete it even if from just that instance.
• The instance hosting the community, because regardless of the other two instances they might not want that there.
• The instance of the user being reported, because it’s their user and if they’re causing trouble they might want to ban the account.

The rest comes naturally: obviously if the account is banned at the source it’s effectively banned globally. If it’s banned on the community’s instance, then you won’t see that user there but might on other instances. And your instance can ban the user, in which case they’re freely posting on other instances but you won’t see it from your perspective.