Articles

A new reason for leaving Ubuntu

So, if you’re won­de­ring your­self: “Why, Ubuntu is in the pro­cess of making ever­y­thing quite a bit more annoy­ing and fucking things up”, yet still think “that might just be mis­jud­ged opi­nion”, then fret no more. There’s an easy way to now know that Cano­ni­cal has offi­ci­ally gone bonkers.

The Ubuntu One Music Store.

After instal­ling an annoy­ing App Market-like “Soft­ware cen­ter” by default, swit­ching users over to a IM cli­ent that’s only remo­tely usa­ble, try­ing to sell you a cloud-based sto­rage solu­tion and swit­ching to Yahoo as the default search engine, you really have to won­der what the guys responsi­ble are up to.

So.

In short, Cano­ni­cal is on the verge of going Apple. Just bail boat while you still can.

Tags:

Friday, February 26th, 2010 Articles No Comments

D&D item: Martyr’s Collar

See­ing how ever­yone else is cur­rently crea­ting inte­res­ting items, I thought that I should throw one of my ideas into the mix. And after a bit of tin­ke­ring with how it should work, I present:

Martyr’s Col­lar Level 5

Res­ting tight against the throat, the wea­rer is always remin­ded of the price of sacrifice.

Lv 5   1.000 gp

Item slot:
Neck
Pro­perty:
This item can mean instant death for the cha­rac­ter. To wield it, the cha­rac­ter must suc­ceed at a hard will­power check. After three failu­res, the cha­rac­ter needs to take an exten­ded rest before try­ing again.
Power (At-Will ♦ Necrotic):
Stan­dard action. A con­scious and wil­ling cha­rac­ter may activate the col­lar while it is around their throat. The col­lar magi­cally con­stricts, seve­r­ing the user’s head from their body. The user’s life energy ser­ves as a power source for the col­lar and sends every attu­ned ally in range (burst 10) to the point defined by the attu­ning pro­cess.
Being able to sur­vive the deca­pi­ta­tion does not save the user, as all of their life energy is used up to power the collar’s magic.
The allies do not need to be wil­ling, con­scious, or even alive. If, for wha­te­ver rea­son, the desti­na­tion is not reachable, the col­lar will not activate. After the tele­por­ta­tion, the col­lar expands to its nor­mal pro­por­ti­ons and loses any attunement.
Power (Daily):
Stan­dard action. Every wil­ling ally in a burst 5 are attu­ned to the col­lar, and the item its­elf is attu­ned to the loca­tion. When the at-will power is used, all allies attu­ned and in range are trans­por­ted back to the cur­rent loca­tion. The col­lar does not need to be worn to be attu­ned; any cha­rac­ter tou­ch­ing the item can initiate the pro­cess. When pas­sing bet­ween owners, the item does not lose con­nec­tion to any attu­ned user or the attu­ned location.

Nobody really knows how these devices ever came to be, but they seem to have been used by devout and loyal war­ri­ors throug­hout time to save com­ra­des from cer­tain death by using their own life to shield them. The ulti­mate heroic sacri­fice, most souls sacri­fi­cing their bodies this way ascend to the Astral Sea.

Tags: , , ,

Monday, February 1st, 2010 Articles 1 Comment

Trusting self-signed certificates with Google Chrome on Linux

Update: added the “C” flag to SSL attri­bu­tes which I acci­den­tally for­got to include.
Also chan­ged $HOST to $host, as $HOST is the shell para­me­ter for the cur­rent hostname…

If you’re not really sure about how you can stop Chrome from per­man­ently remin­ding you that the ser­ver you’re con­nec­ting to is a bad boy (read: using a self-signed cer­ti­fi­cate), you’ll pro­bably end up loo­king at CACert’s Brow­ser Cli­ent page by way of Google. With a bit of rea­ding docu­men­ta­tion, you can pro­bably find out how to import a self-signed cer­ti­fi­cate and mark it as trus­ted, but since you’re pro­bably lazy, you’d rather just copy and paste a few instructions.

First, I have to stress is that blindly trus­ting a cer­ti­fi­cate you down­load off the inter­net is a Bad Idea. But expres­sing a cer­tain laissez-faire atti­tude: if you’re stu­pid enough to copy and paste blindly, you deserve it.

