12. Juli 2013 um 22:04 Uhr von Atari-Frosch
After grmpyoldman has „urged” me to return to identi.ca I found that the site is soon going to change to pump.io. Well, that would be ok for me, but hey, status.net was not meant to be centralized. Since a while I considered to set up my own status.net server, so now I did.
Starting was easy: Download the tarball of the current version (1.1.0), in that case directly to my dedicated server, unpack it, read the INSTALL file and do what it says. It even tells how to create the database; not every installation instruction of a web application does that! Although, I stumbled upon a problem.
I went through the installation instruction until no. 7 and changed only that stuff I had to change to apply to my server. After the subdomain was created in the DNS I pointed my browser to it, got the installation form of status.net, gave it all the data it asked for and run the installation script. Then I wanted to start with the new installation, but got this error message:
The requested URL /main/login was not found on this server.
Well, actually that was correct. That directory did not exist in the status.net directory. So I wrote a status message on identi.ca about that problem, and then there was that nice guy called erkanyilmaz who directed me to the IRC channel #statusnet (English) on Freenode. A really nice and friendly channel! If you consider to play around with statusnet too, you should go there.
I explained the problem there, but it was unknown: No bug report, nothing in the forum. But then Erkan asked me whether I had copied the file htaccess-sample to .htaccess — and I hadn't. So I copied the file and configured it for my installation; all I had to change was the path in line 10 (RewriteBase). And, voilà, my browser showed me the login page of my status.net installation 🙂
Then I had the idea of putting these rewrite rules to the site's configuration in the /etc/apache2/sites-available/$site file as I'm used to do in WordPress installations. But that did not work: apache2 refused to start after that, telling me that the RewriteBase instruction cannot be used that way. So I put it back to the .htaccess file, and now it works again.
In the following weeks I didn't find much time to take care for the installation. I gave it a few plugins (OStatus, LilURL, AutoComplete) and followed all the accounts I used to follow on identi.ca directly.
A few days ago it was announced that identi.ca will eventually move to pump.io, so I downloaded my backup and deleted my identi.ca account. Side note about the backup file: I had downloaded one at end of May, and that one was around 200 kB smaller than the new one from July 10th. I checked the ends of the files and found that the first ended in Januar 2011, while the second ended in February 2011. So these backups are surely not complete! I had started my identi.ca account in 2009.
Today I tried to find all the people I was connected to as long as identi.ca still existed. It seems that most of them did not get themselves a statusnet instance or made an account in an existing one. To find at minimum all the people I know from the Pirate Party Germany I built a group !piratenpartei (thanks to some help; did I already mention that the status.net people are really helpful?) and now I hope to find some pirate folks there.
What I still don't like is that my status.net instance often seems to have some kind of session timeout. When I want to send a status update I often get an error message saying that the status update cannot be sent. [Update 2013-07-15 13:16]
(Sorry! We had trouble sending your notice (400 Bad Request). Please report the problem to the site administrator if this happens again.
Even pressing the send button a second time does not help, only copying the status update, changing to my profile and pasting it there to send it really sends it. I haven't found out where to change something to prevent this – or whether it is just a bug.
Well, in principle it works now, and if somebody wants to join statusnet on my instance, just tell me (I made it „invite only“).