#pfefferle!tell barnabywalters perfect! thanks! and also thanks for pointing me to the <body /> or <html /> as h-entry thing… never thought about that and it makes a lot of things a lot easier… working on my theme to support the comments markup and try to implement the p-in-reply-to into the web mention plugin.
#Loqibarnabywalters: aaronpk left you a message 12 hours, 11 minutes ago: here's the date formatting library I was telling you about. would be curious to hear your thoughts on it! https://github.com/indieweb/date-formatter-php
#Loqibarnabywalters: pfefferle left you a message 1 hour, 15 minutes ago: perfect! thanks! and also thanks for pointing me to the <body /> or <html /> as h-entry thing… never thought about that and it makes a lot of things a lot easier… working on my theme to support the comments markup and try to implement the p-in-reply-to into the web mention plugin.
#Loqiaaronpk: barnabywalters left you a message 28 minutes ago: I merged my mf2-shim changes, pushed to https://packagist.org/packages/mf2/shim — let me know if you want to be added as a maintainer
#barnabywalterstantek: it’s a HUGE security risk and a silly thing to do
#tantekand with that, off to get a late lunch at food carts
#aaronpkI don't show php errors on actual production stuff, but I don't mind as much here
#barnabywaltersaaronpk: the easiest quick fix would just be to use @$parser->parse();
#tantekbarnabywalters - perhaps you can add a section on advice / how-to NOT show PHP notices when selfdogfooding in a new section here: http://indiewebcamp.com/selfdogfood
#aaronpkweird, I also don't remember it requiring mongodb
#waterpigs.co.ukedited /selfdogfood (+911) "/* testing your code in production */ added notes about debugging notices in production, some PHP code samples" (view diff)
#sandeepshettySeems like we do it because it is plain text as opposed to e-content which is HTML... is there another reason for it?
#sandeepshettythe reason it bothers me is because if it were local comment, I would show the whole comments so treating remote comments differently doesn't feel right
#tanteksandeepshetty - another reason is when people write REALLY long comments and it might screw up your comment or reply-context display
#sandeepshettythat should be an explicit rule/guideline that applies to both remote/local comments: truncate any comment greater than x and show a read more link,
#tantek.comedited /FAQ (+849) "sort questions by likelihood of relevance, fix/updated everyone going to want to run their own website question (of course they are, like personal computers, cell phone numbers etc.), add What is new q and a" (view diff)
#aaronpk(if you choose to because it would make your UI better)
#aaronpkyea I replied to a really long note from barnaby and currently I don't truncate it and it kind of messed up my UI
#sandeepshettyand trusting p-summary to be "short" is also not a good idea so that rule could be added explicitly... and shouldn't be a reason to show p-summary by default
#pdurbinaaronpk: 106 words... 689 characters... not *that* long :)
#sandeepshettyit feels like a hack to get a plain text version of the comment (which works for what most indiewebers call "notes" but not for "articles")
#sandeepshettyand that too because php-mf2 was stripping tags from p-* and giving plain text (which is another issue I want to take up after this)
#aaronpkactually that brings up an interesting point. should we even include a p-name property for plaintext notes that don't have a title?
#aaronpklike if the p-name is the same as the p-content, do we need p-name?
#tanteksandeepshetty - it's not about "trusting" in any absolute form
#tantekp-summary is *likely* to be shorter, so you can try using it if the e-content is "too long" (for your UI)
#tantekand if even the p-summary is too long, then abbreviate
#tantekthought I wrote this up on the comments-presentation page
#aaronpkI guess if I grab the e-content and think it's too long, I might as well just truncate it myself. why would I need the p-summary?
#aaronpkI could see using p-summary for articles though
#sandeepshettyaaronpk: I tried my atom feed on feedly and I have p-name = p-summary = p-content and it looks like sh** :)
#tantekaaronpk - because if there is a p-summary and it is shorter, it may be more meaningfully truncated than you might be able to automatically truncate
#aaronpkheh yea, notes don't really have a name. for syndicating to facebook I made up a title like "Note posted on July 6 2013" or something
#tantekp-summary is likely explicitly crafted by the author
#tantekwith even the expectation that that's what syndicated copies might use
#sandeepshettyaaronpk: Thats similar to what I had in mind as a fix
#aaronpktantek: ok so that implies the author is doing intelligent summarization, so that should be documented as a recommendation too
#aaronpkI either automatically create the summary from the first 2 paragraphs plus first photo, or I manually type up the summary for articles
#sandeepshettythe summary concept is also dying out on drupal, wordpress, etc..
#tantekaaronpk - I've got some (pseudo?)code crafted to put the first whole sentence or two into a p-summary
#sandeepshettyespecially since most blogs show the entire content on the list pages
#tantekso that notes can be even more precisely truncated than what people's truncation code does
#tanteksandeepshetty - who cares about what "is also dying out on drupal, wordpress" ?
#aaronpksandeepshetty: I don't think that's necessarily true. especially with inline previews on twitter and facebook, summaries of articles is even more important now
#tantekseriously - none of those are bastions of innovation
#tantekso looking at what's dying out there has very low value
#tantekthere's almost no vision in drupal or wordpress - too much is focused on commercial CMS use-cases
#tantekp-summary just helps give the author some control over how that happens
#aaronpkI agree with sandeepshetty on this one though, it shouldn't be a "rule" to show the p-summary, it should be recommended that you truncate text to fit your UI, and suggested that the p-summary may have a better truncated version
#tantekpreferring full content is better for the indieweb
#sandeepshettyand if p-summary is also long.. truncate that as well
#aaronpkright, truncate to whatever length you want based on your design, but take into account the fact that the p-summary may have a shorter/better version for you to start with if it's present
#sandeepshettywhich brings us to the other problem of displaying html securely.. think we should change this from "you may want to filter some HTML" to "you should filter unsafe HTML"
#tantek.comedited /comments-presentation (+465) "/* How to display */ prefer full content, use p-summary instead of truncating yourself, truncated only if that's what you need per your own site UI/design. also truncate the p-summary or p-name if you have to" (view diff)
#tantekok updated - take a look and see if that reflects what we discussed:
#sandeepshettyDo we need this: "for longer posts where only a part of it is the comment". I would markup this up (or rather not have any markup) as a mention
#Loqisandeepshetty meant to say: Do we need this: "for longer posts where only a part of it is the comment". I would markup this (or rather not have any markup) as a mention
#sandeepshettyShould I remove "for longer posts where only a part of it is the comment" in favor of marking up posts like that as a mention instead of in-reply-to ?