Feature #7874

Find a more stable solution for Tails default chat support channel

Added by emmapeel 2014-09-03 13:43:02 . Updated 2016-06-27 02:33:35 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2015-10-28
Due date:
% Done:

100%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
0
Affected tool:
Instant Messaging
Deliverable for:

Description

IRC networks and Tor are not good friends.
OFTC many tmes blocks exit nodes to prevent spammers. Indymedia is sometimes hard to use and harder to configure with SASL.
We should have a stable solution to give irc support to the users.

Maybe XMPP is a better solution but we raised the problem of having randomly generated account on the server. We would need to find a server that:

  • Allows the creation of new accounts on the go.
  • Erases unused accounts frequently.
  • Supports Tor for real.
  • Has a commercial SSL certificate or is available as a hidden service.

Subtasks

Feature #11306: Move #tails to XMPP Resolved

100


Related issues

Related to Tails - Feature #7753: Decide what to do regarding OFTC Resolved 2014-08-06
Related to Tails - Bug #9072: Pidgin IRC tests often fail due to OFTC Tor blocking Resolved 2015-03-18
Related to Tails - Feature #7690: Host our internal XMPP chatroom on Tails infrastructure Resolved 2014-07-30
Related to Tails - Bug #11183: Document what to do when the #tails IRC Channel ask users for being registered Rejected 2016-02-29

History

#1 Updated by emmapeel 2014-09-03 13:43:57

  • related to Feature #7753: Decide what to do regarding OFTC added

#2 Updated by sajolida 2014-09-22 03:41:26

  • Description updated

#3 Updated by emmapeel 2014-11-26 09:08:55

  • Status changed from In Progress to Resolved
  • Starter set to No

I didn’t find any server that could host as many people as oftc or being as stable, which were two important things.

Meanwhile, oftc is being very welcome to Tor exit nodes. I’m closing this bug until massive blocking happens again.

I didn’t even had to change identity once in the last few months. Before, I had to do it several times until I reached an exit node which could connect, and sometimes I could not connect at all.

#4 Updated by intrigeri 2015-03-19 09:26:39

  • related to Bug #9072: Pidgin IRC tests often fail due to OFTC Tor blocking added

#5 Updated by anonym 2015-03-19 14:58:12

  • Status changed from Resolved to In Progress

I’m reopening this. The past two months have been pretty bad, and yesterday I didn’t manage to get in once when trying continuously for five hours. Today it took me half an hour to get in, finally.

#6 Updated by intrigeri 2015-03-19 15:05:59

  • Subject changed from Finding a more stable solution for Tails default support channel on pidgin to Finding a more stable solution for Tails default chat support channel
  • Assignee deleted (emmapeel)

#7 Updated by emmapeel 2015-03-19 18:52:51

anonym wrote:
> I’m reopening this. The past two months have been pretty bad, and yesterday I didn’t manage to get in once when trying continuously for five hours. Today it took me half an hour to get in, finally.

Yeah I had some problems again, though only the last week. I will keep asking around though I didn’t find a solution that could work for us last time, please comment me any kind of suggestions!

#8 Updated by sajolida 2015-03-20 12:50:40

And lately we’re also having problems with our private channels. Maybe we should consider moving both to a more stable XMPP instance. Also, Tor Messenger will be XMPP only at least for some time, so considering dropping IRC might not be that crazy.

#9 Updated by intrigeri 2015-03-20 21:57:10

  • related to Feature #7690: Host our internal XMPP chatroom on Tails infrastructure added

#10 Updated by intrigeri 2015-03-20 21:59:57

> And lately we’re also having problems with our private channels.

That should be covered by Feature #7690. Maybe we should treat it with higher priority, but then let’s discuss that there.

> Maybe we should consider moving both to a more stable XMPP instance.

