Biella Coleman: 19th century tatoo
Wow, this looks like a real cool research project. Wish they had included some photos as well.
M. Fran ois Vannson. Les logiciels pare-feu ne risquent-ils pas, madame la ministre, de nuire aux logiciels libres ?From: http://www.assemblee-nationale.fr/13/rapports/r1626.asp Which could be approximately translated as follows:
Mme la ministre. Il n y a aucune menace sur les logiciels libres, qui peuvent tout fait accepter des logiciels de s curisation.
M. Fran ois Vannson. Mrs Minister, aren t firewall a threat on Free Software?I must hence express my real disappointment.
Mrs Minister. There is no threat on Free Software who can accept well accept securisation software.
Has anyone experience with Dropbox?It seems to be an interesting web storage service, with 2 GB of free storage.However, the Linux client seems to be closed source
(which is understandable, it seems to have a lot of neat features) - so I
intend to use the web interface only (at least for now).Update #2: There is a
RFP bug
for Debian, some Source is
on the download site. And while this sort (except the images) is GPL, it's
just the nautilus integration part, not the daemon you also need.Did you try Dropbox? Does it work well? I know some people (especially Windows
users) who could benefit a lot from a service like that, so I wonder if I
should recommend them Dropbox. Or is there some better alternative (it should
allow sharing of files though - synchronization is not as essential, it is a
lot about exchanging files too large for usual email in small user groups;
still synchronization probably is a comfortable way of transferring the files
without having to think about it yourself)?No comments in this blog - email me via erich AT debian ORG.P.S.
pub 4096R/6AA15948 2009-05-10
Key fingerprint = 7A33 ECAA 188B 96F2 7C91 7288 B346 4F89 6AA1 5948
uid Ana Beatriz Guerrero L pez <ana@ekaia.org>
uid Ana Beatriz Guerrero L pez <ana@debian.org>
sub 4096R/2497B8B2 2009-05-10
personal-digest-preferences SHA256 cert-digest-algo SHA256Create key
ana@pryan:~$ gpg --gen-key
...
Please select what kind of key you want:
(1) DSA and Elgamal (default)
(2) DSA (sign only)
(5) RSA (sign only)
Your selection? 5
RSA keys may be between 1024 and 4096 bits long.
What keysize do you want? (2048) 4096
Requested keysize is 4096 bits
Please specify how long the key should be valid.
0 = key does not expire
= key expires in n days
w = key expires in n weeks
m = key expires in n months
y = key expires in n years
Key is valid for? (0)
Key does not expire at all
Is this correct? (y/N) y
Real name: Ana Beatriz Guerrero L pez
Email address: ana@ekaia.org
Comment:
You are using the utf-8 character set.
You selected this USER-ID:
Ana Beatriz Guerrero L pez <ana@ekaia.org>
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
You need a Passphrase to protect your secret key.
gpg: key 6AA15948 marked as ultimately trusted
public and secret key created and signed.
gpg: checking the trustdb
gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model
gpg: depth: 0 valid: 3 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 3u
pub 4096R/6AA15948 2009-05-10
Key fingerprint = 7A33 ECAA 188B 96F2 7C91 7288 B346 4F89 6AA1 5948
uid Ana Beatriz Guerrero L pez <ana@ekaia.org>
Note that this key cannot be used for encryption. You may want to use
the command edit-key to generate a subkey for this purpose.
Add other UID
ana@pryan:~$ gpg --edit-key 0x6AA15948
...
command> adduid
Real name: Ana Beatriz Guerrero L pez
Email address: ana@debian.org
Comment:
You are using the utf-8' character set.
You selected this USER-ID:
"Ana Beatriz Guerrero L pez <ana@debian.org>"
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
You need a passphrase to unlock the secret key for
user: "Ana Beatriz Guerrero L pez <ana@ekaia.org>"
4096-bit RSA key, ID 6AA15948, created 2009-05-10
pub 4096R/6AA15948 created: 2009-05-10 expires: never usage: SC
trust: ultimate validity: ultimate
[ultimate] (1) Ana Beatriz Guerrero L pez <ana@ekaia.org>
[ unknown] (2). Ana Beatriz Guerrero L pez <ana@debian.org>
Command> save
Change preferences
ana@pryan:~$ gpg --edit-key 0x6AA15948
...
Command> showpref
[ultimate] (1). Ana Beatriz Guerrero L pez <ana@debian.org>
Cipher: AES256, AES192, AES, CAST5, 3DES
Digest: SHA1, SHA256, RIPEMD160
Compression: ZLIB, BZIP2, ZIP, Uncompressed
Features: MDC, Keyserver no-modify
[ultimate] (2) Ana Beatriz Guerrero L pez <ana@ekaia.org>
Cipher: AES256, AES192, AES, CAST5, 3DES
Digest: SHA1, SHA256, RIPEMD160
Compression: ZLIB, BZIP2, ZIP, Uncompressed
Features: MDC, Keyserver no-modify
Command> setpref SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
Set preference list to:
Cipher: AES256, AES192, AES, CAST5, 3DES
Digest: SHA512, SHA384, SHA256, SHA224, SHA1
Compression: ZLIB, BZIP2, ZIP, Uncompressed
Features: MDC, Keyserver no-modify
Really update the preferences? (y/N) y
gpg: WARNING: no user ID has been marked as primary. This command may
cause a different user ID to become the assumed primary.
You need a passphrase to unlock the secret key for
user: Ana Beatriz Guerrero L pez <ana@debian.org>
4096-bit RSA key, ID 6AA15948, created 2009-05-10
pub 4096R/6AA15948 created: 2009-05-10 expires: never usage: SC
trust: ultimate validity: ultimate
[ultimate] (1) Ana Beatriz Guerrero L pez <ana@debian.org>
[ultimate] (2). Ana Beatriz Guerrero L pez <ana@ekaia.org>
Command> showpref
[ultimate] (1) Ana Beatriz Guerrero L pez <ana@debian.org>
Cipher: AES256, AES192, AES, CAST5, 3DES
Digest: SHA512, SHA384, SHA256, SHA224, SHA1
Compression: ZLIB, BZIP2, ZIP, Uncompressed
Features: MDC, Keyserver no-modify
[ultimate] (2). Ana Beatriz Guerrero L pez <ana@ekaia.org>
Cipher: AES256, AES192, AES, CAST5, 3DES
Digest: SHA512, SHA384, SHA256, SHA224, SHA1
Compression: ZLIB, BZIP2, ZIP, Uncompressed
Features: MDC, Keyserver no-modify
Command> save
Set primary UID
ana@pryan:~$ gpg --edit-key 0x6AA15948
...
Command> uid 1
pub 4096R/6AA15948 created: 2009-05-10 expires: never usage: SC
trust: ultimate validity: ultimate
[ultimate] (1)* Ana Beatriz Guerrero L pez <ana@ekaia.org>
[ultimate] (2) Ana Beatriz Guerrero L pez <ana@debian.org>
Command> primary
You need a passphrase to unlock the secret key for
user: Ana Beatriz Guerrero L pez <ana@ekaia.org>
4096-bit RSA key, ID 6AA15948, created 2009-05-10
pub 4096R/6AA15948 created: 2009-05-10 expires: never usage: SC
trust: ultimate validity: ultimate
[ultimate] (1)* Ana Beatriz Guerrero L pez <ana@ekaia.org>
[ultimate] (2) Ana Beatriz Guerrero L pez <ana@debian.org>
Command> save
Add subkey for encryption
ana@pryan:~$ gpg --edit-key 0x6AA15948
...
Command> addkey
Key is protected.
You need a passphrase to unlock the secret key for
user: "Ana Beatriz Guerrero L pez <ana@ekaia.org>"
4096-bit RSA key, ID 6AA15948, created 2009-05-10
Please select what kind of key you want:
(2) DSA (sign only)
(4) Elgamal (encrypt only)
(5) RSA (sign only)
(6) RSA (encrypt only)
Your selection? 6
RSA keys may be between 1024 and 4096 bits long.
What keysize do you want? (2048) 4096
Requested keysize is 4096 bits
Please specify how long the key should be valid.
0 = key does not expire
= key expires in n days
w = key expires in n weeks
m = key expires in n months
y = key expires in n years
Key is valid for? (0) 0
Key does not expire at all
Is this correct? (y/N) y
Really create? (y/N) y
pub 4096R/6AA15948 created: 2009-05-10 expires: never usage: SC
trust: ultimate validity: ultimate
sub 4096R/2497B8B2 created: 2009-05-10 expires: never usage: E
[ultimate] (1). Ana Beatriz Guerrero L pez <ana@ekaia.org>
[ultimate] (2) Ana Beatriz Guerrero L pez <ana@debian.org>
Command> save
Sign my new key with my old key
ana@pryan:~$ gpg --default-key E8C43461 --sign-key 6AA15948
pub 4096R/6AA15948 created: 2009-05-10 expires: never usage: SC
trust: ultimate validity: ultimate
sub 4096R/2497B8B2 created: 2009-05-10 expires: never usage: E
[ultimate] (1). Ana Beatriz Guerrero L pez <ana@ekaia.org>
[ultimate] (2) Ana Beatriz Guerrero L pez <ana@debian.org>
Really sign all user IDs? (y/N) y
pub 4096R/6AA15948 created: 2009-05-10 expires: never usage: SC
trust: ultimate validity: ultimate
Primary key fingerprint: 7A33 ECAA 188B 96F2 7C91 7288 B346 4F89 6AA1 5948
Ana Beatriz Guerrero L pez <ana@ekaia.org>
Ana Beatriz Guerrero L pez <ana@debian.org>
Are you sure that you want to sign this key with your
key Ana Beatriz Guerrero L pez <ana@ekaia.org> (E8C43461)
Really sign? (y/N) y
You need a passphrase to unlock the secret key for
user: Ana Beatriz Guerrero L pez <ana@ekaia.org>
1024-bit DSA key, ID E8C43461, created 2004-12-06
Send new key to key server
gpg --keyserver pgp.mit.edu --send-key 6AA15948
Hi Ondrej,
How are you?
I am about to publish a new free software project, a new simple PHP framework, and I am interested in your advice.
You started SymPy and were able to make other people join you and develop it with you.
How did you do it?
How did it happen?
Did you actively call for other people or they spontaneously showed interest and joined you?
Are the other major contributor people who were your friends before you started the project?
Did you need to create or manage the project in a particular way to make it attractive to other people?
Are there things you are aware of that promote collaboration or demote it?
I was never successful in doing the same with Winpdb, which while it became reasonably popular, no one has ever joined me to develop it, except for a notable tutorial contribution by Chris Lasher which was developed independently.
Now with the new project, I am wondering what are my chances of making other people try it and take it on. On the one hand it is a new and fresh code base in an interesting field, on the other hand, why would anyone bother to spend their energy on this new project when they have Symfony or Drupal?
What do you think?
BTW, Ohloh believes you have a median of 19,000 lines of changed code per month since the start of their log. Can this be true? Is this humanly possible? According to it SymPy has over 1,000,000 lines of code? I can't understand these numbers. Winpdb has about 25,000 lines after 3 years of development. And from my experience 1,000,000 lines of code projects need about 20-50 full time developers to work on for 2-5 years which is about 40-250 man years. And as if this is not enough you are listed as owner in a dozen other projects in Google code and have enough time to become an awarded scientist. How is this possible?
http://www.ohloh.net/p/sympy/contributors/
BTW2, do you still use Winpdb? If you find yourself using it less, can you say what are the reasons, or what it would take to make it more useful?
BTW3, How is SymPy doing?
Cheers,
Nir
Are the other major contributor people who were your friends before you started the project?No, not a single major contributor was my friend before I started the project. Every single one of them become a developer using the procedure I described above, e.g. first showed on the list or in the issues, and maybe even the very first patch was not a high quality one (and if I was stupid and arrogant, or didn't see the big potential, I would just ignore them). But when given a chance, they became extremely good developers and sympy would simply just not be here without them.
Did you actively call for other people or they spontaneously showed interest and joined you?I very much encourage everyone to contribute, but the initial interest must be in them, e.g. they at least have to show around the mailinglist/issues, so that I know about them. But once I know they are interested in some issue, yes, I try to invite them to fix it, with my help.
So, SHA-1 has potential exploits, but you know what? I only use it for signing plain text things. Email, change files I ve no reason to use it for encryption, as I don t encrypt things
Surely, if anyone is going to make something that collides with a valid signature of mine, it s going to either a) be noticable to the person reading it (random characters in an email?) or b) not be processable by whatever automated sytem is using it.
I ve yet to hear of any exploit that could affect the way I use SHA-1 in a meaningful way. Ok, yes, I m not going to be using it to hash passwords in future (well, GPG uses it to hash passwords, but generally, to be able to crack that, someone would have to have my secret key anyway, which I would count as being compromised!)
If someone can give me a real world example of how this can be used against me, I might go out of my way to replace my key, but for now, I don t see the need. Ok, I might take the next time I meet up with a fellow Debian Developer as a chance to replace my key, but I m not going to go out of my way to do so (as I had to for getting my key signed by my first Debian/Ubuntu Developer in the first place)
We got back from our brief visit to Canada last night. We had a great time,
Vancouver and Victoria were both very nice.
YVR (Vancouver Airport)
This airport has to win the award for nicest airport I've seen. Clearly they
pulled out all the stops in preparation for the Winter Olympics next year.
The airport is very bright, airy and open. Before you even hit the
immigration line, you pass through a couple of water features, some
indigenous art, all of that jazz. Immigration is done in the open in a huge
hall, instead of in the dark bowels of the airport, which was a pleasant
change from the usual US airport immigration experience. (That said, Houston
airport had a pretty nice immigration experience). Oh, and it was blanketed
with free WiFi, which was a nice touch.
Ferry to Victoria
The brief geography lesson I got was that Victoria is on Vancouver Island,
and Vancouver (the city) is not on Vancouver (the island). Go figure.
Getting to Victoria from the airport via BC Ferries was a very seamless
experience. You board a bus from the side of the airport terminal, and it
drives to Tsawwassen, drives onto the ferry, and then you get off the bus
and go sit on one of the passenger levels of the ferry.
BC Ferries
BC Ferries deserves special mention. The ferry itself is huge - 7 decks
(three of them for vehicles). It's a veritable shopping mall on water. It's
got some stores, buffets, exclusive $10 entry lounges, video arcades,
cellular payphones, the works.
The trip to Victoria
The ferry ride took about 1.5 hours, and was very scenic. We passed by a few
smaller islands, and I had an instant flashback to the TV show The Beachcombers that I
used to watch as a kid, particularly the opening sequence.
Victoria
Victoria is a beautiful city. It's the capital of the province of British
Columbia, and I likened it to Canberra in a lot of ways. It had more modern
conveniences than a town with a population of its size would otherwise
normally have.
It was a government and university town. Nice houses, very green in general,
and being an island, there was water everywhere. It seemed to have lots of
bays, and harbours and rivers. It was very nice.
Flight back to Vancouver
We took a Harbour Air seaplane
back to Vancouver on Sunday afternoon. That was fun. I've never been on a
seaplane before. It took about 35 minutes.
Vancouver
First order of business in Vancouver was the purpose of the whole trip:
renewing our visas. That went fine, I'll write a separate post about the
process. Afterwards, we bought tickets for the Big Bus, and toured the city for the
remainder of Monday and Tuesday.
Drive to Whistler
For Wednesday and Thursday, we hired a car, and went a bit further afield.
On Wednesday, we drove up to Whistler to check it out. The drive up took
about 5 hours, because we stopped at every scenic spot we came by.
Waterfalls abounded. There was a lot of work being done on the roads between
Vancouver and Whistler, upgrading them for the Olympics. Whistler itself was
pretty spectacular. Some crazy looking ski runs. The village looked like
Squaw Village on steroids. The drive back only took about 2 hours.
Cleveland Dam, Lynn Canyon suspension bridge
For the last day, we drove to Cleveland Dam, where there was a salmon
hatchery, and checked out the dam, hatchery and surrounding area. It was
lovely and green. After that, we drove to Lynn Canyon to check out the
suspension bridge there (unlike the Capilano Suspension Bridge, which costs
$26 a pop, the Lynn Canyon one is free).
That was all we had time for really. The weather wasn't fantastic during our
stay, but it didn't really prevent us from doing anything either. I'd have
liked to have checked out Stanley Park if we had more time, and Sarah wanted
to go to Grouse Mountain.
We had a near-100% success rate at being picked as Australians, unlike when
we're in the US, where more often than not, people ask us if we're British.
Apparently this is mainly attributed to the fact that Australians run all of
the ski lifts at Whistler. We certainly heard a lot of Australian accents
while we were getting around.
I'd also never seen such a saturation of Starbucks before. In Vancouver,
there were literally Starbucks across the road from Starbucks, and around
the corner from another one. Whistler village had two.
The Canadian accent is cute. They really do tack "eh?" on the end of
everything, although it's phonetically more like "ay?". "House" and "about"
are also pronounced distinctively differently.
Overall, Vancouver wasn't what I'd call bursting at the seams with tourist
attractions, but seemed like a nice city. It was fairly flat. The beggars
were well dressed. Everyone was very friendly. A lot of the taxis were
Priuses. It seemed pretty clean. I could handle living there. Not sure how
bad it gets in winter.
After years of being a dedicated KDE user it seems like it s finally time for me to go back to Gnome. I once tried KDE 4.x from the Debian experimental branch knowing that it s probably unstable and will require a lot of patience. But I was willing to report bugs and dive into new things.
It didn t take long though to find out that graphics were extraordinarily slow with the new desktop effects . The worst was resizing a konsole (KDE terminal window). It took 25 seconds until the window was resized and redrawn! On the interweb I found KDE developers rant about NVidia who didn t support some special extension they needed. They suggested to get an ATI card instead. (No, thanks, I was struggling with the crappy radeon and fglrx drivers on my new work laptop and am sick of ATI for Xorg.) Or I could use a bare XTerm instead. Yeah, right. So I couldn t use the desktop effects. After all I used the non-free NVidia driver for years and it never let me down.
I don t mind doing without eye candy. But the desktop effects were about the only serious way to switch between virtual desktops. Point the mouse into a corner or edge of the screen and get a zoom-out bird s view of the virtual desktops. Nice but quickly annoying. Besides you had to push the mouse pointer a few pixels into the edge (it s not sufficient to just hit the edge) which means that after 10 desktop switches I had to lift the mouse and set it back on the mousepad.
Another annoying issue is that up to now I can t assign functionality to every key on my keyboard any more. I had a neat trick by having 3 3=9 virtual desktops and use my numpad keys 1 to 9 to page through them. 0 on the numpad opened a new shell window. + on the numpad maximized a window. But now I couldn t assign any of those numpad keys. I pressed the 1 but KDE didn t detect Numpad_1 but just 1 . Guess how useful it is to not be able to type the 1 any more. There is a low-priority bug report for KDE from users who want this fixed but it will likely not happen any time soon. So the only way to switch desktops was to poke on the tiny pager widget in my panel. Yuk.
Not to mention that I couldn t put icons on the desktop any longer. There was just a sissy widget that I could use for that purpose but it didn t work like a conqueror or dolphin at all. It was pretty amusing when in KDE 4.2 there was suddenly a feature to re-enable the old behavior. Let me guess, KDE developers - I wasn t the only user you couldn t persuade of the new paradigm?
Next evil thing was performance. KDE 4 takes ages to load. Simple window managers get me started within seconds. Even Gnome. But KDE takes 30 seconds until it s loaded plus some disk grinding in the background. And memory usage wasn t nice either.
And what finally made me mad was stabilty - or rather lack thereof. Everytime the screen saver ran my kbluetooth module crashed. kmail crashed even more frequently than before. (I loved kmail for it s great customizability and feature set.) plasma (the actual window manager) died at least twice a day. Suddenly the panels were looking ugly or crashing.
As a Debian developer I have to follow the unstable branch on my workstation. And there is no distinction between KDE 3 and KDE 4 any more so a dist-uprade inevitably gets all of my applications upgraded to KDE 4 (plus an hour of manual engineering in aptitude because half of my applications weren t upgraded automatically due to different application names and I had a mixed environment). So there I was with KDE 4.2. I really worked with it for a month. I tried hard to get acquainted to its bloatedness and instability. It s really a nice technological preview of what might be possible in the future. Everything is really automatic. Mounting external media. New ways to find programs (although I m not happy with the new K start menu). Funny effects and nice eye candy. But it s far from the rock solid desktop environment that I was used from KDE 3.5.8.
So there I am on Gnome now. I was switching back and forth. One day working on KDE 4.2 and the other day using Gnome 2.26. And although it makes me feel sad I think it s finally time to say goodbye to KDE 4. I have invested a good amount of time and energy into it - even just from a user perspective. But it s not ready. And I finally need to get some work done. A number of projects suffered from my playfulness (my ispmail tutorial, screenshots.debian.net, debexpo, my kids) and it s time to get back to work. And Gnome was pretty surprising. With compiz I have the KDE desktop effects working (here they really do) and they are all customizable. I can assign keys properly again (even the numpad). Everything is pretty fast and stable. I have replaced kmail and its buggy shared calendar feature by Icedove (aka Thunderbird) with the Lightning plugin. Worked from the first minute and hasn t crashed in a week (just have to remember next time to install libstdc++5 to be able to use Lightning). With enigmail I finally have a proper simple working PGP key management that doesn t die and is buggy like hell like in kgpg. And there s the nice Nostalgy add-on that allows me to file emails into IMAP folder quickly again - a feature that just kmail seemed to support so far. Oh, and I see new mail instantly because Icedove supports the IDLE command while kmail has never learned that neat little trick. The Gnome file manager isn t really great for my taste but it s doing its job (dolphin is just much nicer). It s not as nice as KDE but I had to learn that working and stable weighs more than nice. The hard way. And many things I liked about KDE 4 (like starting a new program with Alt-F2 and having a smart application finder and simple calculator in one) are built into Gnome, too. So why bother.
Thanks, KDE, for the years of fun and service. I ll surely miss you. Get back to me should you grow up one day.
Tim and my mother are both neonatologists at the Golisano Children's Hospital inside the University of Rochester.
Earlier today, they had this conversation:
My mother: My son Asheesh is moving to Atlanta.In fact, I'm moving to Atlanta because Shotput Ventures funded me, Nelson Pavlosky, and my friend Raphael Krut-Landau to start a company to improve interactions in the open source / free software world. We get enough money to live in Atlanta from May 18 to August 6, and after that, we have to seek more funding. This has led to a series of ironies. The first is that I am working on a startup. The second is that I left San Francisco to do it. But I have already moved out of San Franisco, and I have left my job at Creative Commons. (Feel free to get in touch with me (outside my website's comments) about filling my shoes there.) Thanks, Nathan and Mike, for giving me the chance to contribute to CC, an organization and project that I have always had a great passion for. For a while, I may seem vague about the project I am about to undertake; it's because I still want to nail down some details between the three of us. When Nelson, Raphael, and I arrive in person, we're going to kick into gear. I've been chatting with a few of you over the past few months about ideas, and I do want to especially thank Karl Fogel and Mako Hill for helping the three of us think through what could be done. Some questions for readers:
Tim: Is it for a girl?
My mother: I don't really know what the kids are doing as far as girls, but no....
Scientific publishing giant Elsevier put out a total of six publications between 2000 and 2005 that were sponsored by unnamed pharmaceutical companies and looked like peer reviewed medical journals, but did not disclose sponsorship, the company has admitted. Elsevier is conducting an internal review of its publishing practices after allegations came to light that the company produced a pharmaceutical company-funded publication in the early 2000s without disclosing that the journal was corporate sponsored.I really hope people use this an an opportunity to detach fully from them.
Scientific publishing giant Elsevier put out a total of six publications between 2000 and 2005 that were sponsored by unnamed pharmaceutical companies and looked like peer reviewed medical journals, but did not disclose sponsorship, the company has admitted. Elsevier is conducting an internal review of its publishing practices after allegations came to light that the company produced a pharmaceutical company-funded publication in the early 2000s without disclosing that the journal was corporate sponsored.I really hope people use this an an opportunity to detach fully from them.
At this point, I d like to take a moment to speak to you about the Adobe PSD format. PSD is not a good format. PSD is not even a bad format. Calling it such would be an insult to other bad formats, such as PCX or JPEG. No, PSD is an abysmal format. Having worked on this code for several weeks now, my hate for PSD has grown to a raging fire that burns with the fierce passion of a million suns. If there are two different ways of doing something, PSD will do both, in different places. It will then make up three more ways no sane human would think of, and do those too. PSD makes inconsistency an art form. Why, for instance, did it suddenly decide that *these* particular chunks should be aligned to four bytes, and that this alignement should *not* be included in the size? Other chunks in other places are either unaligned, or aligned with the alignment included in the size. Here, though, it is not included. Were it within my power, I would gather every single copy of those specs, and launch them on a spaceship directly into the sun.Even if this account represents unadulterated irritation, he leaves us, the reader, with nothing of the irritation, only pleasure. This aftermath of frustration is delivered through the vehicle of humor, which within the hacker context, is the cultural container that best captures the spirit of hacker pleasure or so I will be arguing. Like many humorous rants from the world of hacking (and please send me any others you know of), this text dances with liveliness; it exudes its own rhythm; it glistens to use Ronald Barthes apt phrasing from his short book The Pleasure of Text, which I just finished as part of my theoretical escape into the pleasure-dome. Although there are parts of his book which are to be frank, *really* *not* *pleasurable*, partly due to obscure references to High French Theory, which elide even an academic pair of eyes, the book generally pleases. And one of the most pleasing chunks is his definition of a stereotype:
The stereotype is the word repeated without any magic, any enthusiasm, as though it were natural, as though by some miracle this recurring words were adequate on each occasion for different reasons, as though to imitate could no longer be sensed as an imitation: an unconstrained word that claims consistency and is unaware of its own insistenceIn contrast to the stereotype, a string of words that enchants does so by slipping off the page to hit you squarely in the heart or the gut. Unfortunately, while academic writing steers clear of stereotypes, often trying to present the detailed singularity of a phenomena (even when conditioned by social forces), it does not exactly glisten, though there are a handful of exceptions. I think we need more texts that glisten, even if only during sections or parts of our books and articles (much like the rant helped enliven the more staid technical document). In recent years, in large part due to the influence of free software, there has been an explosion, a move toward going open access. All of this is laudable and I fully embrace it (and have gotten into some small battles over it). But without an aesthetic politics that values pleasure in reading and writing we are doomed to obscurity anyway. A move toward making our knowledge public also required a move toward thinking about the literary aesthetics of pleasure.
At this point, I d like to take a moment to speak to you about the Adobe PSD format. PSD is not a good format. PSD is not even a bad format. Calling it such would be an insult to other bad formats, such as PCX or JPEG. No, PSD is an abysmal format. Having worked on this code for several weeks now, my hate for PSD has grown to a raging fire that burns with the fierce passion of a million suns. If there are two different ways of doing something, PSD will do both, in different places. It will then make up three more ways no sane human would think of, and do those too. PSD makes inconsistency an art form. Why, for instance, did it suddenly decide that *these* particular chunks should be aligned to four bytes, and that this alignement should *not* be included in the size? Other chunks in other places are either unaligned, or aligned with the alignment included in the size. Here, though, it is not included. Were it within my power, I would gather every single copy of those specs, and launch them on a spaceship directly into the sun.Even if this account represents unadulterated irritation, he leaves us, the reader, with nothing of the irritation, only pleasure. This aftermath of frustration is delivered through the vehicle of humor, which within the hacker context, is the cultural container that best captures the spirit of hacker pleasure or so I will be arguing. Like many humorous rants from the world of hacking (and please send me any others you know of), this text dances with liveliness; it exudes its own rhythm; it glistens to use Ronald Barthes apt phrasing from his short book The Pleasure of Text, which I just finished as part of my theoretical escape into the pleasure-dome. Although there are parts of his book which are to be frank, *really* *not* *pleasurable*, partly due to obscure references to High French Theory, which elide even an academic pair of eyes, the book generally pleases. And one of the most pleasing chunks is his definition of a stereotype:
The stereotype is the word repeated without any magic, any enthusiasm, as though it were natural, as though by some miracle this recurring words were adequate on each occasion for different reasons, as though to imitate could no longer be sensed as an imitation: an unconstrained word that claims consistency and is unaware of its own insistenceIn contrast to the stereotype, a string of words that enchants does so by slipping off the page to hit you squarely in the heart or the gut. Unfortunately, while academic writing steers clear of stereotypes, often trying to present the detailed singularity of a phenomena (even when conditioned by social forces), it does not exactly glisten, though there are a handful of exceptions. I think we need more texts that glisten, even if only during sections or parts of our books and articles (much like the rant helped enliven the more staid technical document). In recent years, in large part due to the influence of free software, there has been an explosion, a move toward going open access. All of this is laudable and I fully embrace it (and have gotten into some small battles over it). But without an aesthetic politics that values pleasure in reading and writing we are doomed to obscurity anyway. A move toward making our knowledge public also required a move toward thinking about the literary aesthetics of pleasure.
Next.