User talk:JustAnotherArchivist/hackint vs EFnet
< User talk:JustAnotherArchivist
Jump to navigation
Jump to search
Revision as of 09:35, 4 December 2021 by JustAnotherArchivist (talk | contribs) (→Disagreement/opinion)
Disagreement/opinion
- EFnet
- unstable
ok, if you care
- ridiculous channel, nick, and topic length limits
read the RFCs
- low channel join limits
ok
- varying degrees of IPv6 and TLS support depending on the server; no valid TLS certificates anywhere
do you really like Let's Encrypt monopoly? Things used to work without TLS earlier and no one cared. The same for IPv6
- no services
they explain why they don't want services.
- broken web chat
IRC is not web, it is another protocol. Also read the RFCs about the message length.
- Tor connections generally disallowed/banned
ok
- policy varying per server (e.g. no bots allowed on some servers)
better this than heavy centralization
- no IRCv3 support, and unlikely to ever be added
it is IRC, or Discord, or Matrix or Slack. Some people just want to enforce their opinion on "modern" things.
- Hackint (things not mentioned earlier)
- Tor connections welcome
no, they demand their PoW stuff or there is no way to use the services
- accessibility (XMPP etc., though that's apparently not working properly at the moment)
IRC is IRC. Once again.
- permissive policy (anything legal per German and Dutch laws is allowed)
it doesn't depend on the law, some smaller networks rarely ban people
- backed by like-minded people (Chaos Computer Club)
it would still be better if it was ran by a small group of friends, preferably accepting externally linked servers -- User:Cypherpunks, 2021-12-02
- The instability of EFnet was a horrible annoyance. The lack of services meant we had to maintain channel ops with (usually crappy) scripts, lost it sometimes, etc. There are better ways to spend one's time than regularly going through ~100 channels and fixing ops (for example, you know, archiving stuff). I'm familiar with the RFCs (and the countless ways in which all existing IRC connections, including EFnet, deviate from them), and they have nothing to do with configured length limits or the web chat's lack of line splitting. A working web chat is important so people who are unfamiliar with IRC can easily get in touch with us. Let's Encrypt doesn't have a monopoly on TLS certificates; they were the first to do so, but a few others offer free automatic certificates with ACME as well nowadays. 300 baud modems, 640K of RAM, and open shell logins used to work as well; why would anyone want progress or security? It's not the 80s anymore... –JustAnotherArchivist (talk) 09:35, 4 December 2021 (UTC)