dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.2.5
postmodern has joined #cinch
britneywright has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
sarkyniin has joined #cinch
sarkyniin has quit [Ping timeout: 256 seconds]
txdv has quit [Ping timeout: 264 seconds]
sydney_untangle has quit [Ping timeout: 264 seconds]
sydney_untangle has joined #cinch
sarkyniin has joined #cinch
sarkyniin has quit [Remote host closed the connection]
sarkyniin has joined #cinch
sarkyniin has quit [Ping timeout: 256 seconds]
sarkyniin has joined #cinch
sarkyniin has quit [Remote host closed the connection]
britneywright has joined #cinch
sarkyniin has joined #cinch
sarkyniin is now known as SomeDude
SomeDude is now known as SomeAnonDude
britneywright has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zer0python has joined #cinch
<zer0python>
do you guys know why cinch appears to be resetting its connection?
<zer0python>
it could be something else as I am running it in a VirtualBox
<zer0python>
was just wondering if anyone else here has experienced the issue
<leftylink>
I am so tempted to make some remark like "sometimes I wish that peer would stop resetting my connection" but that's not even relevant to the current situation so I should shut up now
<zer0python>
leftylink, it just seems odd that it seems to reset its connection like every 30-60 minutes
<zer0python>
it could be a peer issue
<zer0python>
it could be something else entirely
<zer0python>
what's odd is that it's only cinch, other IRC clients don't seem to have an issue.
SomeAnonDude has quit [Remote host closed the connection]
britneywright has joined #cinch
ChasedSpade has quit [Remote host closed the connection]