@p@bae.st
@p@bae.st avatar

p

@p@bae.st

I regret to inform you that I have no interest in selling Metal Gear. As I said, I came to take it back.

:fse: FSE is coming back as Revolver. :revolvertan: No admins, no masters. :ocelot:

This profile is from a federated server and may be incomplete. Browse more on the original instance.

p, to random
@p@bae.st avatar

:hacker_f::hacker_s::hacker_e:

New box is on the rack at the datacenter. Updates to follow soon.

p,
@p@bae.st avatar

@MK2boogaloo How would I get a list of those people? I don't know everyone's alts, especially not off the top of my head.

tootbrute, to random
@tootbrute@fedi.arkadi.one avatar

ugh. $260 CAD for a 10 year passport. this citizen thing is a racket.

p,
@p@bae.st avatar

@Ailunarenth @pwm @gabriel @tootbrute

> just as dystopian as the United Kingdom.

Seems that way to me. There's a lot of stuff they're pushing through up there that I can't account for unless they are immanentizing the eschaton.
eschatron_9000.jpg

lanodan, to random
@lanodan@queer.hacktivis.me avatar

Love how fedi calls cats dogs and vice versa, perfect for trolling an eventual AI training.

p,
@p@bae.st avatar

@lanodan One of my favorite parts of that decentralized moderation paper was their attempt at classifying "toxicity" on fedi by feeding TWKN to Google Perspective, which gave neckbeard.xyz the lowest score for the "Sexually Explicit" rank. Fugging the loli waifu: 0% lewd.

p, to random
@p@bae.st avatar

It really bugs me how often ntpd produces slightly out of sync clocks by trying to be overly clever with skew and with trying to not break software that relies on a monotonically increasing clock. If something breaks when the clock fails to increase monotonically, it's shit, I don't care if it crashes. I'd rather it crash so that I know to uninstall it.

So, I tried to do it "right" this time, but I am going with the strategy that works: run ntpdate pool.ntp.org after the net comes up and then periodically run it again from a cronjob. ntpd(1) has some warnings about how if you do it that way, you don't get the cool skew detection, and it should be the opposite

In other news, cargo is a total piece of shit and this should come as no surprise to me because Rust is a language made by children that have no idea what they're doing but every time I have to interact with software written in Rust, the compiler and the tooling find new ways to disappoint me. I should just get a bunch of RISC-V gear so Rust shit won't run and I don't run into problems like this.
boxesallinarow.png

p,
@p@bae.st avatar

@istvan I write Go so immunity to Go is a downside for me.

p,
@p@bae.st avatar

@threat Bring it. I have wanted to punch Klabnik in the dick for at least 15 years.

p,
@p@bae.st avatar

@allison @istvan Yeah, ARM can hop endianness, but I think it's the only one, PowerPC is all BE. (I am going from memory, this may be lies.)

p,
@p@bae.st avatar

@istvan @allison Oh, holy shit. I remember that kernel option to swap the framebuffer's endianness, I bet it was for avoiding running the whole box with the endianness swapped.

p,
@p@bae.st avatar

@lanodan @syzygy Holy shit, I never used it but it looks like it behaves exactly the way I wish ntpd would behave.

Meanwhile, ntpd is...I don't know what it's doing, it appears to be making drift worse:
meanwhile_ntpd.png

p,
@p@bae.st avatar

@lanodan @syzygy

> I think by default chrony sets the clock at launch and then drifts.

Yep, this is what the docs indicate, this is exactly the behavior I want (and apparently they use the ethernet hardware timestamps). ntpd tries to guess at and anticipate drift and then jump to the target time in 250ms increments. As far as I can tell, it has never done that correctly, or those clocks would get closer together rather than one of them speeding up and one slowing down.

> it adjusts by steps of 0.1 seconds unless it's bigger than 3 seconds.

Yeah, reasonable.

p, to random
@p@bae.st avatar

@bot Here is your attention. I am paying attention to you.

Will that last you another year?
what_fresh_hell_is_this.png

p,
@p@bae.st avatar

@e3ea Persistent lunatic that has caused a lot of problems, stuff that's way over the line: cover fire for CP, never more than one degree removed from the swat/dox incidents. Persistent problem even before she turned into a direct liability.

