Conversation

Notices

1. Embed this notice
   Evan Prodromou (evan@cosocial.ca)'s status on Thursday, 28-Dec-2023 12:48:35 JST Evan Prodromou

   I'm interested in hearing from #ActivityPub developers who've successfully mapped #OpenGraph properties from <meta> tags in Web pages onto the `Page` type and its properties in AS2.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Thursday, 28-Dec-2023 13:24:03 JST Evan Prodromou

     in reply to

     • infinite love ⴳ

     @trwnh that's about what I'd expect as a mapping. Have you seen it used to create `Page` objects, for link previews?

   • Embed this notice
     infinite love ⴳ (trwnh@mastodon.social)'s status on Thursday, 28-Dec-2023 13:24:04 JST infinite love ⴳ

     in reply to

     @evan hot take, why not just use the opengraph namespace/iris directly?

     if the goal is to reduce duplication of data, i'd probably recommend the following

     - og:title = as:name
     - og:type = og:type (no way to map this one)
     - og:url = as:url
     - og:image = as:image

     for optional ones:

     - og:description = as:summary

     all the other ones i'd just use ogp.me iris directly

   • Embed this notice
     infinite love ⴳ (trwnh@mastodon.social)'s status on Thursday, 28-Dec-2023 13:59:44 JST infinite love ⴳ

     in reply to

     @evan i have only ever seen link previews implemented out-of-band due to trust issues :/

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Thursday, 28-Dec-2023 13:59:44 JST Evan Prodromou

     in reply to

     • infinite love ⴳ

     @trwnh you mean, on the receiving servers?

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Thursday, 28-Dec-2023 14:47:01 JST Evan Prodromou

     in reply to

     • Ben Pate 🤘🏻

     @benpate nice!

   • Embed this notice
     Ben Pate 🤘🏻 (benpate@mastodon.social)'s status on Thursday, 28-Dec-2023 14:47:02 JST Ben Pate 🤘🏻

     in reply to

     @evan Here’s my take, hope it helps?

     https://github.com/benpate/sherlock

     Sherlock is a #Golang library that assembles any data/metadata it can find on a URL (including #WebFinger, #RSS, #OpenGraph, and #IndieWeb #MicroFormats ) and returns an #ActivityStream back to its caller. There’s composable add-ons for caching and other custom rules.

     Overall, mapping to ActivityStreams was pretty easy. Sherlock is the key component in #Emissary that helps it participate in many different social webs.

   • Embed this notice
     Renaud Chaput (renchap@oisaur.com)'s status on Thursday, 28-Dec-2023 16:02:43 JST Renaud Chaput

     in reply to

     @evan 👀 interested in the replies, as we are thinking about how to federate link previews to avoid having each instance fetch it (and DDOS the link’s server)

     clacke likes this.
   • Embed this notice
     small circle 🕊 in calmness (smallcircles@social.coop)'s status on Thursday, 28-Dec-2023 23:43:44 JST small circle 🕊 in calmness

     in reply to

     • infinite love ⴳ
     • Ben Pate 🤘🏻

     @evan @benpate @trwnh

     There's a #FediverseIdea on this topic that you might add comments / new insights to:

     https://codeberg.org/fediverse/fediverse-ideas/issues/26

     clacke likes this.
   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Friday, 29-Dec-2023 00:44:15 JST Evan Prodromou

     in reply to

     • infinite love ⴳ

     @trwnh another option is accepting the sender-provided metadata to start, and then verifying on a schedule that recognizes that thundering herd problem -- say, a randomized delay between 1 and 300 seconds, with an exponential backoff. And I definitely think having a trusted shared caching server can help immensely.

   • Embed this notice
     infinite love ⴳ (trwnh@mastodon.social)'s status on Friday, 29-Dec-2023 00:44:16 JST infinite love ⴳ

     in reply to

     @evan yes, and it creates a sort of "thundering herd" unintentional ddos for web sites on underpowered providers. there have been ideas on how to solve the trust issue, like randomly verifying some small subset and tracking reputation, or like deferring to a semi-centralized pre-trusted "link preview provider" that is shared between several instances, or even simply ignoring the issue and depending on people to report misleading links. (i prefer the provider approach)

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Friday, 29-Dec-2023 01:10:55 JST Evan Prodromou

     in reply to

     • Renaud Chaput

     @renchap I'll definitely write up a proposal for it.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Friday, 29-Dec-2023 02:19:23 JST Evan Prodromou

     in reply to

     • infinite love ⴳ
     • Emelia 👸🏻

     @thisismissem @trwnh doesn't have to be either-or. Can be also-and. Use sender-provided metadata, and possibly re-verify with a trusted API.

   • Embed this notice
     Emelia 👸🏻 (thisismissem@hachyderm.io)'s status on Friday, 29-Dec-2023 02:19:25 JST Emelia 👸🏻

     in reply to

     • infinite love ⴳ

     @evan @trwnh I'm in favour of third-party providers that give a standardised API for going from link URL to Page or similar representation & provides hashes of the returned object allowing easy verification with the provider

   • Embed this notice
     Kevin Marks (kevinmarks@xoxo.zone)'s status on Friday, 29-Dec-2023 17:45:39 JST Kevin Marks

     in reply to

     @evan we've been looking at that in microformats recently
     https://microformats.org/wiki/metaformats

     clacke likes this.
   • Embed this notice
     Kevin Marks (kevinmarks@xoxo.zone)'s status on Friday, 29-Dec-2023 17:45:43 JST Kevin Marks

     in reply to

     • Ryan Barrett

     @evan this could lead to an OGP to AS2 mapping by @snarfed.org in granary.io

     clacke likes this.