# orderedItems[].object.content
@Benaresh @puppygirlhornypost2 i should try a few advent of code problems in a64 (assembly, i'm not enough of a masochist to use hexadecimal for this). i probably wouldn't end up doing a ton of them though.

# orderedItems[].object.contentMap.en
@Benaresh @puppygirlhornypost2 i should try a few advent of code problems in a64 (assembly, i'm not enough of a masochist to use hexadecimal for this). i probably wouldn't end up doing a ton of them though.

# orderedItems[].object.content
@helle Yeah, i know devtmpfs didn't exist until linux had been out for over a decade. I didn't realize you used to mknod at install time though.

Some of the openbsd features seem not amazingly thought out though, like i don't entirely understand how blocking syscalls from outside libc makes programs more secure. on linux at least you often rop into syscall instructions that are in libc anyway. it's not all bad though, static-pie is nice and pledge and unveil are really easy to use tools, though not as fine-grained as capsicum or seccomp-bpf.

There's also a lot of openbsd not being very flexible, e.g. it really wants to boot from a bsd disklabel partition table so you have to make one even when on uefi. It sounds like something that contributors could fix if the openbsd devs were willing to accept, but they don't seem as easy to contribute to as freebsd (email-based cvs flow vs phabricator)

# orderedItems[].object.contentMap.en
@helle Yeah, i know devtmpfs didn't exist until linux had been out for over a decade. I didn't realize you used to mknod at install time though.

Some of the openbsd features seem not amazingly thought out though, like i don't entirely understand how blocking syscalls from outside libc makes programs more secure. on linux at least you often rop into syscall instructions that are in libc anyway. it's not all bad though, static-pie is nice and pledge and unveil are really easy to use tools, though not as fine-grained as capsicum or seccomp-bpf.

There's also a lot of openbsd not being very flexible, e.g. it really wants to boot from a bsd disklabel partition table so you have to make one even when on uefi. It sounds like something that contributors could fix if the openbsd devs were willing to accept, but they don't seem as easy to contribute to as freebsd (email-based cvs flow vs phabricator)

# orderedItems[].object.content
@pmbrandvold @pluralistic is that how it's supposed to work? i have to make substantial conscious effort to get myself to do things even when i do them every day (e.g. brush teeth)

# orderedItems[].object.contentMap.en
@pmbrandvold @pluralistic is that how it's supposed to work? i have to make substantial conscious effort to get myself to do things even when i do them every day (e.g. brush teeth)

# orderedItems[].object.content
i would like to comment that i am dealing with openbsd for two reasons:

dealing with the annoying stuff is kind of fun

someone is paying me to do this

# orderedItems[].object.contentMap.en
i would like to comment that i am dealing with openbsd for two reasons:

dealing with the annoying stuff is kind of fun

someone is paying me to do this

# orderedItems[].object.content
this seems consistent with my impressions (linux is full of features, freebsd made some different decisions that make sense, netbsd is a competent old unix system, and openbsd is an old unix system designed to infuriate me specifically)

# orderedItems[].object.contentMap.en
this seems consistent with my impressions (linux is full of features, freebsd made some different decisions that make sense, netbsd is a competent old unix system, and openbsd is an old unix system designed to infuriate me specifically)

# orderedItems[].object.content
why is openbsd like this...

linux: /dev is a devtmpfs, a tmpfs where the kernel makes device nodes and udev makes aliases

freebsd: /dev is a devfs, where the kernel creates device nodes

netbsd: /dev is a tmpfs where init creates the device nodes at boot

openbsd: /dev is just part of the normal filesystem, device nodes are created at install time

openbsd manages to make every infuriating design decision i can think of

# orderedItems[].object.contentMap.en
why is openbsd like this...

linux: /dev is a devtmpfs, a tmpfs where the kernel makes device nodes and udev makes aliases

freebsd: /dev is a devfs, where the kernel creates device nodes

netbsd: /dev is a tmpfs where init creates the device nodes at boot

openbsd: /dev is just part of the normal filesystem, device nodes are created at install time

openbsd manages to make every infuriating design decision i can think of

# orderedItems[].object.content
@sen I was mostly thinking about this because my aunt is a politian who gave a speech using AAC and the stress sounded a bit off. It's the kind of thing she had hours to prepare for though, so she would have been able to add stress e.g. while she was reading over it the day before.

# orderedItems[].object.contentMap.en
@sen I was mostly thinking about this because my aunt is a politian who gave a speech using AAC and the stress sounded a bit off. It's the kind of thing she had hours to prepare for though, so she would have been able to add stress e.g. while she was reading over it the day before.

# orderedItems[].object.content
more seriously, it seems like there are tools for disabled people for very quickly saying words and tools for very expressive voice synthesis, but nothing to bridge the gap.

I think an AAC system that used a vocaloid-like engine with an easy way to input things you'd use in a speech, e.g. stress of words, matching cadence of similar clauses, volume changes that vary over time, would be very useful.
You could probably implement some sort of export to vocaloid/piapro/etc, though requiring that sort of input to happen outside the main aac software would compromise the whole "single, fast, accessible interface" goal.

# orderedItems[].object.contentMap.en
more seriously, it seems like there are tools for disabled people for very quickly saying words and tools for very expressive voice synthesis, but nothing to bridge the gap.

I think an AAC system that used a vocaloid-like engine with an easy way to input things you'd use in a speech, e.g. stress of words, matching cadence of similar clauses, volume changes that vary over time, would be very useful.
You could probably implement some sort of export to vocaloid/piapro/etc, though requiring that sort of input to happen outside the main aac software would compromise the whole "single, fast, accessible interface" goal.

# orderedItems[].object.content
when listening to my aunt's speech i noticed that, while the voice was good, the aac tools weren't very expressive for inputting e.g. stress, volume, etc. when pre-preparing a speech.

that's why we need hatsune miku aac.

# orderedItems[].object.contentMap.en
when listening to my aunt's speech i noticed that, while the voice was good, the aac tools weren't very expressive for inputting e.g. stress, volume, etc. when pre-preparing a speech.

that's why we need hatsune miku aac.

# orderedItems[].object.content
"co-funded by the european union" is a threat, if you leave then your government is never going to make up for the hole left by the lack of european structural and investment funds.

# orderedItems[].object.contentMap.en
"co-funded by the european union" is a threat, if you leave then your government is never going to make up for the hole left by the lack of european structural and investment funds.

# orderedItems[].object.content
i guess "co-financed by the european union" is in signs now, it will be many years before those are gone

# orderedItems[].object.contentMap.en
i guess "co-financed by the european union" is in signs now, it will be many years before those are gone

# orderedItems[].object.content
why did this show up in my youtube recommended: https://www. youtube.com/watch?v=8EPcwJribFc

also why does a video from wales in 2024 mention the "european regional development fund", i thought eu funding would be over by now

# orderedItems[].object.contentMap.en
why did this show up in my youtube recommended: https://www. youtube.com/watch?v=8EPcwJribFc

also why does a video from wales in 2024 mention the "european regional development fund", i thought eu funding would be over by now

# orderedItems[].object.content
@quinn my guess is that the EU will keep their current terrible asylum policy for US citizens/residents since all the asylum-seekers would be minorities anyway.

# orderedItems[].object.contentMap.en
@quinn my guess is that the EU will keep their current terrible asylum policy for US citizens/residents since all the asylum-seekers would be minorities anyway.

# orderedItems[].object.content
@flamingspork they should give me a /24 of ipv6

# orderedItems[].object.contentMap.en
@flamingspork they should give me a /24 of ipv6

# orderedItems[].object.content
To the kernel and dynamic linker the name .openbsd.randomdata don't matter, the important part is the program header of type PT_OPENBSD_RANDOMIZE. The fact that libc always has a .openbsd.randomdata means that you can get free randomness pretty easily though:

#include <stdio.h>

unsigned int random __attribute__((section(".openbsd.randomdata")));

int main() {
        printf("random: %d\n", random);
        return 0;
}

# orderedItems[].object.contentMap.en
To the kernel and dynamic linker the name .openbsd.randomdata don't matter, the important part is the program header of type PT_OPENBSD_RANDOMIZE. The fact that libc always has a .openbsd.randomdata means that you can get free randomness pretty easily though:

#include <stdio.h>

unsigned int random __attribute__((section(".openbsd.randomdata")));

int main() {
        printf("random: %d\n", random);
        return 0;
}

# orderedItems[].object.content
wow, openbsd did something i actually like:
ELFs (elves?) have a section called .openbsd.randomdata, and any variable you put in there will be filled with random data by the kernel or dynamic linker when the program is started. OpenBSD puts its stack cookies there so they're ready immediately on program start.

Linux and FreeBSD both put a fixed number of random bytes into the ELF auxiliary vector (for linux, 16 bytes in AT_RANDOM; for FreeBSD 8 * sizeof(long) bytes in AT_CANARY). Their respective libc implementations then have constructors that initialize the global canary variables.

This can be a bit annoying since libc has to make sure its constructor and anything that runs before it don't try to use the stack canary. Normal programs also can't use this mechanism to get syscall-free random numbers since they'd have no way of knowing which are stack canaries they can't leak.

# orderedItems[].object.contentMap.en
wow, openbsd did something i actually like:
ELFs (elves?) have a section called .openbsd.randomdata, and any variable you put in there will be filled with random data by the kernel or dynamic linker when the program is started. OpenBSD puts its stack cookies there so they're ready immediately on program start.

Linux and FreeBSD both put a fixed number of random bytes into the ELF auxiliary vector (for linux, 16 bytes in AT_RANDOM; for FreeBSD 8 * sizeof(long) bytes in AT_CANARY). Their respective libc implementations then have constructors that initialize the global canary variables.

This can be a bit annoying since libc has to make sure its constructor and anything that runs before it don't try to use the stack canary. Normal programs also can't use this mechanism to get syscall-free random numbers since they'd have no way of knowing which are stack canaries they can't leak.

# orderedItems[].object.content
../lix/libstore/filetransfer.cc:680:100: error: ISO C++ requires field designators to be specified in declaration order; field 'effectiveUri' will be initialized after field 'etag' [-Werror,-Wreorder-init-list]
fuck you

# orderedItems[].object.contentMap.en
../lix/libstore/filetransfer.cc:680:100: error: ISO C++ requires field designators to be specified in declaration order; field 'effectiveUri' will be initialized after field 'etag' [-Werror,-Wreorder-init-list]
fuck you

# orderedItems[].object.content
@sad_electronics @opelex i don't think i have any PSUs that claim they'll work at 15Hz, only 50-400Hz. I'm not sure if PSUs would like such long times between peaks

# orderedItems[].object.contentMap.en
@sad_electronics @opelex i don't think i have any PSUs that claim they'll work at 15Hz, only 50-400Hz. I'm not sure if PSUs would like such long times between peaks

# orderedItems[].object.content
@aurora i'm not in germany, want to do my new york state estimated tax for freelancers /s?

# orderedItems[].object.contentMap.en
@aurora i'm not in germany, want to do my new york state estimated tax for freelancers /s?

# orderedItems[].object.content
@aleksana please don't turn your wife into cake

# orderedItems[].object.contentMap.en
@aleksana please don't turn your wife into cake