bystander: hey, there are flames pooring out of the windows on your house

home owner: well if you expect me to do anything about it, you'll need to lodge a formal request for me to look into it

Wrong analogy, methinks.

By the way, I have had good experience with that bug tracker: a problem I reported was fixed after 1.5 years or so.

if you give that page a read, you can see that the project has serious resource and governance problems. to the point where i'm questioning if the operating system is even safe to run anymore

Tinhead bot seems to have lost it's marbles in #freebsd-bugs

i love freebsd and have used it for decades, but if the project cannot address or at least respond to these issues, i'll have to seriously consider moving to a more mature/supported os like debian

mjp, if it is your won article -- great. You could initiate a productive discussion of it on the mailing lists, more suitable to lengthy discourse than IRC. (my personal opinion)

mjp, there are other BSDs, as well.

i'm a user/sysadmin with a full time job and a family, i don't have time to contribure to the project

talking a high and mighty game about governance issues makes you sound like a strasserite

i think if the project is not able or willing to take security seriously, state it and make everyone aware, don't pretend otherwise

mjp, reporting a problem is a tiny fraction of effort of having it fixed.

i dont think anyone would disagree with that

you might be right, but you are at this juncture a disruptive presence

i dont see the project even acknowledging long standing problems, let alone having a plan to address them

wake up calls usually are disruptive

that is the point?

linking master→main under «political commits» really does stand you out as a fascist. please just leave.

bystander: hey, there are flames pooring out of the windows on your house. home owner: you are at this juncture a disruptive presence

ok

analogy incorrect

if you're going to switch to a different OS because of this - switch

it's that simple. if you don't want to visit the house you think is burning, don't visit the house

building stuff as root doesn't seem great

i will probably apply some of their recommendations, at least

i like the house, i have lived here for decades, i dont want to leave

mjp: Then the solution is to constructively contribute. End of story.

i also have a landlord advising me "well if you dont like burning to death, just leave!"

i don't think if fair to blame users of the OS for not fixing its shortcomings, its perfectly valid to just be a user and not contribute

mjp, no contribution -- no complaint.

is that an offical rule of the freebsd project?

i also like it, i can't yet evaluate the difficulty of each proposed change here but running any WAN-facing freebsd i probably should put it on to-do...

or some BOFH quip from the 90s?

mjp, I think it is common sense. And of course, reporting bugs in the tracker counts as a contribution.

do we have literally an moderator on deck right now

i will agree some of the listed things are not really "bugs" per se

if you read the article. many problems have been reported to the project, and ignored? how would creating a bug report for an ignore bug report help?

like, if you have configured swap not to be encrypted, and it's not encrypted, that is correct behavior for the setting

also you have included your X account name at the top of this page of yours. in 2026. that puts you in the lunduke set

i'm not attacking the people or the project, but I think an honest conversation and response is warranted

encrypted swap is what i would consider one of the lesser problems raised here

mjp, a bug report /will/ help, because it will stay open and sore the eyes of the developers.

(this is a recommendation i will probably take)

yeah, was first example, not necessarily most important. i just mean reporting as bugs seems wrong for some of them, so I wouldn't know where it would be considered constructive to raise the issue etc etc

i don't see how making developers have even more sore eyes than they already do would help them when they are already overwhelmed and overworked

now i'm a bit confused, what are you advocating if not for the issues to be fixed?

mewt, report /any/ problem to the bug tracker. Mine was not a bug, either: <bugs.freebsd.org/bugzilla/show_bug.cgi?id=280941> .

interesting, ok

mewt: basically telling us to stop using freeBSD while advertising his (he's a he. i just know it. no woman writes a web like that and is also openly christian.) website with linux hardening tips to us.

hmm

most of the article touches on more than "bugs" suitable for reporting in a tracker, they touch on the stated priorities and goals of the project vs actual reality on the ground, it needs high level evaluation and intevention

LXGHTNXNG: if you are talking about me, you are making some very bad assumptions and are not good at trying to doxx people

I'm not interested in doxing you.

I don't even use X btw, so not sure who's X acct you are talking about?

We're assuming that you wrote the article because you passed it us without any indication that you got it from somewhere else.

the author is not mjp i don't think, the author is a name i've seen around as an arch maintainer before

blakkheim iirc

yes

for some reason there's some negative emotional valence stored against tha name in my memory banks but I can't know what it is

okay. mjp you're forgiven, but all of my comments apply to blakkheim

consider the source before you send things

that's all I will say.

i think my comments on the Xitter profile are off topic, i do find it a bit off-putting. i'm willing to entertain the recommendations given anyways

LXGHTNXNG: you (no one else, not 'we') made wrong assumptions. I have not done anything wrong, i dont need your forgiveness. maybe ease up on the ad hominems though?

unforgiven then. and ignored

mjp, try the mailing lists with those higher-level concerns.

I just realised today that the article was first published over 3 years ago

I doubt lots all of the problems mentioned in it are fixed now.

Oh, hm. blakkheim used to be a regular in here, and was a FreeBSD person, but it was years ago. Anyway, most of the things in that article can be taken as hints for how to configure things. I think there are things in there worthy of being formal bugs, but it'll take some research. Not everything he says there is valid.

IIRC, he was, among other things, the first audio engineer for BSD Now.