Yes, the guardian app allows you to send encrypted messages through their app to their journalists. 100,000 people check the news, one person is whistleblowing. That one person’s messaging traffic is mixed in with the regular news data, so it’s not possible to tell which of those 100,000 people are the source. Signal messages travel through their servers, so anyone inspecting packets can see who is sending messages through signal, just not what the messages contain. Thats a big red arrow pointing to only people sending encrypted messages. With this implementation, those people are mixed in with everyone else just reading news or even just having the app on their device.

Wouldn’t you have to have some sort of MITM to be able to inspect that traffic?

You mean like your workplace wifi that you’re blowing the whistle at?

Earth

I’ve been interested in setting up a monitoring setup like this, mostly out of curiosity about what’s going on when I’m not looking. But I know what the answer is and it’s not as exciting as I’d like it to be.

HP and Asus taught me that specs aren’t all that important sometimes.

Shouldn’t be too bad. It’ll take a while, but you grab an example you have now in word, tweak it until it works in libreoffice and you’re done. The biggest issue I’ve had was constant transitions between the two. If you just move to one it’s a rough start moving, but once you’re there you just edit as always. Word isn’t even that great at keeping it’s own formatting, so it won’t be anything new except for learning a new program. it might get difficult once you get to links and embedding, I haven’t tried that in libreoffice so I can’t speak to whether it’s harder or not.

Beyond that, you should be pdf-ing any finalized documents anyway.

You can set up a pretty robust backup system for pretty cheap if you already have the drives, and the knowledge to set it up yourself. I have two always on devices, an NAS that is my central location for important files, which syncs to a backup device with two hard drives that are synced at different intervals. If a drive fails, it gets replaced, and I haven’t lost the core of my backups, I might lose some incremental backups, but it’s more important to me that I have 3 copies available on different drives. 2 are in one location, the third in a separate location and my syncs are each an interation behind, so if there’s a huge screw up, it’ll take three sync cycles before the main copies are lost (not including the incremental backups I also keep).

This setup allows you to replace drives as they fail so you can constantly update with technologies and don’t need to worry about what’s the best medium.

It’s not wrong, but a lot of people hate being harassed until they buy something.

🤔 I wonder if they’ll hire an American who barely dabbles in self hosting and doesn’t speak 28.35 grams of German. Or would it be 29.6 mL?

I’m not seeing nextcloud mentioned in the article. If they are moving to nextcloud, I wish them the best. It’s great for my personal use, but from my experience it’s lacking in what I would expect in a work environment. With a government entity coming to use them, it would be fantastic to see some improvements on them because they’re almost there.

I upgraded my 7 year old 4tb drives with 14tb drives (both setups raid1). A week later, one of the 14tb drives failed. It was a tense time waiting for a new drive and the 24 hours or so for resilvering. No issues since, but boy was that an experience. I’ve since added some automated backup processes.

My laptop with 4gb of ram and atom processor came with Windows 10 (I purchased it intending to put Linux on it). I tried it out just to see how W10 worked on it and it was absolutely excruciating and borderline unusable, and I was coming from a Pentium M with 512mb of ram. I have no idea how anyone would have thought it could be a functional system running that.

Username checks out

It’s literally a rock that will preserve things

Buy it for life® ?

I don’t think it’s specifically for servers, it’s just their immutable distro. I tried it out a smidge on my cheap laptop, it was interesting. My laptop only has 32gb, so anything immutable really wasn’t a good fit for it. I wasn’t really a big fan of everything I add to it being flatpaks, either.

I think I have enough experience with Linux at this point that an immutable distro is more of an inconvenience to me. I don’t think it would have saved me from my predicament any more than using a non-rolling distro, since this is an OS update, not anything to do with anything I did. Really my biggest setback is that this server is working just fine, so my laziness is letting me not spend a few hours to redo it right and I’m pretty sure I could just run yast and reconfigure the networking and be fine. It really was just going to be a practice/dev server so I could see if I could set things up in an environment that didn’t have many handholding tutorials, the leap server it was dev for ended up moving to Debian because it started running things that I actually wanted to be sure were stable. In my infinite wisdom, this one took over the leap server’s job without changing the OS.

Really, I could have just swapped drives since I was rebuilding in Debian anyway, but Homie don’t play like dat.

I had a BSoD on Windows that googling said “could be hardware or software related”. Thanks, I guess. Nothing in the logs even suggested anything happened except the several hours gap between other useless logs.

I’m stuck (probably not, though) on an old tumbleweed version because something in my networking setup gets borked when I upgrade on a headless server I have running (I know, tumbleweed isn’t for servers, this is why). I just reverted to the snapshot it made before upgrading and bam, like nothing happened.

I should get that worked out, but it works fine, so…

I learned about the “nofail” option the hard way when setting up a headless server and typing the address of my NAS wrong.

You did it twice, so I’ll be the grammar police:

Especially = particularly

Specially = for a specific purpose