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
  • walden@sub.wetshaving.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    12 days ago

    We require applications, and most applications we get are extremely low effort and we don’t approve them. If you have open registrations you’ll be doing a lot of moderation for spam.

    Run the software that scans images for CSAM. It’s not perfect but it’s something. If your instance freely hosts whatever without any oversight, word will spread and all of a sudden you’re hosting all sorts of bad stuff. It’s not technically illegal if you don’t know about it, but I personally don’t want anything to do with that.

      • walden@sub.wetshaving.social
        link
        fedilink
        English
        arrow-up
        0
        ·
        12 days ago

        It’s called Lemmy-Safety of Fedi-Safety depending on where you look.

        One thing to note, I wasn’t able to get it running on a VPS because it requires some sort of GPU.

        • Kalcifer@sh.itjust.worksOP
          link
          fedilink
          English
          arrow-up
          0
          ·
          12 days ago

          One thing to note, I wasn’t able to get it running on a VPS because it requires some sort of GPU.

          This is good to know. I know that you can get a VPS with a GPU, but they’re usually rather pricey. I wonder if there’s one where the GPU’s are shared, and you only get billed by how much the GPU is used. So if there is an image upload, the GPU would kick on to check it, you get billed for that GPU time, then it turns off and waits for the next image upload.

          • db0@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            0
            ·
            11 days ago

            The software is setup in such a way that you can run it on your pc if you have a local gpu. It only needs like 2 gb vram

            • Kalcifer@sh.itjust.worksOP
              link
              fedilink
              English
              arrow-up
              0
              ·
              edit-2
              11 days ago

              That is a cool feature, but that would mean that all of the web traffic would get returned to my local network (assuming that the server is set up on a remote VPS), which I really don’t want to have happen. There is also the added downtime potential cause by the added point of failure of the GPU being hosted in a much more volatile environment (ie not, for example, a tier 3 data center).

              • db0@lemmy.dbzer0.com
                link
                fedilink
                English
                arrow-up
                0
                ·
                11 days ago

                Not all web traffic, just the images to check. With any decent bandwidth, it shouldn’t be an issue for most. It also setup in such a way as to not cause a downtime if the checker goes down.

                • Kalcifer@sh.itjust.worksOP
                  link
                  fedilink
                  English
                  arrow-up
                  0
                  ·
                  11 days ago

                  With any decent bandwidth, it shouldn’t be an issue for most.

                  It’s not only the bandwidth; I just fundamentally don’t relish the idea of public traffic being directed to my local network.