The list of good and stable Jabber-Clients is finished. If you don’t know which one to choose, or which one’s a good one, maybe this helps you a bit. You can find the list if you hover your mouse over “How to chat” – second line.
Candy got finetuned and should now also run on IE (rumors say down to version 7, but I really really hope you are not using Windows XP anymore).
Jappix got it’s latest updates and a short maintainance. – But I still can’t figure out why Jappix needs AGES to send a Message to the chatrooms.
Oh, by the way: Teamspeak 3 Server is up, and maybe I will add a mumble server.
I worked a bit more on the different chatsystems.
First of all: Jappix is available again. But it has no priority if it comes to errors.
Candy now connects to both rooms. “chat” and “bedroom” are now available.
Fixed some errors that images were not shown on this page.
I had to get rid of some old encryption algorythms. RC4 is now disabled, which brings me back the “A” rating on SSLlabs.
Changed the look and feel of the IAF homepage. There are no longer two different menus. You can find Jappix, candy and all tutorials in the menu above.
Due numerous errors, bugs and instability, the chatsystem was changed.
I am sorry if you got used to Jappix, but lately I had too much trouble maintaining it.
People couldn’t connect, messages couldn’t be sent or got recieved by the Server…
I switched the chat to “candy” – Its a way simpler system, but it’s also easier to use and less buggy.
Look to the right. There is a nice menu leading you to the chat, the webmailer and to the account creation.
I hope you like it.
Sorry for the recent restarts.
I upgraded the is-a-furry.org Serverconfiguration to fit the latest security and encryption guidelines.
Sadly I had to cut off SSLv3 due the “poodle” Problem.
Here is the latest SSL check for the Homepage:
and here the latest Security Check on XMPP.net:
Hello and good day,
Is a furry is moving to a new Host. And changes the Hoster in the same time. We are moving from 1and1 to a Bigger hoster with more possibillities and a better server. (Also a bigger bandwith and a better ddos protection).
The change will take place from 10th to 12th of October 2014.
This means on 10th of october, I will disable the feature for new registrations and move the domain to the new System. You still can use your account.
If you registrate between october 10th and 12th and you get an error message: Its mostly because of the move.
After 12th of october, everything should work just perfect.
Do you want to start your own little website? Maybe a furry blog or a forum?
If you want, you can use the “is-a-furry.org” domain for this. Like “https://Vincent.Pawstripe.is-a-furry.org” or “https://vincentfur.is-a-furry.org”. You don’t know how? You have no Idea how to set up a webpage?
You can write me an eMail and ask me for help.
BUT(!) there are some rules!
– To help you, I need to know WHAT you want to do. A short “about me” homepage, an Art Gallery, a forum, a community site? I need Informations.
– You need to stay legal!
– I don’t host yiff sites! (Art Galleries are ok, but no yiff dating sites or stuff like that)
What about the costs?
It’s free. But keep one thing in mind: Is-a-furry.org is a private project. Means I put my own money into this. And my time is limited. It can happen that a request takes some time. – But I am answering!
Today I had a review over all config Files on my webserver and I definitely needed some updates.
I created the SSL and TLS Configuration files for the webserver years ago. Ok, not years.. maybe two or three years ago. And since then, I just copied the configuration line and used it for setting up my stuff.
Today I made a SSL Test and I was shocked. I just got a “B”! – This can’t be. Then I had a look why. I didn’t used the new encryption Protocoll TLS Version 1.2 and I still allowed an very old and outdated one.
Time to rewrite my configuration. Sadly I still use an older version of my webserver – I still get updated and security fixes, but I can’t activate Forward Secrecy – yet. But the Problem is, if I update to the newer version, I have to rewrite all 26 configuration sites for my domains and for the webserver. And the new version is not stable… So I have to wait a bit longer.
Long things short:
I got my A Grade back. It’s just an A- but it is “as safe as it can be” at the moment.
SSL test homepage, webmailer and webclient for the chat
SSL test jabber/messaging in general
A and A- I think thats good for now.
Found the pictures in one of my backups.
Page is completely restored and up and running again.
For those which don’t know:
Is-a-furry.org runs an encrypted Teamspeak³ Server and a Mumble Server is planned.
At the moment I have to get things running here in europe again. So Please be patient.
Due some idiot wich used a bug and deleted the homepage and the webmailer, I had to repair it.
The main functionality is back. the webmailer is working and now I have to fix the looks.
After a long time with just minor things and bugfixes, today there is a big update.
Today was the “We encrypt our connection network” day. Many many XMPP Server Administrators participated and encrypted their connections, and refused unencrypted connections.
And XMPP.net set up a testing page for Serveradmins to test their servers. Well… Is-a-furry.org had a good A. With a score of 100, 90, 90 and 90. After I changed the certificate against one with a 4096 Bit encryption and changed some other variables and upgraded the serverconfiguration, Is-a-furry.org has now a “better” A. 100, 100, 9o, 90.
Anyways. I could easily change everything to a 100 overall, but then there would be some very serious connection problems. 100 overall cuts off many old clients and then many users would have to change to other clients.
This is the “safe as it can be” without cutting off half of the users. I hope you can live with that. But see by yourself:
Why is Google not accessable through is-a-furry.org? It’s simple: Google gives a shit on safe communication.
Google is as hypocrite as fuck. On one hand, they are “pissed” about that the NSA and other secret services try to spy/spied on their internal Datastreams. (From Servercenter to server center) But they are do nothing about to encrypt their XMPP Servers. It is a problem for them to implement and add encryption to their Serversoftware? Seriously? A Company like GOOGLE which programs software like Chrome, or Google earth is not able to add a Simple SSL/TLS encryption to an OPEN and DOCUMENTED Standard?
Google does not care about. And I don’t see any reason to give them a hand. Yes. Ignoring google maybe cuts off thousands of users from is-a-furry.org. But I am not willing to create a weak spot in the encryption chain for google. Google says they will encrypt their service. And as soon as they do this, they can connect to is-a-furry.org.