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

@foone This should honestly be part of the heuristics Ghidra should use. Plus, war you if you do it by accident. Too many times I had wrongly detected (or previously mistakenly declared as) code sections I had to clean up by squinting my eyes and saying “nah, this aint lookin like legit code”

@foone The complex part – apparently – is to get hold of the TOPRE stuff since those aren't individual switches and AFAIK there are only Realforce, HHKB and some Leopolds who use them.

But, yes, I probably should look into it... some day :3

Your post definitely pushed up my motivation for that 0:-)

@foone I'm still procrastinating learning PCB design in order to design the first split keeb using TOPRE switches ... :~

@whitequark Q: What's an anagram of Banach-Tarsky?

A: Banach-Tarsky Banach-Tarsky.

@aral I think back then I simply removed the version lock of RPM fusion and since then the rebases work just so:

https://discussion.fedoraproject.org/t/simplifying-updates-for-rpm-fusion-packages-and-other-packages-shipping-their-own-rpm-repos/30364

@aral Why would you need to do those workarounds for RPM fusion, they're new to me?

No, #Google. #AI #enshittification

@graydon There's a culture clash here. Many, including the Go developers, are okay with sharing data beyond the bare necessary as long as the specific data collected doesn't seem (or wasn't proven to be) harmful.

Many others are against any form of any additional sharing of data beyond what's necessary.

I'm in the latter group. I don't think this is *ever* really necessary. While I can see that it is helpful, the right to self determination of any data produced by oneself is stronger if you ask me.

Having this opt-out is, to me, pretending to have a right to collect data by default.

And also: Telemetry ain't unbiased as well. You won't get many critical infrastructure or privacy conscious people (including many Go versions distributed by Linux distros). This won't be an accurate picture.