As I said in Liferea...
--------------------------------------


Hi,
some thoughts here...

You were asking yourselves why the use of desktop feed readers is declining.
If the comments were open in Liferea's blog ;) , I would have commented, that,
probably, it is because, nowadays, people have many computers (desktop, tablet, phone, etc).
And they want to have access to their feeds from all of them.
So they prefer to use some online service.

I, too, so it happens, to have a second computer, now,
and I was searching for this synchronization thing.
I see that Liferea has support for Tiny Tiny RSS,
but this application is a kind of a "Pro".
It requires a lot for the average users
(webserver hosting, database, cron, a few hours to set it up, and more).
And the commercial services...
why would I want to share my data with them?

So I thought that a simpler (Keep It Simple, Stupid) approach might be more useful,
even if it is more limited.

The idea is for a free, open, sort of synchronization standard,
that would require nothing but an editable text space online
(preferably protected by a password, for reading and writing).

That file could be a text file in an ftp server
(example: ftp://someserver.com/somename.txt)
or a wiki page
(eg http://somewiki.cc/Somepage?action=edit)
or a text file in some hosting service,
or could be in a cloud service etc.
Or this file could be in your desktop computer, or LAN,
to allow synchronization between different feed applications
(like Liferea and Akregator).

So...
Liferea-A from Computer-A would export its state to this file.
Some basic information...
These are the categories (folders)
These are the feeds I subscribe to.
These are the articles (news) I have been informed of.
These I've read.
These I haven't read.
These ones are important.
File was last read on DATE by NAME
File was last edited on DATE by NAME
(DATE could be blank)
(NAME doesn't have to be unique, or could even be blank)

And, then,
Liferea-B from Computer-B,
before updating it's feeds, would first read this text file,
and start from where it was left by Liferea-A.
And before closing, it would report its state to this file.

And then,
Akregator from Computer-C...
and so on...

There are some obvious issues that programmers would have to solve.
Like, what happens when multiple computers try to edit this file at the same time.
And I am in no position to suggest how the syntax of this file would be
other than "as simple and as "lightweight" as possible".
Further more...
is the free software community willing to cooperate on something like this?

But the main advantage is that it requires VERY LITTLE from the user.
Just write access, and a link, to a text file online (support for php editing, through plugins, would be nice)
A password.
A choice as to how often the program should report its state online
(eg "whenever it changes", "every XXXX hours XX minutes XX seconds")
Always report state online before closing? YES/NO
Report time? YES/NO
Signature name to report: A DESCRIPTIVE NAME

This way, hopefully, desktop feed readers would be "back in the game".

And who knows, you might even be able to cover some of the development expenses.
Feed Readers developers could set up some relative service, for a very small, reasonable feed,
that some user might be willing to pay for.

Well, these are my thoughts on the subject...


Reproducible: Always