alethiophile

Slippery slopes are alive and well, particularly in this domain. Go back to 2006 or so and tell them that in a decade, bakeries would be getting sued for not catering gay weddings.

It is entirely right and proper to consider the likely future implications of an act before you decide it's a good idea. Even if it feels really good to stick it to $OUTGROUP just this one time.

No one has lost domain hosting, that I'm aware of. But at least one person got pepper-sprayed, more have been beaten in the street and others have had people going after their jobs based on mistaken identity.

This doesn't address the fundamental point: that if you declare a willingness to censor anyone, then you'll immediately have a whole lot of people trying to convince you that their personal enemies fall in the censor-worthy category. I don't trust domain registrars or CDNs to be the final arbiters of Who Really Is a Nazi.

The answer is that this is, in fact, a slippery slope, because though TDS seem to be something that could be reasonably called actual Nazis (I honestly haven't investigated them to determine the validity of the accusation), we've also got an enormous cottage industry with a thriving amateur sideline of political activists calling anyone they disagree with Nazis. And it's entirely possible for the "X is a Nazi" narrative to get off the ground and self-perpetuate without any actual truth to it, with no one involved actually examining the claim. A lie can run around the world, &c.

If you agree to censor any category of thing, then you'll immediately have a large group of unscrupulous people attempting to cast all their enemies as that thing. The only general countermeasure is to not censor anything.

I'd pick a Raspberry Pi over an Android, just because with the Pi I could plug in an external HD. But in terms of what I actually do, I just run a full server as a NAS, and don't pay any attention to the power bill.

Also, without external keyboard+display, using a laptop as my primary computer would ruin my body in a month flat. Ergonomics are important.

LFS current stable comes from February 2017. The current version rc1 was released today. It's hardly dead, archaic styling aside. (Anyone else remember when books on specific software suites were relevant...?)

The links they give are to upstream. Some are already HTTPS, some redirect from HTTP. I found one case where upstream provides both HTTP and HTTPS and they link to HTTP. They should fix that.

They also provide md5sums of the tarballs, which get checked automatically in their automated build. They should switch to sha256, but there at least exists an integrity check.

I agree it's much more an educational project than a production one. But that would be true regardless; any system you're putting together by hand like this shouldn't be one that's going into production anywhere.

My use case for `chattr +i`: an rsync backup, on a cronjob, into an external drive mounted at a given point. Make the mountpoint directory `+i` so that the root-run rsync doesn't blindly fill up your root filesystem with the backup target, if it gets run while the external drive isn't mounted.