# orderedItems[].object.content
@joepie91 honestly the best thing about nixos you can say is "it replaces your problems with weirder nixos problems"

# orderedItems[].object.contentMap.en
@joepie91 honestly the best thing about nixos you can say is "it replaces your problems with weirder nixos problems"

# orderedItems[].object.summary
making fun of a viral video promoting toxic masculinity stereotypes

# orderedItems[].object.content
@charlotte delta-sigma male

# orderedItems[].object.contentMap.en
@charlotte delta-sigma male

# orderedItems[].object.content
also eidas means that the european union has legally binding xml containing base64-encoded asn1

# orderedItems[].object.contentMap.en
also eidas means that the european union has legally binding xml containing base64-encoded asn1

# orderedItems[].object.content
i think it's funny how the european union has declared that laws are only valid if they are published in the official journal online as pdf with a Qualified Electronic Signature/Seal, guaranteed to be made on a hardware security module. they defined a giant regulation (eidas) to give a legal backing to these electronic signatures and got etsi to write dozens of standards to support the regulation.

they then neglected to have any technical measure to say which certificates are actually allowed to sign official journal issues. I'm pretty sure they could have gotten the CA to include their signature policy in their certificates as a way to show that they're allowed to issue the official journal, but they didn't. they just publish a list of keys on a website.

# orderedItems[].object.contentMap.en
i think it's funny how the european union has declared that laws are only valid if they are published in the official journal online as pdf with a Qualified Electronic Signature/Seal, guaranteed to be made on a hardware security module. they defined a giant regulation (eidas) to give a legal backing to these electronic signatures and got etsi to write dozens of standards to support the regulation.

they then neglected to have any technical measure to say which certificates are actually allowed to sign official journal issues. I'm pretty sure they could have gotten the CA to include their signature policy in their certificates as a way to show that they're allowed to issue the official journal, but they didn't. they just publish a list of keys on a website.

# orderedItems[].object.content
@haskal i think it's possible to get luatex to fully support unicode, but it's still weird to use, and iirc setting up fallback fonts for multiple languages requires dropping into lua

# orderedItems[].object.contentMap.en
@haskal i think it's possible to get luatex to fully support unicode, but it's still weird to use, and iirc setting up fallback fonts for multiple languages requires dropping into lua

