Hi,
* 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
intrigeri wrote (26 May 2014 15:32:17 GMT) :
Please create subtasks for every detected issue, so that we don't
lose track of it. Alternatively, ask me to do so.
Alan?
Done.
___
Tails-dev mailing list
Tails-dev@boum.org
Alan wrote (28 May 2014 21:40:44 GMT) :
So should I add an other preset Retried feed content or something
like that and we suggest in the doc to activate both?
I'm very unsure that this is acceptable UX, and I encourage you to
research other options first (e.g. telling Liferea to go look for
Hi,
intrigeri wrote (26 May 2014 15:32:17 GMT) :
Please create subtasks for every detected issue, so that we don't
lose track of it. Alternatively, ask me to do so.
Alan?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @
Hi,
intrigeri wrote (26 May 2014 15:32:17 GMT) :
* 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.
I realize that the
Hi,
Is there already a way to have one single preset making two
persistence.conf entries?
No. We've guessed a while ago that it will be needed at some point,
but the code doesn't exist yet. I want to write it one of these days,
but definitely not with such a short notice, that late in a
Alan wrote (23 May 2014 09:59:22 GMT) :
* implementing a liferea persistence preset
- Branch:
persistence-setup:feature/6403-implement-liferea-persistence-preset
- Ticket: Implement Liferea persistence preset in Tails wheezy
(https://labs.riseup.net/code/issues/6403)
I suspect
Hi,
anonym wrote (26 May 2014 12:38:40 GMT) :
In other words, a s/usewithtor/torsocks/ is all that's needed, right?
That would be my guess too, but I did not test it.
Given your two responses to this pull request, should I take it that you
reviewed this branch?
Until now, I had only read
26/05/14 15:23, intrigeri wrote:
Hi,
anonym wrote (26 May 2014 12:38:40 GMT) :
In other words, a s/usewithtor/torsocks/ is all that's needed, right?
That would be my guess too, but I did not test it.
Given your two responses to this pull request, should I take it that you
reviewed this
Hi,
anonym wrote (26 May 2014 14:12:02 GMT) :
Ok, whichever way suites you best.
I've fixed the issues I had identified, reviewed Alan's work, fixed
a few other issues, pushed and tested everything, but built no .deb.
I'm now quite more happy with the current content of these branches.
Hi,
intrigeri wrote (26 May 2014 15:32:17 GMT) :
* 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.
I realize that the newly
Hi,
Alan wrote (23 May 2014 09:59:22 GMT) :
* installing lifrerea 1.10 from wheezy-backports and starting it
through usewithtor
Just my two cents on that one:
Our codebase already uses torsocks and torify, and we also have some
custom tsocks somewhere. That's already too much IMO.
AFAIK,
12 matches
Mail list logo