Second, sim­ple copy and paste instructions:

openssl s_client -connect $host:443 -showcerts > temporary_file
certutil -d sql:$HOME/.pki/nssdb -A -t CP,,C -n "$host" -i temporary_file

Third, expla­na­ti­ons:

  • s_client just con­nects to the given host­name, 443 being, as you should know, the (default) HTTP SSL port.
  • –show­certs shows all kinds of infor­ma­tion about the cer­ti­fi­cate, inclu­ding the cer­ti­fi­cate its­elf. You will pro­bably have to hit ^C/^D to stop s_client.
  • If you get mul­ti­ple (and dif­fe­rent) cer­ti­fi­ca­tes, first one will be the ser­ver cer­ti­fi­cate, and second one the CA certificate.
  • cer­tu­til (package hint: libnss3-tools can be used to manage your local «Net­work Secu­rity Ser­vices» SQLite database.
  • The spe­ci­fied argu­ment for cer­tu­til are:
    1. The data­base to use (in this case, the user-specific NSS database).
    2. The flag to add some­thing to the data­base (-A).
    3. The “trust types” for the cer­ti­fi­cate, in “SSL, S/MIME, CA” noti­fi­ca­tion: “P” for a trus­ted peer, and “C” for a cer­ti­fi­cate aut­ho­rity that may issue ser­ver certificates.
    4. A short­name to iden­tify the cer­ti­fi­cate in the data­base. The host­name works well and is fairly obvious.

Tags: , , , ,

Monday, January 25th, 2010 Articles No Comments

A records on top level domains

After I stum­bled upon the won­der­ful URL shor­te­ner http://to/ today and imme­dia­tely began pos­ting it on IRC, I recei­ved a com­ment that someone didn’t even know that is was pos­si­ble to do so. I, of course, could only com­ment “of course it’s pos­si­ble”. But in the same train of thought, I just had to have a look at who else has a valid A record on their top level domain. So I fet­ched the IANA TLD list and, after being baff­led by the puny­code TLDs, threw some sh at the pro­blem:
(for domain in $(grep -v '^#' tlds-alpha-by-domain.txt); do host -t A "${domain}."; done) | grep -v 'has no A record'

For the sake of enjoy­a­bi­lity, I thus offer the results in table form, along with what kind of site is run­ning on port 80. Data time­stamp is 2010–01-08T16:05:00+0100, loca­tion for rou­ting is DTAG-DIAL26 / AS3320.

TLD IP con­tent (port 80)
AC 193.223.78.210 “Always con­nec­ted” (NIC.AC)
AI 209.59.119.34 “Off­shore Infor­ma­tion Services”
BI 196.2.8.205 “It works!”
CM 195.24.205.60 cm [195.24.205.60] 80 (www) : Connection refused
DK 193.163.102.23 “DK Host­mas­ter” (NIC.DK)
GG 87.117.196.80 Chan­nel Isles Domain Registration
HK 203.119.2.28 hk [203.119.2.28] 80 (www) : No route to host
IO 193.223.78.212 NIC.IO
JE 87.117.196.80 Chan­nel Isles Domain Registration
PH 203.119.4.7 HTTP 500.100 via bro­ken Micro­soft IIS
PN 80.68.93.100 Apa­che default home page
PW 203.199.114.33 pw [203.199.114.33] 80 (www) : No route to host
SH 64.251.31.234 sh [64.251.31.234] 80 (www) : No route to host
TK 217.119.57.22 “TK your long URL”, free .tk domain name registry
TM 193.223.78.213 NIC.TM
TO 216.74.32.107 TO./ URL shortener
UZ 91.212.89.8 some WAP page I can’d decipher
WS 63.101.245.10 ws [63.101.245.10] 80 (www) : Connection timed out

So, in short, 5 of 18 (27%) are down­right bro­ken, one is being autistic, and a fur­ther 2 (11%) are not con­fi­gu­red to do anything mea­ningful, lea­ding to a total of 8 — or 44% — of TLD A records being use­l­ess. Bonus: none of the sites have AAAA records and, thus, no IPv6 availability.

Friday, January 8th, 2010 Articles 5 Comments

Discordian iCal calendar

Since I was play­ing around with Date modu­les a bit, I deci­ded to con­jure up some iCal files for the Dis­cor­dian calen­dar, which chro­ni­cles the Year of Our Lady Dis­cord, as descri­bed in the Prin­ci­pia Discordia.

With the goal eli­mi­na­ting any kind of depen­dency on actions by me to gene­rate the calen­dar files, I just pre­ge­ne­ra­ted them for the whole 21st century.

The files are stored at /discordian/$year.ical, with $year ran­ging from 2001 (which was the real start of the cen­tury and the mil­le­nium) to 2100.

For the sake of easy access — and as an expe­ri­ment to see what Google’ll make of it — I’ve com­pi­led a handy table so you can just click for the file you want.

Feel free to include this on your Google calen­dar (will make for an inte­res­ting traf­fic study) or redis­tri­bute it with a kudos to me, lin­king to this page (http://ydal.de/discordian-ical/). Copy­right shouldn’t be an issue since this com­pi­la­tion does not exceed the Schöp­fungs­höhe, but I’ll declare them to be CC-BY-DE 3.0 just in case.

2001 2001 (short) 2051 2051 (short)
2002 2002 (short) 2052 2052 (short)
2003 2003 (short) 2053 2053 (short)
2004 2004 (short) 2054 2054 (short)
2005 2005 (short) 2055 2055 (short)
2006 2006 (short) 2056 2056 (short)
2007 2007 (short) 2057 2057 (short)
2008 2008 (short) 2058 2058 (short)
2009 2009 (short) 2059 2059 (short)
2010 2010 (short) 2060 2060 (short)
2011 2011 (short) 2061 2061 (short)
2012 2012 (short) 2062 2062 (short)
2013 2013 (short) 2063 2063 (short)
2014 2014 (short) 2064 2064 (short)
2015 2015 (short) 2065 2065 (short)
2016 2016 (short) 2066 2066 (short)
2017 2017 (short) 2067 2067 (short)
2018 2018 (short) 2068 2068 (short)
2019 2019 (short) 2069 2069 (short)
2020 2020 (short) 2070 2070 (short)
2021 2021 (short) 2071 2071 (short)
2022 2022 (short) 2072 2072 (short)
2023 2023 (short) 2073 2073 (short)
2024 2024 (short) 2074 2074 (short)
2025 2025 (short) 2075 2075 (short)
2026 2026 (short) 2076 2076 (short)
2027 2027 (short) 2077 2077 (short)
2028 2028 (short) 2078 2078 (short)
2029 2029 (short) 2079 2079 (short)
2030 2030 (short) 2080 2080 (short)
2031 2031 (short) 2081 2081 (short)
2032 2032 (short) 2082 2082 (short)
2033 2033 (short) 2083 2083 (short)
2034 2034 (short) 2084 2084 (short)
2035 2035 (short) 2085 2085 (short)
2036 2036 (short) 2086 2086 (short)
2037 2037 (short) 2087 2087 (short)
2038 2038 (short) 2088 2088 (short)
2039 2039 (short) 2089 2089 (short)
2040 2040 (short) 2090 2090 (short)
2041 2041 (short) 2091 2091 (short)
2042 2042 (short) 2092 2092 (short)
2043 2043 (short) 2093 2093 (short)
2044 2044 (short) 2094 2094 (short)
2045 2045 (short) 2095 2095 (short)
2046 2046 (short) 2096 2096 (short)
2047 2047 (short) 2097 2097 (short)
2048 2048 (short) 2098 2098 (short)
2049 2049 (short) 2099 2099 (short)
2050 2050 (short) 2100 2100 (short)
Friday, November 13th, 2009 Articles No Comments

Ubuntu — why it sucks

Ear­lier this year, I swit­ched from Debian to Ubuntu on both my net­book and my desk­top machine, because it quite plea­sed me how well it worked. For the net­book, this was sort of appro­priate, when igno­ring the fact that a net­book is slow by prin­ciple, but with my desk­top, my choice might have been less than wise.

Jaunty, 9.04, left me with occa­sio­nal ran­dom cra­shing of my X ser­ver, and app­li­ca­ti­ons some­ti­mes only star­ting at the second try, if at all. You’d get situa­ti­ons like bans­hee firing up, dra­wing the win­dow on the desk­top, and then locking up — which my com­piz duly ack­now­ledged by shading the win­dow after about fif­teen seconds. You kill it, you restart it, ever­y­thing works.

Add to this some other app­li­ca­ti­ons (like Evo­lu­tion, Nau­ti­lus and Tom­boy), along with the fact that GNOME Do just seems to ran­domly eva­po­rate into digi­tal not­hing­ness in the course of my uptime, and voila, you have a sys­tem that works mostly well, but just some­ti­mes annoys the hell out of you, espe­cially when the X ser­ver cras­hed the sys­tem because you did some­thing like Alt-Tabbing while you had two app­li­ca­ti­ons run­ning full­screen on dif­fe­rent moni­tors. Yep, it happened.

So, alas and behold, comes the saviour: Ubuntu 9.10, Kar­mic Koala! It shi­nes, it glit­ters, and it saves kit­tens from trees! Ever­y­thing is so much bet­ter with it!

… not.

Kar­mic, in the vain hope to be so much grea­ter to the com­mon good, tries to opti­mize and dumb down things for the users. Which, accor­ding to others, seems to work sple­ndidly — but abso­lu­tely fai­led on my end.

My woes with the rare animal

odin (the desktop)

For the record: odin’s specs are some­thing along the line of a Core2 Duo, GeForce 260 lin­ked to two screens, a couple of tera­bytes of hard drive and a Sound­Blas­ter SB Live! 5.1, after the onbound sound­card star­ted acting up and being gene­rally retar­ded on the gaming OS.

  1. Boot time has gone way … up. Even though it’s sup­po­sed to be opti­mi­zed for qui­cker boot and what­not, my pre­vious “less than ten seconds” boot time some­what dimi­nis­hed in the face of the opti­mi­zed boo­tup, which made my resol­v­conf (which I haven’t even tou­ched!) for no appa­rent rea­son, adding a 30 to 60s time­out on the top.
  2. It sol­ved the cra­shing pro­blems … not at all. The only it actually mana­ged is to get bug-buddy to be all “It looks like nau­ti­lus cras­hed” with a nice dia­log say­ing I should report a bug to Ubuntu. Which I won’t, since there’s not­hing log­wor­thy to sub­mit, it just dies and that’s it.
  3. The sound inter­face has been made super-easy! And, also, bloody hard to con­fi­gure cor­rectly. The new sound pre­fe­ren­ces eschew any kind of know­ledge about your sound card and just pre­sume to know bet­ter than you, which is exactly why it thinks it should fiddle with the Mas­ter volume of my Sound­blas­ter when on four way ste­reo mix up, which con­trols only two chan­nels, and not the PCM, which then regu­la­tes ever­y­thing. Jaunty allo­wed me to change the mixer con­trol to one I deemed best — no dice in Kar­mic. I now need to fire up alsa­mi­xer for that, and can’t use my key­board volume wheel wit­hout fiddling.
  4. Speaking of sound, it has become even more annoy­ing to find a way to turn off the logon sounds with GDM, since gdmsetup has been repla­ced by some­thing which does quite about not­hing at all.
  5. And, of course, hiber­nate doesn’t work any­more. As if any dis­tri­bu­tion would ever get that right.

baldr, the netbook

  1. Boot time has gone way … up. Yes, even one the famed “we sooo lurv you” Atom note­books Kar­mic pre­tends to like so much, per­for­mance pretty much went down the drain.
  2. Impro­ved exter­nal moni­tor sup­port! Plug in a second screen, get none of the real estate! As soon as I plug in the VGA dis­play while the lap­top is still run­ning, screens go irre­ver­si­bly blank until reboot. Having it plug­ged in while reboo­ting allows you to run 800×600 on both dis­plays, clo­ned, wit­hout the abi­lity to change the resolution.
  3. Hiber­nate doesn’t work. Even though it did before.
  4. And myriads of minor nui­san­ces like stut­ters and all that jazz.

May I note that this even hap­pens when being freshly instal­led from source on the net­book, so this is no tale of the com­mon upgrade blues.

Con­clu­sion

Well, I’ll pro­bably be chan­ging dis­tri­bu­tion soo­nish, yet again. Fedora might be a neat idea for the net­book, not yet sure if I will revert to Debian on odin.

The Kar­mic Koala is beco­m­ing incre­a­sin­gly extinct and fails to repro­duce appro­pria­tely even with an accep­ting mindset.

Tags: , , , , ,

Thursday, October 29th, 2009 Articles 2 Comments

Internet address (IPv6) autodiscovery

At the U23 yes­ter­day, we inclu­ded a sim­ple prac­tice les­son on how net­works work. We have a ser­ver on our net­work cal­led fiep.labor.koeln.ccc.de. fiep only has a sin­gle address, 192.168.23.240/25 accor­ding to the local DNS ser­ver, as oppo­sed to the rest of the net­work, 172.23.23.0/24.

The rou­ter did not announce any route for 192.168.23.128/25, but fiep still had addres­ses in other net­works (172.23.23.23 as well as an address in 2001:6f8:100c:1::/48), but they weren’t announ­ced anywhere.

The task, as given, was “to con­nect to http://fiep/hacking4pizza/”. In essence, this redu­ced the task at hand to eit­her just giving your­self an IP in the 192.168.23.128/25 net­work or just set­ting a route for said net­work, and then opening up your brow­ser. Along with other work­a­rounds, of course, that do require know­ledge not easily available.

We had an inte­res­ting case, though: one sin­gle Mac user could con­nect to the host wit­hout pro­blem, just typ­ing in http://fiep/ and everything’s good.

Con­fu­sion was amongst us. We couldn’t quite explain how the Mac mana­ged to just access the site. We assu­med it was IPv6, blo­cked it, and voilà, it didn’t work anymore.

Vague theo­ries were ram­ped up. Mine was the sca­riest, and also rather possible:

  1. The cli­ent looks up the host­name, as usual.
  2. It gets the IP, sees that it has no route to go there.
  3. Next, an ARP request is pus­hed out for the IP.
  4. The switch comes yap­ping along and says “got it!”, along with the MAC address.
  5. The cli­ent then gene­ra­tes an IPv6 address from the MAC address.
  6. Voila, con­nec­tivity.

There’s just two points where this would have went wrong:

  1. Usually, the default route cat­ches any stragglers.
  2. Why gene­rate a v6 address when it gets a con­nec­tion to the v4 address? Of course, it doesn’t know whe­ther the rou­ter will actually for­ward anything at all.

In the end, though, it was some­thing way more sim­ple: we still had an exter­nal DNS ser­ver which pro­pa­ga­ted the public IPv6 address, and the cli­ent was using an exter­nal DNS server.

But try­ing to find out what actually hap­pened did prove quite entertaining.

Tags: , , ,

Tuesday, September 1st, 2009 Articles No Comments

DNS prefetching for spam address verification

See­ing how DNS pre­fet­ching is the new fad with brow­sers, I reckon there’s an easy way to con­firm valid addres­ses of web­mail ser­vice users:

  1. Con­trol a DNS to assign uni­que has­hed hostnames.
  2. Inte­grate links to has­hed host­na­mes in spam mails.
  3. If the reci­pi­ent uses cur­rent Chrome, Fire­fox, etc:
    1. The DNS pre­fet­cher will resolve the host name,
    2. Giving you a con­fir­med hit for the address in your log­files, since your uni­que host­name gets resolved.

Kind of remi­nis­cent of the whole “oh, we can have e-Mails with HTML, let’s put in images!” affair. The only thing that might be a bit of a pro­blem for a spam­mer is get­ting a domain with DNS ser­ver control.

Friday, August 21st, 2009 Articles 2 Comments

Advanced interaction in FPS

There is always a bit of metho­lo­gi­cal slow­ness when it comes to the first per­son shoo­ter genre of com­pu­ter games: deve­l­o­pers are lazy to try­ing some­thing new, lest they fall flat on their faces. This is sort of true when it comes to advan­ces in level design and gra­phics, where there’s a bit of ten­dency to move along, but only on known lines — next to nobody really adopts open levels. If they do, they are eit­her of (next to) no impact at all (I’m loo­king at you, Front­lines: Fuel of War), or they change the whole game into some­thing that gra­vi­ta­tes around cer­tain hot spots, as in S.T.A.L.K.E.R.: Shadows of Cher­no­byl, for example, or the first actual FPS doing this, Strife. And some­thing so open like Ope­ra­tion Flash­point, even though sporting quite impres­sive gra­phics, was never as suc­cess­ful as a rehash like Cry­sis which just slap­ped supreme gra­phics on old and pro­ven FPS concepts.

Then, there was the other extreme, wer some­thing radi­cally new was tried. Games like Tre­spas­ser, which was a game set in the Juras­sic Park uni­verse with some rather nice gra­phics, and a very fre­aky con­trol sys­tem. In this, you directly con­trol­led the arms of your cha­rac­ter, moving them around, rota­ting hands and clen­ching fists manu­ally to grab levers or push buttons.

It was horrible.

But the thing which hasn’t chan­ged at all for quite some time is how your cha­rac­ter inter­acts with the world at large. The big chan­ges in this category:

  1. Doom star­ted out with using your key­board arrows to move you along, and PgUp and PgDn for aiming up and down.
  2. Quake intro­du­ced the mouse into the mix, which still took some time to get adop­ted, though.
  3. Then, Half-Life intro­du­ced the WASD key lay­out to accom­pany its ple­thora of spe­cial keys, which also popu­la­ri­zed the “use” but­ton to inter­act with environ­ment objects, instead of just run­ning into or shoo­ting them.
  4. Recently, game­pad con­trol­lers are often used, and there’s a shift in lay­out map­ping to con­form with the limited amounts of but­ton avail­able on a controller.

And that’s very much it. For eons, you run around using your use but­ton to make stuff do other stuff. Besi­des just activat­ing swit­ches, you have your use key trig­ge­ring dia­lo­gues, opening doors, picking up things, and just about ever­y­thing you can ima­gine. If you do anything that bor­ders on com­ple­xity, you’d pro­bably get a pop-up dia­lo­gue explai­ning your opti­ons to you, totally brea­king game immer­sion and, in a few sorry cases, actually kicking in the fourth wall with a vengeance.

This was the case even with my beloved com­plex games like Sys­tem Shock, even if they tried to be some­what immer­sive in their inter­face. But then, there came the least likely can­di­date for reform ever: Doom III. Nobody expec­ted D3 to be anything but a new “shoo­ting demons” thingy; yet not only did it come along and intro­du­ced story to id Soft­ware games (which Quake IV con­ti­nued to flesh out), but it also intro­du­ced a revo­lu­tio­nary immer­sive way of using com­pu­ter con­so­les: instead of activat­ing them with your use key and then cli­cking around on the screen, D3 just chan­ged the cross­hair into an arrow when you viewed at the con­trols of a ter­mi­nal and allo­wed you to push and mani­pu­late but­tons wit­hout ever brea­king immer­sion into the universe.

An example (just the first few seconds, really):

Example screen­shot, bla­tantly sto­len from the site in my post scriptum:

Doom III: Crane control

But it didn’t last. And I won­der: why? Was it too com­plex? Did it alie­nate the tra­di­tio­na­list that he had to do more than push ‘e’ to use a com­pu­ter? It’s just so good, yet nobody seems pre­pa­red to adopt it to their games. Bioware’s Mass Effect is quite good at try­ing to keep immer­sion high and making the player expe­ri­ence the game, rather than just play it — but they, too, resort to brea­king immer­sion when it comes to com­pu­ter ter­mi­nals, using a com­bi­ned inventory/data sto­rage sys­tem on a sepa­rate screen.

The ques­tion remains: Why? It’s good, it works, it’s not hard to learn — so why avoid it?

P.S.: While sear­ching for good screen­shots, I found an arti­cle cal­led Through The Loo­king Glass — Fully Inter­ac­tive Sur­faces In DOOM3 by Bernd Krei­meier, which explains things in a bit grea­ter detail.

Wednesday, August 12th, 2009 Articles No Comments

Maemo vs. Android

Since I can pro­bably declare my Nokia N810 dead after a rather unde­li­be­rate expo­sure to not really fresh water, I’m on the look­out for a wor­ka­ble repla­ce­ment. See­ing that Apple, des­pite all its glos­si­ness, is quite a pile of crap when it comes to soft­ware deve­l­o­pe­ment and free stan­dards, I thought there was only one choice: Android.

That was, until I found out that the next Maemo device from Nokia, the N900, also dub­bed “Rover”. There’s also real pic­tures avail­able, not mockups.

The N900 would then, of course, be pit­ted against the HTC Hero.

Now, first, hard­ware. A quick comparision:

HTC Hero Nokia Rover
CPU 528 MHz Qual­comm® MSM7200A™ 500/600 MHz OMAP 3430
RAM (phy­si­cal) 288 MB 256 MB
Dimen­si­ons (L⨉W⨉T) 112mm ⨉ 56.2mm ⨉ 14.35mm 59.7mm ⨉ 111mm ⨉ 18.20mm
Weight 135g 180g
Dis­play 3.2″ 320×480 (HVGA) 3.5″ 800×480 (WVGA)
Con­nec­tivity
  • Quad-band GSM/GPRS/EDGE: 850,900,1800,1900 MHz, WCDMA 900,2100 MHz
  • WiFi 802.11 b/g, Blue­tooth 2.0
  • Quad-Band GSM/GPRS/EDGE: 850,900,1800,1900 MHz, WCDMA 900,1700/2100,2100
  • WiFi: pro­bably, Blue­tooth: pro­bably 2.0
Sto­rage 512 MB inter­nal (~150 avail­able), SDHC slot (16 GB) 32 GB inter­nal, SDHC slot (16 GB)

So in essence, the Rover trumps the Hero in sto­rage capa­city and screen reso­lu­tion, has a slight advan­tage in CPU, suc­cumbs in RAM and weighs more. But of course nobody has yet been able to touch the Rover from a reviewer’s point of per­spec­tive, and if it is anything simi­lar to the N810, the sli­ding key­board will wiggle all the time and annoy you.

The main ques­tion would pro­bably the choice of ope­ra­ting sys­tem: Do you want Google’s shiny Android mobile phone ope­ra­ting sys­tem? Or do you want Nokia’s Maemo 5/Fremantle, a Debian port initi­ally desi­gned for mobile devices wit­hout phone connectivity?

From a nerd or hacker point of view, maemo is very inte­res­ting, since it’s basi­cally an embed­ded Debian, with all its advan­ta­ges and disad­van­ta­ges. But you have to ask your­self: so far, the other Nokia Inter­net Tablets have been good secon­dary devices. You have your mobile phone for your RL con­nec­tivity, and the NIT, pro­bably con­nec­ting to the Inter­net via your phone, hand­les the CPU-churning Inter­net activi­ties. The ques­tion ari­ses whe­ther the new gene­ra­tion of smart­pho­nes actually requi­res this kind of distinction.

On the other hand, you have the Android ope­ra­ting sys­tem, spe­ci­fi­cally desi­gned for smart mobile pho­nes. This alone gives it the advan­tage of being more stream­lined to mobile phone needs, which helps quite a bit in usability.

The great advan­tage of the Maemo sys­tem, as oppo­sed to anything around at its time of incep­tion, was it being almost com­ple­tely open source, and based on Debian. So, with a fair bit of luck, you could just com­pile a Debian package in the right build environ­ment, and it would pro­bably run on your maemo device. And since you had GTK as your win­do­wing basis, well, deve­lo­ping your own apps was easy, too.

But with Fre­mantle, Nokia’s chan­ging to Qt to keep up the splif­fy­ness with iPhone OS and Android, which will make all the old GTK app­li­ca­ti­ons look a bit out of date. While this may be a ‘good’ move to go towards mobile pho­nen­ess, it will pro­bably alie­nate the fan­base to no end to sudd­denly have to do Qt. I’m gues­sing this will end bad.

On the other hand, people claim about Android being from evil evil Google, and thus not trust­wor­sty. What I’m asking mys­elf, espe­cially after wri­t­ing down why I’m more inclined towards the Android OS, and, thus, the Hero: is it worth wait­ing for the Rover, being ‘redu­ced’ to my S60r3 phone until I can decide whe­ther it is bet­ter or not?

Tags: , , , , , , ,

Thursday, August 6th, 2009 Articles 3 Comments
  • Bad Company 2 has quite a few subtle puns on other shooters. They poke fun at Modern Warfare 2, but also homage to Crysis and even Heroes. [towo]
  • NO character sheets, of course. #dnd [towo]
  • Highly irritating. 4 counter sheets, 3 maps, 5 DCI cards, one booklet and on character sheets in the #gameday set. #dnd [towo]