What: Seattle Monthly Meet-up, organized by the Pacific Northwest chapter of the American Society for Information Science & Technology.
http://asistpnw.org
Where: Elysian Pub, 1221 E. Pike St., Seattle, WA
When: 7-10pm, 2nd Thursday of every month

Once a month, we’ll get together to have drinks, chat, network, and geek out with fellow information architects, librarians, usability experts, user experience designers, and other like-minded people. It’s open to anyone, so bring a friend — especially those in other local organizations! The format will be casual, but all are encouraged to bring something to discuss — recent work, an interesting topic, or even your resume.

See you there!
-Aaron

Passwords are not particularly secure. It’s hard to make, remember, and use one that is hard for programs to guess. Therefore, people who case about security frequently use a package called OpenSSH for logging into remote hosts to work instead of telnet.

I’ve been working with a bunch of people for the last while, who wanted to have their sessions logging into remote machines not be trivially snoopable and also wanted to not have to remember their passwords for a bunch of machines. I wrote up a set of instructions based on openssh that are designed to make this relatively straightforward.

This is how I normally use remote unix boxes — set my password to an ludicrously long, difficult to crack/remember/whatever string and then use ssh and public key encryption to actually log in. It works for me. These instructions are probably most useful for MacOSX and other unix (Linux) users (and MS Windows users using cygwin on the command line.) Most Windows users will want to use Putty, which is a fine package of encryption tools for that platform.

Technorati Tags: ssh, security, password, openssh, login, remote login

But after a while, I was thinking that I’ve seen touch-sensitive application dependent interfaces before. Eventually, it occurred to me that it was the computer interface from Star Trek..

This selection of PDA-like devices might be clearer. Apparently, the interfaces adapt to the application that you’re running, and are touch-sensitive on the same sort of black screen.

So, in regards to this, I have only one thing to say:

KHAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAN!!!

Here’s some instructions on how to use evite’s suggested method for doing this — giving the event a URL of its own, and then mailing the URL to people.

1. choose the ‘Change Reminders/Include Event Link’ option. This is usually on the right side of the website’s content a ways down. Depending on your template, it will look something like this, but may vary slightly based on the graphics in the site and other things.

2. Enter the name of the party at the end of the URL. After you select that, it will cause a new area to appear further down on the screen where you can schedule reminders and insert a party name at the end of a URL.

If you put something there (like gradparty) as seen here, you’ll then be able to mail people a link to the URL for the party, and they’ll just be able to rsvp there, and they won’t have to go through the RSVP process.

3. Profit For example, for this (non-existent party), you can send out an message with
http://www.evite.com/app/publicUrl/evite@corprew.org/gradparty

in it and people will be able to RSVP.

It has a upcoming reference here, for those of you who are fond of upcoming. If you’re going, feel free to drop me a line.

asist2005