84 posts tagged “mark-pilgrim”
2005
HOWTO Use Your Mac From Anywhere (via) A screencast tutorial by Mark Pilgrim.
Dive Into Greasemonkey. If you’re not in to Greasemonkey yet, now you have no excuse.
Mark Pilgrim goes both ways. Fighting greasemonkey scripts.
2004
XML on the Web Has Failed. Mark Pilgrim concludes a theme he’s been following for quite a while.
Freedom 0. Mark Pilgrim switches to WordPress.
Mark Pilgrim’s Atom feed (via) Atom + XSL + CSS = a self explanatory feed that functions in a browser.
Gmail accessibility. Mark Pilgrim: “The only way Gmail could be less accessible is if the entire site were built in Flash.”
The myth of RSS compatibility [dive into mark]. Sometimes I think Mark’s raison d etre is to upset Dave Winer
2003
Atom autodiscovery test suite
Mark Pilgrim has released the Atom autodiscovery test suite, comprising 148 tests:
[... 130 words]Blogmarks
This entry was going to be another list of links, together with a note about how much I really needed to set up a separate link blog. Then I realised that it would make more sense just to set one up so that’s exactly what I’ve done. I still need to implement the archive but it’s getting dark so I’m posting this and heading home.
[... 211 words]Dive Into Python reborn
Sweet. Mark Pilgrim is working on Dive Into Python again, funded by a dead tree publisher for publication in 2004 (hopefully). The free version will stay available as well. I’ve always preferred reading paper to reading a screen so I’m definitely down for a copy.
[... 135 words]Sitting nervously on the fence
Today’s hot topic is the Winer Watcher, Mark Pilgrim’s new tool that tracks and highlights edits made to Dave Winer’s Scripting News. The blogosphere is pretty much evenly split on this: some people think it is a blatant attack on Dave Winer, tantamount o blogger bullying, while others see it as a neat technical solution to a very real problem.
[... 1,146 words]Javascript, the DOM and application/xhtml
One of the side-effects of switching my blog to serving pages as application/xhtml+xml to browsers that support it (mainly Gecko engine browsers) was that my blockquote citations script simply stopped working in those browsers. The reason this happened is touched upon by Mark Pilgrim in The Road to XHTML 2.0: MIME Types: essentially, when dealing with XML documents Gecko needs you to use document.createElementNS in place of document.createElement when manipulating the DOM.
Safely consuming RSS: RegExps don’t cut it
Mark Pilgrim highlights the severe security issues introduced by RSS aggregators that display potentially unsafe HTML, often executing it in the “secure zone” generally reserved for trusted local documents. Mark suggests a number of dangerous tags and attributes that should be removed before display. Unsurprisingly, regular expressions have cropped up in the comments as the suggested solution. Jamie Zawinsky famously once posted the following to comp.lang.emacs:
[... 396 words]Under the Iron
Under the Iron is a series of interviews with interesting people. The most recent three include one with Mark Pilgrim, which talks in part about Mark’s reasons for creating diveintoaccessibility:
[... 140 words]Python power
Sam Ruby’s ultra-simple 3-paned aggregator is a great example of the power of high level scripting languages. Using the wxPython cross-platform GUI toolkit and Mark Pilgrim’s ultra-liberal RSS Parser it provides a full application in a mere 107 lines of (highly readable and maintainable) code.
[... 127 words]Dynamic Python class methods
Dynamically extending APIs: Mark Pilgrim demonstrates how Python’s “new” module can be used to dynamically add new methods to existing classes at run time, and shows how this can be used to increase productivity when parsing XML. I’ve long been impressed with Python’s ability to add new methods to an object at runtime just by assigning a function reference to an object property but I had no idea it was possible to do this with classes as well. If you liked that tip, Dive Into Python has in depth explanations of more obscure Python features than you can shake a stick at.
Feedback loops
Mark Pilgrim has been having an interesting problem with his Further Reading feature: Feedback loops.
[... 64 words]Generated content observation
Mark Pilgrim is unhappy with XHTML 2.0. Since the rest of the blogging community has already provided mass commentary on his post, I’ll make an observation concerning his further reading feature instead. The first link I saw to Mark’s post (and the one I followed) was on techno weenie, but I was surprised to later notice that techno weenie was not listed in the further reading list. For those who haven’t been paying attention, Mark’s further reading list is automatically generated from referrals, with verification from a clever Python script that checks the source page to make sure there really is a link, extract a relevant portion of the page and attempts to find a permalink for the entry as well.
[... 313 words]Safari conditional comments
The current extended discussion over whether or not Safari should have some kind of specific CSS blocking technique built in (sparked off by Mark Pilgrim) reminds me of a relatively unpublicised feature of Internet Explorer called conditional comments. These specially crafted HTML comments allow web authors to specifically hide code from versions of IE, or alternatively to hide code from any browsers that are not a specified version of IE. Here’s how they work:
[... 198 words]2002
Stuart on plays
Stuart has some interesting thoughts regarding Mark Pilgrim’s latest entry: an excerpt from The Real Thing, a play by Tom Stoppard.
Mark goes XFML
Mark Pilgrim has discovered XFML. He provides an excellent description of the standard, but fails to mention XFML’s most powerful ability; sharing metadata. Here’s how it works:
[... 225 words]Syndication is not publication
Mark Pilgrim pretty much single handedly killed the discussion thread on syndicating weblog content with XHTML started a few days ago by Anil Dash. Stuart’s reply to Mark’s post is definitely worth a read though.
Wired Redesigns
Wired have redesigned, and now boast one of the snazziest CSS layouts on the web. The redesign is explained in A Site for Your Eyes, and has already drawn commentary from Jeffrey Zeldman and Mark Pilgrim (with plenty more certain to come). I think the title of Mark’s entry pretty much sums it up—this could well be the high profile redesign the web standards movement has been waiting for.
Googlebad
Mark Pilgrim explains why Google’s latest update tweaks (mentioned yesterday) are a lot less harmless than they first appeared.
Write on
A year ago, Mark Pilgrim’s manager told him to stop blogging. He refused, and was fired a week later. Today Mark celebrates.
Pingback coverage
The Pingback 1.0 specification is getting some serious attention. Mark Pilgrim and Dave Winer have linked to it. Ben Trott (co-author of Moveable Type and creator of TrackBack, the system that inspired Pingback) has objected to Hixie’s suggestion that Pingback is more transparent than TrackBack, claiming that TrackBack could be made just as transparent by the right blog tools. Ben blogged some further thoughts which lead to the following comment by Phil Ringnalda:
[... 278 words]