Tails

#3 Updated by intrigeri 2013-11-04 09:39:19

redmine@labs.riseup.net wrote (04 Nov 2013 16:48:28 GMT) :
> Upstream version 1.10.3 use an XDG-compliant unversioned config directory name (.config/liferea)

Great!

> 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?

#5 Updated by alant 2013-11-05 05:06:39

> Cool. Would you (kindly) ask the liferea maintainers in Debian if
> they’re interested to prepare and maintain such a backport?

Done, see the subtask Feature #6402

#10 Updated by intrigeri 2014-05-13 15:51:29

alant wrote:
> 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?

#11 Updated by alant 2014-05-22 15:12:25

> Apart of actually publishing the code, what’s left to be done?

There were connection issues with liferea 1.10. I’m investigating a fix.

#14 Updated by intrigeri 2014-05-26 08:30:35

As I wrote on tails-dev@:

   [...] the one (presumably anonym) who will package this new code
   will need to add {build,runtime}-dependencies on the package that
   ships the liferea icon. See commit b76b911 for a past example of
   such a debian/control update.

#17 Updated by alant 2014-05-31 08:59:05

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?

• Liferea has an internal browser, with JavaScript enabled. Not checked if that’s the same in Tails 1.0. This browser has a URL bar, and can be used to browser random web pages. I consider this as a serious bug: Tails should not allow people to so easily browse the web with a much less protected browser, without being aware of the possible problems it may cause. If that’s a regression since 1.0, then that’s a clear blocker for merging this branch. Else, it’s “only” a Priority>>normal bug we’ve been carrying.

• 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.

#19 Updated by alant 2014-07-20 15:08:50

We decided not to use liferea anymore for feed persistence but to wait for thunderbird integration.