Switch to latest js-ipfs-api for /api/v0/dns lookups
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 338
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
### Background
- https://github.com/ipfs/js-ipfs-api/issues/501
- https://github.com/ipfs/js-ipfs/issues/904
- https://github.com/ipfs/js-ipfs-api/pull/665 (right now we send XHR manually)
### Tasks
- [ ] [Confirm](https://github.com/ipfs/js-ipfs-api/issues/501#issuecomment-358056476) that implementation in js-ipfs-api [v17.3.0](https://github.com/ipfs/js-ipfs-api/releases/tag/v17.3.0) is ready for use
- [ ] Update to the latest js-ipfs-api
- [ ] As a part of this task we should update option description and inform user that if DNSLINK lookup is enabled and public gateway is set as an active one, browser extension will send host names of every visited site to it (privacy leakage).
Contributor guide
Research direction
Start by reviewing js-ipfs-api issue 501, js-ipfs issue 904, and the v17.3.0 release to confirm the implementation is ready. Then locate the DNSLINK option and current manual XHR path in the extension. Done means updating js-ipfs-api, revising the option description, and warning about host-name disclosure when a public gateway is active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100