Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

NodeBB

  1. Home
  2. Technical Discussion
  3. Auto-import of deny lists

Auto-import of deny lists

Scheduled Pinned Locked Moved Technical Discussion
dniactivitypubiftas
7 Posts 3 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • julian@activitypub.spaceJ This user is from outside of this forum
    julian@activitypub.spaceJ This user is from outside of this forum
    julian@activitypub.space
    wrote last edited by
    #1

    NodeBB has a very simple allow/deny list capability at present. You paste in a bunch of newline-separated domains, and we block (or optionally, only allow) them all.

    On the road to more fine-grained controls, I discovered that IFTAS publishes a Do Not Interact list in an importable CSV format.

    As maintenance of these lists is important (adding new entries as well as handling removals), it looks to be increasingly important that I add into NodeBB the functionality to follow these lists automatically and update as necessary.

    1 Reply Last reply
    0
    • thisismissem@activitypub.spaceT This user is from outside of this forum
      thisismissem@activitypub.spaceT This user is from outside of this forum
      thisismissem@activitypub.space
      wrote last edited by
      #2

      The problem with the CSV format, is that it doesn't tell you what was removed, only the current state of the data, so you'd need to store previous CSV files to detect removals by diffing new versus old.

      1 Reply Last reply
      1
      • thenexusofprivacy@infosec.exchangeT This user is from outside of this forum
        thenexusofprivacy@infosec.exchangeT This user is from outside of this forum
        thenexusofprivacy@infosec.exchange
        wrote last edited by
        #3

        @julian you might want to check out what GoToSocial does on this front -- it seems very well thought out

        1 Reply Last reply
        0
        • julian@activitypub.spaceJ This user is from outside of this forum
          julian@activitypub.spaceJ This user is from outside of this forum
          julian@activitypub.space
          wrote last edited by
          #4

          This is not an issue if you are rebuilding the instance wide deny list every time it is updated.

          In that case, whenever the list is rebuilt any removed entries will simply not appear in the new list.

          1 Reply Last reply
          0
          • thisismissem@activitypub.spaceT This user is from outside of this forum
            thisismissem@activitypub.spaceT This user is from outside of this forum
            thisismissem@activitypub.space
            wrote last edited by
            #5

            julian in which case you loose anything you manually needed to add. We've had so many conversations about this..

            1 Reply Last reply
            0
            • julian@activitypub.spaceJ This user is from outside of this forum
              julian@activitypub.spaceJ This user is from outside of this forum
              julian@activitypub.space
              wrote last edited by
              #6

              thisismissem not necessarily, I'm planning to build this out as a separate collection of CSV lists, in addition to a list you manually curate. 🙂

              1 Reply Last reply
              0
              • thisismissem@activitypub.spaceT This user is from outside of this forum
                thisismissem@activitypub.spaceT This user is from outside of this forum
                thisismissem@activitypub.space
                wrote last edited by
                #7

                Just spend the tiny bit of extra time and implement basic support for federation policies. Keep track of data snd where it comes from, such that you can react to changes over time

                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                Powered by NodeBB Contributors
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • World
                • Users
                • Groups