Differ Presentation by Post Type

[dshanske]

Develop some method of adapting the presentation based on the markup of the site.

For example, identifying an article, and publishing just title and link, differentiating between this and a note, where the fulltext should be posted. Option for this is the class h-as-article(http://indiewebcamp.com/ActivityStreams)

[snarfed]

definitely! @dshanske, would these orders of precedence work for you?

• article: summary, then name, then content
• note: summary, then content , then name

[snarfed]

(right now, twitter uses summary, then content, then name, for both articles and notes. facebook always uses content.)

[dshanske]

Well, a summary might not fit in a Tweet, but it would on Facebook, for example. Would that be...

• article: summary(if exists), then name(if exists), then content
• note: summary, then content , then name

Related to this is the ongoing photo discussion.

[snarfed]

yeah, I meant those as fallbacks, not combinations. good point, I can also check if each one would fit on Twitter, and fallback if either it doesn't exist or it's too long. sound good?

[dshanske]

Makes perfect sense to me. The biggest problem for me is the ... that many POSSE publishing services do in truncating content on Twitter.

[snarfed]

yeah, ellipsizing is no fun. out of curiosity, though, if the only options available are longer than 140 chars, do you know what you'd want to do instead of ellipsizing?

[dshanske]

Suggest the user fix it? Not sure.

On Sat, Jul 19, 2014 at 1:37 PM, Ryan Barrett [email protected]
wrote:

yeah, ellipsizing is no fun. out of curiosity, though, if the only options
available are longer than 140 chars, do you know what you'd want to do
instead of ellipsizing?

—
Reply to this email directly or view it on GitHub
#228 (comment).

[kylewm]

Unfortunately I'd guess most users would want/expect Bridgy to do the truncation, rather than give an error.

[snarfed]

fixed by snarfed/granary@2a9ce83

[jasonkgreen]

With Twitter, there's the challenge of two distinct use cases

1. You are publishing a link to a longer article
2. You are publishing a single tweet

Case 2 is tricky. I'm guessing that (I use IndieWeb Press This to publish from WP)

WP Post title = name
WP post content = content
WP ??? = summary

When it was pushing content from the post content to the tweet, I was at a loss as to what to title the posts in WP. It's fine to tweet the post title as long as everyone is clear that's how it works. I need to read up on passing h-as-* to IndieWeb Press This.

[snarfed]

thanks for the info @jasonkgreen! that name/content mapping is right. i haven't seen a summary object from a wordpress blog before, so you may be able to ignore that.

as i mentioned on twitter, you can make wordpress use h-as-note by using the Aside post type. if you add this line to the window.onload section of your press_this.js, it should use Aside automatically:

document.getElementById("post-format-aside").checked = true