Marcin Rataj

Mentioning verified fetch at https://docs.ipfs.tech/install/, which is common entry point we send to people. Preview: https://bafybeiaofkeqz22gktyvoykf2h3qpdshzcvogdc4zacfj4uf2rwubahu5e.on.fleek.co/install/

Did not dig into it, but seems the pubsub API changed at some point: 

Renaming resource to follow latest libp2p spec draft and go-libp2p: https://github.com/libp2p/specs/pull/508#discussion_r1550303385 https://github.com/libp2p/specs/pull/508/commits/3c0ac4033dd640425e047ee448771dbca244ba68 https://github.com/libp2p/go-libp2p/pull/2757

This is a placeholder issue for writing spec and tracking implementation. The need is to expose equivalent of `ipfs files stat`'s `Size` and `CumulativeSize` on HTTP gateway somehow, allowing light...

## Problem IPNS Record spec lists Validity, TTL and Seq as uint64: - https://specs.ipfs.tech/ipns/ipns-record/#ttl-uint64 - https://specs.ipfs.tech/ipns/ipns-record/#sequence-uint64 - https://specs.ipfs.tech/ipns/ipns-record/#validity-type-uint64 ..but this only applies to the protobuf fields from IPNS v1. For...

Closes https://github.com/ipfs/specs/issues/467 by updating `Last-Modified` section. We forgot to do that as part of TTL cleanup, and that created contradiction reported by @SgtPooki (thx!)

IPIP-462: Ipfs-Path-Affinity on Gateways

2

## TLDR Extends Gateway specs with optional `Ipfs-Path-Affinity` request header. That is all. If header is present in request, gateway can leverage this optional hint to improve content routing. The...

Manifest files for unixfs loaded via HTTP Gateway

8

This is a placeholder issue for creating a spec for "content root's manifest files" which would be part of the data published on IPFS (eg. `/ipfs/CID/_something` or `/ipfs/CID/.well-known/ipfs/foo`) that provides...

Need for IPIP: Data Onboarding via HTTP POST (and future ipfs:// POST|PUT)

10

## Problem statement HTTP Gateways are the most successful way for retrieving content-addressed data. Successful use of HTTP for retrieval use cases proves that IPFS does not replace HTTP, but...

The goal of this specification is to close #432 and define a subset of possible content paths that ensures compatibility with existing HTTP and Web Platform standards, and have clear...