Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
3 tasks
lidel opened this issue Apr 22, 2024 · 0 comments
Open
3 tasks

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

lidel opened this issue Apr 22, 2024 · 0 comments
Labels
dif/expert Extensive knowledge (implications, ramifications) required effort/days Estimated to take multiple days, but less than a week P1 High: Likely tackled by core team if no one steps up
Milestone
v1.3

Comments

@lidel
Copy link
Member

lidel commented Apr 22, 2024 •
edited

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:
@lidel lidel added the need/triage Needs initial labeling and prioritization label Apr 22, 2024
@lidel lidel added this to the v1.3 milestone Apr 22, 2024
@lidel lidel added P1 High: Likely tackled by core team if no one steps up dif/expert Extensive knowledge (implications, ramifications) required effort/days Estimated to take multiple days, but less than a week and removed need/triage Needs initial labeling and prioritization labels Apr 23, 2024
@lidel lidel changed the title Support badbits.dwebops.pub Support consuming https://badbits.dwebops.pub/badbits.deny Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dif/expert Extensive knowledge (implications, ramifications) required effort/days Estimated to take multiple days, but less than a week P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Milestone
v1.3
Development

No branches or pull requests
1 participant
@lidel