@grahamperrin said:

For what it's worth, I think: don't delete it from BSD Cafe Billboard. It's good to raise awareness of the reputation.

I hadn't thought of it that way. Interesting!

The subject line here does match the title of the linked article. This is good practice, good netiquette

The downvote (from me) is because the value of the article is disupted; you could not have known this when you shared it. It's a downvote for the article, not for you personally

For what it's worth, I think: don't delete it from BSD Cafe Billboard. It's good to raise awareness of the reputation.

The recent Hacker News story that unearthed the article gained very few votes.

@grahamperrin said:

a gentle hint: in the absence of quotation marks, casual readers who don't follow links might wrongly imagine that the words above are yours.

Thank for the remark!
In fact, as you’ve realised, they’re not mine, but the author’s; I’ve tweaked the first post slightly.

@ciotbsd a gentle hint: in the absence of quotation marks, casual readers who don't follow links might wrongly imagine that the words above are yours.

From the Senior Director of Technology at the FreeBSD Foundation in August 2022:

This link gets shared around every now and then, and my response is always the same: there is some useful insight, but there's also information that's so outdated it provides no value, outright misinformation, and self-contradiction. Some of the technical points are fair, and should be and are being addressed. But the commentary is often laughably wrong. The document seems more focused on advancing an agenda than a good-faith effort at improving security in FreeBSD.

• emphases: mine
• https://lobste.rs/s/2xxp8y/freebsd_lesson_poor_defaults#c_mhsghw