Linked by Thom Holwerda on Wed 13th Mar 2013 23:27 UTC
Google "We launched Google Reader in 2005 in an effort to make it easy for people to discover and keep tabs on their favorite websites. While the product has a loyal following, over the years usage has declined. So, on July 1, 2013, we will retire Google Reader. Users and developers interested in RSS alternatives can export their data, including their subscriptions, with Google Takeout over the course of the next four months." This makes me very, very sad. Any good alternatives - alternatives with Windows Phone and Metro applications, that is?
Thread beginning with comment 555377
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Web apps are a failure
by Nelson on Thu 14th Mar 2013 02:49 UTC in reply to "RE: Web apps are a failure"
Nelson
Member since:
2005-11-29

This is solved in Windows 8. You can use a Background Task to fetch and store RSS feeds locally (at 30 minute intervals, when you sign in/sign out, and when internet connectivity changes).

If you use a Clover Trail SoC or an ARM SoC you can take advantage of Connected Standby which lets your PC go into low power states while periodically waking up to run background tasks.

Reply Parent Score: 2

RE[3]: Web apps are a failure
by phoenix on Thu 14th Mar 2013 16:59 in reply to "RE[2]: Web apps are a failure"
phoenix Member since:
2005-07-11

This is solved in Windows 8. You can use a Background Task to fetch and store RSS feeds locally (at 30 minute intervals, when you sign in/sign out, and when internet connectivity changes).

If you use a Clover Trail SoC or an ARM SoC you can take advantage of Connected Standby which lets your PC go into low power states while periodically waking up to run background tasks.


And, how exactly does that get around the 'system needs to be always on to poll' requirement, allow 3rd party apps to sync, allow mobile clients on Android/iOS to sync, etc?

A Windows 8 requirement is also a non-starter for most people.

A server-based setup is the best. This just might push me toward ownCloud. If I need a server running all the time, may as we make it useful.

Reply Parent Score: 5

RE[4]: Web apps are a failure
by Nelson on Fri 15th Mar 2013 02:33 in reply to "RE[3]: Web apps are a failure"
Nelson Member since:
2005-11-29


And, how exactly does that get around the 'system needs to be always on to poll' requirement, allow 3rd party apps to sync, allow mobile clients on Android/iOS to sync, etc?


You don't need to always poll. This isn't really time sensitive information. Its a convenience.

If you run a Background Task at a frequent enough interval (every 15 minutes) you get a degree of freshness of data without plummeting the battery.

This in addition to Connected Standby allowing ultra low power background processing would address a lot of your complaints.


A Windows 8 requirement is also a non-starter for most people.

A server-based setup is the best. This just might push me toward ownCloud. If I need a server running all the time, may as we make it useful.


Sure, it may be. But at that point you're just moving the goalposts. This is a happy middle ground, in my opinion.

Reply Parent Score: 2

RE[3]: Web apps are a failure
by Delgarde on Thu 14th Mar 2013 20:16 in reply to "RE[2]: Web apps are a failure"
Delgarde Member since:
2008-08-19

This is solved in Windows 8. You can use a Background Task to fetch and store RSS feeds locally (at 30 minute intervals, when you sign in/sign out, and when internet connectivity changes).


How does that solve anything? The problems I cited with desktop RSS readers is that the device needs to be turned on, and that it needs to have internet connectivity at all times. I don't see how running a background task helps with either of those issues - nor with the question of syncing across multiple devices.

Reply Parent Score: 2

RE[4]: Web apps are a failure
by Nelson on Fri 15th Mar 2013 02:35 in reply to "RE[3]: Web apps are a failure"
Nelson Member since:
2005-11-29

The background task would run at an interval of 15 minutes (in addition to whenever connectivity changes, a new account session is started, and a plethora of other system trigger events) *and* it runs while the PC is asleep.

You can also (if polling is your thing, as you and the commenter above allude to) implement a Transport Trigger which lets you do long polling in the background. Its used for VOIP scenarios but it would work equally well here.

Reply Parent Score: 2