about: things
on me and coding and some things

MySpace has decided to throw in the towel with regards to its expansion in The Netherlands.   [...] had opened up an Amsterdam office merely 9 months ago but has now announced it will shut it down.

http://www.techcrunch.com/2008/10/26/myspace-gives-up-on-the-netherlands/

And about the idea of moving the dutch operations over to the berlin office? What are they smoking in the US Headquarters? Rest assured that this is pretty much the fastest way to discredit MySpace even further in the eyes of its the dutch users.

endlich krise.

ich wollte das nur mal gesagt haben: mich kotzt dieser komplette web x.0 gehypte scheiss dermassen absolut an das ich einfuerallemal die schnauze voll habe mir das weiter anzusehen.

das vieleicht beste der letzten woche war das die web2.0 berlin vollstaendig an mir vorbeigegangen ist. zufaelliger anlass fuer diesen meinen burst war diese beliebige sammlung von dummgeschwaetze  zum beispiel hier.

was fundamental gegen mich spricht ist mein mangelndes vermoegen ein vermoegen zu haben. egal. ich werd nun weitermachen projekte zu realisieren anstatt sie gegen die wand zu fahren.

endlich krise,
have fun

not really a blog post but the very first entry after the total collapse of my work of rebuilding the antic collection of old stuff fundamentally drowned together with its broken mainboard. gone,

this is now Linux uks 2.6.24-gentoo-r7 #1 SMP Thu Aug 21 14:53:10 CEST 2008 i686 Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz GenuineIntel GNU/Linux
talking.

And as you might see, it took me 55 days before i made a post:

~: uptime
09:12:21 up 55 days, 12:48,  2 users,  load average: 0.00, 0.01, 0.0
~:

and now, back to business, and hopefully more posts about some hot stuff in the future here.

puh, das war nen hartes stück arbeit. meine alter linux hobel wird wohl dank meiner guten pflege bald mal seine 10 Jahresjubiläum feiern aber ansonsten fällt er so langsam deutlich ausseinander. Nachdem nun diese unfreiwillige Ansammlung antiker Software, frei von feature und security updates, mal wieder seinen geist aufgegeben hat und nicht mehr auf die beine kam musste ich nun endlich auf aktuelle versionen umgestellen.

alles nicht so einfach, da das package wartungssystem schon vor jahren seinen geist aufgegeben hat muss man den kram in guter alter weise von hand zusammenkompilen. und schon geht das los mit den dependencies. apache will nicht wg. libxml2, mod_php fehlt, wordpress kann dann nicht mit dem neuen php, und so diverse kleine utilities libs spaeter ist dann mal schnell ein tag weg.

aber wie sagt wordpress doch so schoen:

Consider rewarding yourself with a blog post about the upgrade,

ein neues mysql musste ich mir auch noch hinbasteln und das die Datenbank wohl schon seit jahren auf port 3306 offen war und der “root” account auch ohne password ist beweisst einmal mehr wieviel sicherer doch unix als windows ist.

spiegel|online: “Vorbeugendes Schnüffeln ist tabu – es muss Gefahr für Leib und Leben bestehen, bevor der Staat Festplatten ausspähen darf….: Der Computer wird zum Teil der Persönlichkeit.”

genau! coole jungs, so geht das. damit waere das dann mal geklaert. nur schade das schaeuble jetzt nicht mehre meine backups macht.






Technorati Tags: security, terror, orwell

in my typical love and hate relationship with opensource  (aka open sore) i stumbled over SASL induced configuration pains again today. To cut a long story short, just disable DIGEST-MD5 sasl out on the openfire jabber server and immediatly xmpp4r works like a charm for me.

How to disable digest md5 on Openfire? Not so easy to find out and in a beautiful amateuristic way lots of the advice you find is actually plain wrong.

Put this into your openfire.xml:

<sasl><mechs>PLAIN</mechs></sasl> 
<!-- but put it inside the <jive>...</jive> tags somewhere --> 

, because when you know the name of the right openfire property, and are able to read(in openfire.xml):

    This file stores bootstrap properties needed by Openfire.
    Property names must be in the format: "prop.name.is.blah=value"
    That will be stored as:
        <prop>
            <name>
                <is>
                    <blah>value</blah>
                </is>
            </name>
        </prop>

,then you easily know that <sasl><mechanisms>….</mechanisms></sasl> is bogus.

you usually find your openfire.xml at ${OPENFIRE_HOME}/conf/openfire.xml. and you must restart the the server afterwards, like /etc/init.d/openfire restart.

there is another option, like making the xmpp4r implementation don’t even try to use the digest-md5 mechanism which the openfire server offers. Just disabling DIGEST-Md5 acceptance at /opt/local/lib/ruby/gems/1.8/gems/xmpp4r-0.3.2/lib/xmpp4r/client.rb:108 in Jabber::Client.auth does work, but i will try to get it implemented a littel more selective before posting a xmpp4r fix here. Who knows, there even might be two SASL DIGEST-MD5 implementations on this planet which actually do match? i doubt it, an even then, i don’t care. vote for alt.source.sasl-must-die-die-die and

have fun



Technorati Tags: xmpp, xmpp4r, openfire, jabber, sasl, digest-md5

yep,



found @ http://www.woostercollective.com/2008/01/geek_graffiti.html




Technorati Tags: politics, usa, geek, humor

the title was actually quoted from the the Amazon Web Services Blog. That post reports on a new option of running a version of the Wowza Flash Streaming Video server as a virtualized AMI instance  from insides the Amazon EC2 cloud.

What this all means? You get a real cheap way to build you’re own streaming network. For private videos YouTube will to the trick of serving your private holiday videos to the fans and you don’t have to bother for neither price nor capacities. But with such a thing as a Wowza server on EC2 you can now build your very own YouTube on demand. And it’s running on small pockets too. For only 5$ a month you get the right to do so and beyond that you pay per-hour and bandwith.

But even besides the economics, Wowza brings more to the party. It is a real good piece of software it seems. I worked with it just end of last years and all operations where smooth. Before Wowza choosing a streaming server sometimes to me felt more like “die Wahl zwischen Pest und Cholera”(or Hobson’s choice as i learned). I worked with Wowza last year and it was breeze of fresh air. I think i read somewhere it was written by some old SGI dudes. Ah, good old times, but that is another story(Personal Iris anyone?)

Adobe, the original? Expensive, old-school. heavy. not sexy. Red5 Open Source? Good luck i wish. I never had. Quicktime? Don’t know about QTSS but the DSS variant of it failed on me badly whenever i needed it and on top of that it uses PERL! to serve its admin HTML pages, uha, shudder.

Some fellows became even so desperate as to start recoding things from scratch and try writting an RTMP* server in Erlang. As i said elsewhere, Erlang, power- and beautiful concepts, but such an ugly language. Again, good luck i wish. If someone might want to spent a couple of month on trying to combine Erlang concepts and ruby language on writing a scalable stand-in replacement for the proprietary FLash streaming video server solutions than please give me call. Would be a nice project.


Technorati Tags: wowza, ec2, aws, flash, streaming

Matt Aimonetti released a 1.0.0 version of his googlecharts gem which includes my URI bugfix i blogged about earlier. Me haven’t had so many opensource contributions yet, feels good though.

Technorati Tags: googlecharts

Stumbling again over the gardner group SL hype cycle today i couldn’t resist applying this little fix to it. Those which still care for SL will know what i mean. For the others, don’t bother, looks like you won’t need to watch out for Linden Labs Second Life. Will they ever come back?

Virtual Worlds, mainly in the form of Virtual Goods(GOLD!) will be become bigger and bigger over the years, but this will happen without SL. And rightfully so. Their client is still really bad. No fun in starting it up on my laptop, so i don’t.

If you ever checked the super ugly absolutly non-maintainable source code* of the open source client, you can’t hold back to interpret this as another example of an solution which was not ready to deliver once the markets where ripe for conquer.

have fun

* and don’t forget, “use the source, luke!”




Technorati Tags: secondlife, hypecycle, gardner