http://www.cracked.com/article_18513_5-insane-file-sharing-panics-from-before-internet.html
2010-05-24
Fwd: Insane file sharing panics from before the internet
http://www.cracked.com/article_18513_5-insane-file-sharing-panics-from-before-internet.html
2009-02-02
"Problems" over in the USA
2009-01-14
"friendly" DRM? Better than non-encumbered content? (Update 2009-01-16)
But why is it, that educated people are that immune against realities:
- No DRM, no restriction
- any DRM, restriction; and - if it's not a purely passive watermarking - less value
2009-01-12
How NOT to handle payments
For a simple purchase by credit card (below 30USD) I have to create a separate account with the payment platform! What for?!
Opening the account is a multi-page huge form process... Upon submitting, an error an further fields appear from nowhere. Of course, the mandatory "yes, I want you to spam me" checkbox is checked on each iteration!
And finally, they request my mobile number! No payment without verification of my mobile phone?! WTF?! I don't give my mobile phone number to an anonymous corporation!
As I cannot buy my specific purchase in a different shop, I call them and have a nice 15 min chat to finally get my payment through (no, I didn't call from my mobile phone).
From a customer's view, this payment platform is inacceptable.
2009-01-07
Hail XSL(T)/XSD
Sometimes I just have to wonder what implementors think of XML data exchange:
<MotherTongue1>German</MotherTongue1>
<MotherTongue1Id>2001</MotherTongue1Id>
<MotherTongue2>German</MotherTongue2>
<MotherTongue2Id>2001</MotherTongue2Id>
Upon clarification, no hierarchy should be implied... Attributes seem to have been lost in wonderland. And oh, the id is an index into a proprietary table of languages, some misspelled, some invalid, some multiple times. ISO 639 anyone?
Want to contact a person described in the XML file? Well, there are
<EmailExternal>
<EmailExternal2>
<EmergencyEmail>
[and more]
.. all scattered around in different parts of the file, of course.
At least I have a properly designed and documented schema?! Oh wait, all it does is assign base datatypes to those fields - and then incorrectly. Birth dates are xsl:dateTimes as xsl:date somehow is "not available", other dates are xsl:strings (diversly formatted)... oh and:
<s:element minOccurs="0" maxOccurs="1" name="Gender" type="s:string"/>
means "m" or "w" (female, german: weiblich), of course...
