a:link,a:active color: blue; a:visited color: purple;in boxless.css, but the email link given on the page is invalid! Please, if you're going to obfuscate the email, make it obvious or don't make it a link.
If you design your website so that it requires cookies, you ought to be punched [...] If you implement redirect chains [...] you ought to be kicked and battered, especially if those are implemented with meta refresh instead of HTTP redirect. - Madduck's pet peevesI agree entirely. If you want to save data to my computer, ask me beforehand, else it will be refused. Particularly annoying are people using off-the-shelf applications which do the right thing and don't require cookies (OSCommerce, for example), but their idiot web developers have hacked it into requiring cookies by not thinking through the possibilities and ignoring library routines.
- tcm: the user interface is a nightmare and despite at least half an hour of reading the docs and trying hard, I had not managed to create a .xmi file describing a simple publication workflow. Reason enough to move away from this horrid application.
ArgoUML, a Java-based application (see how desperate I am?) doesn't even want to start with the 1.5 JRE. Lacking any usable editors, I might just implement the whole security update process in Python. At least then it's formally described. If only there was a tool that turned some sort of state description files into valid UML...
- umbrello: 50 Mb of downloads later, I finally had the KDE-based umbrello installed and within five minutes, I understood how to accomplish what I want with the more or less intuitive user interface, although I have still not found out how to associate actions with transitions. Anyway, while I am happily clicking away, umbrello suddenly disappears without a warning, message, or output to the console. Thanks, KDE, for making intuitive software that looks good; whether it's usable and/or stable is an issue with which you need not concern yourself.
http://30boxes.com/signup.php?action=finishSignup&d=aSDFJKLa43da
safjdAL5RLKj4afjrafa45J5kljtyTGJrALKJgFKLsaj5klJ4jkljakljdkalflk
fASJKjdfa4r23890fdfjskl342390fakjlei309dk390ujkal39032kd03j9djd9
Okay, so lets look at this rationally for a bit. How many unique strings can they have from that huge behemoth of an identifier. There are 145 characters. They are using the entire uppercase (26), lowercase (26) and numbers (10), so there are a total of 62 unique symbols for each spot. That gives us a total of 62145 different strings. That's
78848779858160540639233408124436328679807474352650645474403652978
77812230999983634922053904324829205441837830921209410767866820350
39259149646534571887966722870103317751633817974743087029882020930
78213775489032524047364643001443429901072761743321026356976812032
different combinations. In scientific notation, thats 7.8 × 10259. Just for comparison, the entire number of atoms in the universe is high-balled at 6 × 1079 (on this page). That's more than a googol of identifiers for EACH ATOM, EVERYWHERE. Isn't naming each atom once enough? Then you would only need 45 characters, which would nicely fit in one line of my email client if you just shortened your "finishSignup" to "fS" and action to "a". As a bonus, it also saves you approximately 117 bytes of bandwidth per email.
UPDATE: Apparently it has ALL the information, in addition to being completely too long. I replaced it with random crap.
Last week, some friends and I played a very exciting and long (6 hours) game of Risk. At the end, I thought: Too bad we can’t rewind the game and play it fast forward, just see how the tides of colors are waging.Well, on Sunday, I though, why not, and started writing “RiskRecorder”. It is my first larger project with python and gtk+, and I am quite content with both of them. The map is stolen from JRisk, and with that the idea of a gif file that maps pixels to countries. The RiskRecorder is meant to be used during a game of regular risk, to - well - record the moves. As a side benefit, you don’t have to calcuate the number of units you get anymore, as the RiskRecorder can tell you that. You can then save the whole game for later review.It should be in a usable state by now, but I plan to add more features sometime, like better animations and graphs showing development of the game.To try it yourself, you need the program itself (one file so far), then get at least the board.map, board_map.gif and board_pic.jpg from the jrisk CVS repository (you can open any other JRisk map in RiskRecorder, too). You might need to download the python bindings for gtk and cairo, too. On debian, I assume that apt-get install python-gtk2 python-cairo will get you what you need.As always, comments, bugreports and patches are welcome. To follow development, have a look at my svn repository.
Indymedia Centre Tech recently reviewed available CAPTCHAs and alternatives. Please, if your blog uses these images:
Even if you're not in China, you can't rely on google's results from one minute to the next. The ranking algorithm is manipulated by both Search Engine Optimisers as a paid service, and by google's admins as a punishment of sites they don't like. See this google guy's blog for one example of them ranking a site off by hand.
A much dumber idea than Wouter's is charging senders for their emails, as a BBC report says AOL and Yahoo will do. AOL and Yahoo want some of that lovely spam profit?
The oral evidence was heard yesterday and Alex Hudson reported what he saw there.
planned licensing changes to The Regal pub situated below us [...] music playing in the pub, which will be heard in one of our auditoriums [...] join us in our fight by objecting to any licence changes [...] env.health@cambridge.gov.uk [...] by Friday 3rd February 2006.I think that cinema is my most frequent reason for visiting Cambridge (45ish minutes by train from Lynn). I've written. If you're near Cambridge and want film diversity, have you? Update 1: More info on wereallneighbours.co.uk Update 2: More info on indymedia UK
Mentorn television of Glasgow (who produce programs for the BBC) spammed me in October 2005. I now have an Office of the Information Commissioner case number for the incident.
Next.