Just this guy, you know?

  • 0 Posts
  • 47 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle
  • zaphod@lemmy.catoGaming@beehaw.orgLet's discuss: Mass Effect
    link
    fedilink
    English
    arrow-up
    2
    ·
    6 months ago

    It’s all about tone. The original comment was incredibly combative and hyperbolic (“I utterly loathe Mass Effect. I consider it one of the worst pieces of science-fiction ever created.”) so much so that it would easily be mistaken for flamebait given the thread was likely to attract fans of the series.

    It certainly didn’t strike me as the start of an open-minded conversation.

    But in hindsight I should’ve just downvoted and moved on rather than commenting as I did, so that’s on me.



  • zaphod@lemmy.catoGaming@beehaw.orgLet's discuss: Mass Effect
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    6 months ago

    Ahh yes, the old “sticks and stones” defense that completely ignores human nature and basic decency. I use the same logic when I tell other people their babies are ugly. “Look, if you ask me your kid is an eyesore but it’s just my opinion so I don’t know why you’re so mad right now…”














  • That’s a goal, but it’s hardly the only goal.

    My goal is to get a synthesis of search results across multiple engines while eliminating tracking URLs and other garbage. In short it’s a better UX for me first and foremost, and self-hosting allows me to customize that experience and also own uptime/availability. Privacy (through elimination of cookies and browser fingerprinting) is just a convenient side effect.

    That said, on the topic of privacy, it’s absolutely false to say that by self-hosting you get the same effect as using the engines directly. Intermediating my access to those search engines means things like cookies and fingerprinting cannot be used to link my search history to my browsing activity.

    Furthermore, in my case I host SearX on a VPS that’s independent of my broadband connection which means even IP can’t be used to correlate my activity.


  • Honestly the issue here may be a lack of familiarity with how bare repos work? If that’s right, it could be worth experimenting with them if only to learn something new and fun, even if you never plan to use them. If anything it’s a good way to learn about git internals!

    Anyway, apologies for the pissy coda at the end, I’ve deleted it as it was unnecessary. Keep on having fun!


  • No. It’s strictly more complexity.

    Right now I have a NAS. I have to upgrade and maintain my NAS. That’s table stakes already. But that alone is sufficient to use bare git repos.

    If I add Gitea or whatever, I have to maintain my NAS, and a container running some additional software, and some sort of web proxy to access it. And in a disaster recovery scenario I’m now no longer just restoring some files on disk, I have to rebuild an entire service, restore it’s config and whatever backing store it uses, etc.

    Even if you don’t already have a NAS, setting up a server with some storage running SSH is already necessary before you layer in an additional service like Gitea, whereas it’s all you need to store and interact with bare git repos. Put the other way, Gitea (for example) requires me to deploy all the things I need to host bare repos plus a bunch of addition complexity. It’s a strict (and non-trivial) superset.



  • Agreed, which is why you’ll find in a subsequent comment I allow for the fact that in a multi-user scenario, a support service on top of Git makes real sense.

    Given this post is joking about being ashamed of their code, I can only surmise that, like I’m betting most self-hosters, they’re not dealing with a multi-user use case.

    Well, that or they want to limit their shame to their close friends and/or colleagues…