Pretty much all Chinese EVs use LFP batteries. You can hammer a nail into one and it'll just stare at you like you're some kind of dumbass.
Western made ones use NCA or NCM batteries because of range anxiety. But those ones are armored AF so good luck doing any significant damage to them. And I suspect they'll also switch to LFP within the next decade or so anyway.
Or any vehicle with an internal combustion engine, because those burn way more often.
But their fires aren't reported on as much because it doesn't cause as much ~~ragebait~~ engagement.
I'm pleasantly surprised that it takes two did so well. I hope it shows publishers that there's a market for couch co-op!
You might be misunderstanding the value-add of a CDN to self-hosting, so here's my attempt at explaining:
I've been self-hosting things for a very long time. In the old days, we would wrangle our routers to expose port 80 for HTTP (and later, port 443 for HTTPS) and forward those connections to the self-host server and then add the appropriate DNS records to point our website domain to our home IP address (which was its own fun challenge when ISPs refused to give static IP addresses for home plans). Relatively simple.
However, in recent years (especially after the pandemic) the internet has become a much more hostile place. People find vulnerabilities in your nginx/caddy/apache or whatever reverse proxy you use (or router, or any one of the many other parts of your network/software stack) gain access to your local network and your personal data. And then there are bad actors doing DDoS attacks or AI crawlers generating DDoS levels of incoming requests to overload your hardware.
All that combined means it's very dangerous to have your home IP exposed to the internet (allowing any sort of inbound requests) at all.
So, how do we access our self-hosted stuff while we're outside of home? The safest approach is to use a VPN. Tailscale is the most popular one that I've come across. Only client devices that are connected to the VPN have access to your stuff. Random bad actors can't poke your self-hosted stack for vulnerabilities.
Okay, what if you want to share something with people publicly? I for one, use Immich for my photo libraries and it's very easy to be able to share a link to an album for friends and extended family to access without having to install and configure a VPN on their phones.
That is where cloudflare comes in. We can run cloudflared on our machine, which makes an outbound request to cloudflare and creates a tunnel to route all the incoming requests from their servers to your reverse proxy. Your network is still not exposed to the internet, and the edge nodes (the machines that actually front the incoming traffic from the clients) are not owned by you.
Now, I guess it's feasible to rent a VPS on DigitalOcean/OVH/Azure/AWS and run a Tailscale exit node there to achieve a similar result. I haven't looked too deeply into Pangolin but it looks kind of similar. Now you're adding extra work to keep those configured correctly (and up-to-date), is less secure because you're not doing that full time (unlike the engineers at cloudflare) and you're still dependent on that VPS provider to not go down, so the disaster recovery profile hasn't changed all that much.
That's why there's no self-hosted alternatives to a CDN. I guess you can go with their competitors like Fastly/Akamai/etc, but all of them are considerably more expensive. And even the ones that do have free tiers have data limits or bill per gigabyte. That's an extra headache to worry about for that one month your mother decides to take 1000 videos of your son during the family vacation and her phone automatically backed up all of them at full-quality.
Honestly, these days I use fdroid as my primary app store. It's been an amazing way to cut through the junk and find great apps.
I think it's a jab at Postman, which is essentially curl with a GUI.
That's going to become more and more difficult to do over time.
Cars are being designed to be difficult to repair and to fall apart in less and less time.
Woah...an actually heartwarming story that wasn't just a forced positive spin on people coping with the orphan crushing machine!
Color me surprised 🙀
Kudos to Spotify's design language for us being able to determine what app it is from just a generic error screenshot
Evolution doesn't care what happens to you after reproduction because you've already passed on your genes at that point
It's dead. The main dev announced they've ceased development and shut down the main instance.
Eh, that's mostly sensationalization by Western media.
According to my Japanese friends, the new government is quite moderate and their stances on a lot of issues are a lot more nuanced than the headlines imply.