#antiai

47 posts · Last used 4d

Hot on the heels of the recent 100% failures to install #Haiku in either QEMU VM or lappy SSD [https://infosec.space/@MsDropbear42/117335082820301999 https://infosec.space/@MsDropbear42/117333664504154227] today i am simply "delighted" to report a new round of 100% failures... this time with #GhostBSD. After hours of research last night, including watching a few extremely positive videos of the installation & desktop usage UX, i enthusiastically looked forward keenly to trying it out myself, initially at least in a VM. Downloading the ISO took so many hours that i had to go to bed & hope it would complete ok; returning to pooter this morn showed it did. It then passed the sha256sum check fine. I prepared a #QEMU VM for it, with 4GB RAM & 2 cores, & set it for UEFI bootit booted to the initial menu, where i let it time-out into booting the default multi-user optionit showed several lines of text, then went to a pretty GhostBSD splash screenit showed the splash screenit showed the splash screenit showed the splash screenit showed the splash screenit showed the splash screenit showed the splash screenit showed the splash screenit showed the splash screeni aborted itmy research had indicated GhostBSD was supposed to be able to boot with either UEFI or BIOS, but as a check, i created a second VM for the ISO, this time with BIOS-boot, & foolishly i blindly accepted all the other default QEMU settingsthis booted with a conspicuously ugly low-resolution screen compared to before, but after the multi-user option initiated, didn't bother with any splash screen, instead a scrolling text wall showing it was loading the ISO into memory... which then summarily failed with an out of memory error & an indignant message it needed min 4GB. that's on me, the default QEMU was only 1GB, d'ohi edited the VM config to give it 6GB, & retriedit got much further this time, but ended in another failure, this time iirc a seg-fault... FFS! i returned to the first VM, increased its RAM also to 6GB, & tried againsplash screensplash screensplash screensplash screenirritated, i began drafting this whinge-posteventually i discovered the VM had emerged from the splash screen, into a wall of text as per pic, ending in another failure... a seg-faulti am really annoyed at this bullshit. Haiku at least has an excuse, being only beta, but wtaf here, Ghost? Is my only bloody option now to escape the invasion of the slopbots in #linux, for me to dig out my abacus or slide-rule? Pretty pissed off atm. #DropbearPooterising #Linux #LinuxWomen #FOSS #FuckGenerativeAI #FuckSlopbots #AntiAI #NoAI
2
2
2
1
Here is the other thing, a lot of #FLOSS projects are taking in a lot of #LLM generated code now in the grey-limbo of no policy. AND the longer projects take to ban it, the less likely they are to ever ban it. "No policy" means tacit acceptance is the status quo for a lot of projects. The time for #KDE to ban LLM generated code has kind of passed. I just don't believe it's possible for them. Their unlikely to reverse commits like this. https://www.phoronix.com/news/AMD-More-HDR-KWin-Claude-Code AND even if banning it, didn't require reversing prior commits like that; the tacit acceptance of this kind of code, while there is no policy serves to normalize LLM generated code in the project over time. If you need your DE to be llm-code free; time to move on from KDE. #antiAI #noAI
5
4
2
0
Replying to
@thesupertechie@lgbtqia.space prolly depends on what you actually mean here. afaict all linux distros are now tainted by definition, given linus has allowed slopbottery in the kernels... so even if there is some unicorn distro that has vowed no slopbottery [eg, gentoo, elementary], they already begin behind the eightball via the kernels. however, then consider the impact on downstream distros by the choices made of their upstreams. take elementaryOS... aren't they downstream of debian via ubuntu? if so / as such, how do they avoid being enslopified, despite their own fine ethical policy? afaict, those of us vehemently against the scourge of gen-ai are fast losing this struggle, alas #DropbearPooterising #Linux #LinuxWomen #FOSS #FuckGenerativeAI #FuckSlopbots #AntiAI #NoAI
2
1
1
0
Recent noailist.org updates, list of projects reaches 200 The list of projects has reached 200! …with some categories such as Games, Operating Systems, and Social Networking with several additions. The website also reached over 5000 visitors! Two new categories for Education and Bands or Musicians were added. Projects can now use the Badge on the Badge page: https://noailist.org/badge/ The Why No AI page has been updated significantly with recent updates. The How to Help page was added with instructions on how you can help the project. Do you have a Public No-AI statement? Be sure to Add Your Project Want to help? Share this news update elsewhere.
0
2
0
0
Sending good vibes to everyone in the Debian community navigating the recent transitions. If you're using this moment to do a little distro-hopping, consider jumping over to the BSD side. NetBSD offers a completely independent codebase built on a classic, predictable philosophy. You might just find your new permanent home! 🚩💻 #NetBSD #Debian #FOSS #noai #TechCommunity #antiai
0
8
0
0
AI nonsense, rant
0
4
0
0
Replying to
@AeonCypher@lgbtqia.space I thing that calling people #AntiAI in the first place is already making a wrong statement, like calling people #Woke or #AntiFa, they are just people fighting as they can against the new #eldorado built upon theft, monopoly, immorality, gigantic water and electricity waste and direct climate change effects. Yes, it's a wonderful technology. Yes, it can help people do things. Being against the very idea of #AI only means that we don't want to be a part of it, it's a legit choice.
1
2
0
0