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.
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)
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)
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
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
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'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
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.