This isn't relevant (except tangentially to the Internet Archive's Wayback machine), but I'm curious about the ethics (or legal standing) of rehosting the Google Reader app (client side portions) with a re-implementation of the (internal) Google Reader API so that the app remains usable in an unchanging state.
Comments
This isn't relevant (except tangentially to the Internet Archive's Wayback machine), but I'm curious about the ethics (or legal standing) of rehosting the Google Reader app (client side portions) with a re-implementation of the (internal) Google Reader API so that the app remains usable in an unchanging state.
The client code and assets are surely copyrighted by Google, no?
Also, I think the backend is the hard part.
I think there is at least one project out on GitHub that is trying to make a compatible backend API built upon Node.js and other technologies.