3 ms·

I don't want to sound like I'm being negative because this is really cool. When you promise that it will always be free, my immediate thought is that it's unsus

I don't want to sound like I'm being negative because this is really cool. When you promise that it will always be free, my immediate thought is that it's unsustainable. You're putting yourself into the position of one day breaking your promise or shutting down the service if you don't find some other business model to build on. Why not leave the door open for charging later on? oEmbed is a standard, therefore you're not locking anyone into your platform by making it free now and charging later. If they don't like the price, they can just switch back to Emed.ly or some other provider.

samsnelling 13y ago
I completely understand where you are coming from -- Just had this conversation with someone over twitter. oEmbed is a standard, and I really think there are a lot of cool things that can be done with it given the opportunity. Currently, the API is not rate limited, but this may be something I will have to look into in the future (I have only load tested up to 250req/sec). I will be adding a TOS in the few weeks. Where I do plan on charging, is expanding the api to include a "kitchen sink" where I include all data that I can possible grab from a URL. I think this will add real value to the API, and I will end up charging for it once it is finished (probably a few months down the road). oEmbed.io will always be free. If you want to pay or don't like my conditions, then you can go use embed.ly. But I genuinely feel like this is a contribution I am willing to make to the community. Hopefully that sheds a little more light on where my head is at with this!