propter_hog [any, any]

Post hog

  • 0 Posts
  • 32 Comments
Joined 4 months ago
cake
Cake day: July 3rd, 2024

help-circle
  • A few on this machine, mostly the usual “plug-n-play” suspects: openSUSE, Ubuntu, Mint, etc. I’ve narrowed it down to needing a specific driver which will have to be installed after the install, but I don’t have an extra thumb drive for it since the one external drive I do have will have the os on it, and I just haven’t been arsed to make it work on a single drive by modifying the partition to add a second one and put the driver there. It’s just a pain in the ass.














  • That’s why the current state of open source licenses doesn’t work. Commercial use should be forbidden for free users. You could dual license the work, with a single, main license applying to everyone, and a second addendum license that just contains the clause for that specific use, be it personal or corporate. Corporate use of any kind requires supporting the project financially.



  • You mentioned PGP already, but this is exactly what that technology was designed for. You can sign the post with your private key, meaning anyone with the public key can verify its authenticity, and sites such as GitLab make use of this for signing code commits to prove it came from the author listed on the commit. A scaffolding utilizing PGP for blogging may already exist. You’d have to enter your PGP passphrase to seal the post. In fact, you may be able to take advantage of the exact mechanism GitLab and others are already using by publishing by way of a signed git commit, and displaying like a green lock or something on blog posts that are authenticated.