Alternatively, you use the cloudflare money to sue the monopoly to decouple search and all other products, since blocking the AI trawlers shouldn’t have any measurable impact in search rankings

They’re not a url, they’re just a string that’s often a url. There’s no (technical) reason why it couldn’t be a signed public key, or a signed url that the camera app could validate

*Is legally required to say it is against

It does look like Roblox is trying to kill the Linux workarounds, though.

This has been the big issue. I’m confident I can tinker something into working, either with Sober as @osbo9991@lemmy.world said or with enough fighting with Lutris/Proton/Wine for today But when the developers are actively working to prevent it. it’s a hard sell when we already have the Windows install and it’s already working, particularly for something they’ll (nominally) outgrow in a few more years.

This. The minute I figure out how to gracefully migrate my VMs off of Hyper-V I’m done with it. My kids’ machines would already be migrated if they weren’t Roblox enjoyers.

I don’t think it’s possible to tuck enough for them to be otherwise

Yes, but that statement also contains over 50% lies by volume

They can do more than one thing though. Germany should be able to treat both the root cause as well as the acute symptoms.

tl;dr he sandbagged the movement when it was beginning to build momentum with a bunch of, what would charitably be called, misunderstandings of the whole point.

It’s covered pretty thoroughly here: https://youtu.be/HIfRLujXtUo?t=1117

There’s a potentially justifiable use case in training one and evaluating its performance for use in, idk, triaging a mass-casualty event. Similar to the 911 bot they announced the other day.

Also similar to the 911 bot, i expect it’s already being used to justify cuts in necessary staffing so it’s going to be required in every ER to maintain higher profit margins just keep the lights on.

Yes, so you can see how that would be a problem

This only guarantees your WANip:8100 will map to 192.168.0.113:81, and doesn’t address whether or not dns resolution is correct. I would also be weary of using port numbers on wikipedia’s known ports list, as some ISPs will filter those upstream. The last thing is that your router may not want to hairpin that traffic, so if you’re not coming in from the outside it might not be a valid test.

This, it was explicitly supposed to be a joke coin. The fact that it trades fairly consistently (if at low value) is kind of an abberation

Site Reliability Engineering, a.k.a. the sysadmins babysitting the Big servers

That’s my understanding of the gameplan

SRE always starting shit

This is 1000% funnier because of the avatar with the dog head

This is likely correct but the browser’s errors should be telling you what the error(s) is/are.