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
  • db0@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    12 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.

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

          Yeah, that was poor wording on my part — what I mean to say is that there would be unvetted data flowing into my local network and being processed on a local machine. It may be overparanoia, but that feels like a privacy risk.

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

            I don’t see how it’s a privacy risk since you’re not exposing your IP or anything. Likewise the images are already uploaded to your servers, so there’s no extra privacy risk for the uploader.

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

              “Security risk” is probably a better term. That being said, a security risk can also infer a privacy risk.

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

                  For clarity, I’m not claiming that it would, with any degree of certainty, lead to incurred damage, but the ability to upload unvetted content carries some degree of risk. For there to be no risk, fedi-safety/pictrs-safety would have to be guaranteed to be absolutely 100% free of any possible exploit, as well as the underlying OS (and maybe even the underlying hardware), which seems like an impossible claim to make, but perhaps I’m missing something important.

                  • db0@lemmy.dbzer0.com
                    link
                    fedilink
                    English
                    arrow-up
                    1
                    ·
                    edit-2
                    5 days ago

                    You mean an exploit payload embedded in an image, and pwning a system parsing that image through python PIL? While there’s never a 100% chance of anything, you’re more likely to be struck by lightning than this coming to pass and at that point you’re at more security risk at using the internet altogether.