Skip to content

Bridgy Publish to Flickr: detect hashtags and set Flickr tags #604

Open
tantek opened this Issue Jan 17, 2016 · 12 comments

4 participants

@tantek
tantek commented Jan 17, 2016

Bridgy Publish supports publishing photos (including user tags) to Flickr, what's missing is normal / plain Flickr tags.

There are two ways an indieweb post can tag a post that Bridgy Publish should consider picking up:

  1. # hashtags. Hashtags in the (p-)name, (p-)summary, (p-)content property values could (should) be parsed out as intended as tagging the photo/video.
  2. (p-)category markup. Since Bridgy Publish is already parsing for (u-)category properties, and this parsing should be generic to any kind of (*-)category property, if/when a 'category' property is not a URL (thus not person-tag), then it should be treated as a plain text tag.
@snarfed
Owner
snarfed commented Jan 17, 2016

thanks for filing!

publish actually already propagates p-category mf2 tags to Flickr tags. @kylewm added that pretty recently. this is a good nudge to add it to the docs.

as for hashtags in plain text, I'm not sure. i get that #hashtag syntax is pretty universal now, and i get that it's necessary in silos that don't allow explicit tags, but publish users generally own their markup and get to author explicit mf2 tags with p-category.

given that, I'm a bit reluctant to promote text only #hashtags to explicit silo tags... but i dunno. thoughts?

@kylewm
Collaborator
kylewm commented Jan 17, 2016

I notice that Known autolinks hashtags so "category": ["#indieweb"]. If we stripped the octothorpe for silos that don't use it, that might be a happy medium? Then sites like tantek's that want interpret them as tags could make it explicit by wrapping them with a <span class="p-category">

@snarfed
Owner
snarfed commented Jan 17, 2016

(daaamn it's a sunday morning and @kylewm got me all https://www.google.com/search?q=define%3Aoctothrope )

@snarfed
Owner
snarfed commented Jan 17, 2016

stripping octothpus sgtm!

@tantek
tantek commented Jan 17, 2016

@snarfed I'm sympathetic to not overdoing the smarts re: "reluctant to promote text only #hashtags to explicit silo tags".

This might be another example of not over-interpreting text (e.g. whitespace) into markup.

Even if you do end up rejecting this suggestion (to autopromote plain text hashtags to categories/tags), I wanted to capture it (and subsequent analysis) because I expect it will come up again.

@tantek tantek changed the title from Bridgy Publish to Flickr: detect hashtags and p-category and set Flickr tags to Bridgy Publish to Flickr: detect hashtags and set Flickr tags Jan 17, 2016
@tantek
tantek commented Jan 17, 2016

Narrowed the scope since p-category tags are already supported apparently. Just need to update the docs re: p-category. Update: pull request for docs update: #605

@snarfed snarfed added the publish label Jan 25, 2016
@singpolyma

This publish brid.gy did https://www.flickr.com/photos/singpolyma/24001981743/ seems to have the hashtag autolinked (maybe flickr did that from the plain text?) but then the tag itself is not on the post? A bit confusing UX on the flickr side, not sure if my tag ended up on the post or not. My tag is marked up using rel=tag in the hentry, so it seems like brid.gy should be able to pick it up?

@kylewm
Collaborator
kylewm commented Jan 26, 2016

@singpolyma http://sngpl.ma/t4fS0 is returning 404, can you point me to the original that was POSSEd? My guess is mf2py isn't doing backcompat for rel=tag

@singpolyma

@kylewm oh, right, my short domain is still down (grumble,grumble morocco) -- full URL https://singpolyma.net/actionstream/boring-cabinets/

@kylewm
Collaborator
kylewm commented Jan 26, 2016

great! so I think if you just add class="p-category" on that tag, it'll work just fine.

@kylewm kylewm referenced this issue in tommorris/mf2py Jan 26, 2016
Closed

backcompat: rel=tag to p-category #58

@kylewm
Collaborator
kylewm commented Jan 26, 2016

Should be backward-compatible with rel=tag now, so you don't need to change your markup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.