paigeadelethompson · April 15, 2025 23:46
diff --git a/gistfile1.txt b/gistfile1.txt
 I would like to understand a few things:

    What actually precipitated this?
    Why did it take so long for the problem to be addressed?
    What will be done (if anything) to avoid making such an impactful mistake again?

 Among the things that I've been letting slide that I would like to understand are:

    Who are the people who actually have write access to this repository; what actually endorses their trustworthiness and sets them apart from for example a state sponsored actor who's intention is to distribute malware? To be perfectly fair, I've made pull requests myself but who I am is pretty up front and I've been nothing short of generous in making available a means to reach me for professional inquiries. I don't really see that in the accounts that actually maintain Void. I suppose I'd just take somebody at their word that there's some level of discretion but who's word would that be? Who is actually willing to endorse this?

    I've been exceptionally polite all things considered but I feel like most if not all of my inquiries have just been met with passive aggression. If I'm being honest with you the only reason that Void matters to me at all is because a friend of mine likes it, and it just makes things easier if I can use it for projects that we collaborate on (I'm personally satisfied with SystemD/Debian and could really care less what libc I'm using especially if having a preference just makes things more complicated which it does.) As a matter of fact, I don't even like Linux, my preference is to FreeBSD. I like that there are some similarities here, with Void particularly in the package management system but in FreeBSD there is a very clear distinction between base and ports. I can practically guarantee you that you will not commit anything to base if nobody knows who you are.

 But anyway yeah just close the ticket and pretend like nothing happened like you usually do
	I would like to understand a few things:

	What actually precipitated this?
	Why did it take so long for the problem to be addressed?
	What will be done (if anything) to avoid making such an impactful mistake again?

	Among the things that I've been letting slide that I would like to understand are:

	Who are the people who actually have write access to this repository; what actually endorses their trustworthiness and sets them apart from for example a state sponsored actor who's intention is to distribute malware? To be perfectly fair, I've made pull requests myself but who I am is pretty up front and I've been nothing short of generous in making available a means to reach me for professional inquiries. I don't really see that in the accounts that actually maintain Void. I suppose I'd just take somebody at their word that there's some level of discretion but who's word would that be? Who is actually willing to endorse this?

	I've been exceptionally polite all things considered but I feel like most if not all of my inquiries have just been met with passive aggression. If I'm being honest with you the only reason that Void matters to me at all is because a friend of mine likes it, and it just makes things easier if I can use it for projects that we collaborate on (I'm personally satisfied with SystemD/Debian and could really care less what libc I'm using especially if having a preference just makes things more complicated which it does.) As a matter of fact, I don't even like Linux, my preference is to FreeBSD. I like that there are some similarities here, with Void particularly in the package management system but in FreeBSD there is a very clear distinction between base and ports. I can practically guarantee you that you will not commit anything to base if nobody knows who you are.

	But anyway yeah just close the ticket and pretend like nothing happened like you usually do