DefederateLemmyMl

  • Gen𝕏
  • Engineer ⚙
  • Techie 💻
  • Linux user 🐧
  • Ukraine supporter 🇺🇦
  • Pro science 💉
  • Dutch speaker
  • 2 Posts
  • 644 Comments
Joined 2 years ago
cake
Cake day: August 8th, 2023

help-circle


  • Personally I am of the nonanoist denomination. I will curse all the demons of hell when on a new system I type vipw or systemctl edit some.service and I am unexpectedly faced with the demon called nano. Words cannot describe how much I loathe this pityful excuse for an editor, this usurper of editing powers, this illegitimate occupier of the editor symlink. How dare you insult me, the omnipotent god called root, by presenting me with a training tool for novices?!

    Fortunately, there are ancient spells that can nullify its powers. ‘I command you: be gone Satan’, I will utter under my breath as I carefully type in the magic incantation to cast it back into the fiery chasm from whence it came:

    apt -y purge nano
    
    disclaimer

    This post may contain up to 50% satire


  • The thing is, simple can mean two things, and they are quite often at odds with each other.

    It can mean simple to understand, or simple to use.

    For example, a piece of software that’s just a binary, a config file and a man page describing the config file and the software’s behavior is generally quite easy to understand. Like, you can fit the idea of the program entirely into your mind and “comprehend” it, though it may not be easy to use for a novice.

    By contrast, a piece of software that contains additional layers for easy of use, like a GUI to edit options, may be simple to use, but not necessarily simple to understand. The additional layers add more complexity that does not contribute to core functionality of the program, it can become unclear what gets changed where when you click on buttons, the config file is likely not documented, human readable or editable, or it may even be a completely opaque configuration database (the registry), … So making the software more simple to use, often makes it harder to comprehend.

    I, and I think many other nerds, like software that is simple in the “comprehensible” sense, we want to be able to wrap our head around it completely and we don’t mind putting in a little bit of effort to achieve that comprehension, whereas other people prefer to hit the ground running.









  • Second that. I met my partner on OKC 8 years ago, and before I met them I also made lots of connections and had several dates with other people I met via OKC, some of whom I’m still friends with. The site certainly wasn’t perfect, all dating sites are straight up self-esteem murderers if you’re a heterosexual man, but as far as dating sites go, it was the best I’ve used because it actually tried to match you with people who shared values with you.

    At the same time I was also on tinder, and it was a barren wasteland of boring normies and felt more like a meat market than anything. I never had a meaningful match on there.







  • What I used to do was: I put jellyfin behind an nginx reverse proxy, on a separate vhost (so on a unique domain). Then I added basic authentication (a htpasswd file) with an unguessable password on the whole domain. Then I added geoip firewall rules so that port 443 was only reachable from the country I was in. I live in small country, so this significantly limits exposure.

    Downside of this approach: basic auth is annoying. The jellyfin client doesn’t like it … so I had to use a browser to stream.

    Nowadays, I put all my services behind a wireguard VPN and I expose nothing else. Only issue I’ve had is when I was on vacation in a bnb and they used the same IP range as my home network :-|