Being able to write your own rules, log everything, manage your bots however you like, all that stuff is nice. Being able to turn the server off if there is something seriously bad (like a stolen credit card dump for example) is priceless.
-- This post brought to you by Database Barbie
Starting Score:
1
point
Moderation
+3
Insightful=3,
Total=3
Extra 'Insightful' Modifier
0
Total Score:
4
(Score: 1, Funny) by Anonymous Coward on Tuesday March 11 2014, @10:28PM
by Anonymous Coward
on Tuesday March 11 2014, @10:28PM (#14916)
I know the first thing I think of when I hear yet another batch of CC numbers or passwords are leaked is "Damn, I sure hope the chat network I frequent isn't still running!"
Huh. I guess I never thought of that. Here I was just thinking of the legal ramifications of having a bunch of potential legal problems with my channel and needing to be able to preserve data for the Feds. Good thing AC is here to point out the real dangers.
(Score: 0) by Anonymous Coward on Wednesday March 12 2014, @02:03AM
by Anonymous Coward
on Wednesday March 12 2014, @02:03AM (#14985)
Legal ramifications of legal problems? That's a lot of legal. It is just...the luxury edition has so much more legal. It saddens me to think of you missing out.
But anyway, you can still run a bot so you can hand over the logs to the feds, even on freenode. It's just that I don't see the connection between that and turning off the server when there's a data breach somewhere, which is what I was rejoining.
AC was talking about using freenode (or equivalent service) and then that service got hacked and hackers got hold of our passwords and stuffs.
That's a danger.
Running our own IRC does not negate _that_ danger, though, as hackers who can hack freenode also can hack pipedot or any other domain name that we end up using, and if they are good enough, they may still get away with the paswords and stuffs.
(Score: 0) by Anonymous Coward on Wednesday March 12 2014, @04:56PM
by Anonymous Coward
on Wednesday March 12 2014, @04:56PM (#15381)
I'm regularly on Freenode, the second soylent moved to the private server I stopped paying attention. I will not use a 3rd party server for this, IRC was originally thought to be the *independent* safe harbor. Everyone can gather in Freenode from soylent, pipedot and whoever else. Being bound to the good will of the soylent staff kind of defeats the purpose of a fallback channel. In terms of IRC it's freenode or nothing.
I totally agree. Like most nerds, I'm already on freenode. I'm not going to connect to another server just to join 1 channel. That is silly. And they're not going to do as good a job as freenode at managing the service...
Freenode itself was a group of ppl branching off the branches of http://www.efnet.org/ [efnet.org], which itself was a branch off the original IRC network ( not to be confused with http://www.ircnet.org/ [ircnet.org] ), which closed due to malicious server joins etc. Ironically, there is a front page notice of server hacking on the EFNet website as I write this. Security (nick collisions, netsplits, DOS floods, etc) were why freenode, undernet, and many others branched off to begin with (and due to many other reasons I'm sure).
I'm just saying, it is possible that the SN IRC could become the beginnings of yet another improved IRC server codebase if some of the community felt strongly enough to pursue it. Maybe not, and that's fine too, but I don't want to be the one to hamstring a group of others who are motivated enough to try.
There are certainly some very real security concerns when running an IRC server, even if segregated or stand-alone. I don't know what the costs would be for bandwidth usage if we joined it to the freenode, or any other IRC network, or how we would pay for those costs under our current organization/structure. It might, however, be worth the effort, in particular if part of our community decided they would want to dive into the code to improve things. They could of course just dive into the ircd-seven code of freenode too (I have no idea what codebase the SN IRC is based on).
The more that things change, the more they stay the same.
(Score: 0) by Anonymous Coward on Thursday March 13 2014, @08:17AM
by Anonymous Coward
on Thursday March 13 2014, @08:17AM (#15761)
Exactly, nerds are the visitors we are shooting for anyway. It's easy to say go to channel X on freenode. When you tell them you can find the/. ripoff on that network/channel no one is going to join.
(Score: 4, Insightful) by ancientt on Tuesday March 11 2014, @10:00PM
Being able to write your own rules, log everything, manage your bots however you like, all that stuff is nice. Being able to turn the server off if there is something seriously bad (like a stolen credit card dump for example) is priceless.
This post brought to you by Database Barbie
(Score: 1, Funny) by Anonymous Coward on Tuesday March 11 2014, @10:28PM
I know the first thing I think of when I hear yet another batch of CC numbers or passwords are leaked is "Damn, I sure hope the chat network I frequent isn't still running!"
(Score: 1) by ancientt on Wednesday March 12 2014, @12:23AM
Huh. I guess I never thought of that. Here I was just thinking of the legal ramifications of having a bunch of potential legal problems with my channel and needing to be able to preserve data for the Feds. Good thing AC is here to point out the real dangers.
This post brought to you by Database Barbie
(Score: 0) by Anonymous Coward on Wednesday March 12 2014, @02:03AM
Legal ramifications of legal problems? That's a lot of legal. It is just...the luxury edition has so much more legal. It saddens me to think of you missing out.
But anyway, you can still run a bot so you can hand over the logs to the feds, even on freenode. It's just that I don't see the connection between that and turning off the server when there's a data breach somewhere, which is what I was rejoining.
(Score: 1) by Taco Cowboy on Wednesday March 12 2014, @11:41AM
AC was talking about using freenode (or equivalent service) and then that service got hacked and hackers got hold of our passwords and stuffs.
That's a danger.
Running our own IRC does not negate _that_ danger, though, as hackers who can hack freenode also can hack pipedot or any other domain name that we end up using, and if they are good enough, they may still get away with the paswords and stuffs.
(Score: 0) by Anonymous Coward on Wednesday March 12 2014, @04:56PM
I'm regularly on Freenode, the second soylent moved to the private server I stopped paying attention. I will not use a 3rd party server for this, IRC was originally thought to be the *independent* safe harbor. Everyone can gather in Freenode from soylent, pipedot and whoever else. Being bound to the good will of the soylent staff kind of defeats the purpose of a fallback channel. In terms of IRC it's freenode or nothing.
(Score: 1) by Aighearach on Wednesday March 12 2014, @08:17PM
I totally agree. Like most nerds, I'm already on freenode. I'm not going to connect to another server just to join 1 channel. That is silly. And they're not going to do as good a job as freenode at managing the service...
(Score: 1) by NezSez on Thursday March 13 2014, @04:32AM
Freenode itself was a group of ppl branching off the branches of http://www.efnet.org/ [efnet.org], which itself was a branch off the original IRC network
( not to be confused with http://www.ircnet.org/ [ircnet.org] ), which closed due to malicious server joins etc.
Ironically, there is a front page notice of server hacking on the EFNet website as I write this.
Security (nick collisions, netsplits, DOS floods, etc) were why freenode, undernet, and many others branched off to begin with (and due to many other reasons I'm sure).
I'm just saying, it is possible that the SN IRC could become the beginnings of yet another improved IRC server codebase if some of the community felt strongly enough to pursue it.
Maybe not, and that's fine too, but I don't want to be the one to hamstring a group of others who are motivated enough to try.
There are certainly some very real security concerns when running an IRC server, even if segregated or stand-alone. I don't know what the costs would be for bandwidth usage if we joined it to the freenode, or any other IRC network, or how we would pay for those costs under our current organization/structure. It might, however, be worth the effort, in particular if part of our community decided they would want to dive into the code to improve things. They could of course just dive into the ircd-seven code of freenode too (I have no idea what codebase the SN IRC is based on).
The more that things change, the more they stay the same.
No Sig to see here, move along, move along...
(Score: 2) by xlefay on Thursday March 13 2014, @07:02PM
We're actually using Charybdis on which ircd-seven is based ;-)
(Score: 0) by Anonymous Coward on Thursday March 13 2014, @08:17AM
Exactly, nerds are the visitors we are shooting for anyway. It's easy to say go to channel X on freenode. When you tell them you can find the /. ripoff on that network/channel no one is going to join.