1. Unpack the tarball you downloaded on your Web server. Usually a
command like this will work:
- tar zxf statusnet-0.9.9.tar.gz
+ tar zxf statusnet-1.0.1.tar.gz
- ...which will make a statusnet-0.9.9 subdirectory in your current
+ ...which will make a statusnet-1.0.1 subdirectory in your current
directory. (If you don't have shell access on your Web server, you
may have to unpack the tarball on your local computer and FTP the
files to the server.)
2. Move the tarball to a directory of your choosing in your Web root
directory. Usually something like this will work:
- mv statusnet-0.9.9 /var/www/statusnet
+ mv statusnet-1.0.1 /var/www/statusnet
This will make your StatusNet instance available in the statusnet path of
your server, like "http://example.net/statusnet". "microblog" or
Themes
------
-There are two themes shipped with this version of StatusNet: "identica",
-which is what the Identi.ca site uses, and "default", which is a good
-basis for other sites.
+Older themes (version 0.9.x and below) no longer work with StatusNet
+1.0.x, due to major changes in the site layout. We ship with three new
+themes for this version, 'neo', 'neo-blue' and 'neo-light'.
As of right now, your ability to change the theme is site-wide; users
can't choose their own theme. Additionally, the only thing you can
You may want to start by copying the files from the default theme to
your own directory.
-NOTE: the HTML generated by StatusNet changed *radically* between
-version 0.6.x and 0.7.x. Older themes will need signification
-modification to use the new output format.
-
Translation
-----------
-------
The administrator can set the "private" flag for a site so that it's
-not visible to non-logged-in users. This might be useful for
-workgroups who want to share a social networking site for project
-management, but host it on a public server.
+not visible to non-logged-in users. (This is the default for new installs of version 1.0!)
+
+This might be useful for workgroups who want to share a social
+networking site for project management, but host it on a public
+server.
-Total privacy is not guaranteed or ensured. Also, privacy is
-all-or-nothing for a site; you can't have some accounts or notices
-private, and others public. The interaction of private sites
-with OStatus is undefined.
+Total privacy is attempted but not guaranteed or ensured. Private sites
+currently don't work well with OStatus federation.
Access to file attachments can also be restricted to logged-in users only.
+
1. Add a directory outside the web root where your file uploads will be
stored. Usually a command like this will work: