BDFL is the way. Whoever was there the longest should assume the crown and begin crushing this tranny whinging underfoot with expedience. I can't think of a single instance where a BDFL-owned system has gone tits up thanks to trannies. Slackware, OpenBSD and even fuckin' Kiwi Farms all operate under a BDFL, and all of them are doing just peachy. "Democracy" is never the way, remember that!
This blogger is a troon Gabriel "Gabriella" Gonzalez.who has a long history in the functional programming world. He announced his transition in a GitHub gist in 2021.
He is most active on Bluesky, and his posts are mostly tech-related, but also include a lot of gross fetish posting:
BDFL is the way. Whoever was there the longest should assume the crown and begin crushing this tranny whinging underfoot with expedience. I can't think of a single instance where a BDFL-owned system has gone tits up thanks to trannies. Slackware, OpenBSD and even fuckin' Kiwi Farms all operate under a BDFL, and all of them are doing just peachy. "Democracy" is never the way, remember that!
In other tranny news, I feel beset upon by a grim omen in regard to Libreboot. I think they've lost the plot. A couple days ago, I spotted a little something on their codeberg page:
# SPDX-License-Identifier: GPL-3.0-or-later
DL_hash="0a967d7baa7deea750da426a6e48113d8c8c7a32de0f5e8b0a610169e8c948b81e59003f5095ded75d904ccc30ac4f386ebf0d5d477336a0a167857c262473da" DL_url="https://archive.org/download/Topton-H30W-1264NP-4L5G-FW/BK12R415.rar" DL_url_bkup="[URL]https://archive.org/download/Topton-H30W-1264NP-4L5G-FW/BK12R415.rar[/URL]" # Original is hosted on sharepoint, needs some work to download directly from there # So for now we rely on archive.org :( # DL_url_bkup="[URL='https://x8sb8-my.sharepoint.com/personal/support_bkipc_com/_layouts/15/onedrive.aspx?ga=1&id=%2Fpersonal%2Fsupport%5Fbkipc%5Fcom%2FDocuments%2FProduct%2FFCBGA1264%2F1264NP%2D4L%2D5G%2FProduct%20Firmware%2FN150%2FBK12R415%2Erar&parent=%2Fpersonal%2Fsupport%5Fbkipc%5Fcom%2FDocuments%2FProduct%2FFCBGA1264%2F1264NP%2D4L%2D5G%2FProduct%20Firmware%2FN150']https://x8sb8-my.sharepoint.com/personal/support_bkipc_com/_layouts/15/onedrive.aspx?ga=1&id=/personal/support_bkipc_com/Documents/Product/FCBGA1264/1264NP-4L-5G/Product Firmware/N150/BK12R415.rar&parent=/personal/support_bkipc_com/Documents/Product/FCBGA1264/1264NP-4L-5G/Product Firmware/N150[/URL]" ME_bin_hash="3f4b67947c0902c9041043da063af89857fdd8d80bde1f2e294b64cf549c42a2bf94eb5fba3dab06cdb68e7fe2b4315d2ee88ae2f611e0f9552af9fea7d82be8"
# find_me will be skipped if this is y. # a custom extract function is used instead. XBMKmecleaner="y"
# on this board, we simply set the HAP bit # but we do not modify ME at all. this is because # me_cleaner currently has to way to validate # the result when neutering. simply setting # the HAP bit has the same result for users MEclean="n" # - however:
# we still use me_cleaner, merely to extract, in # such circumstances, otherwise lbmk vendor.sh # would be way more complex because we'd have # to resort to ifdtool instead. me_cleaner can # also extract a ME without modifying it
# for Fsp.fd, we don't rely on a download. Instead, # we copy from coreboot.git. The file is defined # by CONFIG_FSP_FD_PATH, split to CONFIG_FSP_M_FILE and CONFIG_FSP_S_FILE # and inserted to CBFS with names CONFIG_FSP_S_CBFS and CONFIG_FSP_M_CBFS # FSPFD_hash="69d945ea208912167af70774178366d2a56ba898ecc1864a4feda86fe96bbf55d408b2aaea2e3406c3f40772b603a9178139f5722015fb622e4e6274bd53ad52" FSPM_bin_hash="619f6f1478554b2fe958da37b1c51c5c9781565424acd48528bd333332b3de2ea728ff21e0048f77f2564c6e242d0382d659415bd16bc8405bd6f9fa7f17d9ac" FSPS_bin_hash="631cd96a912549fa4e792c1f8aefd26c35f98b1f9543958f24a1f87c92f0d91582b85f0b5d58f2651fe90cb526d5225bae2f4ab494745c3f586f7063abde096e"
Read that again. "On this board, we simply set the HAP bit but we do not modify the ME at all." That is a bad, bad sign. The HAP bit, for those of you who are not cripplingly schizophrenic, is an undocumented switch in the ME firmware that allegedly disables the entire Management Engine after hardware init, intended for use by three letter agencies and other secure applications (source). This might sound fine and dandy, but I simply do not trust it. Flipping the HAP bit still leaves the Management Engine intact, network stack and all, in an alleged "suspended" state. On boards up to and including Haswell & Skylake Era chipsets (ThinkPad W541 and T480 respectively), they've been using tools like me_cleaner to actually cut parts of the ME code out, most notably its network and host communication (HECI) stacks. Pivoting from this approach makes Libreboot no better than the "privacy" grifters a la NovaCustom or Purism who claim to ship modern disabled MEs, but just flip the HAP switch and call it a day. Knowing the sort of exploits the ME has been stricken with, I cannot in good conscience use such machines. Not only is it not Libre, it is basically nothing at all. This just makes Libreboot a Coreboot skin.
But, you may ask, why the mucho texto schizo sperging now of all times? Because within the last 24hrs, Franky boy posted this on his mastodon:
i have some massive improvements planned after i get my current batch of minifree orders done this week.
big changes planned for lbmk. big release planned for december 5th!
the changes will be so dizzying.
agenda:
* chromebooks. lots of them.
* more kabylake thinkpads
* alderlake (and possibly newer)
* tianocore and linux payloads
* more
Alder Lake chipsets run a newer version of the Management Engine (v12). As of the latest Libreboot release, they can mangle the ME on everything up to and including MEv11 through a known RCE exploit that lets you bypass boot guard. As far as I am aware, no such exploit exists for MEv12. I see two lanes that can be walked here, either
A) They have found a way to crack Boot Guard on MEv12+ B) They jewed out and are joining the HAP bit grift
That codeberg commit is not giving me confidence towards road #1. This reeks of the same sort of decision making that led to Libreboot's current "binary blob reduction policy" so they can sell newer hardware, granted with the ME chopped up and left dysfunctional, but with a lot more cruft left on-board. My gut tells me this is no different. Looks like the ol' W541 + T480 tag team's here to stay after all. Here's to another 10 years!
This reeks of the same sort of decision making that led to Libreboot's current "binary blob reduction policy" so they can sell newer hardware, granted with the ME chopped up and left dysfunctional, but with a lot more cruft left on-board.
well this is just naturally what happens when you stray from the teachings of St. iGNUcius and away from the light of the One True Editor
proprietary: not even once
Alder Lake chipsets run a newer version of the Management Engine (v12). As of the latest Libreboot release, they can mangle the ME on everything up to and including MEv11 through a known RCE exploit that lets you bypass boot guard. As far as I am aware, no such exploit exists for MEv12. I see two lanes that can be walked here, either
A) They have found a way to crack Boot Guard on MEv12+ B) They jewed out and are joining the HAP bit grift
That codeberg commit is not giving me confidence towards road #1. This reeks of the same sort of decision making that led to Libreboot's current "binary blob reduction policy" so they can sell newer hardware, granted with the ME chopped up and left dysfunctional, but with a lot more cruft left on-board. My gut tells me this is no different. Looks like the ol' W541 + T480 tag team's here to stay after all. Here's to another 10 years!
I plan to look as much into these people as I can. I probably will dive a bit deeper into this situation. Right now I'm working on the second part to the nix thing. I plan to finish that tonight. Then I will see if I can move onto the current nix bullshit.
I really want at the very least make a clear list of who these people are. Make it loud and clear these people are going into these communities and subverting them (idk I always want to say co-opt not sure what the right term here is). Trying to do the classic thing they did with intersectional politics, they just spread it like a virus into everything. I personally want to see this bullshit squashed. Stomped you could say. It's gone further than it ever should have.
And I hope others will do the same.
edit: made it through, uploading videos, and editing the draft now.
edit 2: bro wtf. I was editing and went down to check the video progress the first 2 were done but said "a server error occurred please try again later, I waited for the next one, same thing. I refreshed, and I guess I'll try again. GAY AF.
edit 3: same thing. idk if null broke his gay webiste again or what. But every one of these is failing after it gets uploaded. I rendered them all in mp4 like I did last time. as far as I know there is no reason on my end why this should be happening.
I plan to look as much into these people as I can. I probably will dive a bit deeper into this situation. Right now I'm working on the second part to the nix thing. I plan to finish that tonight. Then I will see if I can move onto the current nix bullshit.
I really want at the very least make a clear list of who these people are. Make it loud and clear these people are going into these communities and subverting them (idk I always want to say co-opt not sure what the right term here is). Trying to do the classic thing they did with intersectional politics, they just spread it like a virus into everything. I personally want to see this bullshit squashed. Stomped you could say. It's gone further than it ever should have.
That can work. I think I would rather put them to the site. If the problem isn't solved tomorrow. I can temporarily upload them there. Since it looks like it will expire within 90 days (or less) on that.