Consider adding the hashed filesystem path

Open
#95 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
html
Domain
api, security

Research direction

Start by reading the File API specification and the duplicate-file use case described in this issue. No implementation file or test is identified, so first determine the relevant API surface and privacy requirements; done criteria should state whether a hashed filesystem path may be exposed without revealing filesystem structure.

Written by the indexing model from the issue text.

Description

feature request

At least having this hash for two files would let us know that the user has dropped the same file twice without exposing filesystem structure, and it would be far less demanding than calculating checksums on file contents.

Dominant language
HTML
Stars
118
Forks
52
Avg merge
9d 16h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from w3c/FileAPI

All issues in w3c/FileAPI

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.