pHr34kY

joined 1 year ago
[–] [email protected] 9 points 2 days ago (9 children)

A bank card is far more practical than a second phone. Even if Google Pay did work on GrapheneOS, I would not use it. It looks like a privacy nightmare.

[–] [email protected] 15 points 5 days ago

Artificial intelligence built upon real stupidity.

[–] [email protected] 25 points 1 week ago (8 children)

As a GrapheneOS user, It would be nice if they made it available to their android platforms first.

[–] [email protected] 8 points 1 week ago

I have configured my home router to redirect all plaintext DNS traffic through it. I did it because Chromecasts try to sidestep DNS and go straight to Google.

While doing that was a couple of lines of nftables config, blocking DoH would require an actively maintained list. Even then, it would be trivial to host your own by renting some server space.

[–] [email protected] 6 points 2 weeks ago

I hope they're just patenting this to prevent other manufacturers from doing it.

[–] [email protected] 33 points 2 weeks ago (5 children)

Even if you can't cleanly remove it, you can probably delete a few system files and break it. It's not like the whole thing will be baked into kernel32.dll.

[–] [email protected] 3 points 3 weeks ago

This was at a stockpile yard at a port where raw mined materials were stored before being shipped.

Basically, if the wind was blowing strong enough in the right direction, it would blow over a nearby town. The problem wasn't really knowing where the dust was going, but where it was coming from. Accurate monitoring could detect exactly which pile the dust is coming from, so you could direct all the water to the source. It's impractical to wet the entire yard, as it's huge.

[–] [email protected] 65 points 3 weeks ago (13 children)

This reminds me of something I worked on at my last job. I made software to detect plumes of dust pollution from a mining site blowing onto a nearby school and town. The EPA issued fines if they detected too much dust over the town. This system could catch it early for quick intervention.

After it was deployed, I got a glimpse of their production config. They hadn't configured the alarms for early intervention. They had configured them so that they could get as close as possible to their allocated limit before they intervened at all. Because, ya know, spraying water on stockpiles of ore is expensive.

Fucking mining companies, man.

[–] [email protected] 4 points 4 weeks ago

I know about that one. The 800MB "fix" for it has been crashing machines quite hard.

I don't have that problem because I don't run Windows.

Windows is shit.

[–] [email protected] 8 points 4 weeks ago (18 children)

IPv6 should not be disabled under any circumstances.

In fact, many devices in my house have IPv4 disabled. Disabling IPv4 on my public-facing SSH reduced the attack traffic to zero.

IPv4 is shit.

[–] [email protected] 59 points 4 weeks ago* (last edited 4 weeks ago) (38 children)

Public-facing: Password generator, stored in a password manager.

Internal LAN: Everything gets the same re-used, low-effort password.

Nobody is going to hack my CUPS server.

view more: next ›