-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
migrate "unofficial" IRC channel to tor-friendly network #1571
Comments
We at Whonix have problems with OTFC and blocking Tor users also. Ticket: |
do Tails and Tor Project face any issues with OTFC? I would find it surprising that they use OTFC if it is blocking users. That ticket makes it sounds ambiguous as to whether it was an individual issue rather than something confirmed by other users/devs. |
Not really specific to projects. HulaHoop user recently reported this It's very much unlikely a Whonix specific issue. The connection works, I don't know what these project's workarounds are. |
sounds like it is worth pinging Secure Desktops about it? |
never mind just saw the new threads on https://lists.torproject.org/pipermail/tor-talk/2016-January/039812.html |
OFTC on the other hand do not have DHE, so pick your poison. |
FYI Tails is moving to Riseup's hosted IRC chatrooms: https://mailman.boum.org/pipermail/tails-dev/2016-January/010005.html info here: https://help.riseup.net/en/chat |
There is confirmation now, that OFTC causes issues for other users also:
They are doing that for years, yet I have not noticed any form of improvement and having greater issues connecting to freenode over Tor than OFTC. |
Michael Carbone:
Riseup only provides Jabber. Not IRC. |
correct I was mistaken, they host multi-user chatrooms not IRC. Functionality seems equivalent though, the Tails folks seemed to find no problem with it. |
They're using it for developer chat set up by appointment. Not public The question is if there are any clients that would provide the comfort |
not sure what the difference is idling on jabber vs IRC. however all users would need to have riseup.net jabber accounts I think, which is a much larger issue. so we can scrap that idea. |
If you actively used IRC clients for years, and then tried to do the same with Jabber clients, you will know. I haven't seen any community public support channel move to Jabber yet. (It's probably not the protocol that lacks something, but the clients.) |
Jabber, as far as I observed it, always needs users to register an account. Accounts on IRC are most times optional. Maybe that's one point why it's less popular for public chat. |
@mfc I think what @adrelanos is talking about is how a lot (most?) users in an IRC room, are not actually there meaning online, but are rather "in the room" still. This is because a lot of people run screen or tmux from a server so can turn off their laptop but still get messages from people at the IRC identity! |
OTFC works fine for me, though it has a self-signed cert. Can't even connect to freenode because of Tor blocking. I propose for now promoting using OTFC and go from there. |
changed on website to OFTC -- thanks @axon-qubes for correcting.... >.< if Tor, Whonix, Tails moves somewhere else we can always change it. |
currently,
#qubes
onirc.freenode.net
is the unofficial QubesOS IRC channel according to the Qubes website.freenode blocks tor connections. given that Qubes recommends users use torified whonix gateway for network traffic, it is weird to point them to a channel that they cannot access.
The Tor Project's IRC channel is on OTFC, as is Tails and Whonix.
It probably makes sense to instead advertise a
#qubes
channel on OTFC, which allows torified connections.The text was updated successfully, but these errors were encountered: