StatusNet 1.0.0

This version has been superseded by StatusNet 1.0.1, which you should use instead.

Announcement
StatusNet version 1.0.0 was planned to be the next version following the StatusNet 0.9.9 release from Aug 2011.

It's the first release from the 1.0.x branch, which has been under development for about 18 months. The step from 0.9.9 to 1.0.0 may seem small numerically, but represents almost 2000 commits!

(To compare: the last branch change, 0.8.3 -> 0.9.0, was about 2600 changes. And there are about 2700 changes in-branch between 0.9.0 and 0.9.9!)

The current 1.0.0rc1 package can be found on the download pages and in the repositories at http://gitorious.org/statusnet/.

Evan expected identi.ca to be moved for OSCON 2011 (July 25 - 29) and his tutorial Building Social Applications with StatusNet. (I missed that one by about 6 weeks. -Evan) The personal sites hosted at *.status.net and the community sites were planned to be moved earlier than that ...

Download
Release candidate 1: 1.0.0rc1: http://status.net/statusnet-1.0.0rc1.tar.gz

Upgrade
If you've been using StatusNet 0.9.9 or lower, or if you've been tracking the "git" version of the software, you will probably want to upgrade and keep your existing data. Try these step-by-step instructions; read to the end first before trying them.

0. Download StatusNet and set up all the prerequisites as if you were doing a new install.

1. Make backups of both your database and your Web directory. UNDER NO CIRCUMSTANCES should you try to do an upgrade without a known-good backup. You have been warned.

2. Shut down Web access to your site, either by turning off your Web server or by redirecting all pages to a "sorry, under maintenance" page.

3. Shut down XMPP access to your site, typically by shutting down the xmppdaemon.php process and all other daemons that you're running. If you've got "monit" or "cron" automatically restarting your daemons, make sure to turn that off, too.

4. Shut down SMS and email access to your site. The easy way to do this is to comment out the line piping incoming email to your maildaemon.php file, and running something like "newaliases".

5. Once all writing processes to your site are turned off, make a final backup of the Web directory and database.

6. Move your StatusNet directory to a backup spot, like "statusnet.bak".

7. Unpack your StatusNet 1.0.0 tarball and move it to "statusnet" or wherever your code used to be.

8. Copy the config.php file and the contents of the avatar/, background/, file/, and local/ subdirectories from your old directory to your new directory.

9. Copy htaccess.sample to .htaccess in the new directory. Change the RewriteBase to use the correct path.

10. Upgrade the database.

NOTE: this step is destructive and cannot be reversed. YOU CAN EASILY DESTROY YOUR SITE WITH THIS STEP. Don't do it without a known-good backup!

In your new StatusNet 1.0.0 directory and AFTER YOU MAKE A BACKUP run the upgrade.php script like this:

php ./scripts/upgrade.php

11. Use mysql or psql client to log into your database and make sure that the notice, user, profile, subscription etc. tables are non-empty.

12. Turn back on the Web server, and check that things still work.

13. Turn back on XMPP bots and email maildaemon.

NOTE: the 1.0.0 version of StatusNet changed the URLs for all admin panels from /admin/* to /panel/*. This now allows the (popular) username 'admin', but blocks the considerably less popular username 'panel'. If you have an existing user named 'panel', you should rename them before upgrading.

UTF-8 Database --

If you are upgrading from a 0.8.x or 0.9.x version, you can safely skip this section.

StatusNet 0.7.4 introduced a fix for some incorrectly-stored international characters ("UTF-8"). This fix is not backwards-compatible; installations from before 0.7.4 will show non-ASCII characters of old notices incorrectly. This section explains what to do.

0. You can disable the new behaviour by setting the 'db''utf8' config option to "false". You should only do this until you're ready to convert your DB to the new format.

1. When you're ready to convert, you can run the fixup_utf8.php script in the scripts/ subdirectory. If you've had the "new behaviour" enabled (probably a good idea), you can give the ID of the first "new" notice as a parameter, and only notices before that one will be converted. Notices are converted in reverse chronological order, so the most recent (and visible) ones will be converted first. The script should work whether or not you have the 'db''utf8' config option enabled.

2. When you're ready, set $config['db']['utf8'] to true, so that new notices will be stored correctly.

Older versions --

IMPORTANT NOTE: StatusNet 0.7.4 introduced a fix for some incorrectly-stored international characters ("UTF-8"). For new installations, it will now store non-ASCII characters correctly. However, older installations will have the incorrect storage, and will consequently show up "wrong" in browsers. See below for how to deal with this situation.

NOTE: the database definition file, laconica.ini, has been renamed to statusnet.ini (since this is the recommended database name). If you have a line in your config.php pointing to the old name, you'll need to update it.

Note that the XMPP bots have changed since version 0.5; see above for details.

Privacy --

With StatusNet 1.0, our default install profile is for private sites.

If you did not specify the privacy level of your site previously, it was public. Now, it's private.

If you upgrade a public site, you will need to reset the privacy level. You can do this in your config.php:

$config['site']['private'] = false;

...or with setconfig.php in the db:

php setconfig.php site private false

...or with the site admin panel.

Changes
This is an abbreviate changelog.


 * Support for private updates, including private-to-groups, private                                                                                                          within a site, and private to followers only.
 * Conversation mode in streams; notices appear along with all replies.
 * Microapps -- post different types of activities to timelines, with                                                                                                          interaction. Events, bookmarks, Q&A, and polls included by default.
 * New 3-column layout in 'neo' theme by default. Older, 2-column layout themes have been removed.
 * Alphabetical, searchable user directory.
 * Alphabetical, searchable group directory.
 * Groups can require all posts to be private ('private groups'), and                                                                                                          limit members to the group.
 * Users can make all posts private to their followers ('private stream'),                                                                                                     and require authorization to follow.
 * General plugin for IM support; added AIM, IRC and MSN to existing                                                                                                           XMPP code.
 * Support for Twitter-like lists, to follow other users without                                                                                                               interfering with the home timeline.
 * Subscription to searches.
 * Subscription to tags.
 * Drupal-style schema system ("schemax") allows in-place database                                                                                                             upgrades from various software versions.
 * Fine-grained control of URL shortening, and an internal URL shortener
 * Extended profile for private, enterprise sites.
 * sites are private by default.
 * Blog plugin for extended posts.
 * Plugin to restrict all users of a site to a single email domain.
 * Plugin to send a daily email summary to site users.
 * Deeper integration with Activity Streams (http://activitystrea.ms) format.
 * Automated upgrade script.

Older and newer versions of StatusNet
Additional versions of the StatusNet code base can be downloaded from Gitorious at http://gitorious.org/statusnet/. If you get an error about the tarball not being available for download, try again in a few minutes. You may need to empty your browser's cache to clear the message. You can also get the latest stable release from http://status.net/download.

For versions before 1.0.0 see README for upgrade notes (note some have found it helpful to upgrade

http://status.net/statusnet-0.9.9.tar.gz (last pre 1.x stable release)

http://status.net/statusnet-0.9.8.tar.gz (very short lived release)

http://status.net/statusnet-0.9.7.tar.gz

http://status.net/statusnet-0.9.6.tar.gz

You may need to upgrade the database with one or both the following depending on the version you are running: mysql -u -p < db/08to09.sql mysql -u -p < db/096to097.sql Also check the database schema with ./scripts/checkschema.php