I've got a hypothesis that the enshittification era of AI is imminent.
Now I hear ya going "it's already slop, it can't be made more shit", which in mind is real is a real lack of imagination.
In order to produce anything using this stuff requires massive amounts of energy and hardware that have so far been fully subsidized by investor dollars, but I don't know how much longer that's going to last. Everyone's starting to get wise the fact that productivity doesn't increase as much as you would think, and so the actual ways to make money with this are going to be very limited, and so prices are going to have to rise and services are going to have to get worse in order to help these companies but you never made money get on after breaking even.
Drink em if you got em, but I think last call is imminent.
Now I hear ya going "it's already slop, it can't be made more shit", which in mind is real is a real lack of imagination.
In order to produce anything using this stuff requires massive amounts of energy and hardware that have so far been fully subsidized by investor dollars, but I don't know how much longer that's going to last. Everyone's starting to get wise the fact that productivity doesn't increase as much as you would think, and so the actual ways to make money with this are going to be very limited, and so prices are going to have to rise and services are going to have to get worse in order to help these companies but you never made money get on after breaking even.
Drink em if you got em, but I think last call is imminent.
No, I'm just a retard from the sticks. Whenever I announce completion of the project I'm working on, you'll see just how retarded I am.
You'll be like "Wait, you just spent all this time and effort to do *THIS*?
You'll be like "Wait, you just spent all this time and effort to do *THIS*?
To understand why I found openBSD annoying, you have to understand what I was using immediately beforehand.
I started on ubuntu, which is something that's familiar to me. All the tools are gnu tools I'm familar with, and it took a few tries to build a package with dependencies but it was ultimately completely doable. Not only can you chroot into a base distro install easily, with linux you're basically able to chroot into different distros which is quite useful. The qemu/binfmt method is amazing -- it lets you chroot into a different CPU architecture's distribution and operate as if you're running natively. It's possible to build an entire matrix of linux distributions and platforms without what is typically considered cross-compilation, and all from one command line.
Next I moved to Haiku. It also used standard gnu utils, gcc and gnu make, and the shell was bash. Package installation and creation with dependencies were both really straightforward. Honestly, working on Haiku even fully through the shell was enough to convince me it's a solid OS worth looking at. I didn't try chrooting. The options for APIs were nice, havng extensive bsd and linux shims for cross-compatibility, as well as native APIs such as the window APIs.
After that I was on FreeBSD. That particular BSD has a lot in common with linux, and it's quite forgiving to compile on, to install on, and FreeBSD really wants you to be building in chroot jails. There are 3 major versions active at any one time and you really want to build and package for each with integrated dependencies, I did exactly that and it went very smoothly. There were few to no surpises.
Next I was on OpenBSD, and I got pretty annoyed. It really doesn't want you using gnu utils, but I need them for what I'm doing so I felt like a second class citizen. The make you call is totally incompatible with gmake. The shell is a bsd shell incompatible with bash. You can chroot, but you can't really spin up an isolated OS for compilation and testing because of limits on the local commands. A lot of files are in unusual spots. Everything else I used so far was able to use non pie/pic libraries without problems but you couldn't even build them on openbsd. The packaging tool has command line options documented for adding dependencies but it doesn't look like you can actually do that without going through their ports system which relies heavily on bsd/make. Then when I finally decided to pull the pin and generate a package without deps, I couldn't open a file dialog box in firefox because it was locked down too much, so I had to install a file manager to drag and drop my updated file onto my nextcloud to get the file off the system.
So yeah, it's just really annoying trying to do what I was trying to do on OpenBSD. I moved to netBSD afterwards and it shares some quirks with OpenBSD I've thankfully already resolved, but even then it isn't nearly as locked down so for example I checked and at least in firefox I was able to open a dialog box with no drama.
But, as I said before, it's all for a reason. OpenBSD didn't make those choices to mess with some dummy from the sticks. They made them as part of their security minded design. For that reason I can find it super annoying, but I can also understand it. If I wanted a thing that would happily just do as it was told, I've got lots of options. But if I wanted something that would not have a root exploit in its base install for years and years, obviously I'm going to pick OpenBSD.
I started on ubuntu, which is something that's familiar to me. All the tools are gnu tools I'm familar with, and it took a few tries to build a package with dependencies but it was ultimately completely doable. Not only can you chroot into a base distro install easily, with linux you're basically able to chroot into different distros which is quite useful. The qemu/binfmt method is amazing -- it lets you chroot into a different CPU architecture's distribution and operate as if you're running natively. It's possible to build an entire matrix of linux distributions and platforms without what is typically considered cross-compilation, and all from one command line.
Next I moved to Haiku. It also used standard gnu utils, gcc and gnu make, and the shell was bash. Package installation and creation with dependencies were both really straightforward. Honestly, working on Haiku even fully through the shell was enough to convince me it's a solid OS worth looking at. I didn't try chrooting. The options for APIs were nice, havng extensive bsd and linux shims for cross-compatibility, as well as native APIs such as the window APIs.
After that I was on FreeBSD. That particular BSD has a lot in common with linux, and it's quite forgiving to compile on, to install on, and FreeBSD really wants you to be building in chroot jails. There are 3 major versions active at any one time and you really want to build and package for each with integrated dependencies, I did exactly that and it went very smoothly. There were few to no surpises.
Next I was on OpenBSD, and I got pretty annoyed. It really doesn't want you using gnu utils, but I need them for what I'm doing so I felt like a second class citizen. The make you call is totally incompatible with gmake. The shell is a bsd shell incompatible with bash. You can chroot, but you can't really spin up an isolated OS for compilation and testing because of limits on the local commands. A lot of files are in unusual spots. Everything else I used so far was able to use non pie/pic libraries without problems but you couldn't even build them on openbsd. The packaging tool has command line options documented for adding dependencies but it doesn't look like you can actually do that without going through their ports system which relies heavily on bsd/make. Then when I finally decided to pull the pin and generate a package without deps, I couldn't open a file dialog box in firefox because it was locked down too much, so I had to install a file manager to drag and drop my updated file onto my nextcloud to get the file off the system.
So yeah, it's just really annoying trying to do what I was trying to do on OpenBSD. I moved to netBSD afterwards and it shares some quirks with OpenBSD I've thankfully already resolved, but even then it isn't nearly as locked down so for example I checked and at least in firefox I was able to open a dialog box with no drama.
But, as I said before, it's all for a reason. OpenBSD didn't make those choices to mess with some dummy from the sticks. They made them as part of their security minded design. For that reason I can find it super annoying, but I can also understand it. If I wanted a thing that would happily just do as it was told, I've got lots of options. But if I wanted something that would not have a root exploit in its base install for years and years, obviously I'm going to pick OpenBSD.
It is my growing opinion that OpenBSD is really annoying.
It's supposed to be annoying, mind you. that's what makes it secure. That's why its logo is a puffer fish, but being annoying for a reason doesn't mean it's not annoying.
It's like, we all have that friend, right? They're super annoying, but you understand why so you tolerate it.
It's supposed to be annoying, mind you. that's what makes it secure. That's why its logo is a puffer fish, but being annoying for a reason doesn't mean it's not annoying.
It's like, we all have that friend, right? They're super annoying, but you understand why so you tolerate it.
Neither is correct.
440m underground is deep enough that you're well under the cold temperatures immediately underground, but not so deep it's painfully hot. It's probably a super stable temperature year round, and you could probably spend all day every day at 440m and the worst you'd have is it's pretty stuffy being surrounded by rock. Ventilation is key in something like that, because it'd be humid and without getting fresh air it gets stale and eventually could get quite dangerous as well.
440m underground is deep enough that you're well under the cold temperatures immediately underground, but not so deep it's painfully hot. It's probably a super stable temperature year round, and you could probably spend all day every day at 440m and the worst you'd have is it's pretty stuffy being surrounded by rock. Ventilation is key in something like that, because it'd be humid and without getting fresh air it gets stale and eventually could get quite dangerous as well.
Pretty impressive for a guy who had one joke one time and has stretched it into an entire career.
As part of an ongoing project I have been setting up various flavors of BSD.
Freebsd, openbsd, netbsd, and dragonfly bsd. Nothing particularly fancy, they are all just living in virtual machines.
Unix is Unix, but it's surprising how different each one is. Freebsd was The most straightforward so far, feeling the most familiar and straightforward. OpenBSD so far has been the most difficult to develop on because it has a lot of security features as mandatory that other OSes recommend set as default. Dragonfly has a lot of similarities with freebsd, but in trying to set it up feel like I was back in 1996, fumbling with manual config files only to have no keyboard or no mouse for reasons known only to God.
Another big difference between them is how they manage current versions of things. Freebsd maintains 3 different version lines going back several years, but openbsd is standardized on whatever the current version is.
Something that is constant between Linux distributions is the Linux kernel, so you can chroot between distributions which is convenient for compiling between distros, whereas BSDs are basically their own thing and each kernel is unique with a long individual genetic line.
Freebsd, openbsd, netbsd, and dragonfly bsd. Nothing particularly fancy, they are all just living in virtual machines.
Unix is Unix, but it's surprising how different each one is. Freebsd was The most straightforward so far, feeling the most familiar and straightforward. OpenBSD so far has been the most difficult to develop on because it has a lot of security features as mandatory that other OSes recommend set as default. Dragonfly has a lot of similarities with freebsd, but in trying to set it up feel like I was back in 1996, fumbling with manual config files only to have no keyboard or no mouse for reasons known only to God.
Another big difference between them is how they manage current versions of things. Freebsd maintains 3 different version lines going back several years, but openbsd is standardized on whatever the current version is.
Something that is constant between Linux distributions is the Linux kernel, so you can chroot between distributions which is convenient for compiling between distros, whereas BSDs are basically their own thing and each kernel is unique with a long individual genetic line.
You ever been about half way through something and started to be like "am I the first person on earth to have done this? There's no way the devs intended this to be the process for making this work!"
"Chronic deficits cause inflation that disproportionately hurt the poor and middle classes are required so the government can pay for:"
You know what's really really gay? Having a strong opinion about what 4 billion men do with their pee pee.
My next book talks about how Tate is essentially the feminized version of masculinity, and it was just takes a few steps further. We get it bro, you were raised by a single mom. Holy shit do we ever get it.
My next book talks about how Tate is essentially the feminized version of masculinity, and it was just takes a few steps further. We get it bro, you were raised by a single mom. Holy shit do we ever get it.
Part of me thinks there could be a really cool vampire story about two different people, one of them taking the opportunity of living forever to become a polymath, extending the positives of humanity well beyond the capacity of us single lifespan, and the other taking the opportunity of living forever to become the ultimate entitled loser, having seen the wealth of tamberlane or the khans and resenting that they don't have a slice of the pie that big.
It's a generic android set top box running on a p281 reference board, apparently using an s905x chip.
Normally you'd press a reset button with a paperclip or toothpick to get it to try to boot off the SD card, but I ended up writing the sd card dozens of times trying to get it going so I drilled the reset button hole and printed a little button (the blue thing sticking out of the side).
Two distributions generally work on these out of the box: CoreELECT which provides a basic experience with kodi, and armbian which provides Ubuntu or debian support.
Neither worked out of the box for me. The armbian distribution written by the armbian app had a lot of complexity but didn't work, and the coreelect didn't either. What I eventually found was ta LibreElec-Generic-S905-9.2.8.19.img file which didn't work out of the box but did hard lock on boot up (which was progress -- the two behaviors before that were either skipping SD booting altogether and loading the android update app or boot looping). I found out that on that one you have to pull the correct .dtb file and copy it to dtb.img on the root of the card, and that one worked, which was a big deal.
That dts file seems really critical. Arm isn't standardized so before you even load a kernel it describes the way stuff is laid out. Finding a working dts file ended up being a key to getting it to boot at all.
Shortly afterwards I found amlogix-s9xxx-armbian by ophub on GitHub, and it didn't work directly but I was able to get an image from that repo to write and then boot using the dts file I got from the libreElect distribution. It seems to support basically all the hardware, after I got everything set up using the ethernet port I was able to get it onto my house WiFi.
It all works, but the 1GB of memory, limited CPU, and the fact everything is running off an SD card means it doesn't feel very snappy. However, the fact that this tiny little box is now a functioning PC is very cool to me, and if I take the SD card out, it returns to being an android set top box.
Normally you'd press a reset button with a paperclip or toothpick to get it to try to boot off the SD card, but I ended up writing the sd card dozens of times trying to get it going so I drilled the reset button hole and printed a little button (the blue thing sticking out of the side).
Two distributions generally work on these out of the box: CoreELECT which provides a basic experience with kodi, and armbian which provides Ubuntu or debian support.
Neither worked out of the box for me. The armbian distribution written by the armbian app had a lot of complexity but didn't work, and the coreelect didn't either. What I eventually found was ta LibreElec-Generic-S905-9.2.8.19.img file which didn't work out of the box but did hard lock on boot up (which was progress -- the two behaviors before that were either skipping SD booting altogether and loading the android update app or boot looping). I found out that on that one you have to pull the correct .dtb file and copy it to dtb.img on the root of the card, and that one worked, which was a big deal.
That dts file seems really critical. Arm isn't standardized so before you even load a kernel it describes the way stuff is laid out. Finding a working dts file ended up being a key to getting it to boot at all.
Shortly afterwards I found amlogix-s9xxx-armbian by ophub on GitHub, and it didn't work directly but I was able to get an image from that repo to write and then boot using the dts file I got from the libreElect distribution. It seems to support basically all the hardware, after I got everything set up using the ethernet port I was able to get it onto my house WiFi.
It all works, but the 1GB of memory, limited CPU, and the fact everything is running off an SD card means it doesn't feel very snappy. However, the fact that this tiny little box is now a functioning PC is very cool to me, and if I take the SD card out, it returns to being an android set top box.
Successfully got this android set top box from 2018 running Ubuntu. Arm64 quad core and 1GB of memory but it's got two USB ports and lots of connectivity so it's a neat little thing to have running a desktop OS.
Once again watching so-called anti-fascists bend over and lick the boot with respect to mandatory age verification in their FOSS operating systems.
Every tiem
Every tiem
The oldest known banksy is from the 90s.
What else was banksy going to be but old? Time doesn't stop just because you're famous.
What else was banksy going to be but old? Time doesn't stop just because you're famous.
Every time I deal with arm linux, it reminds me of why every time I see threats to move away from x86 it gives me the chills in a bad way.
I could build a USB memory stick that would run on a particularly unusual Pentium 3 (since most Pentium 3s didn't have boot from USB) and would be fully capable of booting on every machine released since. Meanwhile, every memory stick that I create for arm needs to be so incredibly specific that just making bootable media is the single most difficult part.
It's kind of a shame because arm has some really cool features that would potentially make it really useful, but without the surrounding ecosystem it's just not a single thing.
I could build a USB memory stick that would run on a particularly unusual Pentium 3 (since most Pentium 3s didn't have boot from USB) and would be fully capable of booting on every machine released since. Meanwhile, every memory stick that I create for arm needs to be so incredibly specific that just making bootable media is the single most difficult part.
It's kind of a shame because arm has some really cool features that would potentially make it really useful, but without the surrounding ecosystem it's just not a single thing.