Archive for the ‘Resources’ Category

Last.fm, Jaiku and Dorit Chrysler - a match made in heaven?

Saturday, May 31st, 2008

Dorit ChryslerIt’s been a while since I wrote about the Jaiku online service, but it’s a service I use all the time, and I love it.

This is, mostly, due to the fact that Jaiku is filled with people, with whom I share interests, but the people there, all, seem to be more interesting than I am, so I can learn new things, and that is the thing in life I love the most.

One of the things I’m very adventurous about is my music, and another of my favourite online services, Last.fm, supports that perfectly.

Yesterday a conversation about Last.fm surfaced on Jaiku:

Jaiku | Det slår mig lige, hvorfor jeg er så vild med last.fm. Jeg kan holde liv i det ved at gøre noget, jeg alligevel ville gøre: Høre musik :-

Translation: It just struck me why I’m so crazy about Last.fm. I can keep it going by doing something, I’d do anyways: Listen to music :-)

That is correct, Last.fm builds and extends your network by comparing your musical preferences to the other users, and it also gives you recommendations based on your listening habits.

Eventually the question was asked: What do you use it for?

This triggered me to use Last.fm again, something I usually only do once a month, and the feature I love the most, is the similar artist radio.

In April 2008 I travelled to Lisbon, Portugal, and I was so fortunate to attend a concert by Dorit Chrysler, a very talented artist from Austria, that has specialised in using the Theremin instrument, a very strange instrument that you control by moving your hands in the electrical field generated by the instrument, that basically is a bend metal-rod.

So the Jaiku post triggered me into finally ripping the CDs I bought in Galeré Zee dos Bois in Lisbon, listening to them, and then using that to listen the Dorit Chrysler Similar Artists Radio.

And what I dug into, was a wealth of wonderful music, that spans from Opera to Classical Chanson, over Russian Abstract Hip-Hop and even the wonderful Colleen, that I already knew.

Here’s a list of some of the wonderful artists I discovered:

  • Robert - A wonderful French chanteuse
  • Gudrun Gut - German female singer. Original member of Einstürzende Neubauten
  • Ute Lempner - German chanteuse
  • Susanna and the Magical Orchestra - Norwegian act that, for instance, does some amazing covers, especially one of Dolly Partons Jolene is wonderful
  • Meret Becker - Another German singer that has be associated with Einstürzende Neubauten

The list goes on, and I’ll recommend exploring the artists that are similar to Dorit Chrysler, you will not regret it.

Last.fm remains one of the most impressive, and genuinely useful, online services - the list of these services is short, the big three are, to me, Jaiku, Last.fm and Flickr.

The picture used here was taken from Last.fm, and is, most likely an official promotional pressphoto, I hope my use here will go under “fair-use”

OIO REST: RESTful web services developed by the Danish Public Sector

Friday, May 23rd, 2008

The Danish Office for IT and Telecommunications (IT & Telestyrelsen) is experimenting with so-called RESTful web services, and I’m very happy to hear that, because this is an indication that something finally is happening again, after years of impasse.

Services for the REST (sry) of us

RESTful web services are the predominant implementation model for web services developed by web 2.0 companies, Last.fm and Flickr are prime examples of services with extensive RESTful web services and APIs (Application Programming Interfaces).

A web service is a software service, or API, that software (application) developers can use to provide functionality to their applications, and thus users. The “web” refers to the fact that the service can be accessed using technology developed for the web, like a standard web-browser.

Other technologies for implementing web services exits, the best known is the web service or (WS_*) stack, often referred to as SOAP. REST is, however, much easier to use than SOAP, because it has a GET based interface, meaning that you can query a RESTful service using simple URIs for instance entered using a browser. REST is also much better understood by commercial web developers in the private sector, and the tools they use, eats REST for breakfast.

Here’s an example: http://oiorest.dk/danmark/veje?q=lindevangshusene

This retrieves the road-code and city-number of the street I live on in XML format, pretty sweet.

What IT&TS has done is that they, two years later, have picked up my idea, so that I don’t have to implement it (well it only means that I’ll never release my own code) ;-).

Concerns that history will repeat itself

I’m pleased, very pleased, and surprised that The Danish Office for IT and Telecommunications (IT & Telestyrelsen) has begun experimenting with such a relevant service, and has actually made some real-word applications available on the web-site.

But! I fear that history might repeat itself.

Something like 3-4 years ago, a sample SOAP service Address Web Service (AWS) was developed by IT&Telestyrelsen, they even had a competition to develop a sample application, and there even was a winner. But AWS never went into production, and the project dropped off the radar, that is until now. It seems that AWS soon will be released for production, and this is great news.

The problem was that I lost faith in AWS, I felt the project had died, so I didn’t really want to develop against it, and I hear the same concerns from others regarding the RESTful services today.

Do we need pseudo-standards like REST?

The RESTful experiments will probably never launch, but with the SOAP/WS_* AWS likely to go into production, we don’t really need them do we?

