Marcin Rataj
Marcin Rataj
[IPIP-351: IPNS Signed Records Response Format on HTTP Gateways](https://github.com/ipfs/specs/pull/351) will return a raw IPNS record, allowing a custom light client to verify IPNS without having to run DHT client. Users...
Extracted loose ends from IPIP-337 (to unblock it), but we need to address below at some point. cc @guseggert @aschmahmann @masih ## Open questions - How do we deal with...
This is placeholder, we need UnixFS specs #331 to land first, then we will be able to refer to that in Gateway/Pathing specs. Ref. - https://github.com/ipfs/kubo/issues?q=is%3Aissue+is%3Aopen+symlink - + suggestion from...
Extracted from https://github.com/ipfs/specs/pull/382: :thought_balloon: would it be possible to separate content from website, so it is easier to work with for people who refuse to deal with anything other than...
Extracted from https://github.com/ipfs/specs/pull/382: `"template": "template.html",` It does not seem to bring much value in the top level dir, can we move it to `src/_includes` to reduce noise?
We have a dedicated https://dnslink.dev website with loose specification, but it lacks necessary maintenance and love. It is also written from IPFS-agnostic perspective, and does not go too deep into...
This is a placeholder issue for creating IPIP to add support for storing explicit MIME/Content-Type in UnixFS DAG itself, like we already do for opt-in `mode` and `mtime`, and acting...
@ipfs/specs-stewards team was created as part of https://github.com/ipfs/specs/pull/289 We need to decide who should belong to the team, sharing responsibility of triaging and reviewing improvement proposals (#289). My initial idea...
We have various routing types, and no high level spec + specific routing types also lack basic specs. Routing specs we should have: - [ ] High level overview of...
Powerful tool used by other projects: ### Bikeshed Python / Batch > Bikeshed is a spec-generating tool that takes in lightly-decorated Markdown and spits out a full spec, with cross-spec...