Retroshare – the next messenger?

I’m gonna play with RetroShare a bit.

RetroShare is a serverless, p2p based communications platform where every single piece of transferred data is encrypted. You find your contacts by their pgp key.

Here’s a link to the homepage.

If anyone wants to poke me on retroshare, my pgp key is on the public key servers with the key id 0x27BD763C.

RetroShare for openSUSE is on the build service.

Survey results are in

Here are the results from the survey:

75% answered “yes” on the question whether they use kontact or not. Those who answered “no” did not get to the rest of the survey. All questions except the last two were multiple choice.

Component usage:

E-Mail 93,42%
Contacts 78,95%
Calendar 77,63%
Feedreader 53,95%
Task list 35,53%
Summary 19,74%
Yellow Notes 17,11%
Journals 10,53%
Time tracking 9,21%
Other 9,21%

Mail protocols:

IMAP 72,6%
POP3 47,9%
Local Maildir 17,8%
Other 11,0%

Calendar sources:

Vcard files 75,0%
Google contacts plugin 29,4%
CardDAV 11,8%
LDAP 10,3%
Kolab etc 10,3%
Other 7,4%
Novell Groupwise 1,5%

Address sources:

iCal file 66,1%
Google calendar plugin 32,3%
CalDAV 21,0%
Kolab etc 14,5%
Other 11,3%

Quality compared to other PIM applications or email clients:

Poor 11,1%
Below average 16,7%
Average 34,7%
Good 33,3%
Excellent 4,2%

Has kontact improved over time:

Improved 23,9%
The same 25,4%
Worse 50,7%

Single sign-on on openSUSE / KDE4, or the three faces of the community

It seems that “the community” consists of three separate groups of people:

  1. the people who loudly demand features
  2. the developers who loudly debate the ethic, moral, technical religious impacts if the features demanded by 1. would be implemented
  3. the small group of developers who watch 1. and 2. and at some point say “Oh for crying out loud. What a noise over 5 lines of code.”

As an example, look at the discussion over the feature request in kmail where someone wants kmail to be able to remove attachments from mails.

As another example, look at this one. Some people would like to see single-sign-on in KDE4. The discussion was long and loud.

And, if you Google a bit, you find that the wallet daemon has had the required dbus call since KDE 4.4.2, for crying out loud!

Just that noone has bothered to point a finger at the required pam modules and helpers.

I’ve packaged them for openSUSE, get them from my OBS project and configure them as described in the readme files included in the packages, and you have single sign on.

Note: single sign on only happens if you actually enter a password on login. The typical suse setup with an user session starting automatically on boot can’t work with this.

Note: this seems to work only for local useraccounts, but not in a NIS environment.

openSUSE 12.1 – coming soon

I’ve been testing openSUSE 12.1 RC2 for a week now, and so far I’m impressed.

Network installation went pretty well (after I had figured out that the reason for the initial woes was the DHCP server here at work, not suse), and so far a lot of stuff that used to need manual intervention “just works” now. For eexample the use of ksshaskpass for ssh-add and other little quirks.

On the other hand there are a few oddities, none of them being the fault of the openSUSE team, as far as I can tell:

  • kopete refuses to “do” MSN – MicroSoft has changed something on their end; kmess needed a patch & rebuild as well
  • no sun java – Oracle has changed the licensing and disallows redistibution now.

Other than that: cool beans.

Especially KDE4 is impressive on this version – KDE 4.7.2 actually works now.

Debian 5, or the joy of working with prehistoric software

For various reasons I had to setup a Debian box. Debian 5.

For building software that would be distributed in binary form and should run on any linux.

The original software that mine derives from is being built on a debian 5 system.

So, I needed one as well.

Enter: VirtualBox for Mac + Debian 5 netinstall.

So far, so good, until I actually cloned my hg repo onto the deb box, and found that the clone had two heads.

… debian uses mercurial 1.0.1 on debian 5.

1.0.1.

seriously.

that is old.

very old.

It’s a miracle that debian has heard of unicode by now.

At least I think they have heard of unicode …

gotta check that.

A tale of two internets

Lately I’ve come to think that there are two separate Internets out there, existing side by side and with little interaction between them.

One of them is the internet that we all know, populated by people who write their little rants about anything they care enough about.

The other is a scary place where semi-intelligent bots imitate human behaviour by auto-generating streams of gibberish aimed at each other, making it look like strangers talking to strangers.

Case in point: get a twitter account. post any random tweet but add “popular” hashtags. Observe the behaviour of “the net”. Pay special attention to some of the new followers you’ll get… do you really believe that someone follows 25000 people?

Who made up this “You have to be on twitter and facebook to be a successful company” fad, anyways?

Related: If “Search Engine Optimization” worked, none of those self-proclaimed “SEO Experts” would have to spam twitter… they would just be found with google.

 

KDE 4.7 – You didn’t think you would get off that easily, would you?

OK, so now I did a clean install on some old work laptop.

openSUSE 11.4, fresh off the DVD, on an empty harddisk.

KDE 4.6 or whichever version comes on the DVD worked fine, using the GSM/UMTS/EDGE card that my company gave me works fine too.

So I’m using that UMTS network to upgrade KDE to 4.7, and after that, plasma crashes every time I try to connect through UMTS… terminating the connection.

So, this time, not even a rollback to 4.6.5.

Yee-haw.