What we do need is an open and free infrastructure, for instance for eFaktura, it’s way too expensive to use the current providers, so I suggest that the next thing you do IT&TS, is to pick up another of my old projects ;-)

In many ways I fail to see the real need for a RESTful service, but RESTful APIs are so much easier to implement than SOAP.

What I’d like to see is light-weight data-formats, like JSON, and JavaScript APIs Google style. The light-weight data-formats are simpler to parse than XML, so I’d love to see a JSON, or similar, version, e.g. something that is closer to the internal representations of data, without going to binary interfaces, even though they’re coming back, for instance through WCF (Windows Communication Framework).

Conclusion: BIG thumbs up! (but it was overdue)

All in all BIG thumbs up to IT&TS for this initiative, keep it up, and stay above the radar in the future, please. We need widely available, and free, services like AWS, and with the competition from Google GeoCoder, which can be implemented with few lines of code - and works with other than Danish addresses, and findvej.dk - that is using it’s own, outdated, copy of data from Kort og Matrikelstyrelsen to provide a nice, URI based service, reviving of AWS, and the new initiatives, were way overdue.

Æbletræet.dk fylder 2 år - stort til-held-og-lykke og Elvis har forladt bygningen

Friday, April 4th, 2008

Elvis Smoking - By Esben ThomsenI går, den 3die April, kunne Æbletræet.dk fejre sin 2 års fødselsdag. Æbletræet.dk er et Internetbaseret, indholdsdrevet, fællesskabs projekt der startede som en idé om at skabe en begynderguide til Mac, men er endt med at være en af de, ja måske det, største Danske online fællesskabsdrevne indholdsdrevne Internet projekter. Projektet er dog, for længst, gået skridtet videre, og indeholder nu artikler om meget andet end Apple.

Historien om Æbletræet, eller MacWiki som det oprindelig hed, er dokumenteret på Wikien, hvilket er ganske unikt, som du kan finde på http://www.theappletree.dk (jeg bruger - bevidst - den Engelske version - da projektet - naturligvis - som nogle af de første - benytter en IDN (International Domain Name) - nogle skulle jo starte, og det blev os.

Ideen til Æbletræet udsprang af det danske forum for Apple fans, Macnyt.dk, en gruppe af faste brugere var blevet trætte af at besvare de samme spørgsmål om og om igen, så det blev diskuteret om man kunne skrive en bog eller lignende.

Fra start af var det klart, for mig, at man absolut ikke skulle skrive en bog, men lave det online på Internettet, og jeg havde noget i baghånden, MediaWiki, det samme system som driver Wikipedia - der er åben og fri software.

Første møde blev afholdt den 3-April-2006, og da jeg kom hjem installerede jeg MediaWiki på min server og oprettede de første artikler.

Der gik noget tid inden de andre projekt deltagere forstod ideen, og indlæringskurven for MediaWiki er ikke just lav, derfor opsatte jeg også et traditionelt forum, som stadig kan findes på http://macwiki.kimbach.org/portal, og diskussionen flød.

Det er fantastisk at arbejde sammen om at producere indhold, og når man kan se at der er mange rettelser på MediaWikis recent changes, så virker det simpelthen ganske inspirerende, og man får lyst til at skrive mere.

Jeg føler det er nødvendigt at aflive nogle myter, da den slags opstår når folk ikke taler sammen.

  • Jeg har ingen ambitioner om at være leder eller bestemme noget som helst
  • Jeg er blevet beskyldt for at tage Æbletræet som gidsel - det kan jeg ikke se - grunden til at vi ikke er på PHP5 - som jeg helt ærligt - ikke forstår er så vigtigt - er at vores udbyder Site5 ikke understøtter det, og da projektet er baseret på gratis og frivillig arbejdskraft, så har det været svært at få ejeren af serveren til at bruge tid til at få flyttet server

Og så et par ord om hvordan jeg fungerer: jeg bliver stresset af at tænke på produktions-problemer, og i påsken forsøgte jeg at opgradere Æbletræet.dk, det gik ikke helt som ventet, jeg bad derfor om, først at få os på PHP5, derefter ville jeg installere MediaWiki 1.12, og så flytte til Gigahost (hvilket jeg ikke tror er så god en idé), hvis man spørger kan man jo få svar, og jeg venter på min frivillige hjælper.

Fundamentalt hader jeg simpelthen drift, og her mener jeg ikke den første installation, men de problemer der - næsten altid - opstår når man skal opgradere serveren - så vidt jeg husker - så har vi nu ikke haft de store produktions problemer - en enkelt gang var vi nede i 48 timer - fordi Site5 havde skiftet IP adresser.

En grundregel - som gælder al drift - er: “if it ain’t (totally) broke - don’t fix it” - på Dansk: “pil ikke ved noget der fungerer, også selv om det ikke fungere helt optimalt”. At dette så betyder at “change” ikke sker, er uheldigt, men det er simpelthen ikke noget man kan byde frivillig arbejdskraft - så ting tager tid!

Jeg har - længe - forsøgt at få vores server opgraderet til PHP5, men igen - frivillig arbejdskraft skal man ikke presse - man må væbne sig med tålmodighed. Tro mig, jeg ved det - for 3 år siden prøvede jeg at køre et del-projekt i min Frivilliggruppe hårdt, det faldt ikke i god jord - og folk hadede det jeg producerede, men jeg producerede! Siden dengang har jeg væbnet mig med tålmodighed.

Efter 2 år kan projektet dog, sagtens, stå på egne ben, og jeg føler at min fortsatte deltagelse i projektet ville betyde en fragmentering af fællesskabet, der - efter min mening - ganske enkelt ikke brug for endnu et Dansk Apple site, og nøj hvor er det imponerende med de nye Apple fora, som i kan se havde vi et Drupal baseret forum allerede for 2 år siden.

Jeg vil derfor, fremover, ikke deltage i projektet som andet end bidragyder, med mindre jeg bliver udelukket - hvilket jo ikke kan udelukkes (pun intended).

Faktisk er det eneste jeg er ked af, at jeg har mistet en fantastisk god ven - det bedste minde jeg har er dengang vi bagte en kage til brug for Dansk Flygtningehjælps 1000 flere arrangement, og jeg undskylder MANGE MANGE gange for Beyoncé, som blev Skypet til dine sarte ører mangen sen nat.

Det sjoveste er faktisk at vi, mest fordi vi havde en åben proces, blev udsat for en domænehaj. macwiki.dk blev registreret af en af den slags personer ,der ikke burde have lov at betræde Internettet, sjovt nok blev navnet jo æbletræet.dk, så fjolset brændte inde med domænet LOL.

God vind kære Æbletræ, det har været fantastisk sjovt! Specielt tak til David, Esben men også Thomas x 2, Wendelboe, Sebastian, Allan, Liv for at have holdt mig ud så længe, noget af en bedrift ;-).

Et par fakta - Æbletræet.dk kører videre, så længe det ønskes. Hvis der er interesse i at bevare navnet, hvilket jeg da tvivler på, så kan det redelegeres, jeg ejer det p.t. I øvrigt sletter jeg aldrig indhold, men da vi ved at dublikeret indhold er noget Google ikke bryder sig om, trækker jeg stikket så snart der er flertal for det.

Jeg er blevet beskyldt for gidseltagning - intet er mig fjernere - jeg er SUPER stolt af at have været med til dette - og det var det jeg kunne få jer med til. Fremtiden tilhører egen-produceret indhold, som man selv hoster og ejer, websitet er dødt! Elvis har forladt bygningen.

Billedet der ledsager denne artikel er en manipulation udført af Esben Thomsen, det er Copyright Esben Thomsen, men jeg håber at dette falder under fair use. Esben kender mig bedre end de fleste, og det “grønne skrig” opsumerer “mig” ganske godt (man kunne sige perfekt)

sIFR inside: mourning the loss of a friend, with a tribute to Mark Wubben

Monday, March 31st, 2008

Logo Sifr2Yesterday I had the, unexpected, pleasure of meeting Mark Wubben in person, and it was great.

The reason: yesterday we had a meeting in relation to a project, and webgrl extraordinarie, Henriette Weber asked if she could bring a guest. Sure! His name is Mark Wubben, do you knew who he is? No, not really!…Well it turned out that I did, he’s the man behind the incredible piece of code known as sIFR.

In case you don’t know what sIFR is - chances are that you don’t - it’s a method to display rich typography on the web, using Flash, but in a completely transparent, and accesible way.

So as a tribute to Mark and the fantastic work he’s done with SiFR, I’ve switched my sites theme to the sIFR experiment, I never got quite finished with last year - it’s based on the standard template.

I got to look at some of the work he’s done at his company, and it’s SUPER cool.

Mark is also finding time - which is amazing - to work on sIFR, and I got a sneak-view of version 3.0 of sIFR, and it’s going API, will be fully scalable etc.

The main reason I stopped my experimentation with sIFR, was because it didn’t support Danish characters, but Mark would LOVE to hear from you, so I’ll ask him for advice - really it’s “just” a matter of providing the correct Flash files. Another reason I stopped using sIFR, was that I didn’t have the energy to chase down nicer fonts, the defaults aren’t exactly the nicest.

Wondering what Mark is up to these days? You’ll better watch it!

If you’re using sIFR, do give Mark a shout, he’d appreciate it, and his work deserves ALL the recognition in the world!

ps. Incidentally I just lost a good friend, due to COMPLETE stupidity on my part, I guees that I’m an a**hole, and the irony is that, he was the one, who drew my attention to sIFR. So long buddy :-(

Getting out of beta: The decade of “search” is over - ushering in the decade of “knowledge”

Wednesday, January 9th, 2008

When “Sergei and Larry” approached Yahoo with a brand new concept of a “search engine”, they discovered, to their dismay, that Yahoo wasn’t really interested in “search”, but in selling ads. So Google was born.

How I discovered Google

In 1998 I was doing a search of myself, e.g. ego-surfing, using my preferred search engine, Lycos, and I was stunned to see that the top hits were Usenet groups that contained my name, several of them in fact, but worse: they had names like kimbach.slut.slut.slut etc.

I was a bit upset, especially since I, at that point, was being sued over violation of the marketing law by a former employer - a case that was later thrown out - but I assumed that they might have created those groups, to slander me, and I was quite sure that it wasn’t me that created those groups ;-).

I took a look at the content of the groups, and they had very low traffic, I only found some spam, which was rare in 1998, and someone who asked the question “who is Kim Bach” - a question I’ve pondered myself, but it didn’t look like it had anything to do with me.

Eventually I contacted the hotline of my ISP, Image Scandinavia, and they referred me to…GOOGLE.

Doing a search on Google, I realised that it had nothing to do with me, but that the groups had been created by a disgruntled husband, and Kim Bach was his ex-wife!

I also believe that using Google for the first time, immediately made me drop Lycos. At that point Lycos actually yielded what I’d label “better results”, but that changed quickly.

Google, originally, cracked “the search code”, and the world changed.

How I discovered Wikipedia

This I also remember clearly, and it’s quite interesting, I googled it - indirectly!

3-4 years ago I was trying find the English word for the type of dog, that is called “gravhund” in Danish, I somehow ;-) knew that a literal translation wouldn’t do, since that would have yielded “diggingdog”, “digdog”, “gravedog”.

So a Google search let me to the English Wikipedia article for Dachshund, and that was what I was looking for!

Seeing Wikipedia was an instant eye-opener, and at that point it hadn’t even dawned upon me, that Wikipedia was pure user-generated content!

Google isn’t interested in “knowledge”

Google won by doing a better job, but now “we, the people” are approaching the world with a concept of a “knowledge engine”, only to discover, to our dismay, that for instance Google isn’t really interested in “knowledge”, but in selling ads.

The difference: “we, the people”, will, surprisingly, transform Google from a “search engine” into a “knowledge engine” as well, no matter what Google does. The algorithm Google uses will give preference to “quality”, at least in the long run, and since “we, the people” are so numerous this will happen sooner rather than later.

Case in point, the best SEO strategy I know of is to create a Wikipedia article, try googling the terms I’ve created Wikipedia articles for (for instance: Kim Schumacher, DB03 and DB07).

You’re brainwashed

Google and the big companies have had us, pretty much, brainwashed to think that we have no say. This is reflected by the response to the launch of the Wikia Search engine, on the historic day, January 7th 2008.

Everyone is trying to compare Wikia Search to Google, and that’s missing the point COMPLETELY, and people should read what Wikia Search are writing:

WE KNOW THAT THE QUALITY OF THE SEARCH IS: “PRETTY LOW” (a polite way of saying that it “stinks”)

The way to help change it, is simply to get involved.

Every-time you do a search on Wikia Search, you’re offered the option to edit a “Mini Article” on the search. A “Mini Article” is just a Wiki article, that explains the search term. The “Mini Articles” will be used to improve the search index.

“Unfortunately” people seems to have been using a search on themselves as a benchmark, meaning that a lot of the “Mini Articles” are links to private and small web-sites, but that reflects the community.

Ego-surfing was also one of the first things I did, and the first hit that could be attributed to me was result number 8, and that yielded the photos I’ve taken, that are in the Flickr pool I created for Sjakket, my former place of work.

Is that my major contribution to the world? Well it’s not that far from it, bordering that I believe that it could be.

Getting involved - choose a community to “work” for

My criteria are:

Not for profit, open, free, strong community, sustainable.

The beer isn’t free however, so you’re allowed to make money, but take into consideration how the money is being made, if it is sustainable etc.

Personally I’ve chosen these organisations

Currently I’m mostly involved in Wikia Search, I’ve found it really intimidating to be a contributor to an Encyclopaedia, so my contributions to Wikipedia have been quite limited, Wikia Search is much less intimidating, and right up my alley.

Where would you put your money (e.g. time)?

In ten years, Google has gone from no to 16.000 employees, but “we, the people” will, in ten years go from no to 6,5 billion, or how many it is that “we” are in 2018.

Where would you put you money (e.g. time)? It will only cost you time, and you’ll be involved in building a beautiful shrine to knowledge and human achievement.

Together we’ll do Google one better: crack the code of “knowledge”, and the world has changed forever.

Free at last, free at last, oh God almighty we’re free at last.

And “we”‘re hiring! No need to submit a resume, come join the fight!

Read more here:

Weaving an untangled web - The Friend of a Friend (FOAF) project

Friday, January 4th, 2008

FOAF Project LogoThe Friend of a Friend (FOAF) project

I really need to “get out more”, since I’ve only just now discovered the Friend of a Friend project (FOAF), and I LOVE it!

