#LoqiAn event is a type of post that in addition to a post name (event title) has a start datetime (likely end datetime), and a location https://indiewebcamp.com/event
#[shaners]Should an event post in a feed be marked up as both an `.h-entry` and an `.h-event` or just as an `.h-event` ?
#[shaners]tantek: remember way back when we talked about the use of `-as-` prefixes to indicated post type (strictly for styling)? Which did we end up liking better?
#[shaners]`h-as-photo` or `as-photo` or `p-as-photo`?
#tantekI'm leaning towards an h-feed has a children[] collection of all its h-* direct descendants in the order they are in, and thus an h-feed can be composite of any h-* objects
#tantekthe interesting thing is that an h-feed can have some items that have a dt-published and others that are just "exist" like an h-event, and that have other datetime relevance
#tantekhmm - perhaps I should nest my events box on my home page *inside* my h-feed
mlncn joined the channel
#tantekjust to follow-through on this (selfdogfood)
#[shaners]kylewm: where is the `type` attr coming from?
#kylewmgood q, I think right now it's just hard-coded to "event" or "entry", but I should make it use post type discovery
#[shaners]So from a CSS perspective, yall that have both `h-entry` and `h-event` posts in one feed, what are you using for your selector to style both types?
#gRegorLoveI also have dt-published even though that's not listed as a property of h-event. I've thought about hiding it if it's published after the event, since I will be backfilling many events.
#tantektitle is a horribly overloaded term that nearly always means something more presentational than semantic (which is why you should use name instead), except in vCard where it means job-title, which is what h-card uses instead.
#tantekshort answer: for a one-off site you don't expect to update much, go ahead an style the mf2 classes instead of complicating your code with more classes. for a site you expect to be "living", figure out the site-specific semantics of your blocks of content, create class names accordingly, and style those *instead of* styling mf2 classes.
#Loqitantek meant to say: short answer: for a one-off site you don't expect to update much, go ahead and style the mf2 classes instead of complicating your code with more classes. for a site you expect to be "living", figure out the site-specific semantics of your blocks of content, create class names accordingly, and style those *instead of* styling mf2 classes.
#tantekbut of course you're welcome to try styling mf2 classes directly on a "living" site and see if you run into the same issues that others of us have - you might not - and you might figure out a way to do it sensibly / maintainable
#Loqitantek meant to say: but of course you're welcome to try styling mf2 classes directly on a "living" site and see if you run into the same issues that others of us have - you might not - and you might figure out a way to do it sensibly / maintainably
#[shaners]p-name: Millennials Got A Raw Deal With Social Media
#[shaners]p-description: Essena O’Neill quitting social media is making a splash. And why wouldn’t it? It speaks to something we inherently knows is true. Social Media is mediated. It is a farce.
#LoqiThat! (or "that ^" or "that ^^^") is a rarely seen reply often emphasizing agreement with a This post, but sometimes[1] merely emphasizing agreement with a previous reply https://indiewebcamp.com/that
#tantekbecause no reason to pollute the parsed data with them
#[shaners]the presentation is part of the user experience though, imo. for example,
#tantekbasically I'm at the point where don't bother to spend time figuring out markup for something unless you have a real world consuming code use-case
#tantekand so far, that doesn't exist for title subtitle etc.
#[shaners]it’s chicken and egg (that i’m about to explain)
#tantekexcept for styling with CSS - so for that just add "normal" class names
#tantekalso - note that Atom *had* a subtitle element, and how many Feed Readers did anything with it? ZERO. ergo, failure, ignorable.
snarfed1 joined the channel
#[shaners]i post a reply to it a reply to apk’s post. my post has (what i present as) a title and subtitle. if subtitle isn’t marked up in a parseable way, when apk shows my post as a reply it won’t contain the subtitle. Or it’ll have the subtitle mushed into the name with its styling. (that could make for a looooong name).
#[shaners]If no one is publishing subtitles, no one can do anything with them. and vice versa.
#gRegorLoveOr subtitle could just be part of the *-content
#tantekshaners - I'm sure there were huge hypothetical arguments for putting "subtitle" into Atom, so they put it in.
#[shaners]tantek: re atom subtitle, was anyone publishing subtitle from their CMSes? or did the spec just provide the properiy?
#[shaners]I used the heck out of it. Until it was ripped from my hands...
#tantekI used it a few times. Then realized I didn't use it very often. Then realized I was an exception in using it at all. Then I learned to stop worrying and love minimal markup.
#acegiakanyone else attach a url to their twitter posse posts? I occasionally get annoyed at having 22 characters I can't use because of it but it feels weird not to
#gRegorLoveI hadn't thought of that and pretty much "never install FB apps" :)
#snarfeduser-configurable FB permissions are (fairly) new
#snarfedthose and especially JIT permissions, ie only ask for each perm when the app is actually about to use it, are great advances in app platform UX
#voxpelliboth h-review and h-entry needs to have their relationship to h-entry and h-feed clarified better – if one published reviews amongst other entries in a feed, then how should one publish or consume it?
snarfed and [shaners] joined the channel
#[shaners]ben_thatmustbeme: and looks like your `id` is still a child of `attributes`, but should be a sibling
snarfed1 joined the channel
#kevinmarksI have put h-review inside h-entry; I suspect that is common
#voxpellikevinmarks: what data do you put in the h-entry and what do you put in the h-review and how would you want a reader to present your review? as an attachment to an entry or as the top level item in the feed?
shiflett, funwhilelost and ttepasse joined the channel
#gRegorLoveI think a /reader can safely display an h-review the same as an h-entry. The properties of h-review could be used to enhance the display in a reader, but it's not required. No fidelity should be lost (or very little?)
#gRegorLoveMy review has dt-published instead of dt-reviewed; that's the only difference so far. I didn't publish a rating or a p-item, etc.
wolftune joined the channel
#gRegorLoveBut agreed, /h-review could probably use a "Why", "How to publish" and "How to consume" sections.
#tantekben_thatmustbeme: could you also hotlink the profile images for the people who RSVPd via FB? (since they have FB image URLs for the profile images) ?
#tantekalso, to all, especially IndieWebCamp co-organizers aaronpk ben_thatmustbeme rhiaro sandro adactio kylewm - I did a BUNCH of copy-editing/rewriting of the have/want a personal site text - please review (and hopefully it's an improvement over what you remember) https://indiewebcamp.com/2015/MIT/Guest_List#Official_Guest_List
#tantekTried to make it more readable, friendlier, more approachable in general
#tantek.comedited /2015/MIT/Guest_List (+170) "/* RSVPs from other sites (Eventbrite, Facebook, Lanyrd) */ link other sites, move to subtext rather than heading" (view diff)
#tantek.comedited /pronoun (+160) "make definition actually meaningful, and why it relates to indieweb. indieweb examples before silo examples (always), move why not preferred to a FAQ" (view diff)
#LoqiA pronoun is a word that people often use to refer to other people or objects instead of their names; on the indieweb you can express which pronouns should be used to refer to you https://indiewebcamp.com/Pronoun
#tantekvaporware is a product that is announced before its release, often with no particular expected release date, or perhaps nothing even partially developed, and is an [[anti-pattern]].