Attendees
- @hannahhoward
- Jorropo
- lidel
Notes
- Stargate: claim that the gateway is the most widely used data transfer protocol for IPFS content
- some things missing from the gateway HTTP protocol
- it’s missing verifiable pathing: CAR files don’t give you the blocks to verify the content
- missing multipeer info
- missing multipeer tooling
- Stargate: it’s just a new response format for gateway queries
- defines a new MIME response format:
application/vnd.ipld.car+stargate
- additional query parameters that you can’t do with the gateway currently
- how it works:
- give it a normal gateway query `GET/
- response is a
stargate message
, it’ll be either one of two things
- it uses CAR files, because they’re well known
- I’ve gone back & fourth on weather I should be using CARs
- why HTTP? it has some good properties
- it’s design is to support lots of caching & being able to get
- URL as cache key
- A URL is a great constraint for a selector
- we often go back & fourth on the kinds of queries we support, but se should look at the hueristic of “if it can’t fit in a URL, it might not be a good querying language”
- lidel’s notes on how this builds upon previously discussed concepts: https://github.com/ipfs/specs/issues/348#issuecomment-1387627152