Archive.is מתקשה ב-oneboxing

סיכום מבוסס בינה מלאכותית

The discussion revolves around issues with Archive.is URLs not being properly oneboxed in Discourse, with users noting that the service returns error codes like 429 and 403. diakopter asks how to extend Onebox to support custom parsing for sites like Archive.is, particularly since Twitter handles such URLs with special cards. codinghorror points out that Archive.is lacks required OpenGraph tags, though diakopter notes that the site does include an og:image and a twitter:description, raising questions about why Onebox requires og:image and treats og:description as mandatory despite the spec marking it as optional. diakopter also provides an example of another failing URL (NBC News) with a 403 error, highlighting broader parsing issues.

Hello! I am curious if there’s a way to extend the Onebox parsing feature to customize how it generates the Twitter-like cards for certain URL pre-fetches.

For instance, I would like it to generate a preview for URLs such as the following

which on twitter displays something like this

So you want special support for archive.is? It looks like it’s missing the tags per the error message.

http://archive.is/mgHP8

I get error code 429, so that service appears a bit wonky:

well I suppose I’m wondering how to develop extensions to Onebox on my own, since I’ve found a few sites that Twitter apparently has special-cased and Discourse hasn’t..

Is there an extension or pluggable point for plugin authors to add custom parsing passes to Onebox?

Thanks for the reply!

oh! I see it has twitter-specific Opengraph tags. I wonder if those could be used..

Note that it does have an og:image property, but only a twitter:description :upside_down_face:

In case it helps diagnose the 429 http response, here’s another example of a Onebox fetch that fails, but with a different (403) response: Iran's hard-line judiciary chief Ebrahim Raisi registers to run for presidency

to clarify this bug report slightly:

  1. the error message says that there isn’t an og:image tag, even though there is one (see toward the bottom of screenshot).
  2. Also, the og:description tag is explicitly marked as optional by the OpenGraph spec, so why does Onebox require it?

Thank you