Sven Slootweg (soft-deprecated) @joepie91@pixie.town

Currently being very amused by the NL cops whining on Twitter about having to put so much effort into arresting climate activists... and being told by both climate activists *and* various right-wing groups like covid deniers that they should stop complaining because they've created this situation for themselves

To clarify, since I cannot edit my original post: with "blocklist" I'm *not* referring to the defederation lists of individual instances! These are often private for good reasons.

Rather, I'm talking about the organized/collective blocklists, the ones that are meant to be used by third parties as recommendations for what to block preventatively.

https://mastodon.energy/@Sustainable2050/111039159882536261

Some reasons why blocklists *should* come with receipts:
1. So that blocks can be verified (you've probably already heard this one)
2. Resultingly, so that more people can actually *use* the blocklist without concerns about legitimacy
3. So that people can keep track of whether the issue has been resolved later
4. So that people can understand what the problematic behaviour was, and recognize it when it moves to another instance
5. So that people can see who were involved, in case those *perpetrators* move to another instance (a couple of serial account creators come to mind here)

Even if you don't personally care about verifying blocks, there are still many other reasons to keep careful track of blocking reasons.

For instance, I've seen entirely too many cases of people warning against Eris, the listener not seeing the problem and ignoring the warning, and then only finally understanding once being shown some of their posts. That only works if you keep receipts.

(That doesn't mean that there aren't people who will ignore the problem regardless of receipts; but those are not the people who will ever take it seriously anyway, they're not the target demographic here.)

(Why this is notable: it's much more common for companies to talk about handing stuff in for recycling, but then outsource the actual recycling part to some unknown third party, where it often just doesn't happen)

TIL that Lidl (or more accurately, their parent company) claims to have a full bottle recycling loop, in that all deposit-collected bottles are returned to *their own* PET recycling plant where they are turned into new bottles, and supposedly all of the PET drinks bottles at their German stores are 100% recycled plastic as a result

How accurate this is, I don't know, but that's what they claim, and they do genuinely seem to have a bunch of PET recycling factories

Also, 90% of these issues are some variant of "techbros are creating new problems faster than I can fix them"

Current mental state: extremely overburdened. It'd be nice if it didn't feel like the foundations of everything were constantly shifting away from under me.

Given that all __overrides usage seems to have been eliminated from nixpkgs in 2014, I am very tempted to just declare the entire feature deprecated in my implementation, this thing is broken in so many ways

Did I mention that I'm trying to write a bug-for-bug-compatible implementation

nix-repl> (rec { c.c = 1; __overrides = { c.d = 4; };}).c
{ d = 4; }

nix-repl> ({ c.c = 1; __overrides = { c.d = 4; };}).c
{ c = 1; }

Nix is a very well-defined language

Great, now I have *two* trackballs that I need to return for warranty, because both have the same button switch failure...