hypothesis / hypothesis/product-backlog

interpolating quotes and comments into bouncer's metadata to improve social media sharing behavior of hyp.is links

Open
#185 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
122
Forks
7
PR merge metrics
No merged PRs in 30d

Description

This issue separates itself from https://github.com/hypothesis/product-backlog/issues/166, which envisions turning annotations into textshots that can be shared on social media. That's desirable and will be great to have.

Here the focus is, rather, on the share cards that Twitter, Facebook, and other services produce when fed bouncer URLs.

Such cards expect (in page metadata) an image, a title and a description. It's easy to interpolate an annotation's quote and comment into bouncer, e.g. by this kind of parameterization:

```








````

Doing that yields, e.g.:

## Twitter

![image](https://cloud.githubusercontent.com/assets/46509/23190647/05ff0576-f84e-11e6-87a5-520c0edd63de.png)

In this case the quote is truncated but we also get to see the comment (which if longer would also be truncated)

## Facebook

![image](https://cloud.githubusercontent.com/assets/46509/23190729/835fe292-f84e-11e6-9890-0fd661e6bbec.png)

In this case the quote is all we get, it’s still truncated, nothing of the comment gets through.

## Rocket Chat

![image](https://cloud.githubusercontent.com/assets/46509/23190680/393f8cc6-f84e-11e6-8056-0bca7a5b7764.png)

## Slack

![image](https://cloud.githubusercontent.com/assets/46509/23190685/42e46bc0-f84e-11e6-82ee-986f5b14151b.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no repository files, tests, or entry points. Start by locating the bouncer URL handler and how its page metadata is generated, then check how quote and comment values could reach the Twitter and Open Graph fields. Done means supported social services show useful quote and comment content in cards without breaking metadata escaping or truncation.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.