3 ms·

Hey bootload; rather OT, but I'm interested in how you are extremely detailed with your sources. Care to share how you organize and retrieve relevant informatio

Hey bootload; rather OT, but I'm interested in how you are extremely detailed with your sources. Care to share how you organize and retrieve relevant information?

bootload 20y ago
RATIONALE: The refs are there because I want readers to be able to judge information quality. ~ http://goonmail.customer.netspace.net.au/2005MAR221100.html http://goonmail.customer.netspace.net.au/2005MAR221100.html Also posting it this way keeps my information intact. OT it maybe, but tough. I'm writing for others to read & judge in the future (as well as the now). PROCESS: The organisation bit, is a custom tool I'm writing called nextgen. Most of the references I'm composing are done real-time from various sources. The text is entered into my 'nextgen' blog engine & I simply cut+paste into here. Once the story is stored (entry + links + tags + image) I can then re-use the text and add the post to other blogs I have. For example the above post also appears here ~ http://flickr.com/photos/bootload/450417776 http://flickr.com/photos/bootload/450417776 This is done manually at the moment, but if I store it, I can automate it. IDEA: "Who owns you?" The concept is along the lines of 'capturing & rescuing all the fragments of my on-line identity since '94. I then become the most authoritative source of me. Most people probably do this by default, but my stuff is spread across the web. I want it back. My own personal supply of data gives me the ability fine grained control of my data and allow - License: control license and re-license my data - Mash: combine various different feeds, text, urls, images etc - Formats: as html, rss, atom - Re-distribute: news.yc, flickr, twitter, slashdot, blog, delicious, foo - Code: web API's means I can interact with data not sites MORE: You can read all about it here ~ http://flickr.com/photos/bootload/sets/72157600015450188 http://flickr.com/photos/bootload/sets/72157600015450188

Hey bootload; rather OT, but I'm interested in how you are extremely detailed with your sources. Care to share how you organize and retrieve relevant information?

bootload 20y ago

RATIONALE: The refs are there because I want readers to be able to judge information quality. ~ http://goonmail.customer.netspace.net.au/2005MAR221100.html http://goonmail.customer.netspace.net.au/2005MAR221100.html Also posting it this way keeps my information intact. OT it maybe, but tough. I'm writing for others to read & judge in the future (as well as the now). PROCESS: The organisation bit, is a custom tool I'm writing called nextgen. Most of the references I'm composing are done real-time from various sources. The text is entered into my 'nextgen' blog engine & I simply cut+paste into here. Once the story is stored (entry + links + tags + image) I can then re-use the text and add the post to other blogs I have. For example the above post also appears here ~ http://flickr.com/photos/bootload/450417776 http://flickr.com/photos/bootload/450417776 This is done manually at the moment, but if I store it, I can automate it. IDEA: "Who owns you?" The concept is along the lines of 'capturing & rescuing all the fragments of my on-line identity since '94. I then become the most authoritative source of me. Most people probably do this by default, but my stuff is spread across the web. I want it back. My own personal supply of data gives me the ability fine grained control of my data and allow - License: control license and re-license my data - Mash: combine various different feeds, text, urls, images etc - Formats: as html, rss, atom - Re-distribute: news.yc, flickr, twitter, slashdot, blog, delicious, foo - Code: web API's means I can interact with data not sites MORE: You can read all about it here ~ http://flickr.com/photos/bootload/sets/72157600015450188 http://flickr.com/photos/bootload/sets/72157600015450188