#crabi did h-card/hCard for my main page, and marked up all the posts with h-entry so far.
[LewisCowles] joined the channel
#[LewisCowles]crab. I think the point is that p-summary is for lists. Surely it would lead to repetition if placed within e-content?
#crab[LewisCowles] i'm not sure i understand why. please explain?
#[LewisCowles]lists of articles, like a blog index or archive page.
#[LewisCowles]As-in it's to provide a short teaser to read the content. It doesn't need to be a part of the content
#crabare you saying you would generate the index with only a summary of each post, and post pages without a summary?
#crabi guess i just don't understand your point. i know it doesn't _need_ to be part of the content, but it's convenient for me if it could be, on a post page.
#crabhmm. i guess the problem is that i'm thinking of the summary as the first sentence of my content, and you are not.
#crabgRegorlove: i could be doing something wrong, or misinterpreting the results, but that looks like the java one doesn't see the summary, but the ruby one does.
#LoqiChris Aldrich mentioned it was his #indieweb anniversary today, which made me wonder when I first encountered indieweb. Turns out it was six years ago! I remember being excited about the idea of federated comments. I had no idea I would be getting in...
#crabi don't know what parser indiewebify.me uses for h-entry, but that does see the summary either (or at least, it doesn't say anything about the summary when validating that page, as i expected it to alongside the other properties it does detect).
#[jgmac1106]I do the same, with my p-summary, I was explaining I set them to display:none
#gRegorloveindiewebify is the php parser, also running at php.microformats.io
#gRegorloveYeah, p-summary inside e-content is valid, so ruby and php parsers are right there (and Python, I'm certain)
#crabTBH, i'm not actually using any of this for anything. i just happened to see "google supports microformats" somewhere, and realised i could markup my stuff with h-card and h-entry pretty quickly.
#crabit's only after i'd already done it that i realised that the microformats google supports aren't the ones i'd added support for :-)
#gRegorloveWe have #microformats too, btw, if there's specific parsing questions or issues
#Loqi[Greg McVerry] Hey #k12 educators moving online, want a greener, more accessible web?
Do you collaborative editing in a wiki not Google Docs, Just checked same article in both places. 56 MB for the gDoc and 17.12 kb for my wiki! Massively smaller
[jeremycherfas], loicm, hs0ucy, confraria[m] and [LewisCowles] joined the channel
#[LewisCowles][jgmac1106] it's very likely the media within your doc was being measured in one, whilst only the data stored in the wiki case?
#[LewisCowles]The XML document formats are a bit bloated. I'm just not sure if the JS to power the google + requests is 56MB (It could be, I just remain hopeful they are not that wasteful)
#[jgmac1106]yeah I could be wrong on my measures, my usual tools weren't working, with my understanding, I would like to correct what I said if I am off by a factor of 10
#[LewisCowles]the amount of times I've been off by an order of magnitude or more
#[jgmac1106]will delete until I can describe my methodology, especially since I am unsure of the size of gDocs and I was doing my best with console topols
#LoqiWebmention is a web standard for mentions and conversations. Whenever someone likes or mentions your posts/episodes on social network, Webmention is notified and will send them back to your website.
1. Turn off Disqus
If your site is currently using ...
#LoqiIt looks like we don't have a page for "Typolog" yet. Would you like to create it? (Or just say "Typolog is ____", a sentence describing the term)
#[snarfed]oof, no, code is not more secure just because you wrote it yourself and you can see it
#[snarfed]all else equal, less and simpler code is indeed more secure
#[snarfed]but big co's have security experts write and review their code, and a bunch of other resources, which will generally outweigh code written by security amateurs like most of us
#[snarfed]the one saving grace may be that homegrown custom code is generally a very small and low value target, so most attackers won't bother with it
#superkuhThe best security is not running code at all and doing things with your eyes manually that can be done manually.
#[snarfed]when possible, sure! manual until it hurts
#superkuhTakes me about 15 seconds to go through 2 days of POST data from pingback/webmention on my sites.
#[tantek]The practical problem we're seeing now however is that BigCo code has gotten so bloated that *despite* their superior security expertise and review, they have much more likelihood of "lurking bugs" than small simple OSS code (which has also likely been security reviewed, since it's OSS)
#[snarfed]eh maybe. yeah the tradeoff of size vs experts does go back and forth
#[snarfed]but OSS definitely _doesn't_ imply security reviewed. i bet the fraction of indieweb OSS code that's been _truly_ security reviewed, for example, by actual security experts, is small to none. by lines, estimated guess, i bet it's under 1%
#[snarfed]as a data point, sadly none of mine has, despite its age and my resources. i wish it had been! code reviewed, yes; security reviewed, no.