The Mini EV is in the US, but its range is just adequate. Then there’s older models, like the Bolt or Leaf. Ford has an EV Transit van for commercial customers, but its range also sucks.
Hyundai Ioniq 6 is out there, at least.
Yeah, the US market for EVs is bad. Just SUVs and trucks with few exceptions. Not even a good (mini) van.
Make the man afraid some more.
I take a different line entirely. If you have $100k household income, and that’s still not enough cover expenses for a family of four, then something is very wrong. By income distribution, 80% of the population makes $100k or less, and it’s completely untenable for them.
I’m having trouble finding a reference to median US living expenses, but you can cut the above number in half if you like. Multiplying it for a family of four won’t necessarily be 4x, but it’ll be more than 2x.
Those figures won’t be that far apart. It will somewhat, because higher incomes will have a bigger house and more luxurious car. However, they’re putting more of their money into investments, not cost of living.
And I’ll reiterate, that’s the average for one person, not a family.
As of 4th quarter 2024, average cost of living for a single person in the US is $4,948/month. Take that $8,333/month, chop off 20% for taxes, and you’re already getting uncomfortably close to that number. For a family of four, I really don’t see how those numbers work at all.
Despite the administration’s crackdown and Johnson’s suspicions, it’s not known whether the leak came from a member of Congress.
Given the clowns in charge, it’s more likely the leak came from inside the White House.
Nah, setting non-standard ports is sound advice in security circles.
People misunderstand the “no security through obscurity” phrase. If you build security as a chain, where the chain is only as good as the weakest link, then it’s bad. But if you build security in layers, like a castle, then it can only help. It’s OK for a layer to be weak when there are other layers behind it.
Even better, non-standard ports will make 99% of threats go away. They automate scans that are just looking for anything they can break. If they don’t see the open ports, they move on. Won’t stop a determined attacker, of course, but that’s what other layers are for.
As long as there’s real security otherwise (TLS, good passwords, etc), it’s fine.
If anyone says “that’s a false sense of security”, ignore them. They’ve replaced thinking with a cliche.
All by themselves, weather forecasting satellites justify every dollar put into space programs. The lives saved are incalculable. We are squandering that benefit for no reason whatsoever.
One of my favorite exchanges from the 2008 election:
Colbert: tell me about growing up with a silver spoon in your mouth on the south side of Chicago
Michelle Obama: we didn’t have silver spoons. We had four spoons.
Colbert: but there were spoons, right?
There are ways they can work around it, but their lead developer was drafted into their country’s military. Ultimately, they’re going to have to make their own phone, and it looks like they’re making plans to do that.
For now, it’s fine.
And they purposely hobbled certain things people want, like inline links and images. Some clients will do it anyway, but it’s against the collective wishes of the developers.
If I wanted to track people on Gemini, I could totally do it. It’d just be in a more server-to-server way than how its evolved on HTTP (pixel trackers and such).
Some people haven’t lived through the time when HTML layout was done through nested tables, and it shows.
Maybe we could have No-JS and No-Client-Storage (which would include cookies) headers added to HTTP. Browsers could potentially display an icon showing this to users on the address bar.
Theoretically, browsers could even stop from the JS engine from being started for the site in the first place. Though I wouldn’t be surprised if the engine is too tied into the code of modern browsers for that to work.
Let’s not. It’s a terrible protocol with amateur design errors.
Since 1970, productivity has increased by 86%. That suggests the output of a 40 hour work week in 1970 could be done in under 22 hours with the same inflation-adjusted wage. That’s not even considering the productivity increases caused by industrialization in the century before 1970 (though the 40 hour work week in the US wasn’t set until 1938).
Admittedly, this is a bit of a naive way of looking at the numbers, but it gives ballpark ideas of how far we might be able to go.
Note that real (inflation-adjusted) pay has only increased 32% in the same time period. This, BTW, is a much more robust argument than saying real pay has flatlined since 1970. Real wages are, in fact, up during that time period, but it’s possible the numbers will shift again over time and return to being flat or down. The pay-productivity gap, however, has only been widening with time and isn’t going to be fixed without drastic changes in policy.
JS does a lot of crap that didn’t need doing in the first place. It can be used in a way that improves performance and user experience, but what’s out there is so far from that.
HTML could maybe be replaced by a specific form of Markdown (one with a real spec), but meh, whatever. Gemini did that, but its limitations are a little too much.
Was never part of the standard.
You want to do what Gemini did. Take Markdown, add some specific features to make up for some blind spots in the original, formalize it, and give your version a specific name.
Specifically these issues: https://github.com/jellyfin/jellyfin/issues/5415
The big one is that video/audio playing endpoints can be used without authentication. However, you have to guess a UUID. If Jellyfin is using UUIDv4 (fully random), then this shouldn’t be an issue; the search space is too big. However, many of the other types of UUIDs could hypothetically be enumerated through brute force. I’m not sure what Jellyfin uses for UUIDs.