|
New Social Networking Graphs |
 |
 |
 |
|
Written by Phantomal
|
|
Friday, 14 August 2009 10:23 |
|
Dear Users, alongside with working on the stability of the servers and services, we're working on new features we can provide to you. And today we want to present you the newest one: The Social Networking Graph Generator. With this feature you can get a map of the userinteractions in your channel. You ever wondered who is talking with who and how much? Now you can see this on a shiny and clear graphic. If you want to know more about this cool new Feature klick here. Greetings, Phantomal |
|
|
Written by Phantomal
|
|
Saturday, 08 August 2009 22:45 |
|
Dear Users, today we updated our software to the new versions of InspIRCd (1.2 Release Candidate 4) and Anope (1.9.1 svn version). While the update of InspIRCd was planned, the update of Anope was unplanned because the old version is not working with the new InspIRCd version. The changelog of InspIRCd shows, that very much bugs have been fixed since RC3. And many of them were bugs wich lead to a server crash or a netsplit. So we believe, that this update will significantly improve our stability. With the Update of Anope, we again enabled email confirmation on registration. This means you will receive a confirmation mail after you registered a nick. This mail contains a nickserv command wich you have to enter at irc. After your email adress is confirmed, you can use your nick. Another change is, that a bug in our DNS Blacklist module has been fixed in RC4. So it is not longer possible to connect to SolidIRC using a TOR anonymous proxy connection. Greetings, Phantomal |
|
Written by Phantomal
|
|
Tuesday, 07 July 2009 20:34 |
|
Hello, i forgot to explain how to get an exception limit for SolidIRC. So here it is: SolidIRC allows 3 connects per IP Adress. This Limit is enforced by our servers. We had those limits in history too, but the new system is only limiting the connect and not killing all users from that ip when someone tries to break that limit. So when you try to connect a 4. client, you will not get a gline for that. You're simply not able to connect. If you're a Bouncer provider or there's another good reason why you need a higher gobal connection limit, we can add an exception. The new exceptions have to be configured at serverlevel wich can only be done by Phantomal. This results in a more strict policy for adding exceptions, because each exception is a possible security problem. If you need an Exception, you have to request it via eMail. You can use
This e-mail address is being protected from spambots. You need JavaScript enabled to view it
or
This e-mail address is being protected from spambots. You need JavaScript enabled to view it
for that. To make it easy for us and to make the process faster for you, you should give the mail a Subject like "Exception Request for SolidIRC". You have to provide the (static) IP Adress for the exception, the number of global connects you need and a reason why you need that exception. Some contact data and an information about the service you're running would be nice to. If it's something wich could be useful to our users we will announce it on this Website. If we accept the exception, we will add it in one or two workdays. If we deny it, we will send you a mail with the reason. Greetings, Phantomal |
|
|
Written by Phantomal
|
|
Tuesday, 14 July 2009 12:15 |
|
Dear Users, as most of you noticed, SolidIRC is undergoing some issues with the stability of our servers. There are different reasons for this, and i want to expalin some of them: 1. The IRC Daemon
We used UnrealIRCd for years. We started in 2003 with a beta Version of unreal, wich was really unstable. We had the same Problems we now having with this release candidate version of InspIRCd 1.2. We decided to use InspIRCd in future and i was sure it should be stable because i know what "Release Candidate" means in developer language. Unfortunately i was wrong. InspIRCd 1.2 is a great program, and i still believe it will work perfectly in some time, but now its having some issues wich let the servers crash from time to time. Last Week we had 2 IRCd crashes wich resulted in short splits because i was around and could start them soon after the crash. 2. The Provider
As you remember we had a longer downtime of our Mainhub with Services and Stats. This downtime was the direct result of a routing Problem of "Versatel", wich is the Internet Services Provider for our Server Provider "Xantron Online". This routing problem disconnected the whole Xantron datacenter from the internet and took aprox 7 hours to fix. I got the information that a part of the Versatel equippment dropped out and had to be replaced. 3. The Servers
Yesterday we had some connection Issues to "Hostway Europe", where Starfleet is hosted. The Problems didn't result in a Netsplit, but in many ping timeouts. Additional the bsr server has been rebootet many times. Im not root on that server, so i have no idea what happened there. I reactivated it this morning, wich resulted in a very short connect split. I write this, because i think we had way to much splits this week. And as you can see, it is not allways helping much to spread the servers over 3 different Hosting Companies because it is possible that all companies having issues at the same time. Im sure, even with this Release Candidate of InspIRCd we should split only sometimes. I hope you still enjoy your stay at SolidIRC and im sorry for all inconvenience caused by this situation. Greetings, Phantomal |
|
The King is dead. Long live the King |
|
|
|
|
Written by Phantomal
|
|
Monday, 22 June 2009 07:33 |
|
Dear Users, as announced on Friday, we changed our ircd and services software on saturday. And i have to say that everything worked out much better than i expected. The Network was available all the time and we switched server by server to the new ircd software. At 12:00 we disabled the last old server and the old services and at 12:30 the new services were up und running. We had only one bigger problem, and that was a bug wich makes the services crash when you delete the last user on a channel access list. But with the help of the Anope developer team we fixed this in a very short time. (Thanks again guys). Statserv was back shortly after the services. Most users i talked to said that the new registration isn't a big deal. And we're really happy that it seems that no nickstealing happened. Channelowner were able to register their channels for the new services before they were installed on the production enviroment, wich means that channel stealing has been prevented too. So we could relax and focus on user support. One open issue we will address soon is the maximum connection limit per host. The new servers are able to see globally how many users connected from a single IP Address, and if the limit of 3 is reached its simply not possible to connect a 4. client. On the old server you could connect 3 clients per server wich makes 12 per ip. We limited it to 3 via our services wich set a gline when the exception limit was reached. The advantage of the old system was, that it was really easy to raise an exception for a single ip (to allow bouncers for example.). The new System is a bit more complex to configure but more secure. In the next few days we will add a way for BNC or webchat provider (like Mibbit) to use a higher exception limit. We will announce it on our homepage when this is finished. Greetings, Phantomal |
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 Next > End >>
|
|
Page 3 of 7 |
