Notices by Erin 💽✨ (erincandescent@akko.erincandescent.net), page 2

@mattly you know, a few decades ago I did some webdev in the much-maligned Zope where the templating language (ZPT/TAL) is a bunch of namespaced elements/attributes jammed into (X)HTML and ever since I have been convinced that it is obviously true and correct that any templating system you use needs to be language aware.

And then I watch people write Helm charts and I despair because shoving together YAML and Go text/template is the worst possible combination I have ever seen.

(“did someone implement the spec wrong?” yes. of course they did. its oauth 2. its more vibes than a spec to begin with and yet people manage to find new and creative ways to violate the bits that are nailed down all the time)

(I was looking at some OAuth 2 client code and found a fossil of this in the form of still supporting parsing responses in x-www-form-urlencoded format and I was like “what. why. did someone implement the spec wrong?!” and it looks like the answer is “no, the spec was just briefly bonkers”)

Early drafts of OAuth2 did what?!

link

@TomF @mcc Intel provided an assembler at one time (ASM86), maybe they still do as part of ICC? And basically “intel syntax” is a descendent of that per oral tradition. It’s Intel syntax because its the syntax that Intel’s asembler used, and that the Intel datasheets use; as opposed to AT&T syntax, the syntax that AT&T’s assembler for Unix used.

When Microsoft made MASM it copied the syntax. Borland’s Turbo Assembler (TASM) copied that. Everything else “intel syntax” is a descendent of those two

In ASM86 and MASM, what mov eax, foo does is not immediately obvious. If “foo” is defined as constant (label EQU 0xf00), it’ll set EAX to 0xf00. If “foo” is defined as a variable, it’ll load the contents of that variable.

TASM added “Ideal Mode”, in which this is always consistent: mov eax, foo always sets EAX to the address of the foo label; mov eax, [foo] loads from that address.

Most other assemblers implementing Intel syntax (NASM, FASM, YASM, GAS w/ .intel_synatx noprefix) are broadly copying Ideal Mode

But it’s all kind of vibes.

@sinbad My general rule with USB-C cables is “Is it flexible? -> Its USB 2 only” / “Is it fairly rigid? -> It’s a USB 3 capable cable of some form”

Honestly when split that way (and I only have a handful of devices which need USB 3 cables) I don’t tend to have many compatibility issues.

As for chargers… thanks to several years of working for tech companies which like MacBooks, I have a plethora of 65W Apple USB-C chargers which can handle basically everything except the most demanding laptops.

Love too see viral posts go past on my timeline that don’t even pass trivial scrutiny:

From the opening paragraphs of the Equifax Wikipedia page:

Equifax was founded as the Retail Credit Company by Cator and Guy Woolford in Atlanta, Georgia, as Retail Credit Company in 1899. By 1920, the company had offices throughout the United States and Canada. By the 1960s, Retail Credit Company was one of the nation’s largest credit bureaus, holding files on millions of American and Canadian citizens

(Maybe the “credit score” is newer? But the credit score is an abstraction to give you an insight on what your credit file says, nothing more)

Overdraft fees meanwhile are basically as old as the cheque.

RE: https://mastodon.social/@MEActNOW/113789371626213991

@hugh @eloy @linus if POSIX stated that CLOCK_REALTIME was seconds UT1 since the epoch, all would be forgiven

Alas.

Remember: If a "second" is 1/86400th of a day, its UT1

If a "second" is "defined by taking the fixed numerical value of the caesium frequency, ΔνCs, the unperturbed ground-state hyperfine transition frequency of the caesium 133 atom, to be 9192631770 when expressed in the unit Hz, which is equal to s−1", its UTC/TAI.

@Beckydog @MOULE <points at lump of cesium> this thing isn’t thinking

Disadvantages of having a physics degree & being a bit of a timekeeping nerd:

You know that most of the time when programmers are talking about UTC timestamps they actually mean UT1. (Except NTP. NTP is also developed by timekeeping nerds)

RE: https://akko.erincandescent.net/objects/874224bb-0390-4b06-9095-37e6cc6118ce

@snowfox @equinox yeah, the CLOCK_TAI <-> CLOCK_REALTIME offet is also integer seconds, which is less than ideal because its probably reasonable to leap-smear these days because of the quantity of questionable software.

@equinox @snowfox IMO the lack of kernel support for non-integer or even algorithmic offsets is one of the biggest impediments to CLOCK_TAI use.

• Most systems don’t have a correct TAI<->UTC offset loaded anyway
• Making it correct requires making CLOCK_REALTIME non-monotonic (which breaks shit!)
• If you do it with leap smear it makes a mess

i.e. fixing shit really needs to start with the kernel, but clock_gettime is a super hot path…

@puppygirlhornypost2 @trwnh @cwebber Object already permits just putting an Object-ID-URI there, Object | Link is a horrible overcomplicated mess (IMO) that should never have made it into the standard >_<

Oh well

@puppygirlhornypost2 For better and worse Congress has no formal sponsors. (Better: No corporate interests distorting things; Worse: things can be a bit more expensive than they otherwise would if ther were sponsors)

(There are some informal sponsors, but informal in this sense means “they donate some services for free e.g. the fat fat internet pipe without getting their logo anywhere)

@puppygirlhornypost2 The 38th Chaos Communications Congress, a gigantic (16,000? person) hacker event in Germany.