# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 15
# self = https://watcher.sour.is/conv/2sgglqa
We need to implement Twitter Cards on Yarn. Right now it has support for Open Graph, but missing Twitter Cards. Thatβs a must for sharing a twt, or a yarn on that social medium.
Wait what?! What's this thing (Twitter is normally blocked here) and why would we do this?
What problem are we solving?
Wait what?! What's this thing (Twitter is normally blocked here) and why would we do this?
What problem are we solving?
@prologic we will gain the ability to share a link to a twt or a yarn on Twitter, and have it render nicely, just like Open Graph does in other mediums. We will gain the ability to provide exposure.
Doesn't a single link to a Twt's permalink already render nicely? It does for me everywhere else π€
Doesn't a single link to a Twt's permalink already render nicely? It does for me everywhere else π€
@prologic nope, it doesnβt render at all OK Twitter. Twitter has its own headers that need to be added.
Sorry but I'm not understanding why we would want to implement Twitter Cards here... We (_or rather me at the time_) chose to implement OpenGraph because I _thought_ (_perhaps I'm wrong_) it was the most commonly adopted standard for rendering a link to a piece of content somewhere else where that somewhere else commonly supports OG Hmmmm ? π€
Sorry but I'm not understanding why we would want to implement Twitter Cards here... We (_or rather me at the time_) chose to implement OpenGraph because I _thought_ (_perhaps I'm wrong_) it was the most commonly adopted standard for rendering a link to a piece of content somewhere else where that somewhere else commonly supports OG Hmmmm ? π€
Okay ignoring my outrage in #c7wd2zq π ...
We can do this -- easily.
Which Card Type are we going to implement?
At the same time we should cleanup the OG rendering for /conv/<hash> links too so they are consistently rendering very similarly.
Okay ignoring my outrage in #c7wd2zq π ...
We can do this -- easily.
Which Card Type are we going to implement?
At the same time we should cleanup the OG rendering for /conv/<hash> links too so they are consistently rendering very similarly.
@prologic my own website I implement a "summary card" and a "summary card with a large image", depending on what's on the yaml header (I use Hugo). For Yarn, I think the safest will be a "summary card".
@fastidious Agreed. Let's go with Summary Card then. Please file an issue linking to the "Summary Card" spec and we'll get this done (_someone will_) π -- Also put in a GFM-style TODO in the Issue to also fix the consistency of the /twt/<hash> vs. /conv/<hash> OG rending too π
@fastidious Agreed. Let's go with Summary Card then. Please file an issue linking to the "Summary Card" spec and we'll get this done (_someone will_) π -- Also put in a GFM-style TODO in the Issue to also fix the consistency of the /twt/<hash> vs. /conv/<hash> OG rending too π