That moment when old #lkml mails of yourself appear on screen.

@hcf @dans_root @earthnewstech @monocles You don't get #SelfCustody of all the keys on their platforms, to the point that #ProtonMail bricks #LKML useage!
Please go to a #CryptoParty and learn abdolute fundamentals re: #Cryptography, #InfoSec, #OpSec & #ComSec.

That moment when old #lkml mails of yourself appear on screen.

""The #Linux rule for regressions is basically based on the philosophical question of "If a tree falls in the forest, and nobody is around to hear it, does it make a sound?".""
Linus wrote that today on #lkml while detesting the whole notion of "ABI changes": https://lore.kernel.org/all/CAHk-%3Dwga8Qu0-OSE9VZbviq9GuqwhPhLUXeAt-S7_9%[email protected]/
To quote more: ""Pretty much any change can be an ABI change - even totally new interfaces change behavior in that something that didn't use to do anything now does something.
[…]
So I absolutely detest the whole notion of "ABI changes". It's a meaningless concept, and I hate it with a passion, because it then results in the "opposite" situation where some projects seem to think that ABI changes are perfectly fine as long as they go along with version number changes.
[…]
So the only thing that matters is if something breaks user-*conscious* behavior.""
And when that happens, the distinction between "bug fix" and "new feature" and "ABI change" matters not one whit, and the change needs to be done differently.
Linus today on #LKML in reply to "A formal request for process clarifications" regarding the non-merge of the TSEM LSM – a Linus Security Module which provides a framework for generic security modeling:
""I already think we have too many of those pointless things. There's a fine line between diversity and "too much confusion because everybody thinks they know best". And the linux security modules passed that line years ago.
So my suggestion is to standardize on normal existing security models instead of thinking that you can do better by making yet another one. Or at least work with the existing people instead of trying to bypass them and ignoring what they tell you.
Yes, I know that security people always think they know best, and they all disagree with each other, which is why we already have tons of security modules. Ask ten people what model is the right one, and you get fifteen different answers.
I'm not in the least interested in becoming some kind of arbiter or voice of sanity in this.
Linus""
https://lore.kernel.org/all/CAHk-=whqz[email protected]/T/#u
@PinoBatch at least #IRC and #MailingLists have tools to #archive conversations and make them searchable, like #PiperMail for #eMail...
And that is a good thing: #Transparency can only work outside of #InformationBlackholes which non-portable & proprietary platforms are.
Now THAT looks like a tutorial I wanted to have: https://blog.gnoack.org/post/lei/
#publicinbox #lkml #plaintextemail #plaintext #email #gitsendemail
One thing that really pisses me off personally is the #regression in terms of #Messenger #Apps. My personal distaste and dislike for #proprietary, #SingleVendor & #SingleProvider #services like #Signal [¹](https://infosec.space/@kkarhan/114234551915193036) [²](https://infosec.space/@kkarhan/114935952643402592), #Telegram, #Discord [³](https://infosec.space/@kkarhan/114865723904157014) [⁴](https://social.treehouse.systems/@krutonium/115157611977216372), #WhatsApp [⁵](https://infosec.space/@kkarhan/114873895410403238), #Slack, #MicrosoftTeams, #discord [⁶](https://infosec.space/@kkarhan/116063760849048926)[⁷](https://infosec.space/@kkarhan/115736223551632209) etc. aside: - *WHY* is there no #CrossProvider #Messenger to handle that shite? - *WHY* does everyone of these shitty providers think people want to download their #bloated #WebApp that takes up triple digit Megabytes if not entire Gigabytes and will gobble up all the #RAM and #CPU each of them can?? This problem ain't new and *already got [solved for corporate social media](https://infosec.space/@kkarhan/114862619013462466) ages ago!* (Not to mention actually good messengers!) - And no, [bridges](https://toots.ch/@dalai/114862754556459439) *[don't](https://swecyb.com/@troed/114862774972645542) count*! - I mean `API 0` - [style](https://digipres.club/@foone/112685423773959519) access because obviously [none of the platforms](https://digipres.club/@foone/112685414638522984) will *allow, endorse or support such an endeavour* and [*actively fight the developers and users*](https://digipres.club/@foone/112685441496803574) ! So yeah, consider this a call for a @[email protected] / #Gajim or @[email protected] / #Pidgin *for garbage platforms!* - Cuz back in the day we had *way worse messengers* yet people actually made #AIM, #ICQ, #MSN, #QQ, #IRC & #XMPP work just fine from one single *"phat" client*! - Can we please get that back? Cuz #WastefulComputing pisses me off! #api0 #Enshittification
Every goto in the Linux kernel / Just another day on the linux-kernel mailing list: https://www.youtube.com/watch?v=v1Mfirg2-Z8
> Visualization of every goto statement in the Linux 6.17 source code.Commentary from a 2003 linux-kernel mailing list discussion about the use of goto. #lkml #data #music #visualisation