Aaron Parecki

Consider using only the character set in NewBase60 to ensure all your URLs are print-safe and unambiguous. If you follow the NewBase60 algorithm it has built-in error correction (e.g. O is considered the same as 0)

Character set: [0-9A-HJ-NP-Z_a-km-z]

More background: http://ttk.me/w/NewBase60

@dissolve333 Sweet! I get the most work done on trains and planes. :-) Forced inability to get distracted by the Internet.

@kevinmarks @Skud @benwerd Yeah I could do that. https://github.com/esripdx/spiderpig I've flattened Wordpress sites with it before. I'd be happy to host it!

@notizblog.org echt cool! Wie kann ich ein copy finden?

@Malcolm_Ocean now it's taken.

@Malcolm_Ocean Not sure if you're joking, lol, but if you're interested, check out http://indiewebcamp.com/how-to-push

@cheryl_crowe Maybe I can get revenge by eating lots of bananas and leaving the peels in the seat pocket

Rotbier - the best after a run! :-)

@benwerd and 45.9 million of those don't know or care what RSS is, and wouldn't care if something replaced it ;-)

@CodeFancier @ungoldman or just, you know, bring it to the apple store and they'll give you a new one

@ungoldman ... said nobody, ever

@superfeedr awesome! I just added a clarifying note to the wiki, but will remove it when that's done! https://indiewebcamp.com/how-to-push#Link_to_your_PuSH_Hub

Suggestion: Change the text in Section 5.1.1 https://pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.4.html#rfc.section.5.1.1 to say "The topic URL MUST be the one advertised by the publisher during the discovery phase."

Section 5.1.1 currently says "The topic URL MUST be the one advertised by the publisher in a Self Link Header during the discovery phase."

However, section 4 says that the topic URL can be specified in *either* the Link header or a tag in the document body, such as an HTML link tag. This change makes the sections consistent.

@julien51 @superfeedr Great! Sent you some details, thanks!

@julien51 @superfeedr I take it back, it does appear to be an SSL error. Do you not recognize the StartSSL root cert?

@known.kevinmarks.com Fixed, thanks! :-) It was an "m" instead of a "j" in the date formatter. That's what I get for writing this on a red-eye flight!

@anomalily my current shoes cost $50 and have lasted about 2 years so far

@veganstraightedge Check out http://slack.indiewebcamp.com @gRegorLove #indiewebcamp

@angelakilduff Thanks! It's running but sometimes it's a little bit slow when a bunch of people are using it. It should catch up soon!

@edsu I am aware. But none of the content I am trying to archive requires JS, so it's not a priority for me.