Commit 4e9ec0d0 authored by Evan Prodromou's avatar Evan Prodromou

merge from testing

parents 24c3a151 c637fe8c
......@@ -3,7 +3,7 @@ README
StatusNet 0.8.2 ("Life and How to Live It")
26 Aug 2009
1 Nov 2009
This is the README file for StatusNet (formerly Laconica), the Open
Source microblogging platform. It includes installation instructions,
......@@ -77,49 +77,79 @@ for additional terms.
New this version
This is a minor feature and bugfix release since version 0.8.0,
released Jul 15 2009. Notable changes this version:
- Laconica has been renamed StatusNet. With a few minor compatibility
exceptions, all references to "Laconica" in code, documentation
and comments were changed to "StatusNet".
- A new plugin to support "infinite scroll".
- A new plugin to support reCaptcha <>.
- Better logging of server errors.
- Add an Openid-only mode for authentication.
- 'lite' parameter for some Twitter API methods.
- A new plugin to auto-complete nicknames for @-replies.
- Configuration options to disable OpenID, SMS, Twitter, post-by-email, and IM.
- Support for lighttpd <> using 404-based
- Support for using Twitter's OAuth authentication as a client.
- First version of the groups API.
- Can configure a site-wide design, including background image and
- Improved algorithm for replies and conversations, making
conversation trees more accurate and useful.
- Add a script to create a simulation database for testing/debugging.
- Sanitize HTML for OEmbed.
- Improved queue management for DB-based queuing.
- More complete URL detection.
- Hashtags now support full Unicode character set.
- Notice inboxes are now garbage-collected on a regular basis
at notice-write time.
- PiwikAnalyticsPlugin updated for latest Piwik interface.
- Attachment and notice pages can be embedded with OEmbed
- Failed authentication is logged.
- PostgreSQL schema and support brought up-to-date with 0.8.x features.
- The installer works with PostgreSQL as well as MySQL.
- RSS 1.0 feeds use HTTP Basic authentication in private mode.
- Many, many bug fixes, particularly with performance.
- Better (=working) garbage collection for old sessions.
- Better (=working) search queries.
- Some cleanup of HTML output.
- Better error handling when updating Facebook.
- Considerably better performance when using replication for API
- Initial unit tests.
This is a minor feature and bugfix release since version 0.8.1,
released Aug 26 2009. Notable changes this version:
- New script for deleting user accounts. Not particularly safe or
community-friendly. Better for deleting abusive accounts than for
users who are 'retiring'.
- Improved detection of URLs in notices, specifically for punctuation
chars like ~, :, $, _, -, +, !, @, and %.
- Removed some extra <dl> semantic HTML code.
- Correct error in status-network database ini file (having multiple
statusnet sites with a single codebase)
- Fixed error output for Twitter posting failures.
- Fixed bug in Twitter queue handler that requeued inapplicable
notices ad infinitum.
- Improve FOAF output for remote users.
- new commands to join and leave groups.
- Fixed bug in which you cannot turn off importing friends timelines
- Better error handling in Twitter posting.
- Show oEmbed data for XHTML files as well as plain HTML.
- Updated bug database link in README.
- require HTML tidy extension.
- add support for HTTP Basic Auth in PHP CGI or FastCGI (e.g. GoDaddy).
- autofocus input to selected entry elements depending on page.
- updated layout for filter-by-tag form.
- better layout for inbox and outbox pages.
- fix highlighting search terms in attributes of notice list elements.
- Correctly handle errors in linkback plugin.
- Updated biz theme.
- Updated cloudy theme.
- Don't match '::' as an IPv6 address.
- Use the same decision logic for deciding whether to mark an
attachment as an enclosure in RSS or as a paperclip item in Web
- Fixed a bug in the Piwik plugin that hard-coded the site ID.
- Add a param, inreplyto, to notice/new to allow an explicit response
to another notice.
- Show username in subject of emails.
- Check if avatar exists before trying to delete it.
- Correctly add omb_version to response for request token in OMB.
- Add a few more SMS carriers.
- Add a few more notice sources.
- Vary: header.
- Improvements to the AutoCompletePlugin.
- Check for 'dl' before using it.
- Make it impossible to delete self-subscriptions via the API.
- Fix pagination of tagged user pages.
- Make PiwikAnalyticsPlugin work with addPlugin().
- Removed trailing single space in user nicknames in notice lists.
- Show context link if a notice starts a conversation.
- blacklist all files and directories in install dir.
- handle GoDaddy-style PATH_INFO, including script name.
- add home_timeline synonym for friends_timeline.
- Add a popup window for the realtime plugin.
- Add some more streams for the realtime plugin.
- Fix a bug that overwrote group creation timestamp on every edit.
- Moved HTTP error code strings to a class variable.
- The Twitter API now returns server errors in the correct format.
- Reset the doctype for HTML output.
- Fixed a number of notices.
- Don't show search suggestions for private sites.
- Some corrections to FBConnect nav overrides.
- Slightly less database-intensive session management.
- Updated name of software in installer script.
- Include long-form attachment URLs if url-shortener is disabled.
- Include updated localisations for Polish, Greek, Hebrew, Icelandic,
Norwegian, and Chinese.
- Include upstream fixes to gettext.php.
- Correct for regression in Facebook API for updates.
- Ignore "Sent from my iPhone" (and similar) in mail updates.
- Use the NICKNAME_FMT constant for detecting nicknames.
- Check for site servername config'd.
- Compatibility fix for empty status updates with Twitter API.
......@@ -225,9 +255,9 @@ especially if you've previously installed PHP/MySQL packages.
1. Unpack the tarball you downloaded on your Web server. Usually a
command like this will work:
tar zxf statusnet-0.8.1.tar.gz
tar zxf statusnet-0.8.2.tar.gz
...which will make a statusnet-0.8.1 subdirectory in your current
...which will make a statusnet-0.8.2 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.)
......@@ -235,7 +265,7 @@ especially if you've previously installed PHP/MySQL packages.
2. Move the tarball to a directory of your choosing in your Web root
directory. Usually something like this will work:
mv statusnet-0.8.1 /var/www/mublog
mv statusnet-0.8.2 /var/www/mublog
This will make your StatusNet instance available in the mublog path of
your server, like "". "microblog" or
......@@ -669,7 +699,7 @@ with this situation.
If you've been using StatusNet 0.7, 0.6, 0.5 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. There is no automated
upgrade procedure in StatusNet 0.8.1. Try these step-by-step
upgrade procedure in StatusNet 0.8.2. 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
......@@ -690,7 +720,7 @@ instructions; read to the end first before trying them.
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 "mublog.bak".
7. Unpack your StatusNet 0.8.1 tarball and move it to "mublog" or
7. Unpack your StatusNet 0.8.2 tarball and move it to "mublog" or
wherever your code used to be.
8. Copy the config.php file and avatar directory from your old
directory to your new directory.
......@@ -1432,7 +1462,7 @@ repository (see below), and you get a compilation error ("unexpected
T_STRING") in the browser, check to see that you don't have any
conflicts in your code.
If you upgraded to StatusNet 0.8.1 without reading the "Notice
If you upgraded to StatusNet 0.8.2 without reading the "Notice
inboxes" section above, and all your users' 'Personal' tabs are empty,
read the "Notice inboxes" section above.
......@@ -1540,6 +1570,7 @@ if anyone's been overlooked in error.
* Jeffery To
* Federico Marani
* Craig Andrews
* mEDI
Thanks also to the developers of our upstream library code and to the
thousands of people who have tried out, installed StatusNet,
......@@ -192,7 +192,9 @@ class NewnoticeAction extends Action
if ($this->boolean('ajax')) {
header('Content-Type: text/xml;charset=utf-8');
$this->xw->startDocument('1.0', 'UTF-8');
$this->element('title', null, _('Notice posted'));
This directory is provided as a courtesy to our users who might be
unable or unwilling to find and install libraries we depend on.
If we "fix" software in this directory, we hamstring users who do the
right thing and keep a single version of upstream libraries in a
system-wide library. We introduce subtle and maddening bugs where
our code is "accidentally" using the "wrong" library version. We may
unwittingly interfere with other software that depends on the
canonical release versions of those same libraries!
Forking upstream software for trivial reasons makes us bad citizens in
the Open Source community and adds unnecessary heartache for our
users. Don't make us "that" project.
Q: What should we do when we find a bug in upstream software?
A: First and foremost, REPORT THE BUG, and if possible send in a patch.
Watch for a release of the upstream software and integrate with it
when it's released.
In the meantime, work around the bug, if at all possible. Usually,
it's quite possible, if slightly harder or less efficient.
Q: What if the bug can't be worked around?
A: If the upstream developers have accepted a bug patch, it's
undesirable but acceptable to apply that patch to the library in
the extlib dir. Ideally, use a release version for upstream or a
version control system snapshot.
Note that this is a last resort.
Q: What if upstream is unresponsive or won't accept a patch?
A: Try again.
Q: I tried again, and upstream is still unresponsive and nobody's
checked on my patch. Now what?
A: If the upstream project is moribund and there's a way to adopt it,
propose having the StatusNet dev team adopt the project. Or, adopt
it yourself.
Q: What if there's no upstream authority and it can't be adopted?
A: Then we fork it. Make a new name and a new version. Include it in
lib/ instead of extlib/, and use the StatusNet_* prefix to change
the namespace to avoid collisions.
This is a last resort; consult with the rest of the dev group
before taking this radical step.
......@@ -781,12 +781,18 @@ function common_path($relative, $ssl=false)
if (is_string(common_config('site', 'sslserver')) &&
mb_strlen(common_config('site', 'sslserver')) > 0) {
$serverpart = common_config('site', 'sslserver');
} else {
} else if (common_config('site', 'server')) {
$serverpart = common_config('site', 'server');
} else {
common_log(LOG_ERR, 'Site Sever not configured, unable to determine site name.');
} else {
$proto = 'http';
$serverpart = common_config('site', 'server');
if (common_config('site', 'server')) {
$serverpart = common_config('site', 'server');
} else {
common_log(LOG_ERR, 'Site Sever not configured, unable to determine site name.');
return $proto.'://'.$serverpart.'/'.$pathpart.$relative;
Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment