SoylentNews is people
SoylentNews
This discussion has been archived.
No new comments can be posted.
Should we have an IRC network of our own?
|
Log In/Create an Account
| Top
| 92 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
For recreational use only.
(Score: 3, Interesting) by tynin on Tuesday March 11 2014, @10:47PM
I voted for go free with freenode, but after reading this, I'm sold with stay independant.
Also, the fortigate at work is blocking pipedot.org, so I really need this site to keep working. I know you cannot help in that regard, but I figured casting this out into the ether will let the ghosts in the machine know my preference so I might damn them should they fail me.
Really, anything to keep the SN message getting to workers who should be working, must be done at any cost.
(Score: 1) by bryan on Tuesday March 11 2014, @11:07PM
Both sites are using Linode; odd that any access would be different. Maybe try HTTPS instead of HTTP?
(Score: 3, Insightful) by Jaruzel on Wednesday March 12 2014, @09:00AM
Corporate proxys/firewalls such as Fortigate tend to block based on blacklists either provided by the supplier and/or maintained internally. As pipedot.org (and SN.org) is a tech news site, you should be able to ask your IT people to unblock it. It's possible that pipedot.org hasn't be classified yet, so is blocked by default (some places do that).
-Jar
This is my opinion, there are many others, but this one is mine.
(Score: 2, Informative) by francois on Wednesday March 12 2014, @06:26PM
Having your own IRC service is absolutely not a guarantee that it won't be blocked by corporate filtering.
Today, soylentnews.org is seen as Information Technology so will probably never be blocked by most filtering policies.
The web chat (chat.sylnt.org) is uncategorized. Most companies (if not all, in some regions) tend to BLOCK when it's uncategorized.
CISO feels safer, as users will not go to the uncategorized Internet. Support/admins cry, as they have to micro manage all the exceptions for the end users.
Of course, asking your BOFH to open a site for you might not be a good idea so the best way to make sure it's not blocked is to ask to the vendors. Most of them allow this, either via a web page or through an email.l #page/FOS_Cookbook/UTM/cb_utm_wf_url_check.html [fortinet.com]
Fortinet : http://docs-legacy.fortinet.com/cb/html/index.htm
Websense : http://csi.websense.com/ [websense.com]
ZScaler : http://zulu.zscaler.com/ [zscaler.com]
Bluecoat : https://sitereview.bluecoat.com/sitereview.jsp [bluecoat.com]
(etc...)
HTH !
--
Francois.
(Score: 2) by Jaruzel on Thursday March 13 2014, @09:41AM
Actually that does help me - thanks very much. It's quite hard digging up all those classification URLs for the different services, so I've bookmarked the above, Cheers.
(I'm having a classification issue with one of my own domains).
-Jar
This is my opinion, there are many others, but this one is mine.
(Score: 2) by Open4D on Wednesday March 12 2014, @06:44AM
lol
One thing people might want to consider is http://www.herdict.org/ [herdict.org] for keeping track of "Web blockages" - including deliberate local blocking of sites you care about. It's a bit crappy, but better than nothing, and I believe all the submitted data are free/open.