Bug #9072
Pidgin IRC tests often fail due to OFTC Tor blocking
100%
Description
We need to come up with alternatives here. Whatever we come up with can have some interesting consequences for our default Pidgin account, i.e. if we pick some other way to access OFTC than what it has configured, isn’t our Pidgin configuration broken then? OTOH, if we’d apply it to the default Pidgin account, we’d enable spammers/trolls and probably get that method blocked too. Or what if we pick another more Tor-friendly network?
I guess an implication of this situation is that OFTC isn’t very suitable for our IRC presence (#tails, #tails-dev etc).
Subtasks
Related issues
Related to Tails - |
Resolved | 2015-10-28 | |
Blocked by Tails - |
Resolved | 2015-05-27 | |
Blocked by Tails - |
Resolved | 2015-06-02 |
History
#1 Updated by intrigeri 2015-03-19 09:26:38
- related to
Feature #7874: Find a more stable solution for Tails default chat support channel added
#2 Updated by intrigeri 2015-03-19 09:31:41
> I guess an implication of this situation is that OFTC isn’t very suitable for our IRC presence (#tails, #tails-dev etc).
Indeed, but we didn’t find any suitable alternative on Feature #7874.
I can’t think of a very good solution. The least bad one seems to be:
- make
Pidgin successfully connects to the "irc.oftc.net" account
just warn if it can’t connect due to OFTC blocking Tor (one needs to look for the “banned” thingie), and limit the consequences of ignoring failures there: - move some tests from IRC to XMPP, so that they are not skipped whenever OFTC blocks Tor. In particular:
- the one about opening a URL from Pidgin.
- maybe have
Using a persistent Pidgin configuration
use XMPP instead of IRC
#3 Updated by intrigeri 2015-04-07 19:21:08
- Assignee set to anonym
#4 Updated by intrigeri 2015-05-09 03:34:35
- Target version changed from Tails_1.4 to Tails_1.4.1
Postponing.
#5 Updated by anonym 2015-05-27 07:05:36
- blocked by
Bug #9478: How to deal with transient network errors in the test suite? added
#6 Updated by anonym 2015-06-02 14:18:15
- blocked by
Feature #9517: Retry connecting to OFTC when it fails added
#7 Updated by anonym 2015-06-02 14:19:07
- blocks #8538 added
#8 Updated by anonym 2015-06-02 14:38:11
This one will be fixed via Feature #9517.
#9 Updated by intrigeri 2015-06-04 21:26:34
- blocks deleted (
)Feature #9517: Retry connecting to OFTC when it fails
#10 Updated by intrigeri 2015-06-04 21:30:22
- blocked by
Feature #9517: Retry connecting to OFTC when it fails added
#11 Updated by intrigeri 2015-06-29 00:43:46
Can this ticket be marked as fix committed, now that Feature #9517 was merged?
#12 Updated by anonym 2015-07-01 11:53:59
- Status changed from Confirmed to Fix committed
- Assignee deleted (
anonym) - % Done changed from 0 to 100
intrigeri wrote:
> Can this ticket be marked as fix committed, now that Feature #9517 was merged?
Yes!
#13 Updated by intrigeri 2015-07-03 03:41:51
- Status changed from Fix committed to Resolved