zlacker

[return to "Had a call with Reddit to discuss pricing"]
1. miki12+gN[view] [source] 2023-05-31 20:48:07
>>robbie+(OP)
This feels like it's all priced for AI companies, TBH. This per-request pricing makes a LOT more sense if you assume that one particular piece of content will only be requested once in your company's history, saved on a server somewhere and used for training forever. You're not paying for a request being processed, you're not even paying to offset any advertising cost, you're essentially paying for the ability to use the requested piece of content forever. Maybe that's what Apollo should do, set up a huge cache layer and proxy all requests for the public data through there? I feel like the power law would apply here, so 80% of the requests would be for 20% of the content. Considering how popular the most popular subreddits are, I wouldn't be surprised if the balance was something like 99-to-1. Cache misses would still need to be fetched from the API itself, but that should drive costs down massively.

If the ToS allow this, the cache layer could even be shared across apps from different developers (developers supporting both iOS and Android might have an advantage here), making the costs even lower.

◧◩
2. paragr+Vc1[view] [source] 2023-05-31 23:13:16
>>miki12+gN
I feel like the better pricing strategy would be something similar to what the geospatial API platforms like Google Maps do, with their explicit no-caching or time-limited-caching clauses. E.g. you're actually prohibited from retaining results from say a geocode beyond 30 days IIRC.

Amazon made this explicit with their Geospatial API pricing ( https://aws.amazon.com/location/pricing/ - "Places" tab) - where the pricing for being able to store a result is 8x higher.

[go to top]