ipfs/ipfs-companion

Switch to latest js-ipfs-api for /api/v0/dns lookups

Open

#357 opened on Jan 16, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (1,992 stars) (364 forks)batch import
good first issuehelp wantedkind/maintenancestatus/ready

Description

Background

Tasks

  • Confirm that implementation in js-ipfs-api 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

Tech stack
javascript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic JavaScriptGitBrowser extension developmentIPFS concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
First, read the linked issues and PR to confirm that the implementation in js ipfs api v17.3.0 is ready for use. Then update the dependency in package.json and ensure the DNS lookup functionality works correctly. Finally, modify the option description to inform users about privacy leakage when using a public gateway. Look at the current codebase for how the API is used and where option descriptions are defined.