Y’know I’ve often wondered that, but authoritarian propaganda seems to have a penchant for keeping its statements plausible. I mean they could take the piss and say it was 500% and it would be just as well. I’m guessing there’s some psychological benefit to be had from keeping it “real”, gives the rubble some kind of logic to cling to?
It does matter, just not the way you might think. Voting in dictatorships is basically a submission ritual.
You joke but behind the Iron Curtain the dictators used to win “elections” with something like 98% of votes. “See, we have some malcontents but they’re a tiny minority.” It was all doctored of course but it’s funny that they bothered to keep it believable when everybody knew the truth, both inside the country and elsewhere.
IRC supports TLS encryption. Many large networks don’t actually have it enabled or use self-signed certs because they still think it’s the 1990’s, but if you make your own server you can use TLS just fine.
If you’re satified you’re probably not missing much.
Most of the Arch-based distros have found a niche of their own and most of them try to offer varying levels of help to the user to sweeten the Spartan experience of vanilla Arch.
Some of them like Endeavour try to keep the interference minimal, they offer some presets and some theming and an installer and stop there.
Distros like Cachy and Garuda are somewhere in the middle, with some quality of life stuff such as graphical package installers, and some custom packages, and streamlined driver install.
A distro like Manjaro or SteamOS takes it to the extreme with a “mommy knows best” setup that only bears a tenuous resemblance to vanilla Arch anymore, and you have to leave it alone to work as intended.
Oh man, I had to go way down in the comments to find a Manjaro fight. I even saw a fight over Mint on my way here. Mint, ffs.
WTF I though Manjaro was the black sheep of the Arch family.
Splitter!
The main limitation in a 1U chassis is the size of the heatsink + fan. They’re typically 80x80mm width/length, and the height is very small. You get 45mm for the whole case so you have to work with a slim (15mm) 80x80 fan and a tiny heatsink that’s 10mm or so. So they have to work at 5000rpm and put out 60dB of noise but even so they’re typically only rated for 80-100W.
I other words I really don’t think it’s worth bothering for a 250W draw. If you can get a 2U space yeah, that gives you much better cooling options.
Don’t even suggest it to the datacenter people. They will laugh at you.
Ok to clarify, I mean if Occulus devs want to publish their games to Steam, they can. But Valve won’t add anybody’s games for them to Steam.
Don’t all the games have to be uploaded to Steam by their rightful developer?
If you have good IPv6 connectivity both at home and away you can look into the Yggdrasil network. It facilitates node-to-node encrypted communications, but it’s decentralized and community-run. Unlike Tailscale, each node can do both communication and relay.
You run the Y client on each device you want to use and if you want to keep things completely private (and you have at least one device that’s not behind CGNAT) you can only add your own devices as peers. If you need to bypass CGNAT you can use one of the community-supplied nodes to act as relays, or set up your own node on a VPS.
The cool feature of Y is that if you’re trying to communicate between nodes A and B and there isn’t a single node that’s peered with both A and B, you can still communicate as long as there are nodes somewhere in the network that know them both. The network will search for you and calculate the optimal relay path. Ofc like I said this is irrelevant if you decide to stick to your own devices, basically you will have your own personal mini Y network completely separate from the main public network.
Even when using the public network there’s no privacy issue, relay nodes cannot snoop on communications only facilitate the connection or not, and once relay to a node has been accomplished the nodes will communicate directly thanks to ICE+STUN, if possible, like Tailscale does.
Please note that nodes are identified by 2001:: random addresses. While the 2001:: address space is huge it’s still only obscurity not security. You still need to have a decent firewall setup on each node, Y does not enforce ACLs or anything like that. It’s also up to you to set up DNS and anything else you might need.
If your services are private they should be behind access authorization or completely private access. Scanning should be a non-issue.
You can further mitigate scanning by getting wildcard certs, putting A/AAAA records on an obfuscated sub-domain rather than the base domain, and not using wildcard CNAME’s.
If they services are public you should be using a CDN anyway. If you don’t like the way Cloudflare does things they’re not the only CDN around, but some of the privacy issue is moot when running a public service.
crowdsec has always struck me as a really odd approach to security. You give out your logs to strangers and block IPs based on their say-so.
The cause and effect are so far removed that I can’t wrap my head about how it’s supposed to be efficient. It’s been proven in real-world tests that it lags badly behind the first waves of new vulnerabilities and by the time it starts blocking IPs that were related to those attacks the attackers have moved on and there are also patches available.
The “thousands of IPs blocked” image reminds me of that WWII airplane bullet-holes image.
Oh it will be, shortly after people stop buying DRM.
It’s popular because it works. You don’t get a lot of choice in the NVR area, most of the other projects are kind of ass too. I’ve been trying lots of them and so far Frigate and Shinobi are the only ones that you can get to show your camera streams, and detecting & recording actually works.
I also don’t think many people care about the security that much. Either that or they run the container like I do in a completely isolated VLAN with the cameras. Honestly, if it wasn’t for the obscene amounts of RAM, CPU and storage it wastes for no good reason I wouldn’t care that much about the security either.
hoe come the developers are not improving the image?
Lots of developers are clueless about Docker. They are used to running their stuff on the metal and piling everything together and they don’t even consider they should clean things up before they ship a docker image.
Gramps Web for example is another humongous image, and it’s humongous because apparently the developer can’t be arsed to separate the building stage from the production stage in their Dockerfile, so they’re shipping all the build toolchains. People have pointed this out to them and they’re like “eh whatever”.
This camera (Reolink E330) doesn’t have HTTP (80 or 443), just RTSP (554), ONVIF (8000) and the proprietary interface that their own app uses (9000).
Yeah Frigate devs claim it can’t be done, but it works in other projects like Shinobi.
They don’t need to be actual users. When they’re trying to start Tailscale on a new device have them pass the authorization link to you and open it on your account. This way their devices are registered as devices for your user. You can tag the devices and write ACLs for them to determine what they can access.
While that’s technically true, in some cases you might want a graphics stack after all. For example if there’s a TV nearby you can get some cool benefits from being able to output directly to it.
But I agree that starting with a desktop distro is probably not the way to achieve it.