# orderedItems[].object.content
@qlp @mos_8502 @geerlingguy PCIe gen 5 and DDR5 would suggest AmpereOne (Altra is the older generation, annoyingly also the only one they'll sell to normal people).

AsRock Rack supposedly making a SSI CEB board for AmpereOne: https://www. asrockrack.com/GENERAL/product detail.asp?Model=AMPONED8-2T/BCM#Specifications

I think CEB mounting holes are almost all in the same place as ATX though, so you should be able to use it in normal ATX cases.

(I'm guessing everyone uses deep boards because ATX just doesn't have enough space to fit VRMs for massive sockets if you have RAM on both sides)

# orderedItems[].object.contentMap.en
@qlp @mos_8502 @geerlingguy PCIe gen 5 and DDR5 would suggest AmpereOne (Altra is the older generation, annoyingly also the only one they'll sell to normal people).

AsRock Rack supposedly making a SSI CEB board for AmpereOne: https://www. asrockrack.com/GENERAL/product detail.asp?Model=AMPONED8-2T/BCM#Specifications

I think CEB mounting holes are almost all in the same place as ATX though, so you should be able to use it in normal ATX cases.

(I'm guessing everyone uses deep boards because ATX just doesn't have enough space to fit VRMs for massive sockets if you have RAM on both sides)

# orderedItems[].object.content
@Jes @geerlingguy The community edk2 porting efforts are nice but they're never quite enough since no one wants to preinstall it on the board's spi

# orderedItems[].object.contentMap.en
@Jes @geerlingguy The community edk2 porting efforts are nice but they're never quite enough since no one wants to preinstall it on the board's spi

# orderedItems[].object.content
this screen is still really funny to me

# orderedItems[].object.contentMap.en
this screen is still really funny to me

# orderedItems[].object.attachment[].name
qemu display of a FreeBSD bootloader screen. It's all text mode and looks normal, except the system it's selecting is "NixOS Warbler 25.05.{some hash} (FreeBSD 14.1-RELEASE)"

# orderedItems[].object.content
@langoor i have gotten bits and pieces by searching and finding websites with an overview, then reading actual specs from 3gpp. it's not really a great strategy though, all the sources i find explain the networks as if you already understand them.

# orderedItems[].object.contentMap.en
@langoor i have gotten bits and pieces by searching and finding websites with an overview, then reading actual specs from 3gpp. it's not really a great strategy though, all the sources i find explain the networks as if you already understand them.

# orderedItems[].object.content
@yassie_j Guantanamo bay addresses all seem to be FPO to me (special USPS service where navy bases outside the US are treated as in the US for postal pricing and addressing but not customs). There's also "APO" for the army and "DPO" for diplomatic installations.

There are other FPO locations as well though, e.g. for ships at sea, so I'm not sure why they call out Guantanamo bay

# orderedItems[].object.contentMap.en
@yassie_j Guantanamo bay addresses all seem to be FPO to me (special USPS service where navy bases outside the US are treated as in the US for postal pricing and addressing but not customs). There's also "APO" for the army and "DPO" for diplomatic installations.

There are other FPO locations as well though, e.g. for ships at sea, so I'm not sure why they call out Guantanamo bay

# orderedItems[].object.content
@annathyst it's devtmpfs for me on nixos and arch, though i wouldn't be surprised if other distros (especially those that don't use systemd) did something different.

here's what i have on nixos:

dev on /dev type devtmpfs (rw,nosuid,size=3287952k,nr_inodes=8213973,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=3,mode=620,ptmxmode=666)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)

# orderedItems[].object.contentMap.en
@annathyst it's devtmpfs for me on nixos and arch, though i wouldn't be surprised if other distros (especially those that don't use systemd) did something different.

here's what i have on nixos:

dev on /dev type devtmpfs (rw,nosuid,size=3287952k,nr_inodes=8213973,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=3,mode=620,ptmxmode=666)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)

# orderedItems[].object.content
@starwall the fact that we think about it at all is very much colonialism, but i think it becoming the default was from artificial vanillin production. it's orders of magnitude cheaper than farming real vanilla and you don't need a lot of it

(also what the fuck: https://en.m.wikipedia.org/wiki/Edmond _Albius)

# orderedItems[].object.contentMap.en
@starwall the fact that we think about it at all is very much colonialism, but i think it becoming the default was from artificial vanillin production. it's orders of magnitude cheaper than farming real vanilla and you don't need a lot of it

(also what the fuck: https://en.m.wikipedia.org/wiki/Edmond _Albius)

# orderedItems[].object.content
@Lyude @aei i am, i'm complaining that it's too tied to linux so i can't port it to freebsd, forcing me to use a shell based thing

# orderedItems[].object.contentMap.en
@Lyude @aei i am, i'm complaining that it's too tied to linux so i can't port it to freebsd, forcing me to use a shell based thing

# orderedItems[].object.content
@leo i think the funniest systemd thing is that journald is socket activated. when systemd tries to log for the first time it's sending a message to itself. once systemd notices it got a message it logs over that same socket that it's starting journald then starts journald

# orderedItems[].object.contentMap.en
@leo i think the funniest systemd thing is that journald is socket activated. when systemd tries to log for the first time it's sending a message to itself. once systemd notices it got a message it logs over that same socket that it's starting journald then starts journald

# orderedItems[].object.content
@ipg i should add more architectures. ppc64 would be easy, the real challenge would be backporting it to nextstep on 68k

# orderedItems[].object.contentMap.en
@ipg i should add more architectures. ppc64 would be easy, the real challenge would be backporting it to nextstep on 68k

# orderedItems[].object.content
@ipg reminds me of this fun binary though:

[artemis@starlight:~/Downloads/XLD 20240511]$ llvm-readobj XLD.app/Contents/MacOS/XLD

File: XLD.app/Contents/MacOS/XLD
Format: Mach-O 64-bit x86-64
Arch: x86_64
AddressSize: 64bit

File: XLD.app/Contents/MacOS/XLD
Format: Mach-O 32-bit i386
Arch: i386
AddressSize: 32bit

File: XLD.app/Contents/MacOS/XLD
Format: Mach-O 32-bit ppc
Arch: powerpc
AddressSize: 32bit

File: XLD.app/Contents/MacOS/XLD
Format: Mach-O arm64
Arch: aarch64
AddressSize: 64bit

# orderedItems[].object.contentMap.en
@ipg reminds me of this fun binary though:

[artemis@starlight:~/Downloads/XLD 20240511]$ llvm-readobj XLD.app/Contents/MacOS/XLD

File: XLD.app/Contents/MacOS/XLD
Format: Mach-O 64-bit x86-64
Arch: x86_64
AddressSize: 64bit

File: XLD.app/Contents/MacOS/XLD
Format: Mach-O 32-bit i386
Arch: i386
AddressSize: 32bit

File: XLD.app/Contents/MacOS/XLD
Format: Mach-O 32-bit ppc
Arch: powerpc
AddressSize: 32bit

File: XLD.app/Contents/MacOS/XLD
Format: Mach-O arm64
Arch: aarch64
AddressSize: 64bit

# orderedItems[].object.content
@ipg ... oh god making a guess isn't even that hard. even on linux they could check the launch executable with llvm-readobj and check if there's a subfile with architecture x86_64. they'd have to think of something for the few games that have wrapper scripts, but still.

need to get a job at valve to make steam suck less

# orderedItems[].object.contentMap.en
@ipg ... oh god making a guess isn't even that hard. even on linux they could check the launch executable with llvm-readobj and check if there's a subfile with architecture x86_64. they'd have to think of something for the few games that have wrapper scripts, but still.

need to get a job at valve to make steam suck less

# orderedItems[].object.content
@ipg i thought apple actually dropped support for loading i686 mach-o files...
is Valve just really bad at detecting when something supports x86_64?

# orderedItems[].object.contentMap.en
@ipg i thought apple actually dropped support for loading i686 mach-o files...
is Valve just really bad at detecting when something supports x86_64?

# orderedItems[].object.content
@astrid @helle (i guess also i spent a while doing "embedded linux" where it was just debian, i didn't start dealing with low-level distro stuff until recently)

# orderedItems[].object.contentMap.en
@astrid @helle (i guess also i spent a while doing "embedded linux" where it was just debian, i didn't start dealing with low-level distro stuff until recently)

# orderedItems[].object.content
@astrid @helle I guess I never had to deal with that because I wasn't doing embedded linux until well after devtmpfs was a thing and i'd just run systemd-udevd/eudev anyway

# orderedItems[].object.contentMap.en
@astrid @helle I guess I never had to deal with that because I wasn't doing embedded linux until well after devtmpfs was a thing and i'd just run systemd-udevd/eudev anyway