Hi, SSL certificate expires now, I'm having a issue renewing it currently (It failed due to a error, and now it's a limit on the rate I can renew at). I will get it sorted ASAP.
Just a heads up if you get a SSL error later tonight.
We have a new member in our family. We got this Husky today. Been really nice, very kind and calm dog. Great with our kids, and they are very excited.
And she can be with us on any adventure, weather is no problem for this dog :)
I will put my personal projects on the back burner for a while, other more important things needs my focus.
It's not that I spend a lot of time with it - but it feels good to take a break from it all. I will run the social media sites I host as normal, but no coding for a while.
The code is out there - free for anyone to test and work with, free to use for what you want. I just do not have the drive for the time being, so I want to put things away and take a good break for a while.
It's been about 4 years since I started https://diasporapod.no, been running very well.
And very few issues, very little downtime. Users has been joining and finding their way over here.
Thanks to each and one of you who use it, keeps me motivated! :)
I'm having issues upgrading https://gnusocial.no to the latest version, I spent last night working on it, and some time earlier today, and will tonight as well, I want to get it up and running again as soon as possible. Not sure what the issue is yet, and not easy to get help.
I upgraded https://diasporapod.no to latest version. Sorry for lagging a little bit behind on that.
There has been so much stuff going on lately that I pushed that back a bit, but now it’s in sync again.
I will take a backup of everything and work on setting up 'nightly' version of gnusocial tonight on https://gnusocial.no , this also means https://diasporapod.no will be down while I do this work. Also I will upgrade some hardware as well.
It was brought to my attention today that https://diasporapod.no some times redirects to https://gnusocial.no - I host both on the same server. If it happens to you - then make sure you log in via the correct https:// url. I'm working on solving it.
Sorry about the confusion caused by this.
I work on fixing it as soon as possible (in between family life and work) - so it might take a little while to figure out exactly what goes wrong and how to reproduce it.