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
  • Kalcifer@sh.itjust.worksOPEnglish
    2·
    5 days ago

    create from it each day or so yo run on the images since it was last destroyed.

    Unfortunately, for this usecase, the GPU needs to be accessible in real time; there is a 10 second window when an image is posted for it to be processed [1].

    References
    1. “I just developed and deployed the first real-time protection for lemmy against CSAM!”. @[email protected]. [email protected]. Divisions by zero. Published: 2023-09-20T08:38:09Z. Accessed: 2024-11-12T01:28Z. https://lemmy.dbzer0.com/post/4500908.
      • §“For lemmy admins:”

        […]

        • fedi-safety must run on a system with GPU. The reason for this is that lemmy provides just a 10-seconds grace period for each upload before it times out the upload regardless of the results. [1]

        […]

    • db0@lemmy.dbzer0.comEnglish
      1·
      4 days ago

      You can actually run it in async model without pictrs safety and just have it scan your newly uploaded images directly from storage. It just doesn’t prevent upload this way, just deletes them.