If there’s any XMPP server that satisfies the requirements the ticket description specifies, I’m all for it. I’m not very hopeful about it, though :( … so if we can’t find any such XMPP server, we might have to reconsider some of these requirements.

#11 Updated by BitingBird 2015-04-10 20:06:48

  • Subject changed from Finding a more stable solution for Tails default chat support channel to Find a more stable solution for Tails default chat support channel

#12 Updated by un 2015-07-03 16:59:37

intrigeri wrote:

> If there’s any XMPP server that satisfies the requirements the ticket description specifies, I’m all for it. I’m not very hopeful about it, though :( … so if we can’t find any such XMPP server, we might have to reconsider some of these requirements.

im.mayfirst.org? as a partner project for specifics? apologies if it’s been suggested; did a quick search and didn’t find.

#13 Updated by intrigeri 2015-07-04 02:30:30

>> If there’s any XMPP server that satisfies the requirements the ticket description specifies, I’m all for it.

> im.mayfirst.org? as a partner project for specifics? apologies if it’s been suggested; did a quick search and didn’t find.

http://im.mayfirst.org/ reads “we now have our very own Instant Messenger service for our members”, so it clearly doesn’t satisfy the our “Allows the creation of new accounts on the go” requirement.

#14 Updated by intrigeri 2016-02-29 22:36:12

  • related to Bug #11183: Document what to do when the #tails IRC Channel ask users for being registered added

#15 Updated by intrigeri 2016-02-29 22:43:58

1.5 years later, I’m in favour of dropping the requirement to support randomly generated accounts, that doesn’t seem to be very realistic: in practice it just forces us to stick to the status quo, that is half of the time our support channel simply does not work for the vast majority of non-technical users.

We would stop auto-generating an IRC “account” for Pidgin, and instead document how users can create their own account (short or long-lived, they get to decide) to access whatever support channel we want to migrate to.

I don’t know what’s available once we’ve dropped this requirement. Does XMPP do everything we need for such a chan?

#16 Updated by muri 2016-03-02 19:14:08

my 2 cents: i’d like to move #tails to another technology rather sooner than later. the irc channel became a pool of scriptkiddies (which like to help out by telling people how to bypass or disable tails security mechanisms) where giving support is nearly impossible. its rather dangerous for new users to join there, i’d say.
i’d say a conference room on conference.riseup.net would be good enough.

i think the two requirements that are not about the throwaway-accounts depend on the xmpp-server a user uses

#17 Updated by sajolida 2016-03-07 13:51:30

+1 to intrigeri
+1 to muri

#18 Updated by geb 2016-03-11 17:56:18

+ 1 to muri. + 1 to Intrigeri to.

But,

- I am note sure changing the technology will change this problem. Maybe partially (IRC is know for being full of trolls), but if it is not we will have to find a solution to work around it.
- And thus, i would really like that we unsure, that the technology we choose will allow tu kick/ban/ignore people in case of necessity. I know XMPP may offer that but i am not sure it is available on every client/server/room. Does somebody have a better understanding than me about it ?

#19 Updated by muri 2016-03-11 19:33:12

  • Assignee set to muri

geb wrote:
> - And thus, i would really like that we unsure, that the technology we choose will allow tu kick/ban/ignore people in case of necessity. I know XMPP may offer that but i am not sure it is available on every client/server/room. Does somebody have a better understanding than me about it ?

+1 to add these requirements. i’ll do some research on that topic in the next few days/weeks (assigning the ticket to me for the time being)

#20 Updated by muri 2016-03-20 21:20:58

  • Assignee deleted (muri)

geb wrote:
> - And thus, i would really like that we unsure, that the technology we choose will allow tu kick/ban/ignore people in case of necessity. I know XMPP may offer that but i am not sure it is available on every client/server/room. Does somebody have a better understanding than me about it ?

so, i did some digging. [https://xmpp.org/extensions/xep-0045.html]xep-0045 (multi user chat) is supported by both ejabberd and prosody and both also support Roles, Affiliations and Privileges. it is possible to unvoice a user, so person can read but not talk. it is possible to kick and to ban people. and clients also can do ignore. roles are lost on leaving a channel, affiliations are permanent.
i’ve only found two clients that are able to manage a room, that are pidgin and gajim, in which gajim has slightly more complete interface for managing a conference room.

(i’ve also stumbled upon https://prosody.im/doc/anonymous_logins and https://www.ejabberd.im/Anonymous-users-support, which could be interesting for requirement 1 and 2, but i’ve not found a server that provides that. i’d still drop that requirement for now, but i’ll definitly look into that later that year)

#21 Updated by sajolida 2016-03-21 16:44:04

Muri: now this ticket has no assignee. How do you think we should follow up on this, or if possible who?

#22 Updated by muri 2016-03-21 17:01:42

sajolida wrote:
> Muri: now this ticket has no assignee. How do you think we should follow up on this, or if possible who?

it didn’t have an assignee before i set it to myself (which i did only so i don’t forget about the tiny research part i wanted to do) and it is listed as a topic for the monthly meeting (don’t know who has put it there)

#23 Updated by sajolida 2016-03-22 15:21:59

> it didn’t have an assignee before i set it to myself (which i did only so i don’t forget about the tiny research part i wanted to do) and it is listed as a topic for the monthly meeting (don’t know who has put it there)

Fair enough! Sorry for the noise…

#24 Updated by emmapeel 2016-04-04 12:52:37

#25 Updated by emmapeel 2016-04-04 12:58:48

#26 Updated by sycamoreone 2016-04-12 12:58:33

Some things that I was told today, that might be helpful:

  • hackint.org runs a XMPP/IRC bridge, that allows one to use IRC channels as Jabber MUCs (e.g. connect to #channel@irc.hackint.org to join a channel). This probably also can be made to work the other way round.
  • hackint.org also runs IRC servers, that can be accessed as onion services and have usable requirements for anonymous access:
    > Anonymous access to hackint has been abused in the past. We do not wish to disable anonymous access, so we are introducing a new policy:
    > Users wishing to connect to hackint anonymously have two possibilities:
    >
    > 1. Connect via a Tor Hidden Service requiring SASL Authentication
    > This means that you need an account before you can access hackint anonymously. In order to create an account anonymously, please use our online registration form.
    > Users connecting this way will receive the hostmask *gateway/tor-hashcash-verified. > > 2. There exists a second Tor entry node that can be used without SASL. > Users connecting this way will receive the hostmask *gateway/tor-unverified.
    >
    > We hope that this new policy will reduce abuse and prevent legitimate, anonymous users from being banned in channels.

hackint.org is run by various local CCC groups in Germany. whois lists the Chaostreff Dortmund. If anonymous XMPP turns out to not work in practice, this might be a place to go to.

#27 Updated by BitingBird 2016-06-27 02:33:35

  • Status changed from In Progress to Resolved