p, to random
@p@bae.st avatar

Apparently, WAF is even more fucking stupid than autotools.
yes,_sizeof_uint32_t_is_4_goddamn_bytes.png

p,
@p@bae.st avatar

@theorytoe Some Python build system that Samba uses.

p,
@p@bae.st avatar

@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.

p,
@p@bae.st avatar

@theorytoe

> edit the makefile to make ir work

"THIS FILE IS AUTOMATICALLY GENERATED --- DO NOT EDIT"

You end up in a feeback loop. We're fucked, there's no one that stops it at the gate, you let one "best practice" in and then you're buried under a mountain of fluoride.

p,
@p@bae.st avatar

@syzygy @theorytoe

> for some reason it couldn't tell if the libc had malloc so it made a definition in a config.h

Dear god.

p,
@p@bae.st avatar

@lanodan I think checking the size of that is probably reasonable for things like memory allocation, though I suspect that it's just a list of all the types in stdint. (And why they can't just use sizeof is a mystery. It is really obvious what's going on if you see if(sizeof(size_t) == 8), and even trivial compilers remove the branch when compile-time constants are compared, but some preprocessor macro for _SIZE_OF_SIZE_T is at least an extra level of indirection, and it is practically guaranteed that they are using #if instead of just if.)

p, to random
@p@bae.st avatar

I don't know why it didn't work before or why it started working now, but the shoutbox client apparently works on bae.st now. I didn't change the code.

p,
@p@bae.st avatar

@sjw Yeah, the client I wrote wasn't working with bae.st when I first wrote it, but apparently as of 43 days ago, it started working fine.

p, to random
@p@bae.st avatar

:revolvertan::hacker_f::hacker_s::hacker_e::saba:

First piece of :fse:'s new hardware has been acquired. Now we just wait for it to ship and for me to get paid again so the next few pieces can be acquired.

New box will be more stable (for anyone that reads my stupid posts and can remember any of them, I am doing the build that I proposed a few years ago, as a joke conversation between :elliot: and :putinlol: because in some initial testing, it turns out to not just be tenable but more reliable) as well as lower power and cooler and easier to do remote service on. It will be less beefy but better suited to the new software. :ocelot:
operatingsystem.mp4

operatingsystem.mp4

p,
@p@bae.st avatar

@MK2boogaloo Well, I can't main Poast because some FSE refugees will not be able to talk to me, and the same with some other instances, but if Baest goes down, I will post on gh0st and Poast about where I am, maybe I'll be on gh0st or I'll be in dcc's closet or something. It's like the presidential succession act, we haven't had this many instances go down for this long, so there's no plan.

p,
@p@bae.st avatar

@MK2boogaloo Can't. Cloudfed.

p,
@p@bae.st avatar

@IAMAL_PHARIUS @MK2boogaloo I can't go back, that place sucks, plus I told them I was gone forever and I am not the sort of person to say I'm leaving forever and then come back. (Hi Opal, hi Eris.)

kirby, to random

ultimate anti foss software stack:
shitty 300 dollar laptop with tpm
windows 11 with extra telemetry on obviously
google chrome with all privacy settings turned extremely low, and a few dozen tabs open
a bunch of pups and old toolbars that dont even work anymore
aim instant messenger

done

p,
@p@bae.st avatar

@pernia @kirby @lanodan Thank you, but unfortunately I hate talking with my mouth and if I am awake I am either hacking or working except the two hours or so hours per day allotted to maintenance of the physical form, like eating and bathing and shitting, and even then, if it's a long enough shit, I will come out with some code.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • megavids
  • Durango
  • DreamBathrooms
  • ngwrru68w68
  • osvaldo12
  • cubers
  • magazineikmin
  • ethstaker
  • Youngstown
  • rosin
  • slotface
  • everett
  • kavyap
  • InstantRegret
  • JUstTest
  • khanakhh
  • thenastyranch
  • anitta
  • modclub
  • GTA5RPClips
  • mdbf
  • cisconetworking
  • tester
  • tacticalgear
  • provamag3
  • Leos
  • normalnudes
  • lostlight
  • All magazines
    •