If you weren't in it for the social stuff then it's probably still a
good tool for you.
Leah, i suffered a similar experience with other software in 2000 with my thesis. Paranoia and redundancy are your loyal allies with your thesis: use redundant pieces of software. For instance, after del.icio.us affair, I use both diigo and evernote
I used tumblr for that. Its bookmarklet works pretty well (though I'm
annoyed at some of its limitations).
I added my own tumblog at the top of my RSS feed list, and when I'd
tumbled a quote or link or photo I wanted to share, I opened it in
Reader and hit Shift-S for "Share".
Note that I didn't *always* do this; I knew a few friends subscribed
to my tumblog directly. This was just for the stuff I wanted to rile
up the beehive!
(I love how Google, intending to drive people to Plus, will drive
people to Tumblr and Posterous and other services that actually solve
their problems. Sweet irony!)
---
Changing topics slightly... (and I maybe should make a new top-level
post for this)
I'm on a jury right now -- yes, it has been a crazy couple of weeks,
thanks for asking -- but when the trial ends I will take some time and
write some code and revive some of these useful yet cruelly
assassinated Reader features. At this point I'd like to gather feature
requests. I'm thinking of a couple of things:
* unify the various terms (share, note, item) around "share" (a la "sharebro")
* a "share" bookmarklet
* that automatically grabs the useful text of the page
* or what's selected
* and publishes a new item to...
* an RSS feed of a person's shares
* that can be subscribed to in any RSS reader e.g. Nootered Reader
* sort of like tumblr or posterous
* and may in fact *be* a tumblr or posterous blog, or be synced to it
* a chrome extension and/or firefox plugin
* that munges the new Reader UI HTML
* adds a "Share" button to sit next to the hideous "Share on Google+" button
* easily pulls in your friends' shares as RSS subscriptions in a new
"shares" Reader folder
* also syncs Plus comments somehow and displays them inside Reader
* Comment View might be tough but it's also on the bluesky list.
BTW my ninja page is still there.
http://www.google.com/reader/shared/alexch
Possible implementations...
* https://plus.google.com/u/0/106783479174075930723/posts/hvAMgzHXRgx
describes using a "bundle" which is a Reader feature
* http://www.ridllr.com/implementation_details creates a "public tag"
and uses google signin (and its app is also called Stream Pool)
"ridllr is requesting permission to:
Manage your data in Google Reader
View and manage your subscriptions, likes, and shares"
I think ridllr and I have basically the same idea, but we may disagree
on the details. I've emailed the author and haven't heard back yet. I
wonder/worry if his stuff is open source, too.
* any more thoughts?
--
Alex Chaffee - al...@stinky.com
http://alexchaffee.com
http://twitter.com/alexch
Along with OSS often comes fragmentation, and there's no central
operator you can trust (with your identity, to keep the service
running).
Just my opinion - but I think a Pinboard/Instapaper model (small
operator that can at least support themselves using proceeds from the
service) is more ideal.
It's possible that with the pricing models of SuperFeedr/App Engine it
will still make sense to make it a multi-user hosted service, but
we'll see.
-JT
This is a nice model, and I've been thinking of something similar for
a (still on the drawing board) version on http://testfirst.org --
where each student will spawn his own Heroku (or AppEngine or whatever
cloud) instance with his own load quota and database. I would maintain
a central server, probably running different code, that would collect
stats and possibly push updates.
My current "OMG MUST REPLACE READER BUT HOW" plan is to not *replace*
Nooter (*) but to augment it via JS hacks. But whatever I do would
rely on open standards (RSS, Atom), open APIs, and open source code,
even if I do end up deciding to get paid for some parts of it someday.
(*) Neutered Google Reader = Nooter
I'm concerned for Francis since the underlying technical problem of
tracking the entire blogosphere, assigning unique ids to posts,
managing updates, caching items that have scrolled off the current
feed, etc. etc. is pretty hard, and so is writing a responsive full
HTML5 GUI.
- A
I don't know what technology stack he's using, but things like
http://superfeedr.com and http://ayup.us/ should help the "tracking"
aspect tremendously, in fact, it's kind of already done.
As for HTML5, jQuery is pretty awesome.
i just found a working google +1 bookmarklet. it's not quite the note
in reader feature, but it at least serves to mark your page somewhere
http://www.labnol.org/internet/google-plus-one-bookmarklet/19474/