bnvk, benprew, josephboyle and scor joined the channel
#KevinMarks_"There’s a feed in the middle showing all your friends’ posts, and some other random stuff along the sides that no one has ever looked at" made me laugh aloud
#_6a68KevinMarks_: that blog post made me laugh and laugh
#_6a68but really, I didn't think it was fair to blame their troubles on the database
#KevinMarks_it's interestingly the same mindset I got from dhh yesterday
#XgFI think lots of people have ran to (Mongo|Redis) because RDBMS are hard (but powerful) and OODBMS are rare
#_6a68sure, but if you don't foresee that you'll need to manage consistency and relations among denormalized data blobs inside your app, you are in for a world of hurt
#_6a68regardless of which implementation of non-relational key-value store you pick
andreypopp, b0bg0d, tpinto and barnabywalters joined the channel
#Loqibarnabywalters: tantek left you a message on 11/13 at 11:16am: very cool! looks like it's picking up the u-url u-uid no problem. However the dt-published and dt-updated is "2013-11-13T" missing the time from: <span class="dt-published published dt-updated updated"><time class="value">6:01</time> on <time class="value">2013-11-13</time></span> which should work per: http://microformats.org/wiki/value-dt-test-YYYY-MM-DD--HH-MM
#barnabywalterstantek: indeed, turns out that was an undiscovered bug from ages ago, value-class time components with single-digit hours weren’t being matched correctly. fixed.
#tantekpoint is, due to the backwards compat support in phpmf2, the existing class="hentry" element in WordPress posts should "just work" for comments, reply contexts etc.
#tantekand if it's not, then why not fix it instead of adding even more markup for microformats2
#JihaisseI'm not sure, but I think that SemPress is a theme developped for mf2 support
#tantekaaronpk interesting. I've written code specifically to address a few of those concerns but not made a big deal of it. It's in CASSIS, let me see if I can document it more explicitly.
#aaronpkyea, but still involves wiring up an interface and javascript and figuring it all out
#tantekwell, sorta. my interface gives me the character count from the server - no JS
#tantekanyway I have a CASSIS building block function you can use in PHP or JS for that.
#tantekI've done a lot of debugging of them for sure
#aaronpkso the context of that quote was a conversation with dreeves of beeminder, they are currently publishing a feed of user-visible improvements to their app on twitter at https://twitter.com/beemuvi and would prefer to have that hosted on their own site
#tantekand I value posting notes that are losslessly retweetable
#aaronpkthe challenge is making an interface that is at least as functional as twitter's
#tantekhas anyone implemented posting in the future on their indieweb site?
#tantek(like the feature in WordPress, I think, to schedule future posts)
#tantekI have some ideas around it that I've been meaning to explore
#snarfedaaronpk, tantek: the common term for that is "urgent at the expense of the important"
#tanteke.g. storing it in "future time" in my flat file structure, and then having my index/stream code only show posts that have been "published" in the "past"
#tanteksnarfed - good to know - that's probably worthy of documenting as an anti-pattern
#snarfedeh yeah, maybe. it's obviously extremely broad, way bigger than indieweb or even tech in general
#snarfedknown solutions are discipline, strong leadership decision making, clear prioritization processes (although getting those right is tricky, often can do more harm than good)
#snarfedand prioritization is hard in so many ways. 1) making real priority decisions in the presence of non-obvious tradeoffs, 2) getting consensus, 3) actually following through and working on highest priority stuff first
#tanteksnarfed - in a community context I allow some amount of others' "urgent" items to dictate what I work on (especially if I can answer quickly) figuring that when I later have something *important* and ask about it - the likelihood of reciprocation is greater.
#snarfedtotally. call that a community building tax
#tantekthe dynamics of prioritization are more complicated in a community context
#tantekI look at it as more of an investment than tax
#snarfedalso, urgent vs important obviously isn't a dichotomy for solving any individual problem. you can do both.
#snarfedit's only an antipattern when there are lots of things to do, and you're overdoing the urgent alternatives instead of the important/long term ones
#tanteksnarfed - right - that first URL of the two above showed a 2x2 matrix of urgent vs important
#aaronpkyeah I'm not happy with the way they look right now, cause they are in reverse chronological order meaning the farthest future event is alwasy on top