On Saturday night, Quitter moved to a new server, updated the Statusnet software that powers it and refreshed the web interface. The new interface is very slick, and rather reminiscient of a proprietary microblogging platform. I suspect this is a deliberate move on the part of the site’s admins who clearly want to promote federated services as a viable alternative to locking your online presence into someone else’s silo.
However, I interact with the service through a number of clients (the exact one varies depending on what device I’m using and what else I’m doing), and it’s the clients that are the main focus of this post.
With the arrival of HTTPS support in Quitter, the configurations of some of these clients will need to be changed. So here’s a quick overview of my experiences so far.
This works out of the box, as expected. I like Mustard.
When I switched to Quitter, Jezra’s light, feature free, Statusnet client needed to be told to stop using HTPS. This, I did by checking the
Disable HTTPS option in the Settings tab.
Interestingly, Heybuddy still happily connects to the new Quitter with
Disable HTTPS checked. But since this is no longer necessary, and because using HTTPS is better than not using it, I have unchecked the option and restarted Heybuddy. And everything is working wonderfully.
Again, Quitter’s lack of HTTPS support led to a few questions around Identicurse when I switched. As with Heybuddy, using HTTPS is better than not using HTTPS. This can be switched on by amending your ~/.identicurse/auth.json file.
The relevant bit should be changed to look like this:
"use_oauth": false, "api_path": "https://quitter.se/api",
OAuth may well also be working by now, but that’s a test for another time.
Again, this works without HTTPS enabled, but it’s better to switch it on. In this case, you need to look for the TwitVim setings in ~/.vimrc. The bit that needs changing should be changed to look like this:
let twitvim_api_root = "https://quitter.se/api" let twitvim_cert_insecure = 0
When I moved from Identica, to Quitter, geting these clients to work without HTTPS was an occasionally painful process. So I have been pleasantly surprised at how painless the switch from HTTP to HTTPS has proved. So all that is left for me to do is to say thank you and well done to @hannes2peer and @3mp0 and ask that, if you use a different client, please do post the necessary config changes in the comments.