• 0 Posts
  • 39 Comments
Joined 11 months ago
cake
Cake day: December 25th, 2023

help-circle
  • For me it’s very simple: NSFW can’t have a general acceptable definition because it depends on culture, background and personal beliefs. There is no way for a collection of communities to have a common definition and even if they would have: enforcement and interpretation is still done by volunteers.

    Therefore All is never safe for work unless I know that my tolerance is lower than all communities within lemmy AND I’m fine with an accidental penis or breast due to human error.



  • Who should do this vetting though? The internet was built up with the idea of technical neutrality - everything else came on top. TLDs came later and were used to either describe the origin of a page or its intended(!) use. That leads to the case that not only can a propaganda outlet mark itself as “info” - it’s actually historically correct to do so as it’s about what the host wants to communicate.

    ICANN, the organisation behind the TLDs, actually always struggles with this btw. A more recent example was the decision which domain should be reserved for local name services. It took y long time (I think years overall) to get to: .internal (edited, brainfart)













  • Sorry for that hazzle! My story is quite different but exactly the same: my father in law “didn’t get around” to do backups and lost his HDD full of important photos and documents.

    That said: I’m quite sure that there are huge regional differences. Without knowing your country just keep that in kind.

    I phoned around several companies. I had a simple first benchmark: either directly speak with a tech savvy person (big plus) or being forwarded to one.

    That eliminated already half of them who had more business than tech.

    The important thing to look out for in hindsight is their transport standards, i.e. how does the broken disk get to them and how does the rescued data get back?

    Be careful of companies who have the potential to take the disk hostage (“we give a quote after first analysis”).

    Paying per file rescued sounds weird to me because that’s not how the rescue process usually works from what I understand.

    The company I went with was very upfront about the best and worst case what to expect, etc. They were very transparent about the risks and their process as well.

    Nearly all of the critical data was rescued and delivered on an encrypted disk. The key was handed out after final payment - a process I quite liked.

    In short: talk to the people and find a way to figure out whom you trust most.





  • (not OP but same boat) Doesn’t really matter to me because google knows my servers external IP which is a non-issue: I don’t expect google to try to attack me individually but crawl data about me. There is no automatic link between my server and my personal browsing habits.

    In terms of attack vector vs ease of use , self hosting searxng is a nobrainer for me - but I do have an external server available for things like that anyway so no additional overhead needed.