Embedly deprecating free tier

[vietqhoang]

Embedly is removing the free tier for their API.

What is the opinion of this library in regards to paid aggregators? The library heavily relies on Embedly and the deadline for their API transition is April 17th.

The announcement can be found here.

[metavida]

That's disappointing! You have a few options with this library:

1. If you decide to pay for Embedly, you can add your API key to the Embedly object: OEmbed::Providers::Embedly.endpoint += "?key=#{my_embedly_key}"
2. If it's acceptable to lose support for some of the sites that Embedly had added custom support for, you can use the built-in providers and provider discovery in this gem to maintain decent free functionality :

OEmbed::Providers.register_all
OEmbed::Providers.register_fallback(OEmbed::ProviderDiscovery)

[metavida]

I've also been meaning to create an official provider for https://noembed.com/ so I suppose this would be a great time to make that happen 😃

[metavida]

With ruby-oembed 0.12.0 (released today) you can now use the built-in Noembed provider as a direct replacement for the built-in Embedly provider.

OEmbed::Providers.register_all
OEmbed::Providers.register_fallback(OEmbed::Providers::Noembed, OEmbed::ProviderDiscovery)

[vietqhoang]

Thanks for the hard work!

[metavida]

A new comment on this very-old thread, because once Pull #78 is released, it will now be possible to add the Embedly key to the built-in provider's required_query_params list.

Advantages

This would allow people to inject their Embedly key using either an environment variable:

ENV['OEMBED_EMBEDLY_KEY'] #=> 'your key'
OEmbed::Providers.register_fallback(OEmbed::Providers::Embedly)

or using a setter:

OEmbed::Providers::Embedly.key = @your_key
OEmbed::Providers.register_fallback(OEmbed::Providers::Embedly)

It will also save folks some confusion by preventing the provider from sending requests to Embedly without a key being set.

Breaking Change!

However, updating the built-in provider to use the required_query_params feature means that folks using the OEmbed::Providers::Embedly.endpoint += "?key=#{my_embedly_key}" work-around must change their code to use one of the new methods of setting their key. Unless I figure out some provider-specific method of detecting a key being injected into the URL.