On 13 Oct 2014, at 20:48, Steve Ebersole wrote:
just a heads up that I have not been able to connect to freenode for
quite
a few weeks now. Still no idea what is up there.
freenode moved to require SSL for some connections afaik. Use 6697 for
port,
and they also changed hostsnames - thus use
irc.freenode.org if you
don't already
And finally the one that annoyed me in US last time I was there. AT&T
customers
cannot connect unless using SASL (
https://freenode.net/sasl/) - maybe
they extended
that to other providers ?
just some ideas.
/max
http://about.me/maxandersen