I joined identi.ca late 2009 ? early 2010 ? I'd always been interested in self-hosting and maintaining autonomous services, so set up indy.im. in October 2010. There were several motivations at the time. * So I could run my own bots. I had some on identi.ca but they kept being blocked/banned; which was fair enough. * As a proxy into twitter - so users could keep their own data, and to obfuscate location/ip addresses * as a mobile interface to UK #indymedia. I published a customised version of the mustard android apk, branded it with an indymedia logo, and hardwired some login credentials in it. Activists could use it on early smart phones and publish short pieces of news and photos to indy.im. The RSS for these would be pulled into the national/regional indymedia's * And as a personal microblog thing.
Sometime towards the end of 2011 news that identi.ca was changing started spreading. There was a push by lot's of North American users to selfhost. Sites like fragdev appeared. I think the oldest remaining one of those is Gomertronic http://dent.gomertronic.com/notice/1
@bob I think the history is missing an early federation wave that predates quitter. @lnxw48a1 @gomerx @jezra @johnnynull are around from that. Fall 2011
Somsants went live early 2012, we hoped other nodes would appear in other barrios de Barcelona and a new sovereign network would be born. But it never happened (yet, anyway). Back then we all ran statusnet software. I don't know the details on exactly how the transition to gnusocial happened. @mattl @mmn I think the !fediverse really took hold after the identica incident. It was as if the sun had been removed from the solar system. Just a few disorientated planets left behind. It was only then, once the overwhelmingly big central node had gone, that other nodes grew in equal conditions.
I also remember Erkan finding us and getting in touch personally by email. Pulling us together, letting us know we were not alone and creating a sense of sysadmin community. I found this old email.
-----------------8<---------------- From: Erkan Yilmaz Date: 2013/7/16 Subject: Fwd: 1. security hole in your Statusnet instance Hola, see below points 1 and 3-5 (don't make the patch public yet until we reach most of the SN admins) join also the SNadmins group (1) + the mailing list (2) so next time I have not so much work to do. Also: if you know the email of other SN admins, tell them please. Erkan
Hi, 1. we discovered today a SQL injection bug in Statusnet (SN) I'm trying to get hold of most SN admins but my dent (1) seems not to reach you (2) this is the fix: http://somsants.net/url/113352
2. The text at the bottom of your statusnet install says: http://somsants.net/url/3787 is a microblogging service brought to you by "Free Software Foundation". but the link is wrong (the part between " ") http://somsants.net/url/113353 3. don't distribute the patch for 1. yet in public before we reach all SN admins (3) 4. Joshua will report this soon as CVE 5. you can reach us in the freenode irc channel #statusnet
@tuttle I never ran my own StatusNet instance. I once ran a Friendica node and now Hubzilla. Setting up my own Microblogging platform has been on my bucket list for ages.