Persistence preset: Liferea
It would be nice to provide a persistence preset for Liferea (that makes little sense to be used without persistence, actually).
However, that piece of software uses versioned configuration directories (e.g.
~/.liferea_1.8/) so if we do it right now, we will have to handle the Squeeze -> Wheezy transition.
A cheaper plan could be:
- wait for Tails on Wheezy to be close enough
- Implement this feature in time to ship it with the first Tails based on Wheezy.
- Kindly ask upstream if they would not mind using a single, unversioned config directory name.
#3 Updated by intrigeri about 6 years ago
firstname.lastname@example.org wrote (04 Nov 2013 16:48:28 GMT) :
Upstream version 1.10.3 use an XDG-compliant unversioned config directory name (.config/liferea)
This version is in jessie and can be backported to wheezy whithout any changes.
Cool. Would you (kindly) ask the liferea maintainers in Debian if
they're interested to prepare and maintain such a backport?
#10 Updated by intrigeri over 5 years ago
There is in implementation ready to test in feature/5711-liferea-persistence-preset
I wanted to have a look, but I can see this branch neither in the main Git repo, nor in the t-p-s one.
Apart of actually publishing the code, what's left to be done?
#17 Updated by alant over 5 years ago
These issues were discuvered during review:
- Feeds that I had already fetched, and read some articles from, are empty after a reboot. When updating it again, the articles I had read already now appeared as unread. I consider this to be a clear blocker.
- Clicking on a feed title in the sidebar is not enough to update it. One has to right-click -> Update. Arguably, that's a minor UI issue. Is it a regression since Tails 1.0?
- If I don't have a Tor Browser running yet, "Right-click -> Open in external browser" doesn't work for me: a new tab is open in Tor Browser, with the right URL, but the page content is not loaded. That external browser seems pretty much disfunctional anyway, I can't load any URL in it. I bet it's simply because the "run with torsocks" thing is inherited by the Tor Browser started by Liferea. This leads me to think that using usewithtor/torsocks was a bad idea, and that configuring a HTTP proxy in Liferea would be much better. I think that's a blocker too.