Today it struck me hard, why exactly they may think that XMPP is overloaded.

Do you know BlackBerry? These fine pieces of handy hardware apparently have an XMPP client.
Have you seen XMPP it produces? Let’s take a look at its presence packet:

<ns30:presence
xmlns:ns3='urn:ietf:params:xml:ns:xmpp-stanzas'
xmlns:ns4='urn:ietf:params:xml:ns:xmpp-streams'
xmlns:ns5='jabber:iq:auth'
xmlns:ns6='jabber:iq:roster'
xmlns:ns7='google:roster'
xmlns:ns8='jabber:iq:privacy'
xmlns:ns9='urn:ietf:params:xml:ns:xmpp-tls'
xmlns:ns10='urn:ietf:params:xml:ns:xmpp-sasl'
xmlns:ns11='urn:ietf:params:xml:ns:xmpp-bind'
xmlns:ns12='vcard-temp'
xmlns:ns13='vcard-temp:x:update'
xmlns:ns14='jabber:x:event'
xmlns:ns15='http://jabber.org/protocol/caps'
xmlns:ns16='http://jabber.org/protocol/muc#user'
xmlns:ns17='http://jabber.org/protocol/commands'
xmlns:ns18='google:nosave'
xmlns:ns19='google:subscribe'
xmlns:ns20='http://jabber.org/protocol/disco#info'
xmlns:ns21='http://jabber.org/protocol/disco#items'
xmlns:ns22='google:shared-status'
xmlns:ns23='google:jingleinfo'
xmlns:ns24='jabber:x:delay'
xmlns:ns25='google:domain'
xmlns:ns26='http://www.google.com/session'
xmlns:ns27='http://www.google.com/session/share'
xmlns:ns28='http://www.google.com/transport/p2p'
xmlns:ns29='urn:ietf:params:xml:ns:xmpp-session'
xmlns:ns30='http://jabber.org/protocol/chatstates'
type='unavailable' from='someone@googlemail.com/BlackBerry855C02AD' to='somenumber@gg.chrome.pl'/>

(Some spaces was replaced by newlines for readability.)

Well… Not much to comment, really…

None Found

There is a better way to configure sharing and receiving files over Bluetooth. Install gnome-user-share package. It is used to share Public folder over WebDAV+Zeroconf, and recently it got support for Bluetooth OBEX transfers.

Open: System -> Preferences -> Personal File Sharing and enable Receiving files over Bluetooth to Downloads folder. It is wise to restrict it to paired devices only. You may also want to enable sharing Public folder over Bluetooth.

That’s it. You may now send photos from your phone to PC over wireless BT connection with no hassle.

None Found

It uses OpenAL for sound, which does not play well with Ubuntu PulseAudio installation. There is a simple way to convince it to work - just point OpenAL to use ALSA or SDL and it works fine then.

Use this one-liner in your ~/.openalrc

$ cat ~/.openalrc
(define devices '(alsa sdl))

Note from Garoth: Tremulous by default uses SDL instead of OpenAL - to make this work, change it to use OpenAL in the options.

None Found

There is no reason to keep the artificial Desktop directory in your $HOME. Let your Home dir be your Desktop and you quickly find how usefull it is.

At the terminal window type:

gconftool-2 --set "/apps/nautilus/preferences/desktop_is_home_dir" --type bool "true"

Your Nautilus should immediately notice the change and reload the desktop contents. If not, just click the desktop and hit F5.

Next, rearrange the folders (by dragging them around and into other folders), make the important ones larger (right click and use resize icon option), set custom icons and put decals on folders to visualize the purpose of the folder (right click and enter properties).

Keeping $HOME right there, always visible constantly motivates to keep it clean, by dragging things lying around to proper place or to the Trashcan.

You may check how it may look like on my screenshot of the Home Desktop.

None Found

First you need to build/install nginx with WebDAV module:

# emerge -av nginx

These are the packages that would be merged, in order:

Calculating dependencies... done!

[ebuild   R   ] www-servers/nginx-0.6.29  USE="debug fastcgi imap pcre perl ssl status webdav zlib -addition -flv -sub" 0 kB

After you verify that your nginx is running, you need to prepare Git server repository.

$ cd /var/www/my.site.dir/htdocs
$ mkdir my-new-repo.git

Initialize a bare repository.

$ cd my-new-repo.git
$ git --bare init

Change ownership of files to nginx user be able to write them.

$ chown -R nginx:nginx .

Then you need to configure a location on your web host with WebDAV access.

# vim /etc/nginx/vhosts.d/my.site.conf

server {
listen          127.0.0.1;
server_name     my.site.hostname;

root            /var/www/my.site.dir/htdocs;

client_body_temp_path   /var/www/my.site.dir/client_temp;
create_full_put_path    on;
dav_access              user:rw  group:r  all:r;

location /my-new-repo.git/ {
dav_methods  PUT DELETE MKCOL COPY MOVE; #PROPFIND
}

}

Give nginx a way to write to client_temp path.

chown nginx:nginx /var/www/my.site.dir/client_temp

Reload nginx.

/etc/init.d/nginx reload

Verify that you can read http://my.site.hostname/my-new-repo.git/description

This is basically all. You have a fully working WebDAV repository. But we do not want all the world to be able to write to the repo, so we need to put some authorization to it. Let’s use simple user/pass authentication.

Create user passwords file.

# htpasswd -c /var/www/my.site.dir/passwd.git tomasz.sterna
New password:
Re-type new password:
Adding password for user tomasz.sterna

Add authentication to nginx location.

        location /my-new-repo.git/ {
dav_methods  PUT DELETE MKCOL COPY MOVE; #PROPFIND
limit_except  GET {
auth_basic      "Git";
auth_basic_user_file    /var/www/my.site.dir/passwd.git;
}
}

and reload nginx.

Then you need to setup your client Git. This is the same as the usuall case, but I will include it here for completeness.

Make sure that you have HTTP support, i.e. your git was built with curl. The easiest way to check is to look for the executable ‘git-http-push’.

Then, add the following to your $HOME/.netrc (you can do without, but will be asked to input your password a lot of times):

    machine servername
login username
password password

…and set permissions:

chmod 600 ~/.netrc

If you want to access the web-server by its IP, you have to type that in, instead of the server name.

To check whether all is OK, do:

curl --netrc --location -v http://username@servername/my-new-repo.git/description

…this should give a description of /var/www/my.site.dir/htdocs/my-new-repo.git .

Now, add the remote in your existing repository which contains the project you want to export:

$ git-config remote.upload.url http://username@servername/my-new-repo.git/

It is important to put the last ‘/’; Without it, the server will send a redirect which git-http-push does not (yet) understand, and git-http-push will repeat the request infinitely.

Make the initial push.

From your client repository, do

$ git push upload master

This pushes branch ‘master’ (which is assumed to be the branch you want to export) to repository called ‘upload’, which we previously defined with git-config.

And currently this is a showstopper. nginx http_dav_module does not support PROPFIND method yet, and git-http-push requires it. I am working on extending http_dav_module to support the missing methods but it’s complicated and I do not have much time for this. For now see comments for possible workarounds.

None Found