#microformats 2013-08-18

2013-08-18 UTC
bnvk, tantek and barnabywalters joined the channel
#
barnabywalters
Having late night thoughts about h-feed
#
barnabywalters
What are the use cases for wrapping entries in feeds?
#
barnabywalters
The only one I can think of is having multiple feeds on one page, e.g. Many people have a blog listing and then a feed of recent tweets in a sidebar
#
barnabywalters
Which creates huge UI and backend challenges further down the chain for subscribers
#
barnabywalters
E.g. I subscribe to a URL. It has multiple feeds on. I either am given a combination of all the h-entries (which may be undesirable in the eg given above)
#
barnabywalters
Or a UI to chose which feed(s) I want to subscribe to
#
barnabywalters
If those feeds don't have ids, then there’s no way to express them as URLs
#
barnabywalters
meaning that feed readers need to store complex extra state about subscriptions
#
tantek
barnabywalters - I think we captured a few use-cases on the wiki
#
barnabywalters
E.g. How to keep track of which unidentifiable h feed(s) are the relevant ones?
#
barnabywalters
And that those subscriptions cannot be exchanged between people as URLs
#
barnabywalters
All in all the possibility for nesting and all the nasty complexity which comes with it (as tantek rightly pointed out when I suggested nested h-feeds as a wrapper for comments) seems like a deal breaker
#
tantek
the use cases on the wiki are sufficient to justify an explicit container of h-entrys with a name - thus an h-feed with a p-name
#
tantek
what specifically is a deal breaker for what?
#
barnabywalters
I would contest that <title> already expresses that semantic at a page level
#
barnabywalters
tantek: deal breaker for actually consuming h-feed markup in feed readers
#
barnabywalters
When I was prototyping one it was an immediate wall I ran up against
#
barnabywalters
And one of the reasons I didn’t get very far — I assumed that being able to consume multiple h-feeds on a page was necessary
#
tantek
I'm not sure it is
#
tantek
I think if you just consume the top level h-feed (or just the first one you find), you're fine
#
tantek
or rather - could you rephrase your problem as a question? :)
#
tantek
as a "How do I …" question
#
tantek
or a "What do I do when …"
#
barnabywalters
Exactly — as soon as you introduce that constraint (one top level h-feed), then h-feed becomes essentially unnecessary as <title> handles the naming use case
#
tantek
maybe. sometimes people do different things with <title> for weird SEO or browser UI reasons
#
barnabywalters
“What do I do when a user subscribes to a URL with multiple distinct h-feeds”
#
barnabywalters
Or multiple nested h-feeds
#
barnabywalters
(On a similar but tangential note, should comments also be h-cites a la reply contexts?)
#
barnabywalters
Thus enabling a consumer to just grab all the h-entries on a page regardless of nesting
#
tantek
yes, comments should likely be citations
#
tantek
since if a consuming application wants to syndicate them, they should go get the original
#
barnabywalters
I’m liking how reply contexts and distributed comments are helping solidify exactly what h-entry and h-cite mean
#
tantek
indeed
#
tantek
all these pieces are helping clarify solidify each other
#
barnabywalters
And verify that they're all actually useful
#
barnabywalters
Which I have not (yet) seen for h-feed
#
tantek
well sandeep found it useful for his h-feed to Atom conversion service
#
tantek
which he is using apparently
#
tantek
I think he's also writing a personal reader
#
barnabywalters
h-feed works fine as a single, top level wrapper
#
barnabywalters
So probably the easiest way to deal with multiple h-feeds in a page is just to ignore them and use the first/top level one
#
barnabywalters
Look for h-feed markup to get feed semantics, then grab all the h-entries regardless of nesting and treat those as the contents
#
tantek
edited /h-feed (+263) "FAQ : What should a subscriber do with a page with multiple feeds"
(view diff)
#
tantek
I don't know about "regardless of nesting"
#
tantek
I would just grab all the h-entries in the children array of the h-feed
#
tantek
or rather, can you express your "probably" assertion as a question (or multiple) ?
#
barnabywalters
“If I parse a page with the goal of displaying a feed of entries, and it has multiple nested h-feeds, what do I do?”
#
barnabywalters
Same for multiple top-level h-feeds
#
barnabywalters
And any combination of the two
#
barnabywalters
Anyway, I need to sleep. Thanks for helping shape and record my confusion tantek
bnvk joined the channel
#
@Pafuxu
エラー: Missing required field "updated". エラー: Missing required hCard "author". ========================= 気にしない、気にしない…。
(twitter.com/_/status/368933221007781888)
tealmage joined the channel
#
tantek
edited /Special:Log/protect () "protected "[[Learn How To Get The Most Out Of Your Home Business]]": stub to block spammers [create=sysop]"
(view diff)
#
tantek
edited /Special:Log/protect () "protected "[[Voyance Gratuite]]": stub to block spam [create=sysop]"
(view diff)
bnvk joined the channel
#
tantek
Phae, tommorris, heads-up - we've got a weird spammer that is vandalizing existing pages.
#
tommorris
tantek: thanks, will take a look and help out in a sec
#
tommorris
wow, they went through the wiki like a dose of salts
#
tantek
yeah I think I got it all so far - but same spammer popped up again and I stopped it after one vandalism
bret, bnvk, shaners, tobyink and pazz0 joined the channel
#
barnabywalters
edited /h-feed () "(-4173) Undo revision 59675 by [[Special:Contributions/00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
(view diff)
nonge, bnvk, barnabywalters, chiui, bnvk_, tobyink, tantek, chiui_, eschnou, krijn, krijnh and shaners joined the channel