raboof @raboof@merveilles.town

Hi there!

I've been on the fediverse since 2018, but recently moved into @merveilles.town, so I guess it's time for a new #introduction!

I'm a #software developer from #Deventer, the #Netherlands. I love #opensource, #NixOS, @reproducible_builds, maintain a #tiling #x11 #windowmanager @notion and help organize @mch2021. I'm part of @hack42 and work on #akka for Lightbend.

Looking forward to meeting all you creative people! Feel free to get in touch, both public and private.

This is perhaps due to a personality trait of mine: I like harmony. When there are clashing standpoints, I like it when they're "talked out" and "resolved". "Shit-talking" is evidence of a breakdown of communication.

Perhaps I should get more comfortable with the fact that people have widely different standpoints, and stop desiring them to be "resolved" when I have no chance of helping that happen.

That does not help the "other victims", though...

Another aspect is that it is not just about me: if someone shit-talks FOSS, they shit-talk the countless people all over the world that dedicate part of their life, often from a genuine desire to improve the world without expecting anything in return.

They might be doing it wrong - but they largely don't deserve the harsh words, either.

The ones doing the shit-talking are probably *also* genuinely thinking they are improving the world, though...

I guess part of it is that those criticisms call into question my deeply-held belief that FOSS can help further those hopes and dreams.

Now, it is quite obvious that it doesn't achieve all those goals all the time - but that was never the goal or expectation. If it just moves towards some of these goals some of the time that should be enough - and I do think that is somewhat obviously the case. So then why the emotional response?

One solution is to just stop caring about those hopes and dreams, but I'd rather not :D

Just unfollowing anyone with such criticisms is useful for self-preservation purposes, but it seems there is something to learn here.

Responding directly seems like it wouldn't do anyone any good.

Quietly taking the abuse isn't working out either.

Sure, these are a privileged person's "problems". But they're mine.

I notice I can get pretty upset when people shit-talk FOSS - like actually lose sleep over it.

I find it hard to put my finger on exactly why, which I guess is part of the reason in itself :D

I think it happens especially when the criticism is around the fundamental hopes and dreams I have for the world: diversity, accessibility, autonomy, independence, openness, all that good stuff.

(sparked by a thread that I lost by unfollowing someone, but anyway it's not a direct reply)

"[PagerDuty Low-Urgency ALERT] You have 1 TRIGGERED Incident"

Mixed signals.

Just noticed it's likely less mysterious than I feared: USB activity (moving the mouse or pressing buttons on the keyboard) will wake the laptop up.

I wonder if that was always the case and the impact was lighter before (it went back to sleep faster), or that this wasn't the case before.

I feel bad for the good people that create the Muse Sequencer, https://muse-sequencer.github.io/ - not to be confused with MuseScore and the Muse Group...

Plotting using #inkcut on #NixOS via #CUPS was broken. Added some more diagnostic logging (https://github.com/inkcut/inkcut/pull/312) and proposed a fix to the package (https://github.com/NixOS/nixpkgs/pull/130660)

Just noticed the main GitHub org for mastodon is no longer https://github.com/tootsuite

It's a good move, but I'm also slightly sad to see the "tout de suite" pun disappear :D

The #openidconnect-based mechanisms ( https://solid.github.io/authentication-panel/solid-oidc/ ) sure seem complicated/convoluted though!

It *might* all be necessary/essential complexity to be able to meet the design goals, of course - but I'm not quite convinced yet. Getting a strong "If this is the answer, are we *sure* we're asking the right question?" vibe.

Checking out #SolidProject a bit.

I like how, for logging in and keeping track of ownership/rights, they separate identity (with #webid) and authentication (with #openidconnect ): this means in principle, you could trivially self-host your identity under your own domain (it is just a file), and use some external service for actually logging into stuff with that identity. Would that service go away or stop being trustworthy, you can switch to a different one without losing your identity.