Ryan Barrett

The quick and dirty path here would be to add this to [`microformats2.render_content`](https://github.com/snarfed/granary/blob/5ae5d2a66fb7152a6e03ad439ee4dcbeb2947088/granary/microformats2.py#L898-L1051). The deeper path would be to [figure out the mf2 for polls](https://indieweb.org/poll), add that to `microformats2.object_to_json`, then...

Working on `Twitter._create()` right now, really feeling the need for this. So much of the logic for interpreting input AS1 objects and deciding what to publish is duplicated, badly, across...

thanks for filing, and for all the details! and great to meet you! this definitely makes sense. i'd happily merge a PR for this, or maybe even implement it myself...

thanks for looking at this! i expect you're right on these points in general. I'll fix them soon!

> Shouldn't > `type = obj.pop('type', None)` > be @type, not type? AS2 prefers `type`, not `@type`, right? `@type` is JSON-LD, right? https://w3c.github.io/activitystreams/core/ only shows `@type` for JSON-LD compatibility, and...

hell yes! agreed, this would be a readability win and simplify some chunks of code a bit too.

[Evidently polls are available in the v2 API.](https://developer.twitter.com/en/docs/twitter-api/data-dictionary/object-model/poll) 😐

Hmm. How do we represent polls in mf2? How about in AS1 or AS2? Let's see... - [mf2: no standard yet](https://indieweb.org/poll) - AS1: ...? - AS2: ...?

[Twitter is now developer-hostile](https://snarfed.org/2023-04-03_so-long-twitter-api-and-thanks-for-all-the-fish), so I don't plan to work on this myself. I'll happily review and merge PR(s) though! Related: https://github.com/snarfed/bridgy-fed/issues/395

Closing as obsolete; Bridgy's Twitter support is headed toward deprecation.