digdilem @ digdilem @feddit.uk

Posts

3

Comments

66

Joined

2 yr. ago

They announced something similar back in 2020 with a working title of "Liberty Linux", so maybe that.

Excellent summary and conclusions.

As long as you set up SPF and DKIM records on your mailserver, you’ll never get marked as spam.

Sorry - that's factually incorrect. If your IP is on a residential block, you'll be downscored. If you're on a dynamic IP, same again, but weighted even more harshly, by pretty much every antispam service. In addition, every commercial service is very secretive about what methods they use, for good reason, so you cannot claim with any accuracy that "you just need to do this $thing to get read". (Although I do agree the original post is not well researched, knowledgeable nor particularly useful to anyone)

SPF and DKIM are essential to getting your email out, but it's not the only thing, and sometimes no matter what you do do, your hit rate is going to be low.

Source: Me. Been running mail servers privately and commercially for over twenty years. Before then, I ran fidonet and netmail services through the 90s and into the tail end of the 80s. There's many things I know bugger all about, but email is not one of them. (And if anyone's interested what I do for personal email now - I use gmail, because it works and maintaining it is somebody else's problem)

AI's been in use in commercial anti-spam for quite a while now - and on the flip side is also being used by the spam senders. Just another front on the unending war.

But spam (and phishing, and all malware) happens because humans get fooled by it. No reason to think AI will be any smarter.

Hahahahaha. Hahahahaha.

<breathe>

Mate, it's been running since RHEL announced the premature termination of Centos Linux 8, back in 2020.

Nice quote - but I don't think it does hold up as truly as it did in the 80s. There is an unimaginable wealth of systems and design tools available now that were not around then. Even something take for granted like a gui schema designer - hell, even SQL itself wouldn't be around until almost a decade later, and that was partly designed to simplify database queries. Every step like that has simplified what we do today. Debugging tools are light years ahead of when I was writing C in the early 90s. Debugging then was pretty much "try and compile it and then fix the errors". Now there's linters, memory profilers, automatic pipelines and all the rest of that. Much of that is offset by the fact we do far more complicated things than we did, and that those very tools mean there's a lot more to learn and master beyond the mere language.

I do concede and agree with your last paragraph. Design is more important than implementation, and elegance of code and concept is a timeless beauty. One of the hardest things I've had to learn is that thinking about coding is often far more productive than actually coding, and too many times I've been a busy fool, re-writing and starting over many times because I later found out a better way.

I disagree completely.

Great! It would be a boring world if we all thought alike.

Programming is inherently difficult,

That's where we differ. I don't think it is - and I'm not saying that because I think I'm good, it's because programming is just a different way of thinking - that's why there's books like "Zen and the art of computer programming" and "The Tao of programming". (I haven't read "No Silver Bullet" but I'll keep an eye open. I was actually writing code back in 1986 so it might be interesting to compare because I think programming has changed a huge amount in that time)

Not all programming is easy, just as not all of it is hard. The range of this subject is massive, and blanket statements, pro or anti, just don't cut it when you dig into it.

I've heard that a lot, but I think it's an outdated view.

Programming should be easy, or at least easier. That's a view shared by everyone who writes and contributes to documentation on all languages and also those who develop the languages as well. (With varying success).

Every damned one of us was a shit coder when we started, that's part of the process - not least amongst us who are self taught. Yet some go on to do great things and be wonderful coders (including yourself, no doubt).

You had a bad experience, fair enough, but it's a big brush to tar everyone with. I think everyone should be a programmer. If nothing else it teaches them a little how software actually works and that's a good thing.

Me too, but I couldn't eat a whole one.

And they've not broken that, RHEL subscribers continue to get access to the source. It's everyone else they've shafted.

War for the overworld. I have thousands and thousands of hours logged.

Run the cables more neatly.

Any work-issued device should be used for just work, right? Surely that's common sense?

But still fractionally as heavy as lorries, which /do/ cause most of the potholes. But the article is designed to trigger our base feelings of anger about paying for a road surface that's often in poor condition.

The car park argument is pretty silly too. Older multi-stories have greater problems from cars being wider, longer and taller than what they were designed for. But again, with the news of the multistorey car park collapsing in New York not that long ago, it's triggering fear, uncertainty and doubt amongst the reader.

Objectively, it's a really good example of how to write a manipulative 'news' story that preys on human emotion. That doesn't make it /true/ though.

Utter tosh.

The Telegraph (who funded this study) have a huge list of anti-EV articles, nearly all of which are technically incorrect and often self-contradictory. They clearly have an agenda and it's likely funded by the oil industry.

Bitwarden's great, and I use it myself. But for a company with groups, "secure" sharing and so on, it just doesn't compete on the features. But even so, LP's card is marked for us.

Agree totally. A great project that just works. Love it

My employer users Lastpass, a commercial solution. That hasn't been a good experience, with downtime, forced re-passwording and worst, having our details stolen from them.

Accusation that the Rebuilders provide nothing back to the community.

Actually, what Redhat are saying about rebuilders is that they "don't add value" - and that's for Redhat, NOT to the community which they patently do. That's quite a badly twisted misquote there, friend.

Also, Redhat didn't create open source software. They're a big player, sure, but I remember writing and releasing my code back in the 80s and 90s when it was called Freeware and Public Domain and distributed on cassette tape.

Y'know, I felt that way to begin with and it certainly took a long time for my fingers to adjust, but I've grown to adjust to that.

And it's better - you can do: "systemctl restart Service1 Service2 Service3" Before, with "system Service1 restart" you could only action on service at a time.

Plus, it's linux, so you can set up aliases to change the order into anything you like, even carry on using the old muscle memory formats. (Although I don't encourage this if you intend working on multiple servers!)