mbommerez
mbommerez
## User observations * Users with lots of uploads in web3.storage experience really slow loading times. * Users with > 1000 uploads are not currently able to see them all...
### Context: As w3name will be available as a separate package and extracted from web3.storage, we want don't want to break current users' setup. ### Scope of this ticket: *...
### Overarching user needs / context: Currently users who use multiple tokens only find CIDs pinned using the first token displayed in their web3.storage account page. The Pinning Services API...
Once w3name is live, we need to remove this end point so everyone uses the new APIs. Note: This is done already in PR #1686 - it needs splitting out,...
Tasks - [ ] Drop `name` db table - [ ] Remove the running CRON job (ticket #1695) that migrates data to Durable Objects Note * The first task is...
If you send a pinning request for CID, but CID doesn't exist / node is offline, our PIN will stay stuck in "queued" status. We should abandon the operation after...
As discussed with @alanshaw - [sister issue for NFT](https://github.com/nftstorage/nft.storage/issues/1870) ### Overarching user needs / context: * We've recently had a user pin hundreds of thousands of CIDs that they do...
## Context Currently we are sending user notifications about storage usage over 75% of their limit. And we send W3s admin a daily email with people who have exceeded their...
This is a potential follow-up/enhancement for the account limiting feature. Currently, restricting accounts is done manually by admins based on the daily email alert that lists accounts which are over...
Sister issue to https://github.com/nftstorage/nft.storage/pull/1936 `status` filter is not a required param, it should be implicity set to 'pinned' when not set by the client.