hackint

@hackintirc

hackint irc network

ircs://irc.hackint.org:6697
Joined October 2015

Tweets

You blocked @hackintirc

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @hackintirc

  1. Jan 2

    Hey , this is clearly worth looking into and one of the major reasons we're currently not supporting bridges into .

    Undo
  2. Retweeted
    8 Dec 2019
    Undo
  3. Retweeted
    14 Sep 2019

    OH: "Das I in IRC steht fuer Influencer"

    Undo
  4. Retweeted
    Undo
  5. Retweeted
    1 Jul 2019

    As scheduled in the Python 3 transition page, since July 1st 2019, the “python” plugin is now compiled with Python 3 by default. For more information, see the blog post:

    Undo
  6. Retweeted
    7 Jul 2019

    Debian "bullseye" repositories have been added on (amd64/i386 only).

    Undo
  7. Retweeted
    Undo
  8. Retweeted
    6 Jun 2019
    Undo
  9. Retweeted
    9 May 2019

    You are working in a blueteam or are just interested in defensive security? Let's meet in at the network.

    Undo
  10. Retweeted
    Undo
  11. Retweeted
    17 Feb 2019
    Undo
  12. 21 Nov 2018

    Our migration to is currently happening. Upon reconnect you will need to verify the new certificate. Please use your system trust store to verify certificates for .

    Undo
  13. 28 Oct 2018
    Undo
  14. 27 Oct 2018

    Yep, certificates are finally on their way. We'll publish a migration schedule as soon as we've figured out the remaining details.

    Undo
  15. 20 Oct 2018

    Network hardware had a fuse that failed and we are currently taking the time to do some long planned maintenance. All leafs have been relinked, the last one roughly 15 minutes ago.

    Show this thread
    Undo
  16. 20 Oct 2018

    A network outtage at one of our hubs is causing a rather grave series of netsplits, not all leafs are correctly relinking. Bridging of Tor, Jabber and Matrix users is affected. We have no ETA yet.

    Show this thread
    Undo
  17. 6 Aug 2018

    This is a reminder not to publicly repost spam messages, as that could very quickly result in an automated ban.

    Undo
  18. 31 Jul 2018

    Abuse is still ongoing, but were able to decrease the necessity for pattern matching by detecting the vulnerable SSH daemons that are being abused for this attack on connect. Also we're stronger together by using and submitting to DNS Blacklists like .

    Undo
  19. 30 Jul 2018

    We warned users of for a long time about the deprecation of the domain. We just delinked the IRCD running on that domain and replaced it with a miniircd, that informs users of the required migration. Use !

    Undo
  20. 29 Jul 2018

    And we're back up. Thanks for your patience!

    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·