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, Pownce 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.0:
38 http://www.openknowledge.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 New features in version 0.6.0 include:
76 * Invitations by email.
77 * Users can mark messages as "favorites" (only Web, not API).
78 * A bridge to push messages on the Laconica instance to an account on
80 * Direct private messages between users on a server (only Web, not API
82 * Restructured off-line daemons.
87 The following software packages are *required* for this software to
90 - PHP 5.2.x. It may be possible to run this software on earlier
91 versions of PHP, but many of the functions used are only available
93 - MySQL 5.x. The Laconica database is stored, by default, in a MySQL
94 server. It has been primarily tested on 5.x servers, although it may
95 be possible to install on earlier (or later!) versions. The server
96 *must* support the MyISAM storage engine -- the default for most
97 MySQL servers -- *and* the InnoDB storage engine.
98 - A Web server. Preferably, you should have Apache 2.2.x with the
99 mod_rewrite extension installed and enabled.
101 Your PHP installation must include the following PHP extensions:
103 - Curl. This is for fetching files by HTTP.
104 - XMLWriter. This is for formatting XML and HTML output.
105 - MySQL. For accessing the database.
106 - GD. For scaling down avatar images.
107 - mbstring. For handling Unicode (UTF-8) encoded strings.
109 For some functionality, you will also need the following extensions:
111 - Memcache. A client for the memcached server, which caches database
112 information in volatile memory. This is important for adequate
113 performance on high-traffic sites. You will also need a memcached
114 server to store the data in.
115 - Mailparse. Efficient parsing of email requires this extension.
116 Submission by email or SMS-over-email uses this extension.
118 You will almost definitely get 2-3 times better performance from your
119 site if you install a PHP bytecode cache/accelerator. Some well-known
120 examples are: eaccelerator, Turck mmcache, xcache, apc. Zend Optimizer
121 is a proprietary accelerator installed on some hosting sites.
126 A number of external PHP libraries are used to provide basic
127 functionality and optional functionality for your system. For your
128 convenience, they are available in the "extlib" directory of this
129 package, and you do not have to download and install them. However,
130 you may want to keep them up-to-date with the latest upstream version,
131 and the URLs are listed here for your convenience.
133 - DB_DataObject http://pear.php.net/package/DB_DataObject
134 - Validate http://pear.php.net/package/Validate
135 - OpenID from OpenIDEnabled (not the PEAR version!). We decided
136 to use the openidenabled.com version since it's more widely
137 implemented, and seems to be better supported.
138 http://openidenabled.com/php-openid/
139 - PEAR DB. Although this is an older data access system (new
140 packages should probably use PHP DBO), the OpenID libraries
141 depend on PEAR DB so we use it here, too. DB_DataObject can
142 also use PEAR MDB2, which may give you better performance
143 but won't work with OpenID.
144 http://pear.php.net/package/DB
145 - OAuth.php from http://oauth.googlecode.com/svn/code/php/
146 - markdown.php from http://michelf.com/projects/php-markdown/
147 - PEAR Mail, for sending out mail notifications
148 http://pear.php.net/package/Mail
149 - PEAR Net_SMTP, if you use the SMTP factory for notifications
150 http://pear.php.net/package/Net_SMTP
151 - XMPPHP, the follow-up to Class.Jabber.php. Probably the best XMPP
152 library available for PHP. http://xmpphp.googlecode.com/. Note that
153 as of this writing the version of this library that is available in
154 the extlib directory is *significantly different* from the upstream
155 version (patches have been submitted). Upgrading to the upstream
156 version may render your Laconica site unable to send or receive XMPP
159 A design goal of Laconica is that the basic Web functionality should
160 work on even the most restrictive commercial hosting services.
161 However, additional functionality, such as receiving messages by
162 Jabber/GTalk, require that you be able to run long-running processes
163 on your account. In addition, posting by email or from SMS require
164 that you be able to install a mail filter in your mail server.
169 Installing the basic Laconica Web component is relatively easy,
170 especially if you've previously installed PHP/MySQL packages.
172 1. Unpack the tarball you downloaded on your Web server. Usually a
173 command like this will work:
175 tar zxf laconica-0.6.0.tar.gz
177 ...which will make a laconica-0.6.0 subdirectory in your current
178 directory. (If you don't have shell access on your Web server, you
179 may have to unpack the tarball on your local computer and FTP the
180 files to the server.)
182 2. Move the tarball to a directory of your choosing in your Web root
183 directory. Usually something like this will work:
185 mv laconica-0.6.0 /var/www/mublog
187 This will make your Laconica instance available in the mublog path of
188 your server, like "http://example.net/mublog". "microblog" or
189 "laconica" might also be good path names. If you know how to
190 configure virtual hosts on your web server, you can try setting up
191 "http://micro.example.net/" or the like.
193 3. You should also take this moment to make your avatar subdirectory
194 writeable by the Web server. An insecure way to do this is:
196 chmod a+w /var/www/mublog/avatar
198 On some systems, this will probably work:
200 chgrp www-data /var/www/mublog/avatar
201 chmod g+w /var/www/mublog/avatar
203 If your Web server runs as another user besides "www-data", try
204 that user's default group instead. As a last resort, you can create
205 a new group like "avatar" and add the Web server's user to the group.
207 4. Create a database to hold your microblog data. Something like this
210 mysqladmin -u "username" --password="password" create laconica
212 Note that Laconica must have its own database; you can't share the
213 database with another program. You can name it whatever you want,
216 (If you don't have shell access to your server, you may need to use
217 a tool like PHPAdmin to create a database. Check your hosting
218 service's documentation for how to create a new MySQL database.)
220 5. Run the laconica.sql SQL script in the db subdirectory to create
221 the database tables in the database. A typical system would work
224 mysql -u "username" --password="password" laconica < /var/www/mublog/db/laconica.sql
226 You may want to test by logging into the database and checking that
227 the tables were created. Here's an example:
231 6. Create a new database account that Laconica will use to access the
232 database. If you have shell access, this will probably work from the
235 GRANT SELECT,INSERT,DELETE,UPDATE on laconica.*
236 TO 'lacuser'@'localhost'
237 IDENTIFIED BY 'lacpassword';
239 You should change 'lacuser' and 'lacpassword' to your preferred new
240 username and password. You may want to test logging in as this new
241 user and testing that you can SELECT from some of the tables in the
242 DB (use SHOW TABLES to see which ones are there).
244 7. Copy the config.php.sample in the Laconica directory to config.php.
246 8. Edit config.php to set the basic configuration for your system.
247 (See descriptions below for basic config options.) Note that there
248 are lots of options and if you try to do them all at once, you will
249 have a hard time making sure what's working and what's not. So,
250 stick with the basics at first.
252 9. At this point, you should be able to navigate in a browser to your
253 microblog's main directory and see the "Public Timeline", which
254 will be empty. If not, magic has happened! You can now register a
255 new user, post some notices, edit your profile, etc. However, you
256 may want to wait to do that stuff if you think you can set up
257 "fancy URLs" (see below), since some URLs are stored in the database.
262 By default, Laconica will have big long sloppy URLs that are hard for
263 people to remember or use. For example, a user's home profile might be
266 http://example.org/mublog/index.php?action=showstream&nickname=fred
268 It's possible to configure the software so it looks like this instead:
270 http://example.org/mublog/fred
272 These "fancy URLs" are more readable and memorable for users. To use
273 fancy URLs, you must either have Apache 2.2.x with .htaccess enabled
274 and mod_redirect enabled, -OR- know how to configure "url redirection"
277 1. Copy the htaccess.sample file to .htaccess in your Laconica
278 directory. Note: if you have control of your server's httpd.conf or
279 similar configuration files, it can greatly improve performance to
280 import the .htaccess file into your conf file instead. If you're
281 not sure how to do it, you may save yourself a lot of headache by
282 just leaving the .htaccess file.
284 2. Change the "RewriteBase" in the new .htaccess file to be the URL path
285 to your Laconica installation on your server. Typically this will
286 be the path to your Laconica directory relative to your Web root.
288 3. Add or uncomment or change a line in your config.php file so it says:
290 $config['site']['fancy'] = true;
292 You should now be able to navigate to a "fancy" URL on your server,
295 http://example.net/mublog/main/register
297 If you changed your HTTP server configuration, you may need to restart
300 If you have problems with the .htaccess file on versions of Apache
301 earlier than 2.2.x, try changing the regular expressions in the
302 htaccess.sample file that use "\w" to just use ".".
307 Laconica supports a cheap-and-dirty system for sending update messages
308 to mobile phones and for receiving updates from the mobile. Instead of
309 sending through the SMS network itself, which is costly and requires
310 buy-in from the wireless carriers, it simply piggybacks on the email
311 gateways that many carriers provide to their customers. So, SMS
312 configuration is essentially email configuration.
314 Each user sends to a made-up email address, which they keep a secret.
315 Incoming email that is "From" the user's SMS email address, and "To"
316 the users' secret email address on the site's domain, will be
317 converted to a message and stored in the DB.
319 For this to work, there *must* be a domain or sub-domain for which all
320 (or most) incoming email can pass through the incoming mail filter.
322 1. Run the SQL script carrier.sql in your Laconica database. This will
325 mysql -u "lacuser" --password="lacpassword" laconica < db/carrier.sql
327 This will populate your database with a list of wireless carriers
328 that support email SMS gateways.
330 2. Make sure the maildaemon.php file is executable:
332 chmod +x scripts/maildaemon.php
334 Note that "daemon" is kind of a misnomer here; the script is more
335 of a filter than a daemon.
337 2. Edit /etc/aliases on your mail server and add the following line:
339 *: /path/to/laconica/scripts/maildaemon.php
341 3. Run whatever code you need to to update your aliases database. For
342 many mail servers (Postfix, Exim, Sendmail), this should work:
346 You may need to restart your mail server for the new database to
349 4. Set the following in your config.php file:
351 $config['mail']['domain'] = 'yourdomain.example.net';
353 At this point, post-by-email and post-by-SMS-gateway should work. Note
354 that if your mail server is on a different computer from your email
355 server, you'll need to have a full installation of Laconica, a working
356 config.php, and access to the Laconica database from the mail server.
361 XMPP (eXtended Message and Presence Protocol, http://xmpp.org/) is the
362 instant-messenger protocol that drives Jabber and GTalk IM. You can
363 distribute messages via XMPP using the system below; however, you
364 need to run the XMPP incoming daemon to allow incoming messages as
367 1. You may want to strongly consider setting up your own XMPP server.
368 Ejabberd, OpenFire, and JabberD are all Open Source servers.
369 Jabber, Inc. provides a high-performance commercial server.
371 2. You must register a Jabber ID (JID) with your new server. It helps
372 to choose a name like "update@example.com" or "notice" or something
373 similar. Alternately, your "update JID" can be registered on a
374 publicly-available XMPP service, like jabber.org or GTalk.
376 Laconica will not register the JID with your chosen XMPP server;
377 you need to do this manually, with an XMPP client like Gajim,
378 Telepathy, or Pidgin.im.
380 3. Configure your site's XMPP variables, as described below in the
381 configuration section.
383 On a default installation, your site can broadcast messages using
384 XMPP. Users won't be able to post messages using XMPP unless you've
385 got the XMPP daemon running. See 'Queues and daemons' below for how
386 to set that up. Also, once you have a sizable number of users, sending
387 a lot of SMS, OMB, and XMPP messages whenever someone posts a message
388 can really slow down your site; it may cause posting to timeout.
390 NOTE: stream_select(), a crucial function for network programming, is
391 broken on PHP 5.2.x less than 5.2.6 on amd64-based servers. We don't
392 work around this bug in Laconica; current recommendation is to move
393 off of amd64 to another server.
398 You can send *all* messages from your microblogging site to a
399 third-party service using XMPP. This can be useful for providing
400 search, indexing, bridging, or other cool services.
402 To configure a downstream site to receive your public stream, add
403 their "JID" (Jabber ID) to your config.php as follows:
405 $config['xmpp']['public'][] = 'downstream@example.net';
407 (Don't miss those square brackets at the end.) Note that your XMPP
408 broadcasting must be configured as mentioned above. Although you can
409 send out messages at "Web time", high-volume sites should strongly
410 consider setting up queues and daemons.
415 Some activities that Laconica needs to do, like broadcast OMB, SMS,
416 and XMPP messages, can be 'queued' and done by off-line bots instead.
417 For this to work, you must be able to run long-running offline
418 processes, either on your main Web server or on another server you
419 control. (Your other server will still need all the above
420 prerequisites, with the exception of Apache.) Installing on a separate
421 server is probably a good idea for high-volume sites.
423 1. You'll need the "CLI" (command-line interface) version of PHP
424 installed on whatever server you use.
426 2. If you're using a separate server for queues, install Laconica
427 somewhere on the server. You don't need to worry about the
428 .htaccess file, but make sure that your config.php file is close
429 to, or identical to, your Web server's version.
431 3. In your config.php files (both the Web server and the queues
432 server!), set the following variable:
434 $config['queue']['enabled'] = true;
436 4. On the queues server, run the command scripts/startdaemons.sh. It
437 needs as a parameter the install path; if you run it from the
438 Laconica dir, "." should suffice.
440 This will run six (for now) queue handlers:
442 * xmppdaemon.php - listens for new XMPP messages from users and stores
443 them as notices in the database.
444 * jabberqueuehandler.php - sends queued notices in the database to
445 registered users who should receive them.
446 * publicqueuehandler.php - sends queued notices in the database to
447 public feed listeners.
448 * ombqueuehandler.php - sends queued notices to OpenMicroBlogging
449 recipients on foreign servers.
450 * smsqueuehandler.php - sends queued notices to SMS-over-email addresses
452 * xmppconfirmhandler.php - sends confirmation messages to registered
455 Note that these queue daemons are pretty raw, and need your care. In
456 particular, they leak memory, and you may want to restart them on a
457 regular (daily or so) basis with a cron job. Also, if they lose
458 the connection to the XMPP server for too long, they'll simply die. It
459 may be a good idea to use a daemon-monitoring service, like 'monit',
460 to check their status and keep them running.
462 All the daemons write their process IDs (pids) to /var/run/ by
463 default. This can be useful for starting, stopping, and monitoring the
469 Sitemap files (http://sitemaps.org/) are a very nice way of telling
470 search engines and other interested bots what's available on your site
471 and what's changed recently. You can generate sitemap files for your
474 1. Choose your sitemap URL layout. Laconica creates a number of
475 sitemap XML files for different parts of your site. You may want to
476 put these in a sub-directory of your Laconica directory to avoid
477 clutter. The sitemap index file tells the search engines and other
478 bots where to find all the sitemap files; it *must* be in the main
479 installation directory or higher. Both types of file must be
480 available through HTTP.
482 2. To generate your sitemaps, run the following command on your server:
484 php scripts/sitemap.php -f index-file-path -d sitemap-directory -u URL-prefix-for-sitemaps
486 Here, index-file-path is the full path to the sitemap index file,
487 like './sitemapindex.xml'. sitemap-directory is the directory where
488 you want the sitemaps stored, like './sitemaps/' (make sure the dir
489 exists). URL-prefix-for-sitemaps is the full URL for the sitemap dir,
490 typically something like 'http://example.net/mublog/sitemaps/'.
492 You can use several methods for submitting your sitemap index to
493 search engines to get your site indexed. One is to add a line like the
494 following to your robots.txt file:
496 Sitemap: /mublog/sitemapindex.xml
498 This is a good idea for letting *all* Web spiders know about your
499 sitemap. You can also submit sitemap files to major search engines
500 using their respective "Webmaster centres"; see sitemaps.org for links
506 There are two themes shipped with this version of Laconica: "stoica",
507 which is what the Identi.ca site uses, and "default", which is a good
508 basis for other sites.
510 As of right now, your ability to change the theme is site-wide; users
511 can't choose their own theme. Additionally, the only thing you can
512 change in the theme is CSS stylesheets and some image files; you can't
513 change the HTML output, like adding or removing menu items.
515 You can choose a theme using the $config['site']['theme'] element in
516 the config.php file. See below for details.
518 You can add your own theme by making a sub-directory of the 'theme'
519 subdirectory with the name of your theme. Each theme can have the
522 display.css: a CSS2 file for "default" styling for all browsers.
523 ie6.css: a CSS2 file for override styling for fixing up Internet
525 ie7.css: a CSS2 file for override styling for fixing up Internet
527 logo.png: a logo image for the site.
528 default-avatar-profile.png: a 96x96 pixel image to use as the avatar for
529 users who don't upload their own.
530 default-avatar-stream.png: Ditto, but 48x48. For streams of notices.
531 default-avatar-mini.png: Ditto ditto, but 24x24. For subscriptions
532 listing on profile pages.
534 You may want to start by copying the files from the default theme to
540 Translations in Laconica use the gettext system (http://www.gnu.org/software/gettext/).
541 Theoretically, you can add your own sub-directory to the locale/
542 subdirectory to add a new language to your system. You'll need to
543 compile the ".po" files into ".mo" files, however.
548 If you've been using Laconica 0.5 or lower, or if you've been tracking
549 the "darcs" version of the software, you will probably want to upgrade
550 and keep your existing data. There is no automated upgrade procedure
551 in Laconica 0.6. Try these step-by-step instructions; read to the end
552 first before trying them.
554 0. Download Laconica and set up all the prerequisites as if you were
556 1. Make backups of both your database and your Web directory. UNDER NO
557 CIRCUMSTANCES should you try to do an upgrade without a known-good
558 backup. You have been warned.
559 2. Shut down Web access to your site, either by turning off your Web
560 server or by redirecting all pages to a "sorry, under maintenance"
562 3. Shut down XMPP access to your site, typically by shutting down the
563 xmppdaemon.php process and all other daemons that you're running.
564 If you've got "monit" or "cron" automatically restarting your
565 daemons, make sure to turn that off, too.
566 4. Shut down SMS and email access to your site. The easy way to do
567 this is to comment out the line piping incoming email to your
568 maildaemon.php file, and running something like "newaliases".
569 5. Once all writing processes to your site are turned off, make a
570 final backup of the Web directory and database.
571 6. Move your Laconica directory to a backup spot, like "mublog.bak".
572 7. Unpack your Laconica 0.6 tarball and move it to "mublog" or
573 wherever your code used to be.
574 8. Copy the config.php file and avatar directory from your old
575 directory to your new directory.
576 9. Copy htaccess.sample to .htaccess in the new directory. Change the
577 RewriteBase to use the correct path.
578 10. Rebuild the database. Go to your Laconica directory and run the
579 rebuilddb.sh script like this:
581 ./scripts/rebuilddb.sh rootuser rootpassword database db/laconica.sql
583 Here, rootuser and rootpassword are the username and password for a
584 user who can drop and create databases as well as tables; typically
585 that's _not_ the user Laconica runs as.
586 11. Use mysql client to log into your database and make sure that the
587 notice, user, profile, subscription etc. tables are non-empty.
588 12. Turn back on the Web server, and check that things still work.
589 13. Turn back on XMPP bots and email maildaemon. Note that the XMPP
590 bots have changed since version 0.5; see above for details.
592 If you're upgrading from very old versions, you may want to look at
593 the fixup_* scripts in the scripts directories. These will store some
594 precooked data in the DB.
596 Configuration options
597 =====================
599 The sole configuration file for Laconica (excepting configurations for
600 dependency software) is config.php in your Laconica directory. If you
601 edit any other file in the directory, like lib/common.php (where most
602 of the defaults are defined), you will lose your configuration options
603 in any upgrade, and you will wish that you had been more careful.
605 Almost all configuration options are made through a two-dimensional
606 associative array, cleverly named $config. A typical configuration
609 $config['section']['option'] = value;
611 For brevity, the following documentation describes each section and
617 This section is a catch-all for site-wide variables.
619 name: the name of your site, like 'YourCompany Microblog'.
620 server: the server part of your site's URLs, like 'example.net'.
621 path: The path part of your site's URLs, like 'mublog' or '/'
623 fancy: whether or not your site uses fancy URLs (see Fancy URLs
624 section above). Default is false.
625 logfile: full path to a file for Laconica to save logging
626 information to. You may want to use this if you don't have
628 locale_path: full path to the directory for locale data. Unless you
629 store all your locale data in one place, you probably
630 don't need to use this.
631 language: default language for your site. Defaults to US English.
632 languages: A list of languages supported on your site. Typically you'd
633 only change this if you wanted to disable support for one
635 "unset($config['site']['languages']['de'])" will disable
637 theme: Theme for your site (see Theme section). Two themes are
638 provided by default: 'default' and 'stoica' (the one used by
639 Identi.ca). It's appreciated if you don't use the 'stoica' theme
640 except as the basis for your own.
641 email: contact email address for your site. By default, it's extracted
642 from your Web server environment; you may want to customize it.
643 broughtbyurl: name of an organization or individual who provides the
644 service. Each page will include a link to this name in the
645 footer. A good way to link to the blog, forum, wiki,
646 corporate portal, or whoever is making the service available.
647 broughtby: text used for the "brought by" link.
648 timezone: default timezone for message display. Users can set their
649 own time zone. Defaults to 'UTC', which is a pretty good default.
650 closed: If set to 'true', will disallow registration on your site.
651 This is a cheap way to restrict accounts to only one
652 individual or group; just register the accounts you want on
653 the service, *then* set this variable to 'true'.
658 By default, Laconica sites log error messages to the syslog facility.
659 (You can override this using the 'logfile' parameter described above).
661 appname: The name that Laconica uses to log messages. By default it's
662 "laconica", but if you have more than one installation on the
663 server, you may want to change the name for each instance so
664 you can track log messages more easily.
669 You can configure the software to queue time-consuming tasks, like
670 sending out SMS email or XMPP messages, for off-line processing. See
671 'Queues and daemons' above for how to set this up.
673 enabled: Whether to uses queues. Defaults to false.
678 The default license to use for your users notices. The default is the
679 Creative Commons Attribution 3.0 license, which is probably the right
680 choice for any public site. Note that some other servers will not
681 accept notices if you apply a stricter license than this.
683 url: URL of the license, used for links.
684 title: Title for the license, like 'Creative Commons Attribution 3.0'.
685 image: A button shown on each page for the license.
690 This is for configuring out-going email. We use PEAR's Mail module,
691 see: http://pear.php.net/manual/en/package.mail.mail.factory.php
693 backend: the backend to use for mail, one of 'mail', 'sendmail', and
694 'smtp'. Defaults to PEAR's default, 'mail'.
695 params: if the mail backend requires any parameters, you can provide
696 them in an associative array.
701 This is for configuring nicknames in the service.
703 blacklist: an array of strings for usernames that may not be
704 registered. A default array exists for strings that are
705 used by Laconica (e.g. 'doc', 'main', 'avatar', 'theme')
706 but you may want to add others if you have other software
707 installed in a subdirectory of Laconica or if you just
708 don't want certain words used as usernames.
713 For configuring avatar access.
715 server: If set, defines another server where avatars are stored in the
716 root directory. Note that the 'avatar' subdir still has to be
717 writeable. You'd typically use this to split HTTP requests on
718 the client to speed up page loading, either with another
719 virtual server or with an NFS or SAMBA share. Clients
720 typically only make 2 connections to a single server at a
721 time (http://ur1.ca/6ih), so this can parallelize the job.
727 For configuring the public stream.
729 localonly: If set to true, only messages posted by users of this
730 service (rather than other services, filtered through OMB)
731 are shown in the public stream. Default true.
736 server: Like avatars, you can speed up page loading by pointing the
737 theme file lookup to another server (virtual or real). The
738 theme server's root path should map to the Laconica "theme"
739 subdirectory. Defaults to NULL.
744 For configuring the XMPP sub-system.
746 enabled: Whether to accept and send messages by XMPP. Default false.
747 server: server part of XMPP ID for update user.
748 port: connection port for clients. Default 5222, which you probably
749 shouldn't need to change.
750 user: username for the client connection. Users will receive messages
751 from 'user'@'server'.
752 resource: a unique identifier for the connection to the server. This
753 is actually used as a prefix for each XMPP component in the system.
754 password: password for the user account.
755 host: some XMPP domains are served by machines with a different
756 hostname. (For example, @gmail.com GTalk users connect to
757 talk.google.com). Set this to the correct hostname if that's the
758 case with your server.
759 encryption: Whether to encrypt the connection between Laconica and the
760 XMPP server. Defaults to true, but you can get
761 considerably better performance turning it off if you're
762 connecting to a server on the same machine or on a
764 debug: if turned on, this will make the XMPP library blurt out all of
765 the incoming and outgoing messages as XML stanzas. Use as a
766 last resort, and never turn it on if you don't have queues
767 enabled, since it will spit out sensitive data to the browser.
768 public: an array of JIDs to send _all_ notices to. This is useful for
769 participating in third-party search and archiving services.
774 Miscellaneous tagging stuff.
776 dropoff: Decay factor for tag listing, in seconds.
777 Defaults to exponential decay over ten days; you can twiddle
778 with it to try and get better results for your site.
783 For daemon processes.
785 piddir: directory that daemon processes should write their PID file
786 (process ID) to. Defaults to /var/run/, which is where this
787 stuff should usually go on Unix-ish systems.
788 user: If set, the daemons will try to change their effective user ID
789 to this user before running. Probably a good idea, especially if
790 you start the daemons as root. Note: user name, like 'daemon',
792 group: If set, the daemons will try to change their effective group ID
793 to this named group. Again, a name, not a numerical ID.
798 The primary output for Laconica is syslog, unless you configured a
799 separate logfile. This is probably the first place to look if you're
800 getting weird behaviour from Laconica.
802 If you're tracking the unstable version of Laconica in the darcs
803 repository (see below), and you get a compilation error ("unexpected
804 T_STRING") in the browser, check to see that you don't have any
805 conflicts in your code.
810 These are some myths you may see on the Web about Laconica.
811 Documentation from the core team about Laconica has been pretty
812 sparse, so some backtracking and guesswork resulted in some incorrect
815 - "Set $config['db']['debug'] = 5 to debug the database." This is an
816 extremely bad idea. It's a tool built into DB_DataObject that will
817 emit oodles of print lines directly to the browser of your users.
818 Among these lines will be your database username and password. Do
819 not enable this option on a production Web site for any reason.
821 - "Edit dataobject.ini with the following settings..." dataobject.ini
822 is a development file for the DB_DataObject framework and is not
823 used by the running software. It was removed from the Laconica
824 distribution because its presence was confusing. Do not bother
825 configuring dataobject.ini, and do not put your database username
826 and password into the file on a production Web server; unscrupulous
827 persons may try to read it to get your passwords.
832 If you're adventurous or impatient, you may want to install the
833 development version of Laconica. To get it, use the darcs version
834 control tool (http://darcs.net/) like so:
836 darcs get http://laconi.ca/darcs/ mublog
838 To keep it up-to-date, use 'darcs pull'. Watch for conflicts!
843 There are several ways to get more information about Laconica.
845 * There is a mailing list for Laconica developers and admins at
846 http://mail.laconi.ca/mailman/listinfo/laconica-dev
847 * The #laconica IRC channel on freenode.net (http://www.freenode.net/).
848 * The Laconica wiki, http://laconi.ca/trac/
853 * Microblogging messages to http://identi.ca/evan are very welcome.
854 * Laconica's Trac server has a bug tracker for any defects you may find,
855 or ideas for making things better. http://laconi.ca/trac/
856 * e-mail to evan@identi.ca will usually be read and responded to very
857 quickly, unless the question is really hard.
862 The following is an incomplete list of developers who've worked on
863 Laconi.ca. Apologies for any oversight; please let evan@identi.ca know
864 if anyone's been overlooked in error.
866 * Evan Prodromou, founder and lead developer, Control Yourself, Inc.
867 * Zach Copley, Control Yourself, Inc.
868 * Earle Martin, Control Yourself, Inc.
869 * Marie-Claude Doyon, designer, Control Yourself, Inc.
880 * Ken Sheppardson (Trac server, man-about-town)
881 * Tiago 'gouki' Faria (entrans)
883 Thanks also to the thousands of people who have tried out Identi.ca,
884 installed Laconi.ca, told their friends, and built the Open
885 Microblogging network to what it is today.