I mean, I think we all recognize that these are gambling sites trying to skirt gambling regulations, so all of their arguments are going to seem ridiculous. “We’re a prediction market, and individuals with specialized knowledge improve our accuracy.” “We allow people to hedge against adverse events, like Elon Musk tweeting over 300 times this week.” “These are financial contracts, not wagers.”

The interviews I’ve seen with “prediction market” CEOs, they’re openly begging for people to trade on confidential, privileged, or classified information, because that’s the source of their markets’ supposed predictive power.

Most of us lived through 2020: saw cities shut down; hospitals using refrigerated trucks as morgues; literally millions of dead. Most of us then saw the vaccine roll out and all of that just went away.

Don’t even get me started on the 1990s. Every new processor generation actually felt faster. Web pages had blinking banners because the creator thought it looked cool, not to advertise a personal information vacuum. There was no better introduction to the public’s absolutely awful sense of style. But I went from talking to international friends for $0.50/minute to free, and it was amazing.

Those companies have extremely well developed propaganda machines. They have to sell their technology and products as benefits to governments (i.e. society) and solutions to chaos (i.e. crime and terrorism), and they have extremely well refined language to describe themselves in positive term. If you don’t look past the company line, it’s easy to believe that the skeptics and warnings are all just FUD from haters, especially when the propaganda pays your mortgage.

Then Palantir goes and publishes an actual fascist manifesto…

To me, that’s the ‘fancy search engine’ mode of AI where it works well and basically focuses the human effort. A needle-in-haystack problem. It might still be missing things, but they’re things you’ve already missed yourself, so no loss.

It’s different from asking Claude, for example, to create a new guest VLAN with limited internet access and access to only a specific service on the private network. For that, you have to 1) trust Claude because you lack the expertise to review, 2) spend time learning the config system well enough to review, or 3) already know the system well enough to check it. 1) just sounds bad. 2) sounds like Claude isn’t saving much time, but maybe helps focus the human where to study, and 3) seems like the human might have been able to just do the job in similar or less time than writing the prompt + reviewing the result.

I feel like the big mistake they continue to propagate is failing to distinguish among the uses of AI.

A lot of hype seems to be the generative uses, where AI creates code, images, text, or whatever, or the agentic uses where it supposedly automates some process. Safe uses in that way should involve human review and approval, and if the human spends as much time reviewing as they would creating it in the first place, then there’s a productivity loss.

All the positive cases I’ve heard of use AI like a fancy search engine - look for specific issues in a large code base, look for internal consistency in large document or document sets. That form lets the human shift from reading hundreds or thousands of pages to reading whatever snippets the AI returns. Even if that’s a lot of false positives, it’s still a big savings over full review. And as long as the AI’s false-negative rate is better than the human, it’s a net improvement in review.

And, of course, there’s the possibility that AI facilitated review allows companies to do review of documents that they would otherwise have ignored as intractable, which would also show up as reduced productivity.

Not familiar with opnSense, but on your PC, you can check the address it assigns - if it’s /128, it’s a single address.

My ISP does not assign a prefix for delegation unless you specifically ask for it. I had to add “request_prefix 1” to my dhclient.conf file to get a /64 I assume opnSense has a friendly setting somewhere for that. For me, the key phrase was ‘prefix delegation.’ After I got that, I could search around and get my solution.

Pretty sure that reflects its stage in the legislative process, not support/opposition. i.e.: out of 100 bills that get introduced, only 1 becomes law.

Because US businesses will only compete and innovate if you force them. Leave them safe behind ramparts of protective trade policies, and they’ll keep coasting on 1990s technology, as the country as a whole slowly becomes a backwater.

Logging power use by my server was one of the motivators to add homeassistant. That also showed me that specific containers use a (relative) ton of background power. Immich and authentik each raised power consumption by 2-3 watts, so I leave them down unless I have specific need.

fud: Fear, Uncertainty and Doubt. A tactic for denigrating a thing, usually by implication of hypothetical or exaggerated harms, often in vague language that is either tautological or not falsifiable.

If the birthdate field is just a random number, then I don’t see why anyone cares - it would have less personally identifying information than the MAC address. I thought the whole reason people are up in arms about this is the proposal/hypothetical where the OS is required to validate that field against government ID databases, thus giving a third party - the OS vendor or whatever contractor performs the validation - a link to real world identity of any computer user.

So, I can see where commercial OSes, like Windows and MacOS, but maybe including Chrome, Red Hat, and similar, would welcome the requirement to collect user ages. Another piece of user data for telemetry, ad serving, etc, with the cover of ‘government made me do it.’

Linux is always going to have weirdos, ready to spin up their own distribution for their own reasons. Like, I remember when the majors all started switching from init to systemd. There’s still a bunch of distros, even some good–sized ones, that avoid systemd. If age verification works its way from facilitating tools to distro mandates, I guarantee that there will be distributions created in jurisdictions without age mandates that exclude any tools that require age validation or with systems to spoof age validation. It’s simply too easy to change linux to avoid this.

85% of the flat retail rate. AFAIK, no company with a rooftop solar program puts them through spot wholesale market prices. I don’t think my provider even participates in the spot market - they own all their own generation with plenty of excess capacity and essentially no net interchange. They also cap participation in net metering at 0.2% of system-wide peak demand, so there’s very little chance they’ll take much of a loss, regardless.

At least in my area, solar roofs still have to pay the usual service fee, an extra fee for grid-tie, taxes and fees on all the power they consume, without deduction for power they deliver. I know many utilities buy power at the same rate they sell it, but mine only pays 85% (before taxes). Solar people pay just fine for grid maintenance.

That’s just systemd adding a birthdate field to their userdb. Doesn’t require that it be filled out or accurate, and especially doesn’t require it to be validated against a government database. I don’t see it as fundamentally any different from adding a userdb field for favorite color, phone number, or blood type.

Without 3rd party validation, I really don’t see the privacy issue with an age field. Without verification, it is, at worst, one more byte available to hash into a unique identifier, but you can feed that field from /dev/random at every query and poison even that hypothetical.

If you only need it to be accessible inside your home, then you just need to run your own DNS. Have your dhcp point at your DNS and your DNS declare itself the master for your domain.

To get full functionality, you’ll probably want to have your registrar point to the public IP you get from your ISP as the domain’s authoritative name server.You should be able to script it to update the registrar when your ISP changes your IP, but that usually happens infrequently enough to do manually. Obviously can’t do that if you’re behind CGNAT.

To get Lets Encrypt certificates, you can do the DNS challenge. If your ISP gives you a (even inconsistent) public IP, you can do fancy ‘views’ with your selfhosted DNS, where it responds with private IPs inside your network and your ISP-given IP outside your network. I have certbot set up to expose my DNS & web server just before it starts its renewal process, then close the firewall after. Once you have the certificate, you can move it to where ever it will actually be used.

Get a 20x20x4" filter, and the fan will suck it right to itself. Don’t even need mounting materials.

To me, the nonstandard port is mostly nice for reducing log spam from scripts. The risk is that using a nonstandard port lulls one into a false sense of security and overlook good sshd practices. Good sshd practices will prevent the script-kiddies just as well as the non-standard port, while a non-standard port will not challenge a targeted attack. And, if you interact with multiple servers, it can be inconvenient to remember a different port for each one.