Yes, I absolutely despise the new UI. I started using reddit specifically because of that compact interface that never autoplays anything, gives you all identically sized thumbnails of videos or pictures etc. When they started trying to force people to that new UI I all but stopped using it. I did find a plugin that takes the new UI and creates its own equivalent of old.reddit.com called sheddit that I am still using when I HAVE to go there. But I also have other complaints about the way that reddit is managed. Too many subreddits are allowed little fiefdoms. I don't like that but I reluctantly see where there isn't much choice. What do have great issue with is any of those little fiefdom subreddits when they make it the front page... i really think that reddit should disallow any closed or heavily moderated subreddit from ever making it to the front page. If it isn't a fully open subreddit, then it should never be on the front page anyway.

That doesn't mean that it actually is one, but everything I've read about this incident (including the material quoted here) strongly suggests it.

If that's the case, it should surprise exactly nobody, for two reasons. First, the sleazebags who run crypto "companies" hire other sleazebags because they have no choice; nobody with a shred of integrity or ethics would work there. Second, because the entire move-fast-break-things attitude coupled with their disdain for the mechanisms of traditional finance has led them to construct highly vulnerable systems that lack adequate compartmentalization.

This doesn't rule out North Korean involvement -- if I were them, I'd have placed my own people inside every major crypto operation a long time ago. It's always nice when your adversaries are paying part of your attack expenses. ;)

(Which is a now a recognized disorder, but so new that it's not clear how to treat it.) This man is an asshole, who treats his employees and the company's customers like they're garbage. He needs to removed immediately and blacklisted for life from the tech industry: we have all kinds of problems and many are caused by people just like this.

The only good news here is that once again, excellent journalism by 404 Media has made us aware of a situation that we really need to know about. My response to reading this just now has been to break one of my own rules (no meetings on Fridays) because we're already using a number of Proton services and were planning to expand our usage. However, it would obviously be well beyond merely irresponsible to do so when there's a madman running the company. I intend to demand his immediate termination for cause, and if that demand isn't met, then we'll reverse course (which will be annoying and expensive) and end our business relationship with Proton. We cannot, in good conscience, even think of relying on a company whose CEO thinks security is unimportant.

If Proton has a board of directors, they need to be in emergency session right now.

""fascist" being thrown around trivializes the millions of people that have died from fascism or dictatorships. From Mussolini, Stalin, Hitler and others."

As someone who's read Hannah Arendt (among many others) I'm well-acquainted with the concept of fascism and the abhorrent consequences of those who espouse it.

Trump is a fascist, and the killing has already begun. See, for example: Update on Lives Lost from USAID Cuts which estimates 500,000 to 700,000 deaths per year from that single decision alone. (Of course almost all of these will be black and brown people, so Trump would prefer that we not count their lives at all.) But as awful as this already is, and it will get worse, it's only part of the killing. His insane health secretary is pushing nonsense, which is why measles is back (and it won't be the only returning disease). His drunk secretary of defense orchestrated the bombing of a girl's school. His gestapo (ICE) is disappearing and killing people on a constant basis. And yet all of these combined may only end up be a fraction of the total deaths due to his wholesale destruction of the environment and his embrace of fossil fuels at a time when we desperately need to be rid of them.

It is entirely possible that by the time he's done that Trump will kill more people than Mussolini, Stalin, and Hitler combined. First, because there are more people to kill; second, because the world situation is more fragile than it was in their time; and third, because modern technology enables killing on a mass scale that simply wasn't possible when those monsters were alive.

So I stand by the word "fascist"; that's exactly what he is. The only remaining question is how high the body count will go before he's stopped.

They had one job, many years ago, and at the time, they did it rather well. Now they can't do anything well: they've turned their search into AI slop (use DuckDuckGo or StartPage instead), Gmail is one of the world's top spam sources, Google Groups is garbage, their cloud outages keep increasing in severity and frequency, they've killed off too many projects/services to count, and their CEO is a fascist thug who kneels before Trump and obeys his every command.

If any part of your computing practice or operation depends on Google, it's time to move somewhere else.

"Why though? These aren't elected officials, they aren't political positions. Why should their information be any more public than who your employer is (assuming you don't work for yourself in a small family owned business)?"

