If you think this post would be better suited in a different community, please let me know.

Topics could include (this list is not intending to be exhaustive — if you think something is relevant, then please don’t hesitate to share it):

  • Moderation
  • Handling of illegal content
  • Server structure (system requirements, configs, layouts, etc.)
  • Community transparency/communication
  • Server maintenance (updates, scaling, etc.)
Cross-posts
  1. https://sh.itjust.works/post/27913098
  • KalciferOPEnglish
    1·
    10 days ago

    A lot of precedent exists for not complying.

    Would you mind citing a case? I’m curious.

    • finitebanjo@lemmy.world
      1·
      10 days ago

      NY Times vs Njalla

      Njalla does comply with some requests, and was forced to shut down some pirate bay instances at one point, though. Ghost is another privacy domain seller.

      Theres also a term for companies called “Bulletproof Registrars.” For example, some Malaysian Registrars apparently don’t have an address and cannot actually recieve most subpoenas.

      Mostly VPNs, I don’t know too much about similar cases with server hosts or domain sellers.

      • KalciferOPEnglish
        1·
        10 days ago

        NY Times vs Njalla

        Do you have an official record of them not complying with an official court-ordered subpoena? I looked into “NYT vs Njalla”, and it seems like it was the NYT making a private request to Njalla under threats of legal action, but no legal action followed [1][2].

        References
        1. “About those threats”. Blog. Njalla. Published: 2018-01-25. Accessed: 2024-11-12T00:33Z. https://njal.la/blog/about-those-threats/.
        2. “Njalla gives New York Times The Pirate Bay treatment”. Staff Writer. Mybroadband. Published: 2018-01-26. Accessed: 2024-11-12T00:36Z. https://mybroadband.co.za/news/internet/246265-njalla-gives-new-york-times-the-pirate-bay-treatment.html.
          • ¶10

            TorrentFreak reported that Njalla did not hear back from the New York Times after sending the response.