I’m also rethinking how to put bulletware in its rightful place
I really like Mike Clark, and these are interesting ideas about conveying information.
Putting Bullets In Their Place
Does your login page Yahoo?
Yahoo! Mail - The best free web-based email!
The Yahoo! mail login page uses some interesting ideas. They hash information on the client-side before attempting to login. They also store retries, and a challenge in hidden fields as well.
I should look into this a bit more. Some of this may be used to make it difficult for scripts to login. Some may be used to make it safer for users of public computers and prevent sensitive information from being cached on the client. Does thelocation.href really instruct the browser to begin loading the URL while the current JavaScript continues execution? I find that hard to believe, but I’ll check it out.
Refactoring the Publishing Process
Erik Hatcher and Steve Loughran mention a future paper I’d really like to read in this excerpt of antbook-update.pdf (application/pdf Object)
So far I haven’t seen this paper, but the idea seems great and I hope to see it soon!Some day soon we will explain how the book was done, and how books could be
done better in future in a little paper, Refactoring the Publishing Process [4].
For now, key points are:
- CVS server on a Redhat 7.1 system, “eiger” in the home DMZ.
- Home stateful firewall (WebRamp) set to allow port 22, ssh through.
- Office XP with tracking enabled.
- Ant wherever we could.
Steve says “I don’t know how it has ended up that you need to have a home
DMZ to keep your server and 802.11b LAN separate from your other boxes,
with two levels of firewall to make deploying across a house complex, but it has.
It’s bad enough defending against script kiddies, pretty soon I’ll have to worry
about the RIAA too.”
