I had trouble too after I changed passwords as recommended; I decided to give client side certificates a go: https://freenode.net/certfp/
Works far better now and I have no longer clear text passwords; Also I can finally have it connect to #hibernate-dev automatically as it properly authenticates before trying to join. Using Konversation. Sanne On 13 October 2014 20:34, Max Rydahl Andersen <mande...@redhat.com> wrote: > 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 > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
