Post

I play around a bit every once in a while with moving it server side, or do that just for the PDSs that have given a bypass key or added the IP to an allow list. I have thought about doing an unbranded version that PDSs can run their own, but then that's one more thing to run.

If the upload rate limit key was by ip & did that would help a bit, but even then, 1k upload for blobs is hard as accounts get older. Mostly just thinking out loud on it. I def think the way to go for bigger PDSs is probably their own migration tool so they can do their own bypass.

I think I may make a PR for the ip & did to be uploadBlob's rate limit key. At least then it could go on the backend to a queue and continue to upload blobs over the course of a few days for one account instead of all accounts going to that single PDS.

I think you really need a migration oauth scope that when granted bypasses blob limits

That would be sweet, I think it may still hit some of the same issues like when is too many blobs, etc. I think in the end the migrator that is going to go into the ref PDS will probably be the best and probably what other PDS implementations should do.

Okay, but say the 1 account had around... 2 million blobs... 🙃