#GWGWell, if you have any ideas. Changing the tgm class would be an issue for future updates of same from upstream.
#GWGinteractivist: You using any of the Indieweb plugins at the moment?
#interactivistGWG: just getting started on the bridgy thing… want to integrate this with BuddyPress ultimately
#interactivistGWG: IMO it's not just individuals that need this, but communities too - keeps the conversation local & global at the same time
prtksxna and eschnou joined the channel
#interactivistGWG: I work with http://commonsinabox.org/ which curates BP-related plugins, much the way that wp-indieweb curates the ones you've selected
eschenal, shiflett and gRegor` joined the channel
#GWGinteractivist: You do commons in a box? Don't they use an alternative plugin installer to the one bundled in wp-indieweb?
#tantekoh ok - did you consider using one and reject it for a specific reason?
gRegor`_ joined the channel
#gRegor`tantek: I was beginning work on a style guide for my site, in part to clean up my CSS. I was weighing the option of using some lightweight reset. I have heard of plenty, but not done much research on them so wanted opinions/experience.
#gRegor`I got a couple +1s for normalize.css. We've used Bootstrap a fair bit at work and I understand it uses normalize.css in part (and much more, of course).
#gRegor`If I experiment with normalize.css or something else, I will document it.
#rhiaroI've used normalize.css for years, it's small, simple and sensible as far as I'm aware, but haven't compared it to any others
JasonO joined the channel
#JonathanNealIMHO, some of the box-sizing: border-box css bases are really nice to work with.
#JonathanNealMaybe someone should make a new one called reasonable.css
#tantekJonathanNeal: it depends on your goals for such a stylesheet
#JonathanNealFor IE8+, and it sets a bunch of useful baseline defaults without getting too up in layouts business.
#tantekhardest part is writing down what is the specific design intent of such a style sheet
rhiaro and pfefferle joined the channel
#tantekin addition to "undohtml.css" (I think "reset" is misnamed, as they're not really *resetting* to something specific), I use one I've called "simple.css" to make a reasonable readable stylesheet for arbitrary semantic markup
#JonathanNealtantek: normalize.css set styles to whatever the most-compatible most-prevelent default was.
#JonathanNealtantek: “it leads to design by rear view mirror of the lowest common denominator” - I remember hearing things like that when it first came out, too. Necolas was already writing the same thing himself, and he understood something about it that kinda made it into an empire. So, tantek, are you suggesting that normalize.css is bad for developers, or as a
#tantekby starting with a badly design foundation, you have a poor baseline to build upon
#JonathanNealidk, isn’t there some proof in the pudding when you consider bootstrap and foundation and all of the developers who have found value in the project?
#tantekhah - that's pretty funny because bootstrap has resulted in so many unmaintainable fragile bloated projects/designs that I'm amazed people still take it seriously
#JonathanNealWas it all just marketing? Why did developers adopt it to begin with? Why do they continue to adopt it?
#tantekbecause of the "first launch / ship" experience is not sucky, look pretty initially, but is hell to maintain / update
#tantekand clients often pay for first deployment of a project, and then rarely for the maintenance
#tantekso developers adopt what "demos well" not what maintains well
#tantekbut here's the thing, for the *indieweb* perspective, for your *own site*, maintains well is 100x more important than demos well
#rhiarobootstrap always seemed to me like an *awful* lot of code for some rounded clicky buttons..
#tantekif those developers were selfdogfooding their use of such tools/frameworks/foundations - they would quickly (in a year or two) find out that such approaches, to put it mildly, sucked
#JonathanNealbut the baseline was useful for developers, i stand by that.
#tantekJonathanNeal: the trick is recognizing it as trendy, and taking the time / energy to evaluate approaches as to whether they are trendy OR based in actual sustainable principles
#JonathanNealknowing that you don’t need to mess with user agent differences is a real gain.
#tantekno one advertises their stuff as trendy, you have to figure that out on your own
#tantekJonathanNeal: that's a much better more minimal principle to use "don’t need to mess with user agent differences" - a good start, but also insufficient (need more principles)
#JonathanNealdon’t throw baby out with the bathwater, normalize has technical benefits, which include reduced time to ship and reduced maintainence.
#tantekas all user agent differences come from their own "html.css" that they use internally (whether in code, or in an actual built-in style sheet)
#tantekpart of that "undoing" is undoing of user agent differences
#JonathanNealnormalizing them seems like the right name for what the project did
#JonathanNealundoing is inspecific, as anything touching a default style could be undoing.
#JonathanNealundoing also sounds like taking something away entirely rather than changing it or setting it somewhere specific. reset seems more undo than normalize.
#JonathanNealAnd remembeer that normalize came out during a time of Chrome, Firefox, Safari, and IE6-9, so why should ua stylesheets be a barrier of entry? Especially for indiewebbers, who don’t need to become css experts.
#JonathanNealThey can, but by nature of indieweb, you don’t need to. That’s why I love all the specs and frameworks folks are making here, because that would be a huge barrier of entry for me.
j12t joined the channel
#tantekyes. those are more good principles "why should ua stylesheets be a barrier of entry? [reduce barrier to entry from ua defaults]"
#GWGI think there is a ground between someone having to demonstrate skill vs having to be an expert.
#tantekit's not even demonstrate skill - that's the key
#tantekit's demonstrate *interest* (AKA passion) and *commitment* (AKA time)
#JonathanNealtantek: In CSS, margins and padding are a barrier of entry. I am still searching for the words: but “width” seems like a explicit request, so when padding changes width, it requires extra calculation, and that’s a barrier.
#tantekJonathanNeal: agreed that the default CSS box model is non-trivial and unnecessarily challenging. nevermind margin collapsing.
#JonathanNealSo, my cheering on something like reasonable.css would be that, to make a baseline that lessened the common stresses in developing with css.
#tantekJonathanNeal: you'll note that my original undohtml.css did 0-out margins
#LoqiKevinMarks_ meant to say: twitter launcthes group messaging. puzzled faces from oldschool twitter users who remember wthen that was the whole point
prtksxna, iandevlin, veselosky, LauraJ and j12t joined the channel
#tantek.comedited /2015/Cambridge (+253) "lock down dates, move other events to Nearby Events section, expand summary, add interested remote participation section" (view diff)
nloadholtes, KartikPrabhu, nloadholtes_, dies_el, KevinMarks, snarfed, interactivist, bigbluehat_, lmorchard23, reidab_ and halorgium_ joined the channel
#aaronpkjgarber: are you getting a timeout on the GET request to /auth?
#gRegor`I have it. You mean on my notes pages, like include the note content?
#snarfedgRegor`: i mean, using the post name or summary in the title, as opposed to it always being "gRegorLove.com — little g big R"
#jgarberaaronpk: It appears so, yeah. Filling in my log in form with my URL and submitting to https://indieauth.com/auth spins and spins until I get an nginx time out from indieauth.com
#LoqiTantek-ing is a method of encouraging people to contribute to the wiki by indirectly prompting the person who first mentioned the term to create a short wiki dfn page for it https://indiewebcamp.com/tanteking
#aaronpkyou're talking about completely separate actions
#aaronpkso once the oauth dance succeeds, they end up back on bridgy with the credentials that bridgy uses to verify their login
#aaronpkassuming you're verifying the login server-side, (which you have to do for twitter), you could do the publish server-side at that point as well
#snarfedaaronpk: yeah, but again, i'm then vulnerable to double submission
#aaronpksome of them will let you verify a request as many times as you want within some time window like 30 seconds. others will allow only one verify for the auth code.
#snarfedthis is fb, tw, and ig. i should probably just do the nonce thing on top.
#snarfedkylewm: curious of what you think of this possible bridgy publish UX change ^^^ (requiring the brid.gy/publish/… link even for the interactive flow)
prtksxna joined the channel
#KevinMarks_re scrobbled etc - we used 'play' in activity streams because it covered audio, video and games
#snarfedhmm. one drawback is, if your server does send wms automatically, this would prevent you from using interactive, since it would always send the publish wm
#aaronpki dunno, my instinct now is that moderated comments should have the same response as async processed comments since they both appear the same to the viewer
#aaronpkalso the point of returning 202 accepted is that it can also return a status URL people can click on to check if the processing is done
#aaronpkpresumably could do the same for moderated comments, to see when their comment is posted
#aaronpkso there is some discussion for the logs on why 202 makes sense for moderated comments
#aaronpkso there is some discussion for the logs on why 202 makes sense for moderated webmention comments <-- (more keywords to search for in the logs later)
mlncn joined the channel
#KevinMarks_there is antispam lore that says not to return different results for "posted" and "queued" as spammers use it as an oracle to test the boundaries of your filter
#KevinMarks_but as we aren't assuming content based filtering that may not be an issue
#aaronpkfrankly the goal is for most webmention endpoints to return 202 regardless of whether a comment is moderated, to encourage async processing