The Friend of a Friend (FOAF) project is creating a Web of machine-readable pages describing people, the links between them and the things they create and do.

Say what?

FOAF is an important part of the so-called semantic-web, and FOAF is just a so-called RDF specification of who you are. RDF (Resource Description Framework) is one of the basic technologies of the semantic web, and it’s nothing more (or should I say less) than an XML schema condoned by the W3C for describing resources.

Think of RDF as “the mother of all links”, RSS and Atom actually uses RDF.

The problem with links

So what is that RDF does better than the tradtional link?

When you create a link, you rarely remember to provide important information about what it is that you actually link to. At best you provide an ALT attribute (description) to an image tag. Google actively uses the ALT tag when indexing images, but if the link to an image contained more information, eg. semantics, Google could do a much better job.

Semantics means that you provide information about content and context, not just a link to it. You could call that metadata, abstracts or just “data”.

Many CMSes uses the URI of posts to provide some semantics, it’s often called SEO (search engine optimisation), the URI of this post has FOAF in it, meaning that a link to this article indeed contains some semantics.

A common standard for the WordPress CMS is that it uses year, month, day and the title of the post to generate the URI.

The problem is that this information should be provided in a structured, machine readable and - most importantly - open format, in order to make it possible to provide semantics.

I actually despise the concept of SEO, since it amounts to cheating, the only valid SEO is:
“provide interesting content”

A semantic “you”

A number of standards for providing semantics exists, one of the most interesting, especially in this day and age of social media, is the FOAF format.

FOAF is a format that describes you and your connections to provide semantics about people (you) and your connections (friends), in a standardised way, using RDF.

The FOAF file contains information about who you are, how to contact you, but most interestingly it contains links to your friends, and their FOAF files.

The beauty of FOAF is, that all you have to do, is:

  1. Create a FOAF file, for instance using FOAF-a-matic
  2. Put it on a server
  3. Provide the URI
  4. Make sure that it can be found by others (e.g. by posting a link on a page you know is indexed)

Chances are that the FOAF spiders will have a feast on your FOAF, sooner rather than later.

Create your FOAF file

It’s quite simple to create a FOAF file, all you need to do is go to FOAF-a-matic, fill in a number of fields, generate the FOAF file, copy it to a text-editor, publish it on your web-site.

Below is a screenshot of the FOAF-a-matic page.

FOAF-a-matic screenshot

Take back your profile, it’s…YOURS!

No need to register with social networking sites, your profile is YOURS.

Who owns the information about “who you are”? You do! Should that information be made available in an open format? You bet! RDF and FOAF is the way to go.

And don’t take my word for it, just take a look at the people who are promoting and developing RDF and FOAF…

So how did the chicken cross the road

I’ll provide you with the story about how I found FOAF, since it’s interesting to say the least.

My good buddy Sebastian Lund just recently set up his blog, Silence is deafening, and I’m looking forward to following it, he’s using a beautiful theme, the Dilectio Theme, developed by Design Disease.

Design Disease has a number of free WordPress themes available, and you can test them, when I tried that, their “Lorem Ipsum” turned out to be an article by no other that TBL, timbl, Tim Berners-Lee, Mr. Web himself, and he was writing about blogging and FOAF…

So:

What an untangled web we’re weawing.

Now I need to think of a good URI for my FOAF file, TBL suggests this:

A lot of people have published data about themselves without using a URI for themselves. This means I can’t refer to them in other data. So please take a minute to give yourself a URI. If you have a FOAF page, you may just have to add rdf:about=”" and voila you have a URI http://example.com/Alan/foaf.rdf#ABC. (I suggest you use your initials for the last bit). Check it works in the Tabulator.

Ready, steady FOAF

So what are you waiting for? Create your own FOAF file, and start sharing.

And now I’m moving on to explore Tabulator, more on that later…

ICT Mythbusters Episode 2: Attack of the Clones! Or Is Microsoft just copying Apple? Or A Tale of Type

Sunday, November 18th, 2007

Banner Mb-Cafepress

Welcome to ICT Mythbusters Episode Two - this time we’ll be investigating the myth that Microsoft is just copying Apple. The post is indeed subtitled “Attack of the Clones”, but bear with me, I have to take a detour to the world of digital typography, before returning to the real topic, so if you’re the impatient type (pun intended), just proceed to the end of the article.

ICT Mythbusters is inspired by the great Discovery show Mythbusters, and you’ll find Episode One here.

Is Microsoft just copying Apple?

Among Apple Macintosh faithfuls, it’s considered common knowledge that Microsoft, with Windows, just made a bad copy of the Apple Macintosh, but who’s copying who?

Erik Spiekermann from the Helvetica DocumentaryWhat triggered me to revisit this myth, that I’ve covered in detail before, was the screening of the great documentary, Helvetica, that I went to yesterday.

In the Helvetica movie Apple Computers was very much the supporting actor, and Apple was indeed mentioned in the credits. More prominently one of the Gurus of Type design, Erik Spiekermann, stated, as a fact, that Microsoft Windows was nothing more than a clone of the Apple Macintosh.

Spiekermann’s statement sounded just like the Apple marketing hype, and the fact that it was being stated by a very influential person in the industry, triggered me.

Firstly: I was somewhat surprised to hear this in a documentary about type. There’s no doubt that all the graphic designers interviewed for the documentary were already using Apple hardware, but I found it strange that Spiekermann’s statement didn’t end up on the cutting floor.

Show some love for the Mac

First there’s no doubt that Microsoft, and Bill Gates always has been great fans of the Apple Macintosh, as the clip below documents:

To create a new standard, it takes something that is just not a little bit different, it takes something that is really new, and really captures people’s imagination, and the Macintosh, of all the machines I’ve seen, is the only one that meets that standard

Case closed: Bill Gates just admitted that Windows is nothing more than a cloned stormtrooper.

Now wait a minute…As you might notice the clip is quite old, and at that time Microsoft was working on creating one of the key selling points, even to this date, for Apple hardware, the Excel spreadsheet.

Excel was originally developed for the Macintosh, and it wasn’t released for Windows until the the dying moments of the 1980ies. In fact, Microsoft has done more for the proliferation of the Apple Macintosh than any other software manufacturer, and you could argue that the commitment to the Macintosh platform that Microsoft guaranteed at the famous MacWorld keynote in 1997, was a pivotal turning point. Steve Jobs even declared:

We have to let go of the notion that for Apple to win, Microsoft has to loose. [...] The era of setting this up as a competition between Apple and Microsoft, as far as I’m concerned that is over.

And then Jobs went on to establish the fact that Apple and Microsoft, together, is the standard with a combined market share of 100%. Whatever Apple and Microsoft does is the standard.

Well I’m sure the $150 million investment by Microsoft, and the televised image of Bill Gates in the background, had something to do with it, but Steve Jobs was just saying exactly what the stockholders and board-members wanted to hear.

What’s your type?

The market for Apple Macintosh was very much created by the fact, that the Macintosh Computer was the first desktop computer capable of doing print quality design, this revolutionised publishing.

Really it wasn’t so much Apple’s technology that helped create this market, as it was the PostScript technology developed by Adobe.

Until PostScript, all fonts used by desktop computers were so called bit-map fonts, it meant that the fonts were digitised to a specific resolution, and they looked horrible if you tried to scale them to a different point size than the one that was provided with the operating system.

Another problem with the bit-map fonts was that they required a lot of storage, laser-printers use a resolution of 300 DPI (dots per inch), a point in typography is 1/72 of an inch, meaning that 12 point X roughly requires 50 x 50 pixels = 2.500 pixels, and you needed that matrix for all 256 possible characters in the character sets used until the 90ies, a rough calculation yields 640.000 pixels, in bytes that is 80.000, meaing that you’d need approximately 80KB to represent a 300DPI bit-map font. Multiply that by several factors, because the italic and bold versions need their own representation as well, and that should once again be multiplied by the number of fonts installed.

Today this doesn’t sound like much, but remember that the first Macintosh came with only 128KB of RAM, and NO harddrive. In those days a Linotype typesetter had a resolution that was a factor 16 higher, so Houston we have a problem.

Mathematics to the rescue

The PostScript technology used mathematics to describe the fonts (quadric Bézíer curves), making them scalable to all sizes, and a special “hinting” algorithm that reduced the processing power needed when rendering the types.

The technology is known as Adobe Type 1. Adobe had also secured licensing deals with Linotype, the dominant player in the type-foundry business, and owner of a huge share of the mainstream fonts.

The fact that that you could do close to print quality proofs on the desktop, and then simply send the PostScript files to the Linotype typesetter, for print quality, and be confident that the result would look the same as the proof, was nothing short of a revolution.

Fight the power - TrueType this

So heavenly bliss, we had scalable fonts of “infinite” quality, and thanks to the software Adobe Type Manager (ATM), type 1 fonts also worked on the screen, delivering the holy grail of desktop publishing, true WYSIWYG (What You See Is What You Get).

So what was the problem with this? The problem was the exorbitant licensing fees that you had to pay Adobe to use the technology and Linotype for the use of their copyrighted fonts.

One of my favourite parts of the Helvetica documentary, is in the scene where we’re taken to the “holiest of holy”, deep below the HQ of Linotype, where they keep the original Hass designs for Helvetica, it’s their “precious”.

Another problem with Adobes technology was that it was very processor intensive, making the screen rendering of the fonts quite slow. Anyone that has ever used ATM on early 90ies hardware will know what I’m taking about.

So Apple was developing a competing technology, TrueType, and later Microsoft and Apple worked together to create an alternative to type 1. Microsofts work included the introduction of replacements for the predominant fonts of the day, Helvetica became Arial, Times Roman became Times New Roman and Courier became Courier New.

Microsoft has contributed a number of major enhancements to TrueType, mainly ClearType, which is an anti-aliasing technology to improve the readability of screen fonts. The technology, which is bundled with Microsoft Reader, has failed to make to much of an impact, but anti-aliasing of screen fonts is the standard today.

Back to the real topic - who’s stealing from who

Oh well, this was a long talk about type, fonts and technology, and proof that the competition between Microsoft and Apple mostly takes place in the minds of the faithfuls (devotees?) of the “Church of Steve Jobs”.

Why is it that neither Bill Gates nor Steve Jobs really want to talk about copying, well it’s because Windows AND Mac OS both are clones.

Xerox Star 8010The work that is the foundation of all graphical user interfaces was done at the Palo Alto Research Center of XEROX, but XEROX being a hardware company, also developed hardware, and the XEROX Documenter or XEROX 8010 Star that really was the first modern computer.
The Star was introduced on April 27th in 1981, several months earlier than the IBM PC. The Macintosh, Windows and GEM shipped 4 years later.

Despite the fact that it wasn’t until the introduction of the NeXT computer, that the mainstream computer industry delivered anything remotely akin to the Star, XEROX failed to make the Star a mass-market product

Attack of the clones! MYTH BUSTED!

Today most people are oblivious of the fact that the Imperial clones were ordered by the agents of the Empire, the ICT equivalents of Count Dooku and Palpatine: Apple and Microsoft. The praise for creating the fantastic tools we have in our hands today should go the XEROX, the Palo Alto Research Center and the amazing people that worked there, for instance Alan Kay, whom Steve Jobs often quotes.

Mythbusted

References

The picture of the real myth busters, Adam Savage and Jamie Heyneman, actually is a banner add, but I make ABSOLUTELY no money from it, if you click it and make a purchase, all proceeds go to the Jamie, Adam and of course Café Press. I hope this will settle any copyright issues with them.

The picture of Erik Spiekermann above, is a still from the Helvetica film, and it is copied from the official site of the Helvetica film. The picture is copyright Gary Hustwit, but I consider my use here to be fair use.

The picture of the XEROX 8010 Star is copied from the wonderful DigiBarn website. The picture is copyright DigiBarn, but since it is under a CC-NA-SA license, I can use it - the wave of the future!

The MYTH BUSTED picture was copied from the webiste of MARIJNBOSCH.COM, there’s no copyright notice on the site, and I consider my use here to be fair use.

iPhone Dev Center - Apple opens the iPhone and iPod touch for developers

Saturday, November 17th, 2007

Iphonedevcenter Loginbanner
iPhone Dev Center - Apple Developer Connection

Apple means business with their promise to open up the iPhone and iPod touch platform to developers with the launch of the iPhone Dev Center, and it looks quite impressive, even though it’s mainly information on how to develop web-applications, and links to already existing information for Mac OS X.

Below is a quote from the mail I just received from ADC:

Available to all ADC Members, the iPhone Dev Center is your complete source for technical information, resources, and expert advice on how to design, code and optimize web applications for iPhone and iPod touch. Take advantage of the iPhone Reference Library, web development guidelines, and sample code to build or optimize your web application. Through ADC on iTunes, you can watch iPhone experts discuss everything from user interface design to optimizing your web applications and content for iPhone.

Once your app is ready, or if you have an existing web app, submit it for possible listing on the Apple web apps page. Log in now and access all the resources of the iPhone Dev Center today.

Unfortunately I don’t think Apple is going to make the platform available to other hardware manufacturers, which is typical Apple, but wouldn’t it be great with Mono ported to the iPhone and iPod touch? And I’m confident that Mono and even Silverlight/Moonlight will be ported to the iPhone platform.

Another brilliant touch (pun intended ;-)), is that the developer resources only is available to registered ADC users, something that the open source communities would barf at, but Apple will get away with it, as usually, and I think that the open source communities should take lessons from Apple.

I think ADC will receive a huge influx of registered users because of this, and it’s a direct path to marketing of the WWDC, which will see an unprecedented surge in attendance next year, which I predict will force Apple into move towards two WWDCs every year, one for mobile and non-mobile devices.

This is yet another brilliant move by Apple - and is that a Steve Jobs version of “the monkey dance” I see on the horizon? Developers, Developers, Developers!

BarCampCopenhagen: Ça plane pour nous!

Thursday, November 8th, 2007

BarCampCopenhagen Logo
BarCamp wiki / BarCampCopenhagen

Ça plane pour nous! …. Ça plane pour nous! … Ça plane pour nous! … Ça plane pour nous! Nous! Nous! Nous! Nous! Ça plane pour nous! uh-u-u-uh! Ça plane pour nous!

I går holdt 3/4 af folkene bag den næste BarCampCopenhagen, planlægningsmøde.

Planlægningsmødet var rigtig hyggeligt (som videoen vist viser) og hvis i kigger derovre, så er der bonus: det var nemlig også produktivt (som det faktum, at vi “sådan set” er klar, viser).

Først og fremmest fik vi lagt skinnerne, i form af to højglanspolerede spor, der kommer til at hedde:

  • Geeky sh*t
  • Kangagoo?

Temaet for de to spor bliver hhv. et teknisk (Geeky sh*t) og et ikke-teknisk spor (Kangaroo?). Emytlogien for Geeky sh*t skal findes i den forrige BarCampCopenhagen, for Kangaroo? Siger jeg: FGI!

Hvis du vil “svæve” med os, så sig til! Vi har plads til i alt 50, og det tal nærmer vi os, hvilket vi er benovede over - TAK for interessen.

Ellers har vi brug for stole, sponsorer (mad, drikkevarer, t-shirts, wi-fi udstyr, gaver) og talere (vi er sådan ca. halvt besat).

Næste BarCampCopenhagen afholdes den 25-januar-2008 hos Beaconware, Gl. Kalkbrænderivej 10, kld. 2100 kbh Ø. BarCampCopenhagen afholdes i overensstemmelse med retningslinjerne for afholdelse af en BarCamp, men sådan generelt er de:

The Rules of Bar Camp

  • 1st Rule: You do talk about Bar Camp.
  • 2nd Rule: You do blog about Bar Camp.
  • 3rd Rule: If you want to present, you must write your topic and name in a presentation slot.
  • 4th Rule: Only three word intros.
  • 5th Rule: As many presentations at a time as facilities allow for.
  • 6th Rule: No pre-scheduled presentations, no tourists.
  • 7th Rule: Presentations will go on as long as they have to or until they run into another presentation slot.
  • 8th Rule: If this is your first time at BarCamp, you HAVE to present. (Ok, you don’t really HAVE to, but try to find someone to present with, or at least ask questions and be an interactive participant.)

by Tantek Çelik as parodied from The Rules of Fight Club.

Pink Dildo Records’s Label Page – Music at Last.fm - Now I manage a record label

Saturday, November 3rd, 2007

Last.fm logoBeneath Contempt Logo

Pink Dildo Records’s Label Page – Music at Last.fm

Yes, I love Last.fm, and after registering as a solo artist on Last.fm (no I’ll not remind you by linking to it - for YOUR own good), I’m now managing a Record Label.
Beneath Contempt Wurst 2

It’s of course Pink Dildo Records I’m managing, and so far I’ve uploaded the non-copyrighted tracks by Beneath Contempt.

In 2000 I investigated the possibility of issuing a CD with Beneath Contempt, called Digital Comeback 2000, with copyrighted covers-tracks, but that was too cumbersome and expensive, so I gave up on it, and the cover-tracks aren’t available on Last.fm either - it would only result it us getting promptly banned, but all the tracks has been made available in FULL and as FREE downloads. N-Joy. Be advised it’s guaranteed to be in GLORIOUS LO-FI.

But it’s quite ridiculous that I can’t make the number one hit by Beneath Contempt, a spoof on Pippi Longstockings called Hippie Longhair, available due to the copyright rules. If you know Danish, and even if you don’t, just follow the link, and make your own version instead - the ultimate in DIY.

“These” limitations will eventual disappear, but only because we now are beginning to make music available for free.

Great Label Manager

As expected the process of uploading material to Last.fm is smooth. The material has to be submitted at 128K MP3 files, and you have to bundle your uploads into releases (e.g. albums). I found it easiest to package your release into a single ZIP file, and then upload it as one release.

After you’ve uploaded the file, Last.fm validates it and I did of couse have some hidden resource forks, that I could iron out, and you’re given the opportunity to change to artist and title of the tracks. The info is read directly from the MP3 file, so remember to have it tagged before uploading it, I had no problems with the process, and considering how much time I just spend uploading pictures to a Share Point Server, this was really easy and productive.

Last.fm also offers to upload the material for you, you just have to send them the CD and they’ll take care of it for you - great customer service.

Last.fm also offers integrated promotion tools, buing of including banner ads, co-marketing deals etc. It’s really quite impressive, and it looks very easy to use.

The traditional music publishers should take note, “Houston: YOU have a problem!”

ps. Trouble in “paradise”

And then I ran into one of the “limitations” of Last.fm’s Label manager.

Oh No - It HurtsI tried to upload the works of another of our “artists”, Oh No, and that name was already taken by, no other, than the brother of Madlib, so now my label and the content is put in an automatic moderation queue, quite understandable, let’s see how that works, and I’m not allowed to manage my label for the next three days, while the account is being scrutinised by the Last.fm staff.

I expect no problems, despite the controversial name of the label and the LO-FI, in mono, no less.

What I expect is than we’ll be told to find another name for the “artist” when publishing on Last.fm, or keep “Oh No” away from Last.fm, which would be a “shame” ;-).

I think the policy of Last.fm makes good sense, but the ambiguty of artist names, especially short and cathcy ones like “Oh No”, is a major problem, and Last.fm could be better at handling that.

If you can’t wait to go back to mono with “Oh No”, you can listen to the tracks we have available on pinkdild.org.