Sounds to me like the data: URI scheme could be of use in this case. For example:
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAwAAAAQCAMAAAAVv241AAAABGdBTUEAANbY1E9YMgAAABl0RVh0U29mdHdhcmUAQWRvYmUgSW1hZ2VSZWFkeXHJZTwAAAAwUExURff395OTk2ZmZtzc3Li4uImJiTIyMnh4eKSkpOvr61VVVU1NTQ4ODv7+/gAAAP////fjZX8AAAABdFJOUwBA5thmAAAAZ0lEQVR42jSOCQ4AIQgDOawaIPz/uYviNpF0gBKJiEY92tQSJQJ+MMC5/QIYvOV4FWxV4MG6VTrCGONNCLIrst4FFnNb7XVmKeyCZUsPzIgazBwNtRfe4D4z8p0u/Pv3d85x4p8AAwD9+QMj1lVBIAAAAABJRU5ErkJggg== But I just tried post a data: URI to del.icio.us , and while it posted - sort of - it's not made public and they've disabled clicking on it for security reasons. (All this fancy new stuff ... sheesh :) I'm not sure what security issues the data URI would raise. I suppose I could could imagine hazards with base64 encoded urls, but ascii text data: URI's couldn't possibly be a problem, and could be easily validated for safety. Any reason you can't turn them on? Or why you wouldn't want to? They're kind of nifty - if faintly useless [Non-text portions of this message have been removed]
