Difference between revisions of "User:JustAnotherArchivist/hackint vs EFnet"

From Archiveteam
Jump to navigation Jump to search
(Created page with "EFnet: * <span style="color: green">more decentralised</span> * <span style="color: green">old</span> * <span style="color: red">unstable (netsplits, server outages)</span> *...")
 
(Move TLS comment to the right point)
 
(5 intermediate revisions by the same user not shown)
Line 5: Line 5:
* <span style="color: red">unstable (netsplits, server outages)</span>
* <span style="color: red">unstable (netsplits, server outages)</span>
* <span style="color: red">ridiculous channel, nick, and topic length limits</span>
* <span style="color: red">ridiculous channel, nick, and topic length limits</span>
* <span style="color: red">low channel join limits (i.e. how many channels you can join from one connection) on almost all servers; limit varies between servers such that a reconnect might cause join errors</span>
* <span style="color: red">varying degrees of IPv6 and TLS support depending on the server; no valid TLS certificates anywhere</span>
** At least one server (irc.colosolutions.net) does not support anything higher than TLS 1.0. This means that you cannot connect to it on current Debian systems, where OpenSSL is configured to enforce TLS 1.2+ by default.
* <span style="color: red">no services</span>
* <span style="color: red">no services</span>
* <span style="color: red">broken web chat</span>
** While there are bots to re-op people automatically, this does not work reliably. For example, the rDNS fails from time to time, especially when many people are reconnecting after a server issue. We've also seen cases where the identd connection failed on a reconnect. These change the hostname and username, respectively, which causes the user mask to no longer be recognised by the opping bots. There is no good way to work around this.
* <span style="color: red">broken web chat (silent truncation of long messages)</span>
* <span style="color: red">Tor connections generally disallowed/banned (exact policy varying per server)</span>
* <span style="color: red">policy varying per server (e.g. no bots allowed on some servers)</span>
* <span style="color: red">no IRCv3 support, and unlikely to ever be added</span>


hackint:
hackint:
Line 13: Line 20:
* <span style="color: green">services (automatic opping/voicing, proper access control for restricted channels)</span>
* <span style="color: green">services (automatic opping/voicing, proper access control for restricted channels)</span>
* <span style="color: green">security: TLS required, valid TLS certificates (one of the few IRC networks!)</span>
* <span style="color: green">security: TLS required, valid TLS certificates (one of the few IRC networks!)</span>
* <span style="color: green">Tor connections welcome</span>
* <span style="color: green">accessibility (XMPP etc., though that's apparently not working properly at the moment)</span>
* <span style="color: green">accessibility (XMPP etc., though that's apparently not working properly at the moment)</span>
* <span style="color: green">policy</span>
* <span style="color: green">permissive policy (anything legal per German and Dutch laws is allowed)</span>
* <span style="color: green">backed by like-minded people (Chaos Computer Club)</span>
* <span style="color: green">backed by like-minded people (Chaos Computer Club)</span>
* <span style="color: green">(partial) IRCv3 support</span>
* <span style="color: red">not very old</span>
* <span style="color: red">not very old</span>
* <span style="color: red">run entirely by one organisation</span>
* <span style="color: orange">operated by regional chapters of the CCC</span>


Stability comparison over about 4 months (end of August to end of December), excluding network issues on my side:
Stability comparison over about 4 months (end of August to end of December), excluding network issues on my side:
Line 23: Line 32:
* EFnet: 8 disconnects, 68 netsplits of unknown total time because sometimes there is no proper rejoin of the split server; several server outages where everyone connected just suddenly times out, not easily trackable
* EFnet: 8 disconnects, 68 netsplits of unknown total time because sometimes there is no proper rejoin of the split server; several server outages where everyone connected just suddenly times out, not easily trackable
* hackint: zero disconnects, four netsplits totalling less than 10 minutes (574 seconds) and rejoining cleanly every time
* hackint: zero disconnects, four netsplits totalling less than 10 minutes (574 seconds) and rejoining cleanly every time
These numbers are based on connections from a server at OVH in Canada. The EFnet connections were to Colosolutions (New York); the hackint servers are in Germany and the Netherlands, but the details aren't known.

Latest revision as of 13:19, 23 August 2020

EFnet:

  • more decentralised
  • old
  • unstable (netsplits, server outages)
  • ridiculous channel, nick, and topic length limits
  • low channel join limits (i.e. how many channels you can join from one connection) on almost all servers; limit varies between servers such that a reconnect might cause join errors
  • varying degrees of IPv6 and TLS support depending on the server; no valid TLS certificates anywhere
    • At least one server (irc.colosolutions.net) does not support anything higher than TLS 1.0. This means that you cannot connect to it on current Debian systems, where OpenSSL is configured to enforce TLS 1.2+ by default.
  • no services
    • While there are bots to re-op people automatically, this does not work reliably. For example, the rDNS fails from time to time, especially when many people are reconnecting after a server issue. We've also seen cases where the identd connection failed on a reconnect. These change the hostname and username, respectively, which causes the user mask to no longer be recognised by the opping bots. There is no good way to work around this.
  • broken web chat (silent truncation of long messages)
  • Tor connections generally disallowed/banned (exact policy varying per server)
  • policy varying per server (e.g. no bots allowed on some servers)
  • no IRCv3 support, and unlikely to ever be added

hackint:

  • stable
  • services (automatic opping/voicing, proper access control for restricted channels)
  • security: TLS required, valid TLS certificates (one of the few IRC networks!)
  • Tor connections welcome
  • accessibility (XMPP etc., though that's apparently not working properly at the moment)
  • permissive policy (anything legal per German and Dutch laws is allowed)
  • backed by like-minded people (Chaos Computer Club)
  • (partial) IRCv3 support
  • not very old
  • operated by regional chapters of the CCC

Stability comparison over about 4 months (end of August to end of December), excluding network issues on my side:

  • EFnet: 8 disconnects, 68 netsplits of unknown total time because sometimes there is no proper rejoin of the split server; several server outages where everyone connected just suddenly times out, not easily trackable
  • hackint: zero disconnects, four netsplits totalling less than 10 minutes (574 seconds) and rejoining cleanly every time

These numbers are based on connections from a server at OVH in Canada. The EFnet connections were to Colosolutions (New York); the hackint servers are in Germany and the Netherlands, but the details aren't known.