Gregory's Server
[3/5]
After lengthy negotiation NC eventually acquiesced to handing off datacrystal, and to swapping out the file-serving back end with an S3 bucket as an initial transition step while a replacement could be built. It'd help relieve the cost burden.
It took a lot of convincing, and I don't think he really understood that S3 was *way* more cost-effective than the way files were currently being served. At one point he posted "Sending thumb drives to Canada doesn't help" like he couldn't just upload the files into the bucket.
==>
[4/5]
One real kick in the teeth came after switching the back-end to AWS S3. AWS was the initial pick because it was obvious that if something didn't happen fast, the site would die, and AWS was the easiest initial choice.
Discord staff set up the S3 bucket, and had to walk NC through the changes that needed to be made to the back-end. To help reduce the financial burden on NC, Discord staff gladly offered to pay the S3 bill -- to the tune of $200 or so per month.
After some further research, it became apparent that Discord staff could save a significant amount of money by changing S3 providers. The new bucket was set up, but when the time came to make the change NC refused to do it, even though he was not the one footing the bill.
==>
[4/5]
One real kick in the teeth came after switching the back-end to AWS S3. AWS was the initial pick because it was obvious that if something didn't happen fast, the site would die, and AWS was the easiest initial choice.
Discord staff set up the S3 bucket, and had to walk NC through the changes that needed to be made to the back-end. To help reduce the financial burden on NC, Discord staff gladly offered to pay the S3 bill -- to the tune of $200 or so per month.