Linked by Thom Holwerda on Thu 21st Mar 2013 12:49 UTC
Google "Google's Chrome and Android operating systems will remain separate products but could have more overlap, Executive Chairman Eric Schmidt said, a week after the two came under a single boss." That's that, then.
Thread beginning with comment 556103
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: At least
by WorknMan on Fri 22nd Mar 2013 00:48 UTC in reply to "RE[3]: At least"
WorknMan
Member since:
2005-11-13

Actually, the biggest problem with the demise of Google Reader is that it can't easily be replaced by offline apps. It's chief advantages are that it's always online - meaning that nothing ever gets missed - and that storing state on a central server allows feeds to be accessed from multiple devices without syncing.


Well, it's like email in that way... you need somewhere for the data (email) to be stored, but you don't need to have the APP in the cloud. I think what we really need is for the RSS standard to be updated that defines a standard way of storing FEEDS in the cloud, so you can use whatever app you want and then have a server that stores the feeds, and if the server goes down, you just move the feeds to a different server, and continue using the same app.

Reply Parent Score: 2

RE[5]: At least
by Delgarde on Fri 22nd Mar 2013 01:02 in reply to "RE[4]: At least"
Delgarde Member since:
2008-08-19

Well, it's like email in that way... you need somewhere for the data (email) to be stored, but you don't need to have the APP in the cloud. I think what we really need is for the RSS standard to be updated that defines a standard way of storing FEEDS in the cloud, so you can use whatever app you want and then have a server that stores the feeds, and if the server goes down, you just move the feeds to a different server, and continue using the same app.


The problem isn't where the feeds are stored - that's already on the net, whether by a cloud provider or someone's personal web server. The problem is where the subscriptions are stored, and where you keep the information of which feeds you've read.

If you're using a desktop reader, then each client (laptop, work desktop, mobile, etc) has to track that stuff itself, so that a) if you subscribe to something new, it needs to be separately added to all clients, and b) any given client doesn't know which items you've already read on a different client. Google Reader solved that problem by centralising that info...

Reply Parent Score: 2

RE[6]: At least
by WorknMan on Fri 22nd Mar 2013 01:09 in reply to "RE[5]: At least"
WorknMan Member since:
2005-11-13

If you're using a desktop reader, then each client (laptop, work desktop, mobile, etc) has to track that stuff itself, so that a) if you subscribe to something new, it needs to be separately added to all clients, and b) any given client doesn't know which items you've already read on a different client.


Right, that's what I meant when I said 'feeds' ;) Why can't we standardize all that shit so any app would work with any 'feed repository'? In other words, I set up my feeds/subscriptions/whatever on a server, and then I can use whatever app(s) I want to access them.

We already do this with email (IMAP), so don't see a reason why it couldn't work with RSS. Google has already proven it can work, but the only problem is that everybody was using the same repository/API.

Edited 2013-03-22 01:11 UTC

Reply Parent Score: 2

RE[6]: At least
by moondevil on Fri 22nd Mar 2013 07:47 in reply to "RE[5]: At least"
moondevil Member since:
2005-07-08

It is called IMAP in email's case.

Any given protocol would just needs to have enough information to track those situations.

Reply Parent Score: 2