do you have supermarket monopolies in the US though?
I’m not in the US. And the post is about Canada. But the problems are global.
You are right, it’s not a monopoly in the strict sense. In most countries, including mine, there are a few serious choke points in the supply chain. Basically, there’s two or three supermarket chains, a handful of specialized logistics companies (turns out here they’re one that handles all packaged cheese distribution for all supermarkets) and then a very small number of producers per item (most detergents and soaps you’ve ever heard of are from one of two companies world wide).
If you dig deeper, it doesn’t really get any better. Yes, there are a lot of farmers, but consolidation is happening as we speak. Also, all fertilizer, herbicide and most of the seeds come from the usual suspects. So, yes, there are many companies involved, but there isn’t a whole lot of actual competition.
It’s really well documented and easy to config. You just open the page for your IDP, follow the instructions, set a few config setting and you’re off.
The user interface is also really good at this. Often custom identity providers feel hacked on, here it’s integrated really well.
I believe the implementation is based on nextauth.js
Store torrent files. The magnet links are just the hashes of the torrent files.
Yes, the magnet link points to a specific torrent file, but you will only be able to get them if anyone is still sharing it and currently online.
If you have the torrent file and the content, you can start a new swarm if the old one is dead. If you only have the magnet link and the content, you can’t.
Ugh. I know that feeling. That’s why I’ve blacklisted salt stack.
https://news.ycombinator.com/item?id=5993959
There’s a particularly toxic combination of ignorance, laziness, NIH and hubris that you need to make a mistake like that, and I want it nowhere near my servers.
Now, I admit, I’m not one to get carried by the drama in the FOSS sphere (still use Gitea)
This is a bit of a “bell curve meme” situation. I’m extremely about the drama, and I’m back to gitea. The forgejo guys are good at branding, but I’m not seeing great project stewardship. I’ll take my chances with the commercial guys for now.
It’s very possible. If you carefully manage your attack surface and update your software regularly, you can mitigate your security risks quite a bit.
The main problem is going to be email. I have found no reliable way to send email that does not start with “have someone else do it for you” or “obtain an IP block delegation”.
The trouble with cloudflare is that there is just one. It’s one of the best registrars out there, the only free/cheap and usable DNS host (have you seen what route53 charges per zone??). That without getting into the whole tunnels and DDoS mitigation end of things, which is nearly unique at any price point.
The problem with cloudflare is that we’re missing three other cloudflares to move to if they decide to pull evil shit.
Caveat emptor, split DNS can cause issues down the line that are a proper nightmare to debug.
Don’t do it unless you a) understand what is happening on your network when you config it this way b) have the tools and ability to verify it is working like you think it should and troubleshoot when things eventually break and c) can exercise enough control over your network to make sure all DNS resolution in your LAN happens the way you think it should.
The “wings clipped” tweet still haunts me.
She is such a remarkable and genuine person, we are all worse off without her contributions.