Skip to content

Support consuming https://badbits.dwebops.pub/badbits.deny #126

Description

@lidel

We want rainbow to be enough to do badbits handling at ipfs.io / dweb.link.
If it is good enough for us, it will be good enough for people who self-host.

Unfortunately, https://badbits.dwebops.pub/badbits.deny is not append-only (https://github.com/protocol/badbits.dwebops.pub/issues/32733), and HTTPSubscriber from nopfs assumes the list is. We also gave bug around CAR handling.

Below is a list of known issues that we need to close to make it a viable recommendation:

Activity

  1. added
    need/triageNeeds initial labeling and prioritization
    on Apr 22, 2024
  2. added this to the v1.3 milestone on Apr 22, 2024
  3. added
    P1High: Likely tackled by core team if no one steps up
    dif/expertExtensive knowledge (implications, ramifications) required
    effort/daysEstimated to take multiple days, but less than a week
    and removed
    need/triageNeeds initial labeling and prioritization
    on Apr 23, 2024
  4. changed the title [-]Support badbits.dwebops.pub[/-] [+]Support consuming https://badbits.dwebops.pub/badbits.deny[/+] on Apr 23, 2024
  5. removed this from the v1.3 milestone on May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High: Likely tackled by core team if no one steps updif/expertExtensive knowledge (implications, ramifications) requiredeffort/daysEstimated to take multiple days, but less than a week

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions