5,680 karma · joined February 15, 2019
IMAP seems to also be having some sort of problem... Thunderbird has been stuck at "Looking up outlook.office365.com..." for a while.
The exhaust of 250 years of fossil fuel energy production is stored in your lungs and bloodstream. It kills five million people every year. As bad as some of the nuclear accidents have been, it's minuscule compared to what happens on a daily basis in the oil/gas/coal industry.
Most professional builders drive big Savannah vans, which can not only carry full sheets of plywood, but also keep them dry. Plus, the front blindspot is less than one meter.
I don't disagree about transit though.
But in that niche I can really see cheap EVs taking off. I know several people who live in Toronto whose cars have never been more than ~80 KM from home, and rarely been over 100 KM/h. That's a perfect EV user.
And a huge plus would be to get rid of the monster American trucks & SUVs that take four parking spots and two lanes at a time...
We'll see how BYD's handle the bone chilling Montreal winters... Unless they're an absolute flop, I can see some fairly solid future prospects.
(I live in Ontario, but I've been to Le Belle Province quite a bit ;) )
https://www.quebec.ca/en/transports/electric-transportation/...
https://www.quebec.ca/en/transports/electric-transportation/...
The most essential check is SPF and DKIM which authenticate if the message has come from an authorized server. The problem is that most mail services are too lenient with mismatched sender identification. On one hand, people would be quite vocal about their mail provider sending way too much legitimate (but slightly misconfigured) mail to the spam folder. However it allows situations like to happen where the FROM header, the "From:" address, and the return path are all different.
Most mail systems have several stages of filters, and the first ones (checking authentication) are quite basic. After that, attachments, links, and contents are checked for known malware. Machine learning might kick in after this, if certain criteria are met. Mail security is very complicated and works well except for the times it falls flat on its face like this.
https://en.wikipedia.org/wiki/Sender_Policy_Framework https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail
Unfortunately I don't have a source, and would appreciate a UK national with better understanding than me to chime in :)
The G-100D is also quite small, but the faux pentaprism at the top makes it just a bit too big to justify being MFT.
https://petapixel.com/2025/06/28/the-panasonic-lumix-gm-5-is...
Unlike your car, a four-stroke engine with a catalytic converter, a leaf blower is a two-stroke that burns oil by design. The amount of particulate emissions is hard to understate, and the amount of NOx these belch out is staggering. Asthma, cancer, heart disease, COPD, all are on the table with this type of system.
https://en.wikipedia.org/wiki/Two-stroke_engine#Emissions https://en.wikipedia.org/wiki/NOx#Health_and_environment_eff...
https://en.wikipedia.org/wiki/IPv4#Header https://en.wikipedia.org/wiki/Internet_Protocol_Options https://en.wikipedia.org/wiki/IPv4#/media/File:IPv4_Packet-e...
The biggest problem is that most of the popular tools are built for the target audience of "dedicated infra team", when in reality most k8s users don't really have that.
If it was just about cooling and power availability, you'd think people would be running giant solar+compute barges in international waters, but nobody is doing that. Even the "seasteading" guys from last decade.
These proposals, if serious, are just to avoid planning permission and land ownership difficulties. If unserious, it's simply to get attention. And we're talking about it, aren't we?
The main risk with directly attached storage is that most kernels will do "buffered writes" where the data is written to memory before it's committed to disk. Yanking the drive before writes are synced properly will obviously cause data loss, so ejecting is always a good idea.
Generally, NAS is a bit safer for this type of storage because the protocols are built with the assumption that the network can and will be interrupted. As a result, things are a bit slower since you're dealing with network overhead. So, like everything, there are some trade-offs to be made.
Ultimately the problem is that in a lot of big corps, IT is basically unaccountable for setting things up wrong. Their only KPI is tickets closed, not the quality or success rate of their fixes.
I once had a recurring problem with patch cables between workstations and drops going bad, four or five in one area that had never had that failure rate before. Turns out, every time I replaced one somebody else would grab the "perfectly good" patch cable from the trash can beside my desk. God knows why people felt compelled to do that when they already had perfectly good wires, maybe they thought because it was a different colour it would make their PC faster... So, now every time I throw out a cable that I know to be defective, I always pop the ends off. No more "mystery" problems.
I'm a bit spoiled with the beefy 2.5 in my Mazda... Though it's still about 480 HP less than this beast ;)
> 2.0-liter boxer engine ... 670 horsepower and 680 lb-ft of torque
Those are V10 numbers coming from something the size you'd find in an econo-box.
Obviously unlike your Camry this thing is not going to do 300,000 KMs over its lifetime, and will be rebuilt frequently. This is the extreme end of the engineering tradeoff, and it's interesting to see what happens when the scale tips all the way over.
Example: https://www.cbc.ca/news/canada/toronto/raccoon-resistant-bin...
https://xkcd.com/1739/ - but with "terraforming"
https://www.google.ca/maps/@33.6867973,-116.2608676,25994m
It's clear to me as an outsider that California has serious water sustainability problems. I mean, how long can this last?
https://buffaloride.org/buffalobicycle https://worldbicyclerelief.org/product-development/
In terms of privacy & security, like everything it comes down to risk model and the trade-offs you make to exist in the modern world. Nextcloud is for sharing files, if nothing short of perfect E2EE is tolerable it's probably not the solution for you, not to mention the other 99.999% of services out there.
I think most of the problems people report come down to really bad defaults that let it run like shit on very low-spec boxes that shouldn't be supported (ie raspi gen 1/2 back in the day). Installing redis and configuring php-fpm correctly fixes like 90% of the problems, other than the bloated Javascript as mentioned in the op.
End of the day, it's fine. Not perfect, not ideal, but fine.