Marcin Rataj
Marcin Rataj
@hsanjuan fyi this PR updates `go-ds-pebble` to version with updated constructor from https://github.com/ipfs/go-ds-pebble/pull/39 by @gammazero
Ref. https://docs.libp2p.io/concepts/nat/circuit-relay/ The page should mention that - relays are limited by default (time/bytes) - relays only allow specific libp2p protocols to be relays (e.g. ping, identify, hole punching ones)...
Seems that w3name uses old version of https://www.npmjs.com/package/ipns, missing two changes: - `v3.0.0` brings security fix - https://github.com/ipfs/js-ipns/pull/180 - record `ipns.create` continues to create records with both V1 and V2...
> Filling public issue because this died in private channels and threads many times > Part of work towards https://github.com/ipshipyard/roadmaps/issues/9 and https://github.com/ipshipyard/roadmaps/issues/15 > This is also helping with webseeds from...
> Writing down clarification proposed by @hsanjuan idea from https://github.com/ipfs/boxo/issues/862#issuecomment-2693727250 This PR clarifies that trustless gateways and clients SHOULD avoid returning and processing HTTP 3XX redirects. Gateway URL changes should...
[trustless-gateway.ts#L92](https://github.com/ipfs/helia/blob/95911757de749bdf8cab7591f0fa5473fd1af9cf/packages/block-brokers/src/trustless-gateway/trustless-gateway.ts#L92) does not seem to have any protection against being tricked into fetching terabytes of data. Helia should have a response size check and config option similar to [HTTPRetrieval.MaxBlockSize](https://github.com/ipfs/kubo/blob/master/docs/config.md#httpretrievalmaxblocksize) from...
> Filling issue based on triage discussion today, cc @gammazero if below prior art context is useful Currently, we have no "requests in flight" cap in `boxo/gateway` and require reverse...
We need to find a solution to situation where defunct gateways start returning redirects back to `ipfs.io` and `dweb.link`, effectively acting as amplification vector. There is some prior art solution...
This is similar to https://github.com/ipfs/boxo/issues/771 but at the time of writing this _all_ UD DoH resolvers seem to be down, breaking DNSLink websites loaded via `boxo/gateway` if the domain name...
> Extracted from [internal slack thread](https://ipshipyard.slack.com/archives/C06TGA7P3B2/p1743685974227309?thread_ts=1743684015.167559&cid=C06TGA7P3B2) Right now (2025Q1, rainbow v1.12), Rainbow will resolve every DNSLink domain passed via `Host` header, which is not the best configuration for public HTTP...