ipfs/ipfs-companion

Inspect current impl. in Brave vs Chrome of Local Network Access

Open

#1364 opened on Mar 16, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (1,992 stars) (364 forks)batch import
P2area/bravearea/chromiumhelp wantedneed/analysis

Description

Test behavior in Brave, maybe we can remove special-casing now:

Contributor guide

Tech stack
javascript
Domain
security
Issue type
refactor
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Browser extension developmentIPFS basicsNetwork security concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
First, review the linked Brave issue (51843) and the IPFS in web browsers discussion (#184) to understand the current special casing. Then, set up a test environment with both Brave and Chrome to compare how Local Network Access is handled. Check the ipfs companion source code for any existing logic related to local network access and identify where special casing may be removed if behavior now aligns.