The technical things being described here put a bottom on the operational costs of standing up the servers ex nihilo.
Yes, you can stand up a server that can respond to 2300r/s and handle 200GB/day (6 TB/month which is another few hundred dollars)... and the storage for it.
The problem with standing this up is the "how do you pay for it in a way that isn't out of the goodness of your own heart" - because part of the reason people are using these is to avoid paying Reddit or see advertisements.
You will also need someone to answer take down requests for whatever legal reason exists. If you do not handle the takedown and leave it to be unmoderated, there are a number of other applications that serve as an example for the community that forms there.
The difficult part is not paying for compute, egress, or storage. The difficult part is figuring out how to get the customers to pay for it and to pay for the staff needed to maintain server and legal availability.
Writing an app that acts as a conduit for data is quite a different than than being responsible for hosting a service that provides that data.
Yes, you can stand up a server that can respond to 2300r/s and handle 200GB/day (6 TB/month which is another few hundred dollars)... and the storage for it.
The problem with standing this up is the "how do you pay for it in a way that isn't out of the goodness of your own heart" - because part of the reason people are using these is to avoid paying Reddit or see advertisements.
You will also need someone to answer take down requests for whatever legal reason exists. If you do not handle the takedown and leave it to be unmoderated, there are a number of other applications that serve as an example for the community that forms there.
The difficult part is not paying for compute, egress, or storage. The difficult part is figuring out how to get the customers to pay for it and to pay for the staff needed to maintain server and legal availability.
Writing an app that acts as a conduit for data is quite a different than than being responsible for hosting a service that provides that data.