@theorytoe The answer is that there's this simple and nice make(1), and then people complicate it, and that introduces portability problems, and then and then people shout at you that your Makefile doesn't work on VMS, and then a one-liner gets bloated into 30 lines of horseshit. The xz vulnerability is more like an autotools vulnerability: shit can sneak right in there because no one even wants to *look* at configure.ac or anything in the m4/ directory. So they think they can have something simpler and easier to manage if they abandon the ball of mud and start over with a new system for expressing a dependency tree, not realizing that when the portability cult arrives, they will have you compiling a million test programs to find out how big uint64_t and int32_t are, because if you put portability checks around types added for portability, you get double the portability. When looking at the code to see exactly what this unholy build system was called, the first thing I saw, near the top of their configure script (which is a bare shim that just invokes other build scripts) was that they override $JOBS, because even if you have taken care to set $JOBS to a number that makes sense on your machine, attempting to execute jobs in parallel triggers Python threading bugs on AIX. I haven't ever even logged into an AIX system and I don't think I know anyone that uses it, so I definitely don't want the build to slow to a crawl for that.
Portability is really nice, but this portability cult formed, and they try to turn the act of hacking on cool shit into a bureaucratic phantasmagoria, and then once those people reach critical mass, it's all "THAT FILE HAS A BASH-ISM IN IT" and "THAT'S UNDEFINED BEHAVIOR PER C11 AND THE DSM-V" and then people fuck off to elsewhere. In the mean time, there are people that throw a fit if your code wouldn't work on 1's complement systems that use EBCDIC instead of ASCII, and they end up producing code that isn't even backwards-compatible with itself, so you try to update a piece of software and there's an entire Gordian knot of dependencies to rebuild because library $x v1.1.0.2 is not compatible with $x v1.1.0.1. Unix people used to be able to joke that Windows users had to reformat and reinstall every month; that joke hits a little too close to home nowadays, when all of this complete shit code goes out of its way to be theoretically compatible with a system that runs Xenix, but is not compatible with a system from a year ago.
Somewhat related, I recently read some commentary :dmr: had about the fan-fiction that X3J11 tries to pass off as a standardization effort, and it seems pretty clear why most of the post-ANSI extensions were completely ignored by the authors of the C programming language:
> The fundamental problem is that it is not possible to write real programs using the X3J11 definition of C. The committee has created an unreal language that no one can or will actually use.
You see this same pattern repeat over and over again: process wonks and "best practices" fascists come in and make a tower of incomprehensible and self-contradictory rules and the effect is to kick people out of the language/ecosystem/OS so that they can be petty bureaucrats and issue memoranda to a depopulated nation as the lords of the tumbleweeds.
> Is that the dev board Level1Tech had on his channel?
I don't know who he is. This is a DevTerm with their R-01 board, an Allwinner D1 RISC-V SOC, single-core, 1GB RAM. ( https://www.clockworkpi.com/devterm The RISC-V chip is not just their cheapest option, I can also legitimately say that I use a cyberdeck with an experimental CPU. Plus it runs cooler with no heatsink than the ARM cores run with the fan blasting, lasts at least 8 hours on battery.) I have produced a Slackware image for it, that's what's running there. ( https://media.freespeechextremist.com/rvl/full/17b30212e33512e8aa6e861a4adb9744b4a70a7b2d6febab72df4b0816f2f0e8 )
Except that I haven't attempted to run a browser on it (besides w3m), it's speedy enough, though most of what I use it for is drawterm to talk to Plan 9 and ssh to talk to Linux and run xpdf (shoved a 128GB uSD onto it), awk-based wiki for note-taking, etc. Like, everything I use compiles and runs fast enough on it because most of the stuff I use was already fast in the 90s. irb takes a few seconds to give me a prompt, that's the only real annoyance, but I already use awk or dc for the 90% case.
> Ampere has some reasonably priced 128 core ARM kits:
$4500 is probably reasonably priced for 128 cores and 96GB of RAM but it's still a little pricier than building out a cluster. A Turing Pi 2 has four slots, 16 of their RK1s would be 128 cores, the 8GB model you'd end up with more total RAM and for four boards and eight chips, it'd run you 4*$200+16*$150=$3200 and you end up with more total RAM. (The 32GB RAM ones are $300, so for 512GB total you'd have to shell out $5600.) That's up-front, though: building it out piecemeal is an option if it's a cluster. you_can_see_a_lot_of_dust_and_beard_hair_if_you_zoom_in.jpg
> I'm sure there are better options to view/ filter your own timeline, but this very much site aesthetics.
It's not an aesthetic choice, it's UX for people that land on the page for the first time. I don't give a damn about normie-UX but have been in the industry long enough.
> People srr not sure what instances exists, what they are about, and don't want to memorize/ make 10 different accounts.
Sure. I'm not the right person to ask about mass adoption.
> none of the admins are actually pushing for monetizing the platform
Not relevant; he says he's trying to push mass adoption, and if that really is the case, he's doing it wrong. What the admins are doing is the admins' business.
> From a functional, user standpoint, I think soapbox is probably the most user friendly.
It's dogshit on a paper plate as far as I can tell, but that's Gleason's business, not mine.
> no one is actually making an effort to do so as far as I can tell.
This is not a place where people are likely to make any money. Some of the commie instances have whales because they are appealing to the upper-middle class and take "donations" but anyone else is in the red. FSE has never taken donations, it's all out of pocket. (I think the closest that happened was graf sent me a couple of PSUs but I paid him back a week later.)
Anyway, my thoughts on Soapbox are my thoughts: I'm not a user nor a contributor nor a fan and won't be in any of those categories in the future, so I don't want to spend time discussing it. I'm writing code.
@Aspergtame@MK2boogaloo@Tony Fucks up threads, fucks up notifications, fucks up URLs, basically a copy of Twitter but slow as shit. If you have suggestions for improving it, feel free to contact the developer; my point is I can't use it.
The first thing was the login-wall. Gleason claims to be after mass-adoption but nobody creates an account just to find out what's going on: they need a reason to sign up. Most people don't know what fedi is or how it works, so the way Pleroma works out of the box is good: it just shows people the timeline. It works for Poast because people know who graf is, but you get very few people that see it and just sign up. Last time I saw him discuss this, he said "Oh, you just put /timelines/fediverse at the end of the URL" but nobody's gonna know to do that and even if you make it a link, that's a click. I used to suggest these things to him before I concluded that he is useless to talk to, but he ignores things like that.
@Tony@MK2boogaloo Ha, I'm actually using bloat except I used the PleromaFE to make an announcement and drop some of the spambots those kids were running from their Discord server. But yeah, I can't into Soapbox FE. It fucks up notifications and fucks up threads and is basically Twitter but slow as a motherfucker. pretty_much_a_1:1_copy_of_twitter.png
@Tony@MK2boogaloo Well, bae.st works for now, and people know where to find it. I appreciate the offer, it's nice to be welcome to crash on people's couches. I want to get FSE rolling as quickly as possible though so I am slanging code right now.