#petermolnarhi all, question about the upcoming UK event: I've over calculated my spare time a bit and it seems I could only join for Saturday. Would it be an issue if I cannot join on Sunday?
#Loqipetermolnar: GWG left you a message on 8/15 at 12:25pm: I have a question for you about your full page cache plugin
#petermolnar!tell GWG I was out for vacation, please poke me about wp-ffpc any time
alanpearce, adactio, Sebastien-L, friedcell, squeakytoy, tantek, glennjones, scor and Nadreck joined the channel
#tantek.comedited /https (+731) "/* Level 2 security */ added instructions for https-only just for your admin UI (e.g. with self-signed cert), which I first tested by deploying to my own site" (view diff)
#barnabywaltersjust been improving the way shrewdness (and taproot/subscriptions) subscribes to non-PuSH-enabled content, to reduce server load (and load on my wallet)
#barnabywalterskylewm: you’re not going to try to create a recursive subscription now are you?
#petermolnarGWG so far I was not able to reproduce the draft saving issue with wp-ffpc, could you please give me a few more details about your wordpress setup & the backend?
#GWGpetermolnar: I also found it wasn't necessarily beating fastcgi_cache on a tmpfs in page serving
#aaronpkI'm gonna have to set up the PuSH thing for the IRC logs again aren't i
#petermolnarGWG: fastcgi_cache on a tmpfs is an insanely fast thing, as it is in-memory and nginx built-in thing, no network connection to anywhere, I do not expect a mere WP plugin to be faster than a C code :)
#barnabywaltersaaronpk: well by default I just fall back to superfeedr subscriptions, but I also encourage you to set up PuHS 0.4 (the new, good variety) and will help if I can
#barnabywaltersbasically: add two link elements to the page, then send a HTTP request whenever the content updates
#GWGpetermolnar: I did want to test it though. I thought maybe direct nginx memcache serving could beat fastcgi serving
#barnabywaltersI’d like to write a PHP one though, in the same style as taproot/authentication or taproot/subscriptions so it can either be set up on it’s own or bolted onto an existing application
#barnabywaltersso to make an arbitrary resource PuSH 0.4 enabled requires two <link> elements or HTTP headers: rel=self to the canonical URL of the current page, and rel=hub to the hub used for subscriptions
#kylewmbarnabywalters: and shrewdness will use those if the normal h-feeds have them?
#tantekooh - is someone here actually consuming PuSH updates?
#barnabywaltersyep, shrewdness will attempt to subscribe at the designated hub, falling back to using superfeedr’s polling service
#tantekis there any indicator in the UI that it is seeing PuSH updates directly from the source (rather than superfeedr) ?
#tanteki.e. I post PuSH notifications from tantek.com but ever since status.net went down I have no idea if anyone is consuming them
#kylewmok that's awesome, right now I'm only sending PuSH notifications for Atom feeds, but I will add the h-feeds in ASAP
#barnabywalterstantek: your homepage doesn’t have link rel=self so doesn support PuSH 0.4 — it should be really easy to enable it though! just add the link element/header and send pings for your homepage
scor joined the channel
#kylewmbtw, an embarrassing thing is when you meet julien51, and ask him a question about PuSH and he asks which hub you are using and you say pubsubhubub.appspot.com
#barnabywaltersI would have thought he’d be happy about it — he genuinely cares about decentralisation
#kylewmI mean he didn't flip over the table or anything
#kylewmhe just chuckled and said he couldn't help debug it then
#kylewmor rather couldn't look at the logs to see why it wasn't pinging IFTTT immediately
#bear"According to the RSS Advisory Board's Best Practices Profile, identifying a feed's URL within the feed makes it more portable, self-contained, and easier to cache. For these reasons, a feed should contain an atom:link used for this purpose."
ShaneHudson and KartikPrabhu joined the channel
#tantekshould != must. thus implementations must NOT require rel=self from a publisher.
paulcp and paulcp_ joined the channel
#bearI'm in complete agreement with you about rel=self being over-engineered cruft that we should actively disabuse folks from using
#bearit's just process noise and needs to be hacked out of daily use IMO
#ben_thatmustbemeyeah, i tried to force weird situations. the original idea for start and end was that you could site exact phrases rather than it assuming the whole paragraph.
#ben_thatmustbemeplus I figured with that format it falls back to ##something as a fragmention as previously defined
#ben_thatmustbemeits just a blank ID (so search body tag) and no end text (so assume the entire parent entity)
npdoty, colintedford and jonathanfrei1 joined the channel
#KartikPrabhuI am quite concerned about Firefox accepting the + symbol in the id without encoding. Can't seem to find a definitive spec for URL fragments
#bearcould the fragment be implied by what element the anchor is relative to?
#bearhmm, thinking about it - probably not because fragments could be pulled from inside of a long <p> item
#tanteksimpler is arguable (what is simple?) where as shorter is objective metric
paulcp joined the channel
#ShaneHudsonThere may be a potential problem with the entire quote, especially if using a CMS. Not only do shorter work better but URLs do have a max char limit, which may be reached by accident with the entire quote
barnabywalters and gRegor` joined the channel
#KevinMarksOk, so that gives a case for ellipses of some kind
#ShaneHudsonAs in wherefore..capulet to quote shakespeare? That would certainly make it shorter
mcepl, glennjones and smcgregor joined the channel
#KevinMarksI'm thinking about quoting practice. I use ellipses in tweeted quotes all the time
#ben_thatmustbemeKevinMarks, I moved on from the ellipses in the fragmention because it could easily by in the text. i figure better to use something that should encoded in the URL, thus the #start#stop
#ben_thatmustbemethe biggest issue i saw with using this type of fragmention is what happens if the start and stop are actually in different elements
#barnabywaltersaaronpk: did you get anywhere with your turn-any-resource-into-an-image thing?
#bearjonnybarnes - yes, that would be a great mention for https page
#ShaneHudsonNot sure I trust that... "Nice. shanehudson.net is using a certificate signed with SHA-256, a form of SHA-2.", shanehudson.net doesn't have a cert at all
#bearShaneHudson - your site is returning a cert for .co.uk
#jonnybarnesill open an issue on the github repo for that ShaneHudson
#tantekthis was specifically just for achieving Level 2
#tantekI'm both unsure what setting HSTS *does* for your admin page, nor how to.
#snarfedsure. i'm happy to drop the HSTS part. my main goal was to revise the language about leaking cookies, since the first request will often still leak credential cookies
#snarfedwe can instead say explicitly to mark the login cookies with the secure flag, to achieve the same goal
#snarfed(should be obvious, but too many servers still don't)
#tantek.comedited /https (+187) "/* Level 2 security */ numbered list, has a logical order of implementation, expand/explain why for #2 and #3" (view diff)
#tantekso first question about secure cookies, looks like I can inspect whether or not a cookie is secure in the Firefox preferences / Privacy / Cookies… button/dialog
#tantekif it says "Send For: Any type of connection" that's not secure
#rascultantek right after that "ensuring that the cookie is always encrypted when transmitting from client to server"
#kevinmarks.comuploaded /File:gplusfail.png "Google+ profile preview fails when a person has 2 accounts as it doesn't show the email or profile URL to disambiguate"