Pensoj de Paŭlo

The standard answer to embedding source code listings in a LaTeX document is the listings package. It works in pure LaTeX, by parsing the source code and highlighting some parts of them.

An alternative I just found on Stack Overflow is the minted package, created by Konrad Rudolph. It uses the Pygments library to do the actual parsing and highlighting.

I did not yet try the package, but I will and then update this post for my experiences.

It shows that each of my seven browsers here has a unique fingerprint.

In most of them, even the Accept header is already unique (there is Esperanto as first language, followed by German and English).

Just half an hour ago, the new Cryptography Stack Exchange site transitioned from private beta to public beta.

The original private beta period was extended because of not enough questions. Now we have 70 questions, 152 answers (and only two questions without any answers at all, apart from some ones closed as off-topic).

If you ever had a cryptographic question, ask it now. You don’t even need to get an account.

These were my questions (in reverse chronological order, and at the same time in vote number order):

• Guarding against cryptanalytic breakthroughs: combining multiple hash functions
• bcrypt: can one efficiently iterate valid hash output values?
• Is using slow password hashing on the client side easier attackable than on the server side?

Some study seems to show that lower-IQ users tend to use more Internet Explorer (and even more older IE versions), while higher-IQ ones tend to use Opera and Camino (and IE with Chrome Frame). Firefox, Safari and Chrome are preferred by the “middle” bunch.

Is this really so? (I’m using Opera, by the way.)

Update (2011-08-08): Looks like this report was a hoax. The linked question had an answer detailed analyzing this, but it is deleted now, instead there is an answer explaining the hoax.

An example on how not to ask questions and give answers on Stack Overflow.

This is a proposal to create a questions-and-answers site about constructed languages (like Esperanto) in the Stack Exchange network. It just some days ago got from the definition phase (when it was discussed and decided which types of questions would be on topic and off topic) into the commitment phase.

To be created, the proposal needs commitments from more potential users, including some that are already a bit active at other Stack Exchange sites (like Stack Overflow).

Then there will be a private beta phase, when the committers will ask questions, answer them, define tags and so on. Then comes a public beta - here the we would need to attract the crowd.

At the end of the public beta phase the site will be either become an official Stack Exchange site, or be deleted again (if there was not enough traffic or similar).

(This procedure is the same for all proposals, and explained in the Area 51 FAQ.)

For my part, I think I will mostly answering questions about Esperanto (and maybe general ones).

There is also a proposal Esperanto Language & Usage, but this is still in the defining phase, and not even near the commitment phase.