scor, spinnerin, tantek, peck_lx, heath, elf-pavlik, b0bg0d and cweiske joined the channel
#bretaaronpk, I'm working on implementing some simple javascript code to display webmention data from pingback.me on a static web page, but so far I only see how to make api requests with the api key which is private. Are you able to make it so I can access the data without revealing the API key?
#cweiskeI can't think how this would be possible using direct communication from browser to pingback.me
#@sandeepshettyPubSubHubbub (by Google for Google) or any push based solution for the web is unnecessarily complex for #indieweb. Polling works just fine.
friedcell, peck_lx, andreypopp, hmans and barnabywalters joined the channel
brianloveswords, erinjo, tantek, b0bg0d and andreypopp joined the channel
#tantek!tell sandeepshetty PuSH was trivial to implement as a publisher. I think it's a good spec, except for the Atom dependency, which yes we should fix to work with HTML (hAtom/h-entry) in addition.
#@SergioLuqueLe meilleur hashtag pour les émissions á venir de Indie Web Recordings ? #IndieWeb #IWR #IndieWebRec … #help ! #mercidavance
eschnou joined the channel
#@JonhyBleezRT @SergioLuque: Le meilleur hashtag pour les émissions á venir de Indie Web Recordings ? #IndieWeb #IWR #IndieWebRec … #help ! #mercidavan…
spinnerin joined the channel
#@sandeepshetty@blaine In the context of #indieweb (decentralized) where the mode will be couple of hundred followers I'm guessing it should do just fine.
eschnou and sandeepshetty joined the channel
#Loqisandeepshetty: tantek left you a message 2 hours, 27 minutes ago: PuSH was trivial to implement as a publisher. I think it's a good spec, except for the Atom dependency, which yes we should fix to work with HTML (hAtom/h-entry) in addition.
#barnabywaltersaaronpk: I do mention that the parser does no filtering and all data should be suitably filtered, but I should add that particular case as an example
#aaronpknone of the examples I was looking at had e-name
#sandeepshettyand with what eschnou there seems to be a big security hole.. which is why I left out the bit about what to do with the webmention in the spec
#tantekif someone puts "&" in the text, you should keep it, and escape when publishing if necessary
#aaronpktantek: yea my goal is plaintext, whatever that takes
#tantekpremature html escaping causes plaintext corruption
#barnabywaltersaaronpk: “i don't get <, I get <” is not the case
#tantek.comedited /2013/Guest_List (+405) "/* Creators */ putting in placeholder images for folks that forgot to - based on what they have at their site, github, twitter, or otherwise linkto from the contact/about pages. feel free to change, but something is better than nothing, public URLs" (view diff)
#tantekok folks I just added a bunch of images for the slackers
#eschnouaaronpk, hmm.. just commented and it didn't show up...
#tantekso if you want a different image (ahem, caseorganic, termie), you might want to edit your RSVP
#sandeepshettyso the reason I brought this up is that if everyone plans to do plain text feeds then how do we add the lost context (microforats related to citation, etc.)
#barnabywalterssandeepshetty: it’s safe to parse microformats and display the data in whatever way you see fit — provided the output is all htmlencoded
#tanteksandeeshetty - feel free to add your questions to an FAQ section on the /plaintext page
#sandeep.shetty.increated /plaintext (+285) "Created page with "* Displaying HTML content from external sites (feeds, webmention, etc.) posses a security risk. * Prefer plaintext * Whats the right way to sanitize external content. * However c..."" (view diff)
#tantekso I start writing an @-reply, and then realize I can improve the UI-flow of my @-reply authoring, so I jump into writing code...
#barnabywalterssandeepshetty: go by the microformats spec (assume plaintext from name, summary and HTML from content) and if you overencode, it’s the publisher’s problem which needs to be fixed on their end
#barnabywaltersif in doubt (dealing with unknown properties), encode
#aaronpkbarnabywalters: wait what! now you say name has to be plaintext?
#sandeepshettyThis isn't a publishing problem.. it's a security one... assume malicious parties...
#aaronpkeschnou: yea probably I am not following the redirect...
#aaronpkyes in this case I really do want to subscribe to that thread, and the thread on barnaby's site too. which is going to quickly turn into a de-duplication problem :)
#tantekgives up on incremental coding improvement for now, but has noted what functions he needs to change to get the incremental UI improvement he wanted.
#eschnouaaronpk, I cheated and pinged manually with the good link and it is there, yeah!
#barnabywaltersmy initial thoughts on how to fix it are to see if the content which is expected to be e-* parses as HTML
#barnabywaltersthe problem mainly is that if you expect a property to be parsed as e-* but it was marked up and parsed as p-*, you’re either going to get incorrect HTML or mistake encoded HTML for literal HTML
#tantekbarnabywalters - worth bringing that up in #microformats
#barnabywaltersmy brain is frazzled from a day of statistical stuff and an evening of whatever it was we were just discussing ;) off to bed now
#tantekis still doing lots of catch-up coding on the whole comments / reply-contexts thing.
#sandeepshettyaaronpk: re getting notifications about new comments.. old school blogs used to have a "email me when a new comment is posted" type feature
#aaronpkyea! i think that's what eschnou was alluding to
#eschnouone of the challenge is that I do all this synchronously, but when the comment thread gets long, it means someone posting a new comment sees the waiter rolling for a while...
#aaronpkeschnou: I implemented a simple task queuing system into p3k this weekend
#eschnouthe good thing is I never really have much comments on my site anyway :-)
#sandeepshettyeschnou: You can jsut fork off a process...
#sandeep.shetty.increated /queueing (+158) "Created page with "Approaches to handle work asynchronously * A proper queuing system like beanstalkd, gearman * Make an entry somewhere for the task and then have a cron do it."" (view diff)
#tantekI was using an h-as-reply class for my replies, but now I'm finding I don't have much use for it
#tantekfor display purposes (e.g. reply contexts) I can simply ask, does this post have an in-reply-to URL or not?
#tantekand if does, display it as a reply with reply context
#aaronpk+1 for syndication links at the very least
#tantekaaronpk, thanks, I do appreciate that input
#tantekin figuring out what to prioritize implementing, sometimes it's hard for me to tell which itch is hurting more
#aaronpkthat would at least let me auto-discover your syndicated posts when replying. also when reading your site it's not a big deal to click through to a tweet most of the time
#tantekso outside perspective can help a lot there :)
#tantekso e.g. "View on Twitter" and "View conversation on Twitter" links then?
#tantekwould that be click-through discoverable enough?
#tantek.comedited /Falcon (+489) "/* Working On */ add more specifics/reasons for rel syndication link use-cases" (view diff)
#tantekI'm really glad I'm documenting this itching intuition before/while implementing this stuff, as then it feels much more real than the hypothetical "if only …" or "I wish…" type declarations people usually make
#tantekas I implement each one, I plan to move the reasoning bits to the generic pages on each subject
#tantekI don't think we can avoid "threading" at least semantically whatever we do. Threading happens naturally due to the freedom of hypertext structures and our use of in-reply-to links
#tantekthis is independent of any protocol decisions/design
#aaronpki'm not talking about threading in terms of nesting and indented displays
#tantekI'm saying it's useful to acknowledge that semantic threading is inevitable
#aaronpktends to lend itself to overengineered sites
#aaronpkI used to implement strict breadcrumbs both on my personal site and also commercial sites I was making, eventually just dropped the whole thing.
#sandeepshettyaaronpk: re Comment-Notifications I think what you are looking for is doen by salmon..
#sandeepshettysending comments upstream (hence the name salmon)
#aaronpkpossibly. I would have to dig back into xml land to figure that out, and I remember it being really painful before
#sandeepshettyMight be interesting to think about how it could be done with webmention
#sandeepshettytantek: re the '&' bug: if you encode "tantek & aaronpk" only during displaying it as html, then it still "appears" as "tantek & aaronpk"
#Loqisandeepshetty meant to say: also re composite streams (discussione from 2013-05-28): I guess I'm the onely one that has onely a single post type...
#tanteksandeepshetty - no, the default is that people only have a single post type. a blog post.
#sandeepshettydoesn't it kinda suck to have the ux dictate the backend?
#tantekbecause I want to make things look different, it makes sense to do so based on an explicit semantic difference.
#aaronpkmostly due to syndicating content elsewhere. pushing to twitter, if I had <a href="http://tantek.com">Tantek</a> somewhere, twitter would only display Tantek. Same for when barnaby's site would pull out my h-entry.
#tanteksandeepshetty no! UX should always dictate the design of EVERYTHING
#sandeepshettytantek: When you have sometime take a look at https://github.com/converspace/markaround its a very early draft.. I'm hoping to start implementation in a months time... I know there are something there that you don't like (based on your markdown wiki page)
andreypopp joined the channel
#tantekoh you've seen my markdown rant page huh? ;)
#tantekI see we agree on some things "only one way to do something"