Because those of us who work for governments (which I've done, twice) are public servants. We are accountable to our supervisors and their supervisors and so on, but that chain of accountability ultimately ends with the citizens of the city/county/state/province/country that pays us. We are required, by basic professional ethics, to always keep their best interests in mind, and -- in my view -- to put their interests ahead of our own.

In both the cases I mentioned above, not only was my basic personal information available to everyone -- name, address, position, etc., -- but so was my salary. As it should be: the people paying me have the right to know what they're paying me, and what they're paying me for.

It's interesting that you quoted that line, because Koenig delivered it with quiet menace. I've always wondered -- and maybe someone reading this knows -- whether JMS wrote it or Koenig himself added it, because it comes from another, much older sci-fi series: The Prisoner. My guess is that both of them saw it at one point or another, and thus were aware of the (repeated) line and its meaning.

However it found its way into B5's dialogue, it was an excellent choice -- another of the many fine bits of writing, along with "...because I have poisoned your drink" and "He is behind me; you are in front of me." and of course: "Nobody listen to Zathras".

It's not the devil; it's just garbage and is only used by inferior people who don't know any better -- and are too lazy to learn. In that sense it's useful: it allows us to easily identify the incompetent and stupid, which is why I use it as an interview question. (Seriously. It's just one in a list, and it's not the first or last, so there's no particular indication that it's a key. Of course I permanently reject any applicant who answers it incorrectly, but one thing I've noticed is that these people also tend to be seriously lacking in other areas as well. For example, a couple of months I interviewed someone who considered themselves a senior Linux expert but couldn't write a single line of awk(1) -- which is pathetic. I didn't hire them but I did recommend some remedial reading to them in the hopes that they might invest some minimal effort in self-improvement.)

These data centers are the sources and sinks for all kinds of abuse and attacks; have been for many years. The Russian government doesn't care what they go after as long as it's not in Russia, so the operations using these data centers operate with impunity.

Of course I've had most of them completely firewalled out for years, but every now and then one of them picks up an additional network block that's allocated elsewhere, the attacks start, and it's necessary to add that block to one of the existing rulesets. There are many sources for lists of Russian network blocks; one of them is IPdeny country block downloads, which is updated quite often. (That link is for IPv4; note link on the page itself for IPv6.)

Note: it's advisable to make the firewall rules bidirectional. If you're defending a server environment, and nothing running there requires outbound access to Russia, then make sure nothing has that access and make sure that you set alarms on any attempt -- because they may be an indication that you've been compromised and someone is trying to exfiltrate data. If you're defending a user environment, this is trickier -- on the one hand, none of your users should be accessing anything in the Russia, on the other hand they may get very upset when they find out they can't. But if -- for example -- your users are business users, and there's no business reason for anyone to reach Russian network space, then you can probably impose this as a matter of corporate policy. On the other hand, if your users are ISP clients, then you may not be able to make this stick.

None of this is a panacea. Proxies, VPNs, hosts in non-Russian clouds, compromised systems elsewhere in the world, all kinds of things combine to make this approach inadequate. But you should do it anyway, for two reasons: first, there's no point in making it easy for them. Second, if you don't perform this bit of due diligence, and things go sideways, you may be asked some very pointed questions about why you chose to skip something this obvious and easy.

I'm pretty sure BarKlanBitch "volunteers" by giving sermons in his Klan Crossburning Incest Shit Trailer Park, like all the GOPedophile Klan Bitch Treason Cunts.

Do us a favor, off yourself so you don't waste the money that would have gone to you, BlahTheKlanFuckingShitragCuntboy Nazi Bitch. You GOPedophile Retardican Klan Party Fucks are all a cancer we should get our society some chemo for anyways.

1. Security
2. Security
3. Security
OpenBSD's maintainers are focused on security because they recognize that if you can't compute securely...you can't compute. They're (relatively) quick to remove code, (relatively) slow to add code, because -- as we've learned -- this is just about always the path to improved security.

4. Simplicity. The base OpenBSD install is small and runs efficiently on minimal hardware: I have a test system that's over 20 years old and it just hums along with each new version. Of course you can add any of thousands of packages, but they're not cluttering up everything by default. Note that this minimal install is also aligned with security: "ps" on base install doesn't show much running and 'netstat -a" doesn't show much listening. Contrast with many contemporary Linux distributions that install and run all kinds of things by default.

5. Firewall. OpenBSD's "pf" is the best firewall available, period. it's easy to configure (uses text files), easy to maintain, runs well with minimal CPU and memory, and in almost all cases, is only bandwidth-limited by the speed of the network interfaces.

6. Robustness. OpenBSD continues to stay functional in situations that would lock up or just crash other distributions. A few months ago, one of my systems was hit with a novel DoS attack that pushed the load average over 40; that system was still responsive at the command line and I was able to squelch the attack...and then everything just went back to normal. No reboot necessary. Of course that's how everything should work but it's not how most things really work.

7. Stability. While of course there are occasionally flag days on which old things stop working, for the most part, OpenBSD is very stable. Code that you compiled and ran on OpenBSD 5.7 is highly likely to compile and run on OpenBSD 8.0. Yes, there are scattered exceptions to this -- but worth noting is that some of those aren't the fault of OpenBSD, they're the fault of bad code.

8. FAST response to security issues. If something turns up, OpenBSD developers drop everything and deal with it. Fixes show up quickly, even to obscure bugs that are difficult to exploit or for which there is no known exploit.

The closest thing to OpenBSD in the Linux world is Slackware (and I run it on a few systems). But as good as it is...it's not OpenBSD.

Pretty much every headline can stop right there. ICE are Klan Retarded Treason Bitches, and the rest of DHS are just as much Treason Cunt Retards.

I've run so many Unix and Linux distributions that I've lost count -- starting with Unix v6 on a PDP-11. (I've also contributed a few bits of code here and there along the way.) OpenBSD has clearly established itself as gold standard for robustness. It's not perfect -- nothing is -- but it's the best we've got.

It's not fancy, it's not trendy, it's sometimes a bit of a pain, but if you're serious about security, this is what you want to be running -- particularly on anything that has to face the public Internet. It's well worth the investment of time and effort.

Texas, the Shit State that was barely a country before they wanted to be a Slave State. Fuck Texas, it's a White Supremacist Treason Shit Slavemonger Klan Bitch state.