Notices by lj·rk (ljrk@todon.eu)

CVE-shitposting

By now I'm convinced that one of the primary causes of education failing in school is that people

a) underestimate children's intelligence, while at the same time
b) setting high expectations on knowledge/experience.

Unfortunately, when they're expectations in (b) are proven wrong, they do not provide them with an appropriate definition or learning materials. Instead, they further go down (a) by lowering their estimate of the children's intelligence.

ChatControl, or the French initiative to reduce the amount of cat girls in heat within the EU.

@ryanc No FLINTA* SingStar/Karaoke?

It's kind of hard how we ADHDers suffer from the paradox effect of ADHD. Yet, many of us (includijg me) do like our morning stimulants to "help us get awake". But's not the awake thing really, at least not how neurotypicals feel it (AFAICT). I'm not stimulated. I'm just... less overwhelmed. Not more awake, just less tired. Less "ugh". But that's not the same thing as being awake!

@strypey @nate Yes and no. From a legal or technical standpoint, all this is true. It is legally allowed, technically necessary. But this doesn't mean it's ethical and that it doesn't violate consent.

I can walk up to two people speaking in "public" to eavesdrop on their conversation. But just because I can, doesn't mean it's right. I can scrape endless pfp images from WhatsApp through their contacts API. But doesn't mean it's right.

So no, just because it's possible it doesn't mean "permission enough". It' just means that it's necessary and people have accepted the risk. Explicit permission is something different entirely. This is about consent, a human property, not about technological or legal constructs.

@nate @strypey Absolutely, there's this difference. But I'd argue it can only be consensual if whatever happens is somewhat "expected". And depending on the service in question, this isn't always the case. Some people go to the Fedi because they don't want to have their stuff on AT...

Realizing "hey gays" is broadly gender neutral, yet actually not inclusive to everyone. Good that this usually doesn't matter because all my friends are gay.

Hey gayyys! :3

QT @alice
https://lgbtqia.space/@alice/114736690113006188

Is that your pubkey in my ~/.authorized_keys, or are you just happy to see me?

There's many theories what the "forbidden fruit" in the paradise actually was, and most scholars agree that it was unlikely to be an apple (just as Jesus wasn't white). One theory is that the fruit tree Eve stood below was a date palm.

Which means that basically Adam & Eve got expelled from the paradise because they had a date and God hadn't. Would a triad relationship b/w the three have fixed paradise? Why does monoamory and envy always ruin things?

@inthehands ugh!

@inthehands I've been to a Starbucks once because they had a toilet. How do they make macchiatos there? :'-D

Apple just works. They're the UX pros.

@lanodan @ska Oh absolutely, I won't argue against you on that! It's just... that some in the committee have (had?) the habit of basically claiming any UNIX as alive as long as they could spin up a VM of them... .

Of course this is absurd because then one couldn't do any changes at all that may break old UNIXen. But that's the state that POSIX has indeed been in for quite some time unfortunately :'-D

Oh, also fuck Alien UNIX

@lanodan @ska absolutely! but arguing about a UNIX being "gone" is very difficult territory in a working group that's defining what UNIX™ is and mostly about cosplaying a time where this matters. I love POSIX, I really do, but I've attended one of the Austin Groups meetings as an intern. And that was enough for a lifetime.

@lanodan @ska I mean quite generally the "rationale" for anything like this is usually: some implementor already did it like this so we need to write the standard s.t. it fits. POSIX started out as XPG, so mostly just documenting preexisting common interfaces rather than defining ones for the future. If they tried the latter, that often failed (e.g., pax). So my money is on: Some UNIX did something weird in that case and that's why this clause is part of POSIX ^^'

@WeirdWriter @rysiek

These two paragraphs struck me in particular:

> That’s in stark contrast to, say, Google+, which despite corporate backing, incomparably larger budget, and being pushed down people’s throats through forced integration with YouTube, survived mere seven years, nine months, and a week.

Because unfortunately Google probably doesn't see that as a problem. Or even as the Fedi winning. For them, longetivity doesn't matter, but peak user count.

> And once it shut down, it shut down. A social network of millions just blipped out of existence one day. All those moments – lost in time, like tears in rain.

This, too, for them is a good thing. No-one else can profit from "their" data.

This just makes it so crystal clear how the big one's interests aren't aligned with ours. Google+ wasn't really failing in their book, it had served its purpose and then ceased to do so. To us, this is loss. To Google this is just business.

@nikitonsky @alcinnz will do gladly once at home (hopefully, remind me if I forget 😅)

Prepared the next handball training session :3

This time I'm gonna torture my poor little souls with running technique :blobcatdevil:

In all honesty though, I see so many people with bad technique, which does not only mean a higher likelihood of injuries, but also just ... less efficient. I know I'm a fast runner, but a good deal comes from good technique (hanks to my parents, both marathon runners or triathletes, as well as my first sports teacher who actually was good and taught injury-prevention, motivation and didn't care much about total "performance").

@alcinnz As someone who's been using Alabaster for some time... that clicks very much with me :'-D

I also played with some themes and interestingly did exactly what @nikitonsky described regarding replacing colors with typography. This was initially inspired by putting code in a thesis document (for print) and I always found the heavy usage of colors very distracting there. I toned them down and replaced some with italics (for things you don't want to make stand out but notice when reading) and bold (for things you want to stand out). And then I used this in my editor as well.

Indeed, the comparison with the thesis also makes sense when considering Knuth style "Literate Programming": Write a document explaining design choices (primary content) which just happens to contain code interspersed with it. Effectively reversing the role of code and comments. In line with that, I didn't "highlight" comments but made them high contrast black-on-white whilst toning down the contrast of code slightly and choosing a thinner weight for code (in documents).