tantek, parzzix, snarfed, lukebrooker, emceeaich, wolftune and nitot joined the channel
#tantek.comedited /post-type-discovery (+614) "Normative References h-entry for property names in the algorithm, Activity Streams for JSON, microformats2-parsing for canonical microformats2 JSON, cite normative references inline where needed" (view diff)
#acegiakAnyone else using bridgy finding that their POSSE tweets are coming up as mentions?
#tantekI wonder if it might be possible to put some of the response-type discovery smarts on the webmention endpoint itself rather than depending on Bridgy to get the typing right
#acegiakI've been a little absent so I'm not 100% up to date on what's happening
#acegiakbut I'm aware we need to work out a way to make salmentions less hacky so it can go in the main semantic linkbacks repo
#GWGacegiak: Bridgy has been through a round of enhancements that have prompted some issues. I haven't gotten many mentions of late, as I've been less active of late, due injury.
#GWGBut let's see...on the WordPress side, a bunch of pushes on Semantic Linkbacks and Webmentions...nothing earth shattering.
#aaronpkmy new micropub endpoint actually does a hybrid of that, when it goes to store the post in microformat syntax it changes any value to a string if there's only one value for that property
#KartikPrabhuaaronpk: I have been laggin behind on micropub developments with my endpoint so might have write some code to see how easy/hard it is
#KevinMarksaaronpk: if you get to 11 or 12 and name content are both empty, does it matter what kind of post it is?
#KartikPrabhuaaronpk: is step 11 supposed to give False if name is blank string an there does not exist a content?
#aaronpkKevinMarks: i'm not sure, i guess i might want to not show a post if there is no content i know how to show, and the result of the algorithm as it stands won't tell me that
#aaronpkKartikPrabhu: i don't think so, the algorithm is written to stop processing only if the step says "it is a ___ post"
#KartikPrabhuaaronpk: oh. if the post has no content property it immediately satisfies Step 6 and is a note
#aaronpkalso realizing there are going to be a lot of post types that are not standardized/formalized that I'm going to want to publish immediately that I'gm oing to have to figure out how to deal with
#aaronpkconsidering just scoping everything under p3k-* properties to avoid the issue (and probably not include that markup on the published post_
#tantektrue - I should include an FAQ about that - about why it's good that a "note" is the ultimate fallback
#tantek.comedited /post-type-discovery (+30) "/* Other Types Under Consideration */ add more types under consideration as pointed out by aaronpk. invitation, tag-of" (view diff)
#aaronpkokay i think this works, but it is slightly less obvious what is happening since I have to carry over the content from step 6-7 all the way to step 13
#aaronpkcould you add this before step 6? "If the post has no "content" property and no "summary" property, or if both are empty, then it is a note post"
#aaronpkright now I read step 6 and I can't actually do anything until I get to step 8, and then I still have to remember what was happening in step 6 to continue
#kylewmtantek: should I add my note to the wiki about the content.contains(name) check that i do?
#aaronpk(and yes you should basically be reading this as pseudocode since I'm using functions that are not defined in the gist, primarily $this->get)
#tantek.comedited /post-type-discovery (+434) "resolved issue, "unknown" is worse than "note" as fallback, display/presentation is outside the scope of this specification" (view diff)
#tantek.comedited /post-type-discovery (+396) "resolve issue, reject video for now due to only one "current" u-video example. all other video examples are old or don't use u-video" (view diff)
#tanteksorry to reject video aaronpk - evidene not there for it yet :/
#tantek!tell kylewm what do you think of making the note / article distinction an "OR" e.g. "name.contains(content) OR content.startswith(name)" means post is a note?
KevinMarks, Geng, friedcell, mlncn, interactivist, elf-pavlik, ttepasse and nitot joined the channel
#ben_thatmustbeme!tell aaronpk, tantek re: video tag, my u-video does NOT link to the post, look at the source and see for yourself, pin13 reads it that way (bug?) (unmung parses that differently). It needs to be moved to the <source> tag is all. Should check that before you comment on others implementation.... i mean really, that would make no sense. honestly, i think working out some way for the tag to be on the <video> / <audio>
#ben_thatmustbeme/ <photo> tag would be better for when there are multiple sources
#[tantek]Ben, I don't think I made that wiki edit.
#[tantek]However, thanks for the "how to" improvement on /video !
#Loqi[tantek]: ben_thatmustbeme left you a message 1 hour, 52 minutes ago: re: video tag, my u-video does NOT link to the post, look at the source and see for yourself, pin13 reads it that way (bug?) (unmung parses that differently). It needs to be moved to the <source> tag is all. Should check that before you comment on others implementation.... i mean really, that would make no sense. honestly, i think working out some way for the tag to be on the <video> / <audio> http://indiewebcamp.com/irc/2015-09-30/line/1443610171345
#[tantek]I think perhaps that was aaronpk'so observation? Not sure if he was using pin13 or what. I just did view source at the time I checked, and then cited your example (as the only recent right one!) in post type discovery.
wolftune, rosetree, scoates, LanceyWork and [aaronpk] joined the channel
#Loqi[aaronpk]: ben_thatmustbeme left you a message 3 hours, 36 minutes ago: re: video tag, my u-video does NOT link to the post, look at the source and see for yourself, pin13 reads it that way (bug?) (unmung parses that differently). It needs to be moved to the <source> tag is all. Should check that before you comment on others implementation.... i mean really, that would make no sense. honestly, i think working out some way for the tag to be on the <video> / <audio> http://indiewebcamp.com/irc/2015-09-30/line/1443610171345
#[aaronpk]I definitely was looking at the parsed result from pin13. I pretty much never actually view source anymore since people's html tends to be harder to read than the mf2 JSON
#Loqikylewm: tantek left you a message 9 hours, 28 minutes ago: what do you think of making the note / article distinction an "OR" e.g. "name.contains(content) OR content.startswith(name)" means post is a note? http://indiewebcamp.com/irc/2015-09-29/line/1443590514605
#kylewm.comedited /post-type-discovery (+509) "/* Issues */ add example of name.contains(content), ask if there are examples of content.startswith(name)" (view diff)
snarfed1 joined the channel
#kylewmfiatjaf: yeah unfortunately. the only reliable way I know of to find the comment ids is to look at the post's /comment edge in the api
#tantekso about PuSH, and it specifies SHA1 which is obsolete, and perhaps specifying any particular crypto is problematic for this reasons, though not doing so may hurt interop
#tantekand about the ability to force at PuSH hub to use "none" as a security vulnerability that should be documented in a Security & Privacy considerations section
#voxpelliaaronpk: the signature is "sha1=abc123" no? So already pluggable
#aaronpkespecially since it's totally irrelevant to the actual functionality of PuSH "In the context of social web applications, it is considered good practice to include a From..."
#tantekand yeah - if it's not obvious why a feature is there (documented use-case) then lets push to remove it
#voxpelliFrom-headers must be emails according to its spec and would therefore require WebFinger:esque identifiers
#aaronpkit just seems that "it is considered good practice" is not very compelling
#voxpelliaaronpk: remember our discussion around PuSH based private messaging? That's kind of the purpose of such a header I think
#tantekperhaps anywhere you see "it is considered" should be a red flag
#tantekvoxpelli: yeah, first the JSONpocalypse, and now everything JSON-related in W3C is going through a JSONLDpocalypse.
#voxpellitantek: isn't everything on the IndieWeb-wiki just patterns considered to be best practices rather than strict standards that requires compliance? ;)
#aaronpkthe IWC wiki doesnt make unsubstantiated claims that something "is considered best practice"
#tantekvoxpelli: there is a big difference between "Here are real world examples with permalinks and real people citations" vs. "it is considered to be" zero citations zero mention of specific people.
#voxpelliKnow Blaine talked a lot about From headers at Federated Social Web Summit in Berlin 2011, that's when OStatus was about to go JSON and lots of talks about private messaging was in the air
#tantekit is considered to be is a form of [[weasel wording]] that is sometimes used in specifications to justify features or assertions that have little or no basis in actual citable evidence or real world examples, because if it did then such citations would be cited!
#aaronpkvoxpelli: re the signature, it's true the payload format allows a sort of extensibility by doing something like sha256=xxxx instead of sha1=xxxx
#voxpelliaaronpk: did you find any other issue with PuSH? One challenge with it right now is that it's a versions document rather than a living spec
#ben_thatmustbemethat was in regards to video tag thing from earlier
#voxpelliaaronpk: perhaps file an issue about making a living PuSH spec to take over after 0.4? So it can keep up with all other living specs
#aaronpkben_thatmustbeme: oh you know what's happening with the php one? it's getting a blank value from the u- property, and then doing the relative URL resolution on it, resulting in the page's URL
#ben_thatmustbemesort of tempted to do <span class="e-video"><video><source> ....
#aaronpkvoxpelli: are we stuck on making progress on 0.4 because it's versioned?
#voxpellitantek: in relation to PuSH it feels like a living spec is what the IndieWeb community would want, right? But feed readers and the blogosphere probably doesn't want any changes
#aaronpkbut now I'm thinking about dropping that whole idea and switching to something more like https://github.com/aaronpk/ca3db instead, which supports storing multiple versions of content easier
#aaronpki'm not totally happy with either solution though
#KartikPrabhuaaronpk: thanks for documenting this. will be useful for my file storage plans
#tantekooh I'm definitely interested in ideas around storing multiple version of content, in particular multiple versions of files and URLs
#aaronpkthe key is "Note that without appending ":" to folders, it would be impossible to store all these files on disk since "example.com/tags" would have to be both a file and a folder.", but basically chose ":" because it looks like / in Finder
#aaronpkthat's what broke in my current implementation, I started getting errors about not being able to create files then I realized what was happening
#ShaneHudson_Basically a way to access the counter of generated content (ie. a list). So you can reset the numbers etc. Basically one of the first CSS variables.
#ShaneHudson_I used it to hide the default numbers and add them back in as a psuedo, so that it could be styled further than usual
#ShaneHudson_Also, current-color is a really nice one that has pretty good browser support now, lets you get the current text colour. So you can create nice underlines (with a gap for hanging letters) using shadows etc with the colour set to the current. Useful, though hacky
#acegiakthere's a scene atthe end of serenity where the graves have looping bits of video holographically projected and it's subtle but lively and nice
#acegiakwhich is what I want gif profiles to feel like