search

ethersphere / gateway-ui

Swarm Gateway website
https://gateway.ethswarm.org
BSD 3-Clause "New" or "Revised" License
11 stars 11 forks source link

Document and standardize (?) the meta information that Gateway uses #109

Open AuHau opened 3 years ago

mfw78 commented 3 years ago

As part of this, as mentioned in the discord, it could be handy to know perhaps the neighborhood of the bee node that was responsible for responding to a request. The use case that I have is when using the bzz.link gateway, it works most of the time, though some bee nodes report a 404 error when trying to open the specific site.

An alternative to this would be for a swarm-cli tool to automate the stewardship of missing chunks in neighborhoods and report on those missing chunks by neighborhood.

AuHau commented 3 years ago

@mfw78 not sure if you talk about the same thing like I do. When there is an uploaded file using Gateway it is actually uploaded as Collection that consists of several files - the uploaded file and metafile(s) that stores preview (for images) and generic metadata (like file name, file size, file type). Then the index file is pointed to the original uploaded file.

I am talking about standardizing the metafiles so we could use that across the ecosystem like for example in the pastebee.com.

mfw78 commented 3 years ago

@AuHau Sure, I understand. That's a good idea. I'm approaching it more broadly from the use of a gateway for other projects, and particularly when the health of the gateway is important to understand how this may be impacting a dApp for which it depends.

Issue #110 refers.