5 Laconica 0.7.4 ("Can't Get There From Here")
8 This is the README file for Laconica, the Open Source microblogging
9 platform. It includes installation instructions, descriptions of
10 options you can set, warnings, tips, and general info for
11 administrators. Information on using Laconica can be found in the
12 "doc" subdirectory or in the "help" section on-line.
17 Laconica (pronounced "luh-KAWN-ih-kuh") is a Free and Open Source
18 microblogging platform. It helps people in a community, company or
19 group to exchange short (140 character) messages over the Web. Users
20 can choose which people to "follow" and receive only their friends' or
21 colleagues' status messages. It provides a similar service to sites
22 like Twitter, Jaiku and Plurk.
24 With a little work, status messages can be sent to mobile phones,
25 instant messenger programs (GTalk/Jabber), and specially-designed
26 desktop clients that support the Twitter API.
28 Laconica supports an open standard called OpenMicroBlogging
29 <http://openmicroblogging.org/> that lets users on different Web sites
30 or in different companies subscribe to each others' notices. It
31 enables a distributed social network spread all across the Web.
33 Laconica was originally developed for the Open Software Service,
34 Identi.ca <http://identi.ca/>. It is shared with you in hope that you
35 too make an Open Software Service available to your users. To learn
36 more, please see the Open Software Service Definition 1.1:
38 http://www.opendefinition.org/ossd
43 This program is free software: you can redistribute it and/or modify
44 it under the terms of the GNU Affero General Public License as
45 published by the Free Software Foundation, either version 3 of the
46 License, or (at your option) any later version.
48 This program is distributed in the hope that it will be useful, but
49 WITHOUT ANY WARRANTY; without even the implied warranty of
50 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
51 Affero General Public License for more details.
53 You should have received a copy of the GNU Affero General Public
54 License along with this program, in the file "COPYING". If not, see
55 <http://www.gnu.org/licenses/>.
57 IMPORTANT NOTE: The GNU Affero General Public License (AGPL) has
58 *different requirements* from the "regular" GPL. In particular, if
59 you make modifications to the Laconica source code on your server,
60 you *MUST MAKE AVAILABLE* the modified version of the source code
61 to your users under the same license. This is a legal requirement
62 of using the software, and if you do not wish to share your
63 modifications, *YOU MAY NOT INSTALL LACONICA*.
65 Additional library software has been made available in the 'extlib'
66 directory. All of it is Free Software and can be distributed under
67 liberal terms, but those terms may differ in detail from the AGPL's
68 particulars. See each package's license file in the extlib directory
74 This is a minor bug-fix and feature release since version 0.7.3,
75 released Apr 4 2009. Notable changes this version:
77 - Improved handling of UTF-8 characters. The new code is *not* backwards
78 compatible by default; see "Upgrading" below for instructions on
79 converting existing databases to the correct character set.
80 - Unroll joins for large queries. This greatly enhanced database
81 performance -- up to 50x for some queries -- at the expense of making
82 an extra DB hit for some queries.
83 - Added an optional plugin to use WikiHashtags
84 (http://hashtags.wikia.com/) for the sidebar on hashtag pages.
85 - Optimized Twitter friend synchronization.
86 - Better error handling for Ajax posting of notices, including
87 HTTP errors and timeouts.
88 - Experimental Comet plugin -- supports the cometd and the Bayeux
89 protocol. Using this plugin, you can show "real time" updates on the
90 public and tag pages. However, server configuration is complex.
91 - If queues are enabled, update inboxes and memcached off-line. Speeds
92 up posting considerably.
93 - Correctly shorten links posted through XMPP.
94 - <link> elements for pagination, supported by some browsers like Opera.
95 - Corrected date format in search API.
96 - Made the public XRDS file work correctly.
101 The following software packages are *required* for this software to
104 - PHP 5.2.x. It may be possible to run this software on earlier
105 versions of PHP, but many of the functions used are only available
107 - MySQL 5.x. The Laconica database is stored, by default, in a MySQL
108 server. It has been primarily tested on 5.x servers, although it may
109 be possible to install on earlier (or later!) versions. The server
110 *must* support the MyISAM storage engine -- the default for most
111 MySQL servers -- *and* the InnoDB storage engine.
112 - A Web server. Preferably, you should have Apache 2.2.x with the
113 mod_rewrite extension installed and enabled.
115 Your PHP installation must include the following PHP extensions:
117 - Curl. This is for fetching files by HTTP.
118 - XMLWriter. This is for formatting XML and HTML output.
119 - MySQL. For accessing the database.
120 - GD. For scaling down avatar images.
121 - mbstring. For handling Unicode (UTF-8) encoded strings.
122 - gettext. For multiple languages. Default on many PHP installs.
124 For some functionality, you will also need the following extensions:
126 - Memcache. A client for the memcached server, which caches database
127 information in volatile memory. This is important for adequate
128 performance on high-traffic sites. You will also need a memcached
129 server to store the data in.
130 - Mailparse. Efficient parsing of email requires this extension.
131 Submission by email or SMS-over-email uses this extension.
132 - Sphinx Search. A client for the sphinx server, an alternative
133 to MySQL or Postgresql fulltext search. You will also need a
134 Sphinx server to serve the search queries.
136 You will almost definitely get 2-3 times better performance from your
137 site if you install a PHP bytecode cache/accelerator. Some well-known
138 examples are: eaccelerator, Turck mmcache, xcache, apc. Zend Optimizer
139 is a proprietary accelerator installed on some hosting sites.
144 A number of external PHP libraries are used to provide basic
145 functionality and optional functionality for your system. For your
146 convenience, they are available in the "extlib" directory of this
147 package, and you do not have to download and install them. However,
148 you may want to keep them up-to-date with the latest upstream version,
149 and the URLs are listed here for your convenience.
151 - DB_DataObject http://pear.php.net/package/DB_DataObject
152 - Validate http://pear.php.net/package/Validate
153 - OpenID from OpenIDEnabled (not the PEAR version!). We decided
154 to use the openidenabled.com version since it's more widely
155 implemented, and seems to be better supported.
156 http://openidenabled.com/php-openid/
157 - PEAR DB. Although this is an older data access system (new
158 packages should probably use PHP DBO), the OpenID libraries
159 depend on PEAR DB so we use it here, too. DB_DataObject can
160 also use PEAR MDB2, which may give you better performance
161 but won't work with OpenID.
162 http://pear.php.net/package/DB
163 - OAuth.php from http://oauth.googlecode.com/svn/code/php/
164 - markdown.php from http://michelf.com/projects/php-markdown/
165 - PEAR Mail, for sending out mail notifications
166 http://pear.php.net/package/Mail
167 - PEAR Net_SMTP, if you use the SMTP factory for notifications
168 http://pear.php.net/package/Net_SMTP
169 - PEAR Net_Socket, if you use the SMTP factory for notifications
170 http://pear.php.net/package/Net_Socket
171 - XMPPHP, the follow-up to Class.Jabber.php. Probably the best XMPP
172 library available for PHP. http://xmpphp.googlecode.com/. Note that
173 as of this writing the version of this library that is available in
174 the extlib directory is *significantly different* from the upstream
175 version (patches have been submitted). Upgrading to the upstream
176 version may render your Laconica site unable to send or receive XMPP
178 - Facebook library. Used for the Facebook application.
179 - PEAR Services_oEmbed. Used for some multimedia integration.
180 - PEAR HTTP_Request is an oEmbed dependency.
181 - PEAR Validate is an oEmbed dependency.
182 - PEAR Net_URL2 is an oEmbed dependency.
183 - Console_GetOpt for parsing command-line options.
185 A design goal of Laconica is that the basic Web functionality should
186 work on even the most restrictive commercial hosting services.
187 However, additional functionality, such as receiving messages by
188 Jabber/GTalk, require that you be able to run long-running processes
189 on your account. In addition, posting by email or from SMS require
190 that you be able to install a mail filter in your mail server.
195 Installing the basic Laconica Web component is relatively easy,
196 especially if you've previously installed PHP/MySQL packages.
198 1. Unpack the tarball you downloaded on your Web server. Usually a
199 command like this will work:
201 tar zxf laconica-0.7.4.tar.gz
203 ...which will make a laconica-0.7.4 subdirectory in your current
204 directory. (If you don't have shell access on your Web server, you
205 may have to unpack the tarball on your local computer and FTP the
206 files to the server.)
208 2. Move the tarball to a directory of your choosing in your Web root
209 directory. Usually something like this will work:
211 mv laconica-0.7.4 /var/www/mublog
213 This will make your Laconica instance available in the mublog path of
214 your server, like "http://example.net/mublog". "microblog" or
215 "laconica" might also be good path names. If you know how to
216 configure virtual hosts on your web server, you can try setting up
217 "http://micro.example.net/" or the like.
219 3. Make your target directory writeable by the Web server.
221 chmod a+w /var/www/mublog/
223 On some systems, this will probably work:
225 chgrp www-data /var/www/mublog/
226 chmod g+w /var/www/mublog/
228 If your Web server runs as another user besides "www-data", try
229 that user's default group instead. As a last resort, you can create
230 a new group like "mublog" and add the Web server's user to the group.
232 4. You should also take this moment to make your avatar subdirectory
233 writeable by the Web server. An insecure way to do this is:
235 chmod a+w /var/www/mublog/avatar
237 You can also make the avatar directory writeable by the Web server
238 group, as noted above.
240 5. Create a database to hold your microblog data. Something like this
243 mysqladmin -u "username" --password="password" create laconica
245 Note that Laconica must have its own database; you can't share the
246 database with another program. You can name it whatever you want,
249 (If you don't have shell access to your server, you may need to use
250 a tool like PHPAdmin to create a database. Check your hosting
251 service's documentation for how to create a new MySQL database.)
253 6. Create a new database account that Laconica will use to access the
254 database. If you have shell access, this will probably work from the
257 GRANT ALL on laconica.*
258 TO 'lacuser'@'localhost'
259 IDENTIFIED BY 'lacpassword';
261 You should change 'lacuser' and 'lacpassword' to your preferred new
262 username and password. You may want to test logging in to MySQL as
265 7. In a browser, navigate to the Laconica install script; something like:
267 http://yourserver.example.com/mublog/install.php
269 Enter the database connection information and your site name. The
270 install program will configure your site and install the initial,
271 almost-empty database.
273 8. You should now be able to navigate to your microblog's main directory
274 and see the "Public Timeline", which will be empty. If not, magic
275 has happened! You can now register a new user, post some notices,
276 edit your profile, etc. However, you may want to wait to do that stuff
277 if you think you can set up "fancy URLs" (see below), since some
278 URLs are stored in the database.
283 By default, Laconica will use URLs that include the main PHP program's
284 name in them. For example, a user's home profile might be
287 http://example.org/mublog/index.php/mublog/fred
289 On certain systems that don't support this kind of syntax, they'll
292 http://example.org/mublog/index.php?p=mublog/fred
294 It's possible to configure the software so it looks like this instead:
296 http://example.org/mublog/fred
298 These "fancy URLs" are more readable and memorable for users. To use
299 fancy URLs, you must either have Apache 2.x with .htaccess enabled and
300 mod_redirect enabled, -OR- know how to configure "url redirection" in
303 1. Copy the htaccess.sample file to .htaccess in your Laconica
304 directory. Note: if you have control of your server's httpd.conf or
305 similar configuration files, it can greatly improve performance to
306 import the .htaccess file into your conf file instead. If you're
307 not sure how to do it, you may save yourself a lot of headache by
308 just leaving the .htaccess file.
310 2. Change the "RewriteBase" in the new .htaccess file to be the URL path
311 to your Laconica installation on your server. Typically this will
312 be the path to your Laconica directory relative to your Web root.
314 3. Add or uncomment or change a line in your config.php file so it says:
316 $config['site']['fancy'] = true;
318 You should now be able to navigate to a "fancy" URL on your server,
321 http://example.net/mublog/main/register
323 If you changed your HTTP server configuration, you may need to restart
329 To use a Sphinx server to search users and notices, you also need
330 to install, compile and enable the sphinx pecl extension for php on the
331 client side, which itself depends on the sphinx development files.
332 "pecl install sphinx" should take care of that. Add "extension=sphinx.so"
333 to your php.ini and reload apache to enable it.
335 You can update your MySQL or Postgresql databases to drop their fulltext
336 search indexes, since they're now provided by sphinx.
338 On the sphinx server side, a script reads the main database and build
339 the keyword index. A cron job reads the database and keeps the sphinx
340 indexes up to date. scripts/sphinx-cron.sh should be called by cron
341 every 5 minutes, for example. scripts/sphinx.sh is an init.d script
342 to start and stop the sphinx search daemon.
347 Laconica supports a cheap-and-dirty system for sending update messages
348 to mobile phones and for receiving updates from the mobile. Instead of
349 sending through the SMS network itself, which is costly and requires
350 buy-in from the wireless carriers, it simply piggybacks on the email
351 gateways that many carriers provide to their customers. So, SMS
352 configuration is essentially email configuration.
354 Each user sends to a made-up email address, which they keep a secret.
355 Incoming email that is "From" the user's SMS email address, and "To"
356 the users' secret email address on the site's domain, will be
357 converted to a notice and stored in the DB.
359 For this to work, there *must* be a domain or sub-domain for which all
360 (or most) incoming email can pass through the incoming mail filter.
362 1. Run the SQL script carrier.sql in your Laconica database. This will
365 mysql -u "lacuser" --password="lacpassword" laconica < db/carrier.sql
367 This will populate your database with a list of wireless carriers
368 that support email SMS gateways.
370 2. Make sure the maildaemon.php file is executable:
372 chmod +x scripts/maildaemon.php
374 Note that "daemon" is kind of a misnomer here; the script is more
375 of a filter than a daemon.
377 2. Edit /etc/aliases on your mail server and add the following line:
379 *: /path/to/laconica/scripts/maildaemon.php
381 3. Run whatever code you need to to update your aliases database. For
382 many mail servers (Postfix, Exim, Sendmail), this should work:
386 You may need to restart your mail server for the new database to
389 4. Set the following in your config.php file:
391 $config['mail']['domain'] = 'yourdomain.example.net';
393 At this point, post-by-email and post-by-SMS-gateway should work. Note
394 that if your mail server is on a different computer from your email
395 server, you'll need to have a full installation of Laconica, a working
396 config.php, and access to the Laconica database from the mail server.
401 XMPP (eXtended Message and Presence Protocol, <http://xmpp.org/>) is the
402 instant-messenger protocol that drives Jabber and GTalk IM. You can
403 distribute messages via XMPP using the system below; however, you
404 need to run the XMPP incoming daemon to allow incoming messages as
407 1. You may want to strongly consider setting up your own XMPP server.
408 Ejabberd, OpenFire, and JabberD are all Open Source servers.
409 Jabber, Inc. provides a high-performance commercial server.
411 2. You must register a Jabber ID (JID) with your new server. It helps
412 to choose a name like "update@example.com" or "notice" or something
413 similar. Alternately, your "update JID" can be registered on a
414 publicly-available XMPP service, like jabber.org or GTalk.
416 Laconica will not register the JID with your chosen XMPP server;
417 you need to do this manually, with an XMPP client like Gajim,
418 Telepathy, or Pidgin.im.
420 3. Configure your site's XMPP variables, as described below in the
421 configuration section.
423 On a default installation, your site can broadcast messages using
424 XMPP. Users won't be able to post messages using XMPP unless you've
425 got the XMPP daemon running. See 'Queues and daemons' below for how
426 to set that up. Also, once you have a sizable number of users, sending
427 a lot of SMS, OMB, and XMPP messages whenever someone posts a message
428 can really slow down your site; it may cause posting to timeout.
430 NOTE: stream_select(), a crucial function for network programming, is
431 broken on PHP 5.2.x less than 5.2.6 on amd64-based servers. We don't
432 work around this bug in Laconica; current recommendation is to move
433 off of amd64 to another server.
438 You can send *all* messages from your microblogging site to a
439 third-party service using XMPP. This can be useful for providing
440 search, indexing, bridging, or other cool services.
442 To configure a downstream site to receive your public stream, add
443 their "JID" (Jabber ID) to your config.php as follows:
445 $config['xmpp']['public'][] = 'downstream@example.net';
447 (Don't miss those square brackets at the end.) Note that your XMPP
448 broadcasting must be configured as mentioned above. Although you can
449 send out messages at "Web time", high-volume sites should strongly
450 consider setting up queues and daemons.
455 Some activities that Laconica needs to do, like broadcast OMB, SMS,
456 and XMPP messages, can be 'queued' and done by off-line bots instead.
457 For this to work, you must be able to run long-running offline
458 processes, either on your main Web server or on another server you
459 control. (Your other server will still need all the above
460 prerequisites, with the exception of Apache.) Installing on a separate
461 server is probably a good idea for high-volume sites.
463 1. You'll need the "CLI" (command-line interface) version of PHP
464 installed on whatever server you use.
466 2. If you're using a separate server for queues, install Laconica
467 somewhere on the server. You don't need to worry about the
468 .htaccess file, but make sure that your config.php file is close
469 to, or identical to, your Web server's version.
471 3. In your config.php files (both the Web server and the queues
472 server!), set the following variable:
474 $config['queue']['enabled'] = true;
476 You may also want to look at the 'daemon' section of this file for
477 more daemon options. Note that if you set the 'user' and/or 'group'
478 options, you'll need to create that user and/or group by hand.
479 They're not created automatically.
481 4. On the queues server, run the command scripts/startdaemons.sh. It
482 needs as a parameter the install path; if you run it from the
483 Laconica dir, "." should suffice.
485 This will run eight (for now) queue handlers:
487 * xmppdaemon.php - listens for new XMPP messages from users and stores
488 them as notices in the database.
489 * jabberqueuehandler.php - sends queued notices in the database to
490 registered users who should receive them.
491 * publicqueuehandler.php - sends queued notices in the database to
492 public feed listeners.
493 * ombqueuehandler.php - sends queued notices to OpenMicroBlogging
494 recipients on foreign servers.
495 * smsqueuehandler.php - sends queued notices to SMS-over-email addresses
497 * xmppconfirmhandler.php - sends confirmation messages to registered
499 * twitterqueuehandler.php - sends queued notices to Twitter for user
500 who have opted to set up Twitter bridging.
501 * facebookqueuehandler.php - sends queued notices to Facebook for users
502 of the built-in Facebook application.
504 Note that these queue daemons are pretty raw, and need your care. In
505 particular, they leak memory, and you may want to restart them on a
506 regular (daily or so) basis with a cron job. Also, if they lose
507 the connection to the XMPP server for too long, they'll simply die. It
508 may be a good idea to use a daemon-monitoring service, like 'monit',
509 to check their status and keep them running.
511 All the daemons write their process IDs (pids) to /var/run/ by
512 default. This can be useful for starting, stopping, and monitoring the
515 Twitter Friends Syncing
516 -----------------------
518 As of Laconica 0.6.3, users may set a flag in their settings ("Subscribe
519 to my Twitter friends here" under the Twitter tab) to have Laconica
520 attempt to locate and subscribe to "friends" (people they "follow") on
521 Twitter who also have accounts on your Laconica system, and who have
522 previously set up a link for automatically posting notices to Twitter.
524 Optionally, there is a script (./scripts/synctwitterfriends.php), meant
525 to be run periodically from a job scheduler (e.g.: cron under Unix), to
526 look for new additions to users' friends lists. Note that the friends
527 syncing only subscribes users to each other, it does not unsubscribe
528 users when they stop following each other on Twitter.
532 # Update Twitter friends subscriptions every half hour
533 0,30 * * * * /path/to/php /path/to/laconica/scripts/synctwitterfriends.php>&/dev/null
535 Built-in Facebook Application
536 -----------------------------
538 Laconica's Facebook application allows your users to automatically
539 update their Facebook statuses with their latest notices, invite
540 their friends to use the app (and thus your site), view their notice
541 timelines, and post notices -- all from within Facebook. The application
542 is built into Laconica and runs on your host. For automatic Facebook
543 status updating to work you will need to enable queuing and run the
544 facebookqueuehandler.php daemon (see the "Queues and daemons" section
547 Quick setup instructions*:
549 Install the Facebook Developer application on Facebook:
551 http://www.facebook.com/developers/
553 Use it to create a new application and generate an API key and secret.
554 Uncomment the Facebook app section of your config.php and copy in the
555 key and secret, e.g.:
557 # Config section for the built-in Facebook application
558 $config['facebook']['apikey'] = 'APIKEY';
559 $config['facebook']['secret'] = 'SECRET';
561 In Facebook's application editor, specify the following URLs for your app:
563 - Callback URL: http://example.net/mublog/facebook/
564 - Post-Remove URL: http://example.net/mublog/facebook/remove
565 - Post-Add Redirect URL: http://apps.facebook.com/yourapp/
566 - Canvas URL: http://apps.facebook.com/yourapp/
568 (Replace 'example.net' with your host's URL, 'mublog' with the path
569 to your Laconica installation, and 'yourapp' with the name of the
570 Facebook application you created.)
572 Additionally, Choose "Web" for Application type in the Advanced tab.
573 In the "Canvas setting" section, choose the "FBML" for Render Method,
574 "Smart Size" for IFrame size, and "Full width (760px)" for Canvas Width.
575 Everything else can be left with default values.
577 *For more detailed instructions please see the installation guide on the
580 http://laconi.ca/trac/wiki/FacebookApplication
585 Sitemap files <http://sitemaps.org/> are a very nice way of telling
586 search engines and other interested bots what's available on your site
587 and what's changed recently. You can generate sitemap files for your
590 1. Choose your sitemap URL layout. Laconica creates a number of
591 sitemap XML files for different parts of your site. You may want to
592 put these in a sub-directory of your Laconica directory to avoid
593 clutter. The sitemap index file tells the search engines and other
594 bots where to find all the sitemap files; it *must* be in the main
595 installation directory or higher. Both types of file must be
596 available through HTTP.
598 2. To generate your sitemaps, run the following command on your server:
600 php scripts/sitemap.php -f index-file-path -d sitemap-directory -u URL-prefix-for-sitemaps
602 Here, index-file-path is the full path to the sitemap index file,
603 like './sitemapindex.xml'. sitemap-directory is the directory where
604 you want the sitemaps stored, like './sitemaps/' (make sure the dir
605 exists). URL-prefix-for-sitemaps is the full URL for the sitemap dir,
606 typically something like <http://example.net/mublog/sitemaps/>.
608 You can use several methods for submitting your sitemap index to
609 search engines to get your site indexed. One is to add a line like the
610 following to your robots.txt file:
612 Sitemap: /mublog/sitemapindex.xml
614 This is a good idea for letting *all* Web spiders know about your
615 sitemap. You can also submit sitemap files to major search engines
616 using their respective "Webmaster centres"; see sitemaps.org for links
622 There are two themes shipped with this version of Laconica: "identica",
623 which is what the Identi.ca site uses, and "default", which is a good
624 basis for other sites.
626 As of right now, your ability to change the theme is site-wide; users
627 can't choose their own theme. Additionally, the only thing you can
628 change in the theme is CSS stylesheets and some image files; you can't
629 change the HTML output, like adding or removing menu items.
631 You can choose a theme using the $config['site']['theme'] element in
632 the config.php file. See below for details.
634 You can add your own theme by making a sub-directory of the 'theme'
635 subdirectory with the name of your theme. Each theme can have the
638 display.css: a CSS2 file for "default" styling for all browsers.
639 ie6.css: a CSS2 file for override styling for fixing up Internet
641 ie7.css: a CSS2 file for override styling for fixing up Internet
643 logo.png: a logo image for the site.
644 default-avatar-profile.png: a 96x96 pixel image to use as the avatar for
645 users who don't upload their own.
646 default-avatar-stream.png: Ditto, but 48x48. For streams of notices.
647 default-avatar-mini.png: Ditto ditto, but 24x24. For subscriptions
648 listing on profile pages.
650 You may want to start by copying the files from the default theme to
653 NOTE: the HTML generated by Laconica changed *radically* between
654 version 0.6.x and 0.7.x. Older themes will need signification
655 modification to use the new output format.
660 Translations in Laconica use the gettext system <http://www.gnu.org/software/gettext/>.
661 Theoretically, you can add your own sub-directory to the locale/
662 subdirectory to add a new language to your system. You'll need to
663 compile the ".po" files into ".mo" files, however.
665 Contributions of translation information to Laconica are very easy:
666 you can use the Web interface at http://laconi.ca/pootle/ to add one
667 or a few or lots of new translations -- or even new languages. You can
668 also download more up-to-date .po files there, if you so desire.
673 There is no built-in system for doing backups in Laconica. You can make
674 backups of a working Laconica system by backing up the database and
675 the Web directory. To backup the database use mysqldump <http://ur1.ca/7xo>
676 and to backup the Web directory, try tar.
681 The administrator can set the "private" flag for a site so that it's
682 not visible to non-logged-in users. This might be useful for
683 workgroups who want to share a microblogging site for project
684 management, but host it on a public server.
686 Note that this is an experimental feature; total privacy is not
687 guaranteed or ensured. Also, privacy is all-or-nothing for a site; you
688 can't have some accounts or notices private, and others public.
689 Finally, the interaction of private sites with OpenMicroBlogging is
690 undefined. Remote users won't be able to subscribe to users on a
691 private site, but users of the private site may be able to subscribe
692 to users on a remote site. (Or not... it's not well tested.) The
693 "proper behaviour" hasn't been defined here, so handle with care.
698 IMPORTANT NOTE: Laconica 0.7.4 introduced a fix for some
699 incorrectly-stored international characters ("UTF-8"). For new
700 installations, it will now store non-ASCII characters correctly.
701 However, older installations will have the incorrect storage, and will
702 consequently show up "wrong" in browsers. See below for how to deal
705 If you've been using Laconica 0.6, 0.5 or lower, or if you've been
706 tracking the "git" version of the software, you will probably want
707 to upgrade and keep your existing data. There is no automated upgrade
708 procedure in Laconica 0.7.4. Try these step-by-step instructions; read
709 to the end first before trying them.
711 0. Download Laconica and set up all the prerequisites as if you were
713 1. Make backups of both your database and your Web directory. UNDER NO
714 CIRCUMSTANCES should you try to do an upgrade without a known-good
715 backup. You have been warned.
716 2. Shut down Web access to your site, either by turning off your Web
717 server or by redirecting all pages to a "sorry, under maintenance"
719 3. Shut down XMPP access to your site, typically by shutting down the
720 xmppdaemon.php process and all other daemons that you're running.
721 If you've got "monit" or "cron" automatically restarting your
722 daemons, make sure to turn that off, too.
723 4. Shut down SMS and email access to your site. The easy way to do
724 this is to comment out the line piping incoming email to your
725 maildaemon.php file, and running something like "newaliases".
726 5. Once all writing processes to your site are turned off, make a
727 final backup of the Web directory and database.
728 6. Move your Laconica directory to a backup spot, like "mublog.bak".
729 7. Unpack your Laconica 0.6 tarball and move it to "mublog" or
730 wherever your code used to be.
731 8. Copy the config.php file and avatar directory from your old
732 directory to your new directory.
733 9. Copy htaccess.sample to .htaccess in the new directory. Change the
734 RewriteBase to use the correct path.
735 10. Rebuild the database. For MySQL, go to your Laconica directory and
736 run the rebuilddb.sh script like this:
738 ./scripts/rebuilddb.sh rootuser rootpassword database db/laconica.sql
740 Here, rootuser and rootpassword are the username and password for a
741 user who can drop and create databases as well as tables; typically
742 that's _not_ the user Laconica runs as.
743 For PostgreSQL databases there is an equivalent, rebuilddb_psql.sh,
744 which operates slightly differently. Read the documentation in that
745 script before running it.
746 11. Use mysql or psql client to log into your database and make sure that
747 the notice, user, profile, subscription etc. tables are non-empty.
748 12. Turn back on the Web server, and check that things still work.
749 13. Turn back on XMPP bots and email maildaemon. Note that the XMPP
750 bots have changed since version 0.5; see above for details.
752 If you're upgrading from very old versions, you may want to look at
753 the fixup_* scripts in the scripts directories. These will store some
754 precooked data in the DB. All upgraders should check out the inboxes
757 NOTE: the database definition file, stoica.ini, has been renamed to
758 laconica.ini (since this is the recommended database name). If you
759 have a line in your config.php pointing to the old name, you'll need
765 Before version 0.6.2, the page showing all notices from people the
766 user is subscribed to ("so-and-so with friends") was calculated at run
767 time. Starting with 0.6.2, we have a new data structure for holding a
768 user's "notice inbox". (Note: distinct from the "message inbox", which
769 is the "inbox" tab in the UI. The notice inbox appears under the
772 Notices are added to the inbox when they're created. This speeds up
773 the query considerably, and also allows us the opportunity, in the
774 future, to add different kind of notices to an inbox -- like @-replies
775 or subscriptions to search terms or hashtags.
777 Notice inboxes are enabled by default for new installations. If you
778 are upgrading an existing site, this means that your users will see
779 empty "Personal" pages. The following steps will help you fix the
782 0. $config['inboxes']['enabled'] can be set to one of three values. If
783 you set it to 'false', the site will work as before. Support for this
784 will probably be dropped in future versions.
785 1. Setting the flag to 'transitional' means that you're in transition.
786 In this mode, the code will run the "new query" or the "old query"
787 based on whether the user's inbox has been updated.
788 2. After setting the flag to "transitional", you can run the
789 fixup_inboxes.php script to create the inboxes. You may want to set
790 the memory limit high. You can re-run it without ill effect.
791 3. When fixup_inboxes is finished, you can set the enabled flag to
797 Laconica 0.7.4 introduced a fix for some incorrectly-stored
798 international characters ("UTF-8"). This fix is not
799 backwards-compatible; installations from before 0.7.4 will show
800 non-ASCII characters of old notices incorrectly. This section explains
803 0. You can disable the new behaviour by setting the 'db''utf8' config
804 option to "false". You should only do this until you're ready to
805 convert your DB to the new format.
806 1. When you're ready to convert, you can run the fixup_utf8.php script
807 in the scripts/ subdirectory. If you've had the "new behaviour"
808 enabled (probably a good idea), you can give the ID of the first
809 "new" notice as a parameter, and only notices before that one will
810 be converted. Notices are converted in reverse chronological order,
811 so the most recent (and visible) ones will be converted first. The
812 script should work whether or not you have the 'db''utf8' config
814 2. When you're ready, set $config['db']['utf8'] to true, so that
815 new notices will be stored correctly.
817 Configuration options
818 =====================
820 The sole configuration file for Laconica (excepting configurations for
821 dependency software) is config.php in your Laconica directory. If you
822 edit any other file in the directory, like lib/common.php (where most
823 of the defaults are defined), you will lose your configuration options
824 in any upgrade, and you will wish that you had been more careful.
826 Starting with version 0.7.1, you can put config files in the
827 /etc/laconica/ directory on your server, if it exists. Config files
828 will be included in this order:
830 * /etc/laconica/laconica.php - server-wide config
831 * /etc/laconica/<servername>.php - for a virtual host
832 * /etc/laconica/<servername>_<pathname>.php - for a path
833 * INSTALLDIR/config.php - for a particular implementation
835 Almost all configuration options are made through a two-dimensional
836 associative array, cleverly named $config. A typical configuration
839 $config['section']['option'] = value;
841 For brevity, the following documentation describes each section and
847 This section is a catch-all for site-wide variables.
849 name: the name of your site, like 'YourCompany Microblog'.
850 server: the server part of your site's URLs, like 'example.net'.
851 path: The path part of your site's URLs, like 'mublog' or ''
853 fancy: whether or not your site uses fancy URLs (see Fancy URLs
854 section above). Default is false.
855 logfile: full path to a file for Laconica to save logging
856 information to. You may want to use this if you don't have
858 locale_path: full path to the directory for locale data. Unless you
859 store all your locale data in one place, you probably
860 don't need to use this.
861 language: default language for your site. Defaults to US English.
862 languages: A list of languages supported on your site. Typically you'd
863 only change this if you wanted to disable support for one
865 "unset($config['site']['languages']['de'])" will disable
867 theme: Theme for your site (see Theme section). Two themes are
868 provided by default: 'default' and 'stoica' (the one used by
869 Identi.ca). It's appreciated if you don't use the 'stoica' theme
870 except as the basis for your own.
871 email: contact email address for your site. By default, it's extracted
872 from your Web server environment; you may want to customize it.
873 broughtbyurl: name of an organization or individual who provides the
874 service. Each page will include a link to this name in the
875 footer. A good way to link to the blog, forum, wiki,
876 corporate portal, or whoever is making the service available.
877 broughtby: text used for the "brought by" link.
878 timezone: default timezone for message display. Users can set their
879 own time zone. Defaults to 'UTC', which is a pretty good default.
880 closed: If set to 'true', will disallow registration on your site.
881 This is a cheap way to restrict accounts to only one
882 individual or group; just register the accounts you want on
883 the service, *then* set this variable to 'true'.
884 inviteonly: If set to 'true', will only allow registration if the user
885 was invited by an existing user.
886 private: If set to 'true', anonymous users will be redirected to the
887 'login' page. Also, API methods that normally require no
888 authentication will require it. Note that this does not turn
889 off registration; use 'closed' or 'inviteonly' for the
891 notice: A plain string that will appear on every page. A good place
892 to put introductory information about your service, or info about
893 upgrades and outages, or other community info. Any HTML will
895 dupelimit: Time in which it's not OK for the same person to post the
896 same notice; default = 60 seconds.
897 logo: URL of an image file to use as the logo for the site. Overrides
898 the logo in the theme, if any.
899 ssl: Whether to use SSL and https:// URLs for some or all pages.
900 Possible values are 'always' (use it for all pages), 'never'
901 (don't use it for any pages), or 'sometimes' (use it for
902 sensitive pages that include passwords like login and registration,
903 but not for regular pages). Default to 'never'.
904 sslserver: use an alternate server name for SSL URLs, like
905 'secure.example.org'. You should be careful to set cookie
906 parameters correctly so that both the SSL server and the
907 "normal" server can access the session cookie and
908 preferably other cookies as well.
913 This section is a reference to the configuration options for
914 DB_DataObject (see <http://ur1.ca/7xp>). The ones that you may want to
915 set are listed below for clarity.
917 database: a DSN (Data Source Name) for your Laconica database. This is
918 in the format 'protocol://username:password@hostname/databasename',
919 where 'protocol' is 'mysql' or 'mysqli' (or possibly 'postgresql', if you
920 really know what you're doing), 'username' is the username,
921 'password' is the password, and etc.
922 ini_yourdbname: if your database is not named 'laconica', you'll need
923 to set this to point to the location of the
924 laconica.ini file. Note that the real name of your database
925 should go in there, not literally 'yourdbname'.
926 db_driver: You can try changing this to 'MDB2' to use the other driver
927 type for DB_DataObject, but note that it breaks the OpenID
928 libraries, which only support PEAR::DB.
929 debug: On a database error, you may get a message saying to set this
930 value to 5 to see debug messages in the browser. This breaks
931 just about all pages, and will also expose the username and
933 quote_identifiers: Set this to true if you're using postgresql.
934 type: either 'mysql' or 'postgresql' (used for some bits of
935 database-type-specific SQL in the code). Defaults to mysql.
936 mirror: you can set this to an array of DSNs, like the above
937 'database' value. If it's set, certain read-only actions will
938 use a random value out of this array for the database, rather
939 than the one in 'database' (actually, 'database' is overwritten).
940 You can offload a busy DB server by setting up MySQL replication
941 and adding the slaves to this array. Note that if you want some
942 requests to go to the 'database' (master) server, you'll need
943 to include it in this array, too.
944 utf8: whether to talk to the database in UTF-8 mode. This is the default
945 with new installations, but older sites may want to turn it off
946 until they get their databases fixed up. See "UTF-8 database"
952 By default, Laconica sites log error messages to the syslog facility.
953 (You can override this using the 'logfile' parameter described above).
955 appname: The name that Laconica uses to log messages. By default it's
956 "laconica", but if you have more than one installation on the
957 server, you may want to change the name for each instance so
958 you can track log messages more easily.
963 You can configure the software to queue time-consuming tasks, like
964 sending out SMS email or XMPP messages, for off-line processing. See
965 'Queues and daemons' above for how to set this up.
967 enabled: Whether to uses queues. Defaults to false.
972 The default license to use for your users notices. The default is the
973 Creative Commons Attribution 3.0 license, which is probably the right
974 choice for any public site. Note that some other servers will not
975 accept notices if you apply a stricter license than this.
977 url: URL of the license, used for links.
978 title: Title for the license, like 'Creative Commons Attribution 3.0'.
979 image: A button shown on each page for the license.
984 This is for configuring out-going email. We use PEAR's Mail module,
985 see: http://pear.php.net/manual/en/package.mail.mail.factory.php
987 backend: the backend to use for mail, one of 'mail', 'sendmail', and
988 'smtp'. Defaults to PEAR's default, 'mail'.
989 params: if the mail backend requires any parameters, you can provide
990 them in an associative array.
995 This is for configuring nicknames in the service.
997 blacklist: an array of strings for usernames that may not be
998 registered. A default array exists for strings that are
999 used by Laconica (e.g. 'doc', 'main', 'avatar', 'theme')
1000 but you may want to add others if you have other software
1001 installed in a subdirectory of Laconica or if you just
1002 don't want certain words used as usernames.
1003 featured: an array of nicknames of 'featured' users of the site.
1004 Can be useful to draw attention to well-known users, or
1005 interesting people, or whatever.
1010 For configuring avatar access.
1012 dir: Directory to look for avatar files and to put them into.
1013 Defaults to avatar subdirectory of install directory; if
1014 you change it, make sure to change path, too.
1015 path: Path to avatars. Defaults to path for avatar subdirectory,
1016 but you can change it if you wish. Note that this will
1017 be included with the avatar server, too.
1018 server: If set, defines another server where avatars are stored in the
1019 root directory. Note that the 'avatar' subdir still has to be
1020 writeable. You'd typically use this to split HTTP requests on
1021 the client to speed up page loading, either with another
1022 virtual server or with an NFS or SAMBA share. Clients
1023 typically only make 2 connections to a single server at a
1024 time <http://ur1.ca/6ih>, so this can parallelize the job.
1030 For configuring the public stream.
1032 localonly: If set to true, only messages posted by users of this
1033 service (rather than other services, filtered through OMB)
1034 are shown in the public stream. Default true.
1035 blacklist: An array of IDs of users to hide from the public stream.
1036 Useful if you have someone making excessive Twitterfeed posts
1037 to the site, other kinds of automated posts, testing bots, etc.
1042 server: Like avatars, you can speed up page loading by pointing the
1043 theme file lookup to another server (virtual or real).
1044 Defaults to NULL, meaning to use the site server.
1045 dir: Directory where theme files are stored. Used to determine
1046 whether to show parts of a theme file. Defaults to the theme
1047 subdirectory of the install directory.
1048 path: Path part of theme URLs, before the theme name. Relative to the
1049 theme server. It may make sense to change this path when upgrading,
1050 (using version numbers as the path) to make sure that all files are
1051 reloaded by caching clients or proxies. Defaults to null,
1052 which means to use the site path + '/theme'.
1057 For configuring the XMPP sub-system.
1059 enabled: Whether to accept and send messages by XMPP. Default false.
1060 server: server part of XMPP ID for update user.
1061 port: connection port for clients. Default 5222, which you probably
1062 shouldn't need to change.
1063 user: username for the client connection. Users will receive messages
1064 from 'user'@'server'.
1065 resource: a unique identifier for the connection to the server. This
1066 is actually used as a prefix for each XMPP component in the system.
1067 password: password for the user account.
1068 host: some XMPP domains are served by machines with a different
1069 hostname. (For example, @gmail.com GTalk users connect to
1070 talk.google.com). Set this to the correct hostname if that's the
1071 case with your server.
1072 encryption: Whether to encrypt the connection between Laconica and the
1073 XMPP server. Defaults to true, but you can get
1074 considerably better performance turning it off if you're
1075 connecting to a server on the same machine or on a
1077 debug: if turned on, this will make the XMPP library blurt out all of
1078 the incoming and outgoing messages as XML stanzas. Use as a
1079 last resort, and never turn it on if you don't have queues
1080 enabled, since it will spit out sensitive data to the browser.
1081 public: an array of JIDs to send _all_ notices to. This is useful for
1082 participating in third-party search and archiving services.
1087 Miscellaneous tagging stuff.
1089 dropoff: Decay factor for tag listing, in seconds.
1090 Defaults to exponential decay over ten days; you can twiddle
1091 with it to try and get better results for your site.
1096 For daemon processes.
1098 piddir: directory that daemon processes should write their PID file
1099 (process ID) to. Defaults to /var/run/, which is where this
1100 stuff should usually go on Unix-ish systems.
1101 user: If set, the daemons will try to change their effective user ID
1102 to this user before running. Probably a good idea, especially if
1103 you start the daemons as root. Note: user name, like 'daemon',
1105 group: If set, the daemons will try to change their effective group ID
1106 to this named group. Again, a name, not a numerical ID.
1111 You can get a significant boost in performance by caching some
1112 database data in memcached <http://www.danga.com/memcached/>.
1114 enabled: Set to true to enable. Default false.
1115 server: a string with the hostname of the memcached server. Can also
1116 be an array of hostnames, if you've got more than one server.
1117 base: memcached uses key-value pairs to store data. We build long,
1118 funny-looking keys to make sure we don't have any conflicts. The
1119 base of the key is usually a simplified version of the site name
1120 (like "Identi.ca" => "identica"), but you can overwrite this if
1121 you need to. You can safely ignore it if you only have one
1122 Laconica site using your memcached server.
1123 port: Port to connect to; defaults to 11211.
1128 You can get a significant boost in performance using Sphinx Search
1129 instead of your database server to search for users and notices.
1130 <http://sphinxsearch.com/>.
1132 enabled: Set to true to enable. Default false.
1133 server: a string with the hostname of the sphinx server.
1134 port: an integer with the port number of the sphinx server.
1139 A catch-all for integration with other systems.
1141 source: The name to use for the source of posts to Twitter. Defaults
1142 to 'laconica', but if you request your own source name from
1143 Twitter <http://twitter.com/help/request_source>, you can use
1144 that here instead. Status updates on Twitter will then have
1152 enabled: A three-valued flag for whether to use notice inboxes (see
1153 upgrading info above for notes about this change). Can be
1154 'false', 'true', or '"transitional"'.
1159 For notice-posting throttles.
1161 enabled: Whether to throttle posting. Defaults to false.
1162 count: Each user can make this many posts in 'timespan' seconds. So, if count
1163 is 100 and timespan is 3600, then there can be only 100 posts
1164 from a user every hour.
1165 timespan: see 'count'.
1172 banned: an array of usernames and/or profile IDs of 'banned' profiles.
1173 The site will reject any notices by these users -- they will
1174 not be accepted at all. (Compare with blacklisted users above,
1175 whose posts just won't show up in the public stream.)
1180 Options with new users.
1182 default: nickname of a user account to automatically subscribe new
1183 users to. Typically this would be system account for e.g.
1184 service updates or announcements. Users are able to unsub
1185 if they want. Default is null; no auto subscribe.
1186 welcome: nickname of a user account that sends welcome messages to new
1187 users. Can be the same as 'default' account, although on
1188 busy servers it may be a good idea to keep that one just for
1189 'urgent' messages. Default is null; no message.
1191 If either of these special user accounts are specified, the users should
1192 be created before the configuration is updated.
1197 The software will, by default, send statistical snapshots about the
1198 local installation to a stats server on the laconi.ca Web site. This
1199 data is used by the developers to prioritize development decisions. No
1200 identifying data about users or organizations is collected. The data
1201 is available to the public for review. Participating in this survey
1202 helps Laconica developers take your needs into account when updating
1205 run: string indicating when to run the statistics. Values can be 'web'
1206 (run occasionally at Web time), 'cron' (run from a cron script),
1207 or 'never' (don't ever run). If you set it to 'cron', remember to
1208 schedule the script to run on a regular basis.
1209 frequency: if run value is 'web', how often to report statistics.
1210 Measured in Web hits; depends on how active your site is.
1211 Default is 10000 -- that is, one report every 10000 Web hits,
1213 reporturl: URL to post statistics to. Defaults to Laconica developers'
1214 report system, but if they go evil or disappear you may
1215 need to update this to another value. Note: if you
1216 don't want to report stats, it's much better to
1217 set 'run' to 'never' than to set this value to something
1223 The software lets users upload files with their notices. You can configure
1224 the types of accepted files by mime types and a trio of quota options:
1225 per file, per user (total), per user per month.
1227 We suggest the use of the pecl file_info extension to handle mime type
1230 supported: an array of mime types you accept to store and distribute,
1231 like 'image/gif', 'video/mpeg', 'audio/mpeg', etc. Make sure you
1232 setup your server to properly reckognize the types you want to
1234 uploads: false to disable uploading files with notices (true by default).
1235 filecommand: The required MIME_Type library may need to use the 'file'
1236 command. It tries the one in the Web server's path, but if
1237 you're having problems with uploads, try setting this to the
1238 correct value. Note: 'file' must accept '-b' and '-i' options.
1240 For quotas, be sure you've set the upload_max_filesize and post_max_size
1241 in php.ini to be large enough to handle your upload. In httpd.conf
1242 (if you're using apache), check that the LimitRequestBody directive isn't
1243 set too low (it's optional, so it may not be there at all).
1245 file_quota: maximum size for a single file upload in bytes. A user can send
1246 any amount of notices with attachments as long as each attachment
1247 is smaller than file_quota.
1248 user_quota: total size in bytes a user can store on this server. Each user
1249 can store any number of files as long as their total size does
1250 not exceed the user_quota.
1251 monthly_quota: total size permitted in the current month. This is the total
1252 size in bytes that a user can upload each month.
1257 Options for group functionality.
1259 maxaliases: maximum number of aliases a group can have. Default 3. Set
1260 to 0 or less to prevent aliases in a group.
1265 oEmbed endpoint for multimedia attachments (links in posts).
1267 endpoint: oohembed endpoint using http://oohembed.com/ software.
1272 Some stuff for search.
1274 type: type of search. Ignored if PostgreSQL or Sphinx are enabled. Can either
1275 be 'fulltext' (default) or 'like'. The former is faster and more efficient
1276 but requires the lame old MyISAM engine for MySQL. The latter
1277 will work with InnoDB but could be miserably slow on large
1278 systems. We'll probably add another type sometime in the future,
1279 with our own indexing system (maybe like MediaWiki's).
1284 The primary output for Laconica is syslog, unless you configured a
1285 separate logfile. This is probably the first place to look if you're
1286 getting weird behaviour from Laconica.
1288 If you're tracking the unstable version of Laconica in the git
1289 repository (see below), and you get a compilation error ("unexpected
1290 T_STRING") in the browser, check to see that you don't have any
1291 conflicts in your code.
1293 If you upgraded to Laconica 0.7.4 without reading the "Notice inboxes"
1294 section above, and all your users' 'Personal' tabs are empty, read the
1295 "Notice inboxes" section above.
1300 These are some myths you may see on the Web about Laconica.
1301 Documentation from the core team about Laconica has been pretty
1302 sparse, so some backtracking and guesswork resulted in some incorrect
1305 - "Set $config['db']['debug'] = 5 to debug the database." This is an
1306 extremely bad idea. It's a tool built into DB_DataObject that will
1307 emit oodles of print lines directly to the browser of your users.
1308 Among these lines will be your database username and password. Do
1309 not enable this option on a production Web site for any reason.
1311 - "Edit dataobject.ini with the following settings..." dataobject.ini
1312 is a development file for the DB_DataObject framework and is not
1313 used by the running software. It was removed from the Laconica
1314 distribution because its presence was confusing. Do not bother
1315 configuring dataobject.ini, and do not put your database username
1316 and password into the file on a production Web server; unscrupulous
1317 persons may try to read it to get your passwords.
1322 If you're adventurous or impatient, you may want to install the
1323 development version of Laconica. To get it, use the git version
1324 control tool <http://git-scm.com/> like so:
1326 git clone http://laconi.ca/software/laconica.git
1328 To keep it up-to-date, use 'git pull'. Watch for conflicts!
1333 There are several ways to get more information about Laconica.
1335 * There is a mailing list for Laconica developers and admins at
1336 http://mail.laconi.ca/mailman/listinfo/laconica-dev
1337 * The #laconica IRC channel on freenode.net <http://www.freenode.net/>.
1338 * The Laconica wiki, http://laconi.ca/trac/
1343 * Microblogging messages to http://identi.ca/evan are very welcome.
1344 * Laconica's Trac server has a bug tracker for any defects you may find,
1345 or ideas for making things better. http://laconi.ca/trac/
1346 * e-mail to evan@identi.ca will usually be read and responded to very
1347 quickly, unless the question is really hard.
1352 The following is an incomplete list of developers who've worked on
1353 Laconi.ca. Apologies for any oversight; please let evan@identi.ca know
1354 if anyone's been overlooked in error.
1356 * Evan Prodromou, founder and lead developer, Control Yourself, Inc.
1357 * Zach Copley, Control Yourself, Inc.
1358 * Earle Martin, Control Yourself, Inc.
1359 * Marie-Claude Doyon, designer, Control Yourself, Inc.
1360 * Sarven Capadisli, Control Yourself, Inc.
1361 * Robin Millette, Control Yourself, Inc.
1372 * Tryggvi Björgvinsson
1376 * Ken Sheppardson (Trac server, man-about-town)
1377 * Tiago 'gouki' Faria (i18n managerx)
1379 * Leslie Michael Orchard
1383 * Tobias Diekershoff
1387 Thanks also to the developers of our upstream library code and to the
1388 thousands of people who have tried out Identi.ca, installed Laconi.ca,
1389 told their friends, and built the Open Microblogging network to what