Show newer

@wmd@chaos.social Met het huidige autogeile kabinet? Ik kan het me niet voorstellen.

Join a new discord and see an empty nsfw channel.

Break the ice by immediately posting OSHA violations

TIL a new version of the IMAP standard was published in August 2021

i have a theory that when you meet someone who truncates something like "$6.99" in speech as "six dollars", you know that person has never been broke

@aeva@mastodon.social My uninformed guess would be the same reason as why JS has class syntax; because people will complain if it doesn't, regardless of whether it'd actually make sense in the language.

@Peetz0r This is the ultra cheapo kind, 30 minute resolution, and yep, 30 minutes of downtime when I'm asleep

@kim Imagine how much easier it would be if you could just manage cron tasks by plugging in physical timers

My modem now auto-reboots every night to work around a memory leak, and this is the reboot script I used:

@evelyn@misskey.bubbletea.dev @emilis Why on earth is it even a company

imagine if my brain let me turn all the cool and viable ideas i have into shareable projects

@starless Already completed the latter, it was nice :D Never heard of the former though, will have a look, thanks!

@silvermoon82@tech.lgbt I have... strong feelings about this :) The main problem is that there's just currently no (credible) automated way to reliably assess the risk involved in dependencies, and it's unlikely that one can ever exist because of the nature of the problem. The best you can do there is pretty much "spotting known problems to look at", and that scope will be very limited.

*Ideally*, you would manually review every dependency. This is actually viable in practice in JS, *if* (and only if) you strictly stick to single-responsibility dependencies that have a very well-defined scope, but even then it's still a very time-consuming process, and there should really be good tooling for doing this collaboratively across the community, to spread the work.

But... there isn't. :|

I explicitly don't trust for-profit corporations to build such tooling, because "for-profit" and "public commons" don't go together and it'll invariably end in doing free labour for a commercial party rather than a genuine community project. But there's also very little ongoing work in this area in general.

The 'immediate' advice I generally give for JS nowadays is to stick strictly with single-responsibility dependencies regardless of how high it makes the dependency count go up. Because that way many of your dependencies will simply not *need* maintenance, and swapping out a dependency in the worst case is super cheap. It's also much easier to audit them manually because all code is 'local' instead of coupled to other parts of the stack.

(I wrote a bit more about the counterintuitive nature of JS deps over on the birdsite a while ago, if you're interested: twitter.com/joepie91/status/10)

@starless I do have a bit of a soft spot for the 'ragtag band of queer weirdos flying through space' subgenre, but I imagine that that might not be that big of a genre :)

@silvermoon82@tech.lgbt Ahh, yeah. I guess they changed their pitch up quite a bit since I last looked at them - previously they were very much trying to be "the solution to funding OSS, pay once to pay everybody", which I really didn't like because they were essentially positioning themselves as a monopolistic OSS funding gatekeeper, intentional or not.

The current presentation does seem a lot better and a lot more measured. I have no idea how accurate their metrics are, though, and I do hope that it isn't just prioritizing Tidelift-affiliated packages...

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.