ash
When adding/replacing pins with the pinning service API... We currently put these in the DB without validating the data is an array of mutliaddr. Note: should be array of strings...
We've recently had a user pin hundreds of thousands of CIDs that they do not have access to and can never retrieve. This adds load to our cluster and dagcargo...
Currently we check the _CID_ is not on the deny list, but it's possible for a CID + path to be on the deny list, meaning that anything below a...
A few quick suggestions for the gateway docs (https://nft.storage/docs/concepts/gateways/#the-nftstorage-gateway): * Under "The NFT.Storage gateway" there's too many words before the gateway URL! I'd make it big, front and centre after...
The pins cron job is currently filtering out CIDs that are stored on nft2. This needs to be removed when all data has finished copying over to nft3. https://github.com/nftstorage/nft.storage/pull/1265#discussion_r800757323
> Part of UX improvements for sharing local files (#342) Uploading is currently broken when dropping a directory
Some suggestions to tidy up the quota exceeded email:
refs https://github.com/web3-storage/web3.storage/pull/1455#discussion_r897851572 In NFT.Storage we have just 1 compose file that sets up all the things but we have multiple in Web3.Storage. https://github.com/nftstorage/nft.storage/blob/main/packages/api/docker/docker-compose.yml If we want to keep the separation...