Marcos Wright-Kuhns

With ruby-oembed 0.12.0 (released today) you can now use the built-in [Noembed](https://noembed.com/) provider as a direct replacement for the built-in Embedly provider. ```ruby OEmbed::Providers.register_all OEmbed::Providers.register_fallback(OEmbed::Providers::Noembed, OEmbed::ProviderDiscovery) ```

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. ##...

Interesting. Thanks for reporting this!

I was trying to think through the use-cases for this. The primary use-case I was coming up with was for people that need to regularly collect both the http _and_...

Yeah, I do like the idea of adding official SSL-ready providers, and I like the sounds of `OEmbed::Providers.register_all(:https)` too! Seems like a solid path forward.

Nokogiri & ActiveSupport::JSON are both covered. So close to closing this one!

Hi @hmans, Have you tried using the json gem instead of ActiveSupport's JSON? Either `require "json"` before you require ruby-oembed *or* call `OEmbed::Formatter::JSON.backend = 'JSONGem'` I likely won't have time...

Yes, I can confirm that the `start_at` values are indeed Unix timestamps in milliseconds and that the official API documentation (e.g. https://developer.pagerduty.com/api-reference/b3A6Mjc0ODIwNw-create-an-event-rule-on-a-service ) should definitely be corrected too. You can...

Acknowledged that the current wording in the documentation is misleading since `severity` is indeed a PD-CEF field. The solution you can use today is to use [the `severity` action](https://registry.terraform.io/providers/PagerDuty/pagerduty/latest/docs/resources/event_orchestration_service#severity) to...

No, currently it’s not possible to send any additional headers with requests made by this library. Given [Vimeo’s documented need for a header](https://developer.vimeo.com/api/oembed/videos) this seems like a totally fair feature...