glokal

Google is great. I just want to say this up front so there are no misconceptions about why the following is interesting. Specifically, I just don't like it that the Google cookie identifies myself to them and they can easily collate years of search queries made by myself. Now, there are several solutions:

-Don't accept the cookie. Then, however you also don't have your preferences.
-Delete cookie from time to time and then redo preferences. Annoying and I'm not doing it as often as I should.
For Firefox there are certain extensions that will do the following (or similar) for you but since I very heavily use Konqueror's "Web Shortcuts" I took the time to modify my search URIs a bit. With this I can specify my preferred language setting as well as have more than ten results on a page and toggle safe searching all of which are used every time I utilize the shortcuts.
One can just edit the default search URI for Google and append variables to achieve this.

&hl=de would set your language to German. This is very helpful when you have several shortcuts say "gges", "ggde" or "ggfr" depending on the content you are currently searching for, since it really does matter in terms of how Google assigns relevance.
&num=50 sets the number of items per page returned. So for more than 10 items you no longer have to click around. Maximum 100 according to Google.
&safe=off toggles your filtering settings. Possible values are on/off. If not set it will default to moderate safe search for images. Non-image searching only seems affected if safe is set to on. I couldn't see a difference between moderate or off for regular searching.
Here is one possible variant that uses all three of these options as well as the KDE defaults.
http://www.google.com/search?q=\{@}&ie=UTF-8&oe=UTF-8&safe=off&hl=de

A warning though, at least in recent KDE versions changing your language settings changes web shortcuts, such as to which version of Wikipedia, Google etc your shortcuts are pointing. I did not try out whether this would break modified shortcuts so don't do it if you didn't have your settings written down ;-)

KDE stores these shortcuts as .desktop files and they can be found in the users directory ~/.kde/share/services/searchproviders or for systemwide defaults (in Gentoo) in /usr/kde/3.x/share/services/searchproviders.
This makes exchanging them quick and painless.

So here we are the Faculty Tech Showcase 2006. Fun. The most fun thing here is definitely the 3d printer. We have already given away several Ubuntu CDs and people have show interest and some actually seemed interested in our causes. Nile, however, will be arrested for using the copyrighted image of the Mac/PC commercials in his presentation, maybe...
Still better than having a fight to the death with the Microsoft booth.
Should have brought some Kubuntu CDs...

Update: We just talked to several people from Academic Technology and apparently they are really interested in doing presentations with us about usability and accessibility for programs like nvu as well as FOSS in general. Sweet.

What would us geeks do without IRC...
Today it started a discussion about at least attempting to start a meshed wireless network in Gainesville.

Meshed? Ad-Hoc? OLSR? Potatoes?! The terminology involved does take some time to get used to but the underlying principles are not that complicated. What it essentially boils down to is creating a wireless network with standard equipment such as 802.11b that basically everybody uses when not being connected via actually wires. Traditionally you have access points which handle several clients and your wireless network is limited to the reach of your access point. With such a meshed network, everbody puts their wireless network card into ad-hoc mode and with a special routing software acts as a node in a network that can talk to every other node. The point is that when more and more devices get added a cloud develops that moves outward and spans a wider area.
If there is a node on Main Street and you live on 2nd Street and become a node yourself you extend the network outward so that now people on, say, 4th Street can use it too.

Many businesses already offer free wifi for their customer and there is already the campus network, so why bother? Because we can. It's a neat experiment and it wouldn't really hurt us if it failed. In the beginning this will probably not be interesting for the average end user since it does require using the OLSR daemon on every client. It would be possible to rely on a technique that also allows for the classic client/ap approach but it really defeats the whole idea of building a growing cloud since most people would probably not make the effort to even find the daemon. (However later on specific nodes might bridge to a regular AP where many people pass through). I'm currently in favour of OLSR since it is the protocol that has shown in actual working clouds that it can build meshed networks of enormous size.

If I get the consent of everybody involved I plan to take the first step by installing a node at the CMC within the next few weeks. The idea is to use a Linksys WRT54 or WAG54 router and flash it with the freifunk firmware, as well as getting a decent home made antenna on the roof. This should first of all serve as a proof of concept and possibility to try things out and improve on antenna design and the like. This node will however not be connected to the public internet since the ISP doesn't allow the usage for this connection and there is just no way around that. Hopefully, at some point the owner of a node will be willing to share his connection but understandibly this might require the forming of a group of several consenting members to not put the burden on a single person. Some people might argue that this will invite abuse by people who are trying to do bad stuff undiscovered through this network. However, following this logic basically no business could be offering free wireless to their patrons since any evildoer could be wardriving in the parking lot. Furthermore, my apartment is surrounded by other students and my wireless card picks up 21 cells including 3 without encryption. However, the Linksys devices have such limited resources that keeping logs is pretty much physically impossible. So all of that should not be such a big deal, even though one should watch out for noisy people -- there is no protocol encryption.

This is probably the solution that will get the least support from legislators as well as businesses since they can't really control the network, which is a factor in making it the most interesting, in my opinion. Interestingly enough this is probably one of the cheapest ways to getting a large scale network running. What is definitely missing is a good name (preferably usable not only as a domainname but also for the ESSID) and lots of people. Strangely enough, the site for the picopeering agreement doesn't seem to exist anymore, I'll add this when I find it.

OK, if anybody reads this the critique is probably going to be pretty harsh. /me ducks :-)

Allright,
2006.1 hit the mirros a few hours ago and the new handbook is online.
I expect to have the german translations for x86 & amd64 handbooks for current as well as 2006.1 ready by Thursday 20:00CEST. All other arches should follow in the following days.
We are currently having a few showstoppers on gentoo.de concerning the additions to GuideXML from gentoo.org that haven't been integrated yet. Thus, *please* use www.gentoo.org/doc/de instead of www.gentoo.de/doc/de.

Update: Yeah, 20:00CEST my ass. It's going to be a bit closer to 23:00EST.

Update 2: x86 & amd64 are in, I'm waiting now for the website to sync to see if I broke anything. After that I might do one more arch or go straight to bed..not sure yet.

Update 3: Nothing burning yet, and hppa is in as well.