GideonBear

joined 1 year ago
[–] [email protected] 2 points 1 day ago* (last edited 1 day ago)

Because:

  1. If you install any new software that needs updating, you don't need to update your alias.
  2. If any software makes changes that break your alias, (theoretically) the bit of software should be able to fix it quickly, without you needing to pay any attention to it.
  3. The bit of software can more easily do advanced things than the simple alias. For example, I added functionality to update JetBrains Toolbox and IDE's installed with it. A simple alias could not do this, because Toolbox does not have a simple update command, however I made it work by enabling automatic updates temporarily, and then inspecting the log for updates. Now the end-user doesn't have to think about this at all. Other things that could be done but are not implemented yet include parallelization, and listing updated components in a neat summary (PR linked).

Of course if you're a minimalist, then you probably don't have that much stuff that needs upgrading in the first place. For me personally I have deb-get, uv, cargo, and flatpak, to name a few; the alias was getting longer and longer until I was able to remove it completely by switching to Topgrade.

[–] [email protected] 2 points 2 days ago (5 children)

Can I introduce you to Topgrade? ;)

[–] [email protected] 3 points 3 weeks ago (1 children)

I love the feeling of just forking something to add your wild tiny feature. I forked LeechBlockNG to notify my friend when I pressed "Override" :)

Or finding a tiny bug in some software, then spending multiple hours learning their codebase so you can fix it. And then building and using your fork because they're too slow with merging it...

Using open source software + having enough experience and confidence to figure out most things (given enough time, of course) software-related is so empowering.

 

I have started to send GDPR art. 17 data deletion requests to some companies using https://yourdigitalrights.org/ . Mostly, to avoid my e-mail leaking in a data breach. However, the template contains a line stating:

Please note that I do not consent to any personal data which is part of this request to be used for any purpose other than fulfilling this request, except in the case of a suppression list, which you may keep in order to ensure that you do not collect any of my personal data in the future.

This means that my e-mail address is still stored (from what I can find sometimes hashed, sometimes in plaintext) in their database. As far as I can find, they are not required to delete it from the suppression list if I ask, but still; isn't it extremely counter-productive to explicitly state that it's okay for them to store it in a suppression list (where it can still leak)? Is there any downside to stating in the request that I wish for it to be deleted from there as well?

[–] [email protected] 16 points 2 months ago

#define endl "\n"

[–] [email protected] 4 points 7 months ago

I would like to recommend SCEE if you've been using StreetComplete for a while. It offers some advanced features like editing tags, but more importantly some needed QOL improvements like the overlay quick-selector, and GPX notes.