Oh, you two know each other already?
[Happy Labor Day, people. Especially those of you in the Academy, who don’t imagine those two fellows are involved in your lofty endeavor.]
Oh, you two know each other already?
[Happy Labor Day, people. Especially those of you in the Academy, who don’t imagine those two fellows are involved in your lofty endeavor.]
Clean energy shouldn’t be a partisan issue. But it is. And that means those who who want this country to be a leader in clean energy — those who want to avoid catastrophic global warming and avoid the worst of peak oil — need to start becoming single issue voters.”
Publishers have traditionally been intermediaries between authors and readers, but some experiments (PLoS One, Wikipedia and the like) seem to indicate that they are moving into the realm of serving as apomediaries. In the realm of blogs, apomediation is the main force affecting much of the talent running blogs. Publisher intermediation is not what it once was.
Google is perhaps the most prominent apomediary, guiding results to the top based on apomediation.
Apomediation feels like the net effect of an information economy that no longer operates on a scarcity model. Now, information is readily available any time. Intermediaries will still be needed, but less often than before, in fewer roles, and for shorter durations.”
Laura Fisher plurked the mysterious phrase “mitten is vaguery” earlier this evening. Turns out that in the context of the GoPlan project management site… she’s right.
Seems like some kind of deep but odd database corruption has crept in at GoPlan. Whenever a hyperlink to Laura’s account appears on our project site, my name appears; when a link to me appears, her name shows up. Click “Laura Fisher” and you’ll be emailing me, for example; I edit something and the RSS feed records her as doing it.
She’s nowhere near as wordy or bossy as I am, so this is clearly a mistake.
Update: Tiago Macedo from GoPlan support responds by pointing out that Laura’s account record has my name in it, and my account record has her name in it, so ‘if you change your name everything will be “as expected”.’
And the big question right here is: How did private, session-associated data get mixed up, and how often does that typically happen in a bugless, secure, safe Web application these days?
Scary. Very close to asking for a refund on this one issue. WTF, WeBreakStuff?