@ajsadauskas @JessTheUnstill also #BlackBerry's #PlayBook #Tablet was released as a accessory screen for their Phones, which gave it "#WiiU-Effect" in terms of marketing.

• Plus #RIM relying hard on business clients and their proprietary applianced mail systems and having big carriers upsell to business people made them look outdated & quite literally out of touch once #iPhone went mainstream.

I mean, the hardware was never their problem and #SMS-Typists swear by their #BlackberryCurve's #keyboard but BlackBerry's #toolchain - just like #SymbianOS's - was just hideous to the point that devs like @fuchsiii didn't even want to try making #Apps for those devices.

• Unlike #Mozilla fucking up #FirefoxOS by refusing to sell devices to #developers, by the time RIM & #Nokia came from their high horses, their market shares had been squeezed into mere "rounding errors" by #iOS and #Android as it was way cheaper and easier to get #Apps developed, tested, sold, bought and use them than on their devices.

#Sony even released some #Symbian #S60 devices but since they didn't have the same signing keys, one couldn't even #sideload apps (not to mention they didn't had the #OviStore on those either!)...

@ryanc add the file used to store it into .gitignore is propably not an option?

Maybe you can setup a build script that merges that secrets.list into a final build file and exclude that as well?

I mean, I did such seperation and build scripting in some cases a while ago...

@dalias personally I think that #Linux #Kernel needs to prioritize what it wants.

#AFAICT Linux always prioritized clean, lean & human-readable #C code over features, efficiency and sometimes even security.

#Rust being turned into an integral part would extremely complicate the #build process and add a shitload of #dependencies to build @OS1337 or any other #minimal / #embedded OS that it would be a net negative by just making the whole #toolchain bigger, bulkier, more complex and convoluted.

@BrodieOnLinux @that_leaflet @AuntyRed
@SecureOwl if this ain't some #StateSponsored #SupplyChainAttack it was at least so methodical that it's definitely some sort of specific attack against a specific target...

I mean, I've seen weird #3Dchess in #ITsec so I'd not be surprised if this was just some #1337hax0r wanting to take revenge on an employer/client who still owed them pay...

I mean, that whole #xz #backdoor has serious #nocom vibes:

https://www.youtube.com/watch?v=elqAh3GWRpA&t=79s

#TLDW: people literally gaslit an admin with specific packet flooding into filing a specific bug report so a specific fix would be implemented that would get a #backdoor implemented in #Spigot, a popular #Minecraft #Server #Toolchain...

@joepie91 Don't forget:
- #Mumble for #VoiceChats

- #Linphone as #SIP / #VoIP client

- #gparted and #ddrescue as well as #testdik & #photorec for halding storage and recovering data.

And ofc all the tools I need daily like #SSH (#OpenSSH), #OpenVPN, #WireGuard, #IPsec, #pfSense, #OPNsense, #ipFire, #LUKS/ #dmcrypt and the whole #toolchain needed for OS/1337 like #gcc, #musl, #toybox, #dropbear and so on.

#OS1337
https://os1337.com

Noch weiter gedacht: wenn das Buch fertig ist, landet es per weiterem Knopfdruck im #AutorinnenBuchShop
...und 5 Tage später beim lokalen Buchdrucker ( gibts das bzw. macht das Sinn? Was #BoD zentral kann, kann vielleicht auch mein lokaler Copyshop dezentral? ).

Bei mir sind das nur Ideen - aber wahrscheinlich machen das andere schon so oder ähnlich? #leanPublishing #autorenleben

Oder haben schon gelernt, dass das so doch nicht geht?

#JoachimKreativWeg #kreativeWertschöpfung #toolchain
2/2