I write English / Escribo en Español.

Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.

This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.

  • 0 Posts
  • 15 Comments
Joined 3 years ago
cake
Cake day: July 26th, 2023

help-circle
  • Back in the time when I disliked it and, to a lesser extent, AppArmor, the reason was pretty simple:

    It forces services to lie to me / It gets in the way of software doing what I tell it to do.

    The examples would be rather simple. Need to spin up a second instance of a database server, sure, just set up the given config file with datadir=/mount/point/second/disk/var/lib/database. Should work… Nope. Database errors out despite the directory existing and being writable and all permissions being right. Insists it’s “file permissions”. Try to look around, to no end. Then it turns out there is some secret NSA Cabal infiltrated in my server already that… for some weird reason, forces databases to be installed on /var/lib even though when that is almost full and I mounted a second disk to have more room. And thus the service lies to me, says file permissions, well I checked them several times and they were alright.

    Stupid NSA cabal thing stupidly getting in the way of configuring things and adding more entrypoints you have to edit and services you have to configure just to start up a program. I want to start a database, not set up a DEFCON 1 line! Those days I was beginning to miss SQLite already…

    Similar issues I had with webservers, network share servers, joysticks and gamepads, and even audio devices. Never got a clear idea of what it was, software says something like “permission error” or “not a device file” but I checked and those are alright. A long sigh, remember than when you install a new computer you have to disable SELinux and AppArmor and reboot, boom, done, everything magically works.

    Fortunately things have improved a long way since, but back in the day, they were one of the most grating obstacles to me for getting friends, let alone clients, to adopt Linux.












  • It’s not possible to really anonymize whichever option if it has to be used repeatedly enough that a pattern is formed, in particular for cash. That’s why one-time options are so important: because, given enough time, the past is in the past.

    Not to mention that the bitcoin option means having to buy into the scams and felonies that is crypto in the first place.

    As for lifetime subscriptions being “hard to properly price”, I don’t see why Proton can’t consult with SDF on the matter. SDF offers a multitude of services of noticeably high involvement – heck you get shell on their servers – so I don’t see how routing a tun/tap interface goes much more difficult than that.


  • The other was the person using a personally identifiable payment method, although I’m not familiar with Proton’s policies on retaining that data.

    There is no circumstance under which Proton should have kept this data, assuming the account was old enough. Sure, you can say “credit” but I can just as well say that if Proton sells its business on the idea of keeping data secure or at as-low risk as possible, then they should offer lifetime / one-time payment options so that the payment information would have expired already or at least would not be renewed forever.

    And don’t tell me that doesn’t exist. I’m a user of SDF. They offer such plan.