This "new" site is part of a larger effort by that slob to kneecap or compromise US government Web sites, and steal your personal data.

I first read about the effort here: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fthedreydossier.substac...

Yesterday, she took a look under the hood of America.gov, and yes, it's as bad as everything else the DOGE vandals have been doing: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fthedreydossier.substac...

Up until this point, government Web sites were designed, built, and maintained by the agencies responsible for that government service. For example, if you wanted to apply for or renew your passport, you would go to state.gov, which is run by the US Department of State, which is responsible for processing applications for and issuing passports. No other department has lawful jurisdiction over passports.

From the point of view of the law, that's still true. But the slob, without anyone's permission, kluged together passports.gov. This site was built and is run by the White House's "National Design Studio," completely outside the law and without any independent oversight. The State Department was not consulted and has nothing to do with it. Further, the site is filled with third-party trackers, analytics, and some custom code that copies every page you view, including form contents, to an unknown third party.

Oh, and the guy leading the National Design Studio and in charge of building these fake sites? He's Joe Gebbia -- cofounder of Airbnb. Read both articles for more details.

In short, you should treat America.gov as a malware site and stay well away from it. Under no circumstances should you feed it any of your personal information.

Just to note, the WSL containerisation approach is horrible for anything I/O intensive. WSL 1 had ELF binaries supported by the kernel and ran natively, this is a far superior approach to WSL 2's containerisation when it comes to raw speed.

I benchmarked this a few months ago and it was between 300%-600% slower on raw disk performance I/O.

Unfortunately, CustomCSS is dead. See announcement:

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fgithub.com%2FAris-t2%2FCus...

It still worked for me perfectly with the previous Firefox ESR (140.x), but with 153.x I suddelny got my search box (yes I want a separate search box, not automatic search from the url bar!) with double line spacing. No other issues though.

The announcement has a couple of other recommended projects as suggested migration paths.

Get locally produced stuff instead of imported ones from overseas. "Local" does not necessarily mean like from nearby farm, but whatever has minimal time spent in logistics.

Problem with shipping fruit from faraway places is that they are typically picked raw, and then they ripen during the months they spend in a shipping container and finally get an artificial ripening (e.g. with ethylene gas) at the end of journey. Of course they do not have nutrients or taste.

Just wondering, since related topic is Tesla FSD. EU is right now debating on whether to allow FSD across all member states. Some member states have permitted it already, but the big decision is still to be made. There's an interesting report from Belgium where Tesla FSD decided to disobey traffic laws around pedestrian/cyclist zones (going 50 kph in 20/30 kph zones, overtaking cyclists in bicycle lanes, etc).

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.johanna.be%2Fimages%2F...

Results start on page 12, but summary include the nice snippet

"Performance in home zones was similarly concerning. Of the 12 tested home zones, FSD exceeded the 20 km/h legal limit in five cases (42%), averaging approximately 26 km/h. In two-thirds of the tested locations, the system incorrectly isplayed a higher speed limit, typically 30 km/h or 50 km/h. Given that home zones are specifically designed as shared spaces here pedestrians, including children, may occupy the full width of the street, these findings raise significant safety concerns."

So yeah, I'll just drive myself unless car manufacturer assumes full liability when it decides to run over some kid on their bicycle.

If the RAM limitation was to prevent resellers from sourcing cheap RAM chips, and adding them to low RAM versions of RPi for a markup, and the RAM limitation is easily bypassed with and SPI firmware downgrade, then what is to stop the resellers from continuing to do that and also downgrading the firmware? What's the point?

Seriously, there's a ton of articles about this, but here's a link directly from Google:

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fsupport.google.com%2Fand...

Steps 1 & 2 are for the one-time 24-hour cooloff, step 3 is just like before. Oh and note 2e: "After the security delay is complete, you can choose whether to keep the advanced flow on for seven days or indefinitely."

What on earth are you talking about?

As others have already said, you need to give *one-time* permission to sideload. The only question asked is if you want to allow sideloading forever or for 7 days. Those are the timeframe choices. It's not for every single app.

So, get a new phone, go through the menus, allow sideloading, allow forever, reboot phone, 24 hours later you can install whatever APKs you want.

Ok, sorry, but while I get the initial backlash for when Google was going full Apple-style walled garden, the new approach where you need to *one time* enable "yes, allow sideloading" after you get your device (and wait 24 hours) is just fine.

The 24-hour waiting period is exactly for those scammer cases where they ask you to "download and install random APK from some https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fscammers.are.us%2F0wned.... real fast or your money is gone, emergency!" - it stops those.

Of course Google can change those terms later, but at that point you might as well install Lineage or Graphene (or get Jolla phone and use Sailfish - they have launched new product just recently). For now that *one-time* 24-hour waiting period is just fine and I really don't get the complaints apart from some scaremongering about "they'll try to lock it up again in a few years". Ok, and then what? It's not like those heavier options for degooglefying are going away?

It's not real. It's not intelligent. It's a probability matrix - a very good one, but that's what it is. When people say they 'convinced it', what actually happened was they started using language recognisable in a subset of the model's training data and the model responded using probability with data from that same subset as it's statistically closer.

In this case, they used language which is the kind floating around with people negative to AI, and so the AI constructed a sentence using data in their "negative to AI" section. Nobody got convinced of anything. It's very impressive, but it's 'just' a probability matrix.

Well, there *is* the Ford argument ("If I had asked what customers want, they would have said faster horses") so sometimes new tech will find it's uses.

Sometimes "world is not ready" - product comes along that doesn't really take off, but a decade or two later someone makes a cheaper and more polished version that sells like hotcakes.

And sometimes it's just crap being pushed out with the grand thought of "if you build it, they will come". Who remembers all the stuff that poured forth 25 years ago with the dotcom bubble? LGR ( https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.youtube.com%2F%40LGR ) likes to sometimes videos out of them.

But yeah, for this one my guess is that this is a solution looking for a problem. Considering that AI-generated porn hasn't really taken over human actresses despite that industry usually being in forefront of all kinds of tech, I wouldn't bet on this one either.

I see it as

"We created a monster in the name of our almighty god greed, and you have to regain the control we lost.

Without it costing us anything, of course."

I just wanted to let you know that you have successfully driven me off of /., after some 25 years.

Not just you, obviously, the site has been in steep decline for a long time, but you were such a huge asshole that you managed to be the last straw. So, congrats for that. I won't be back.

I was listening to this on BBC news on my commute this morning (in the UK). They said it attacked a Medicare site, which is the Australian national health system. My immediate thought was "ah, so someone in the US asked it to do something with Medicare records and forgot to limit it to just the US then". So off the AI trots to do exactly what it was asked to do - "collect records on Medicare', without any regard to geography at all. Hence this 'hack'.

I mean, I'm just guessing so that opinion is worth what you just paid for it. It does sound plausible to me though.

"I'll america you in your americaing america!" – Smurf Intelligence