Speak Freely To Be Withdrawn January 15

wrenhunt writes "The Speak Freely site has this: 'On January 15th, 2004, Speak Freely will be discontinued and removed from this Web site. Existing users may continue to use the program as long as they wish, but no further releases will be forthcoming. For details and the reasons why Speak Freely is being discontinued, please see the full end of life announcement.'" The reasons are various and interesting; it's graceful of the author to provide an explanation of why a piece of software is going away. Update: 01/11 19:22 GMT by T : As reader pi_rules points out, this story is a duplicate -- my apologies.

Comments

Re:Don't forget...

[Anonymous Coward]

Speak Freely. What is it all about... is it good, or is it whack?

Okay, an offtopic question.

[SharpFang]

Since this story is a dupe, which seems to put end to most of ontopic discussion, let me ask about something offtopic. Not enough for ask slashdot, but quite okay for such a thread.

Okay, I recently bought a new keyboard after the old one had an "accident" with a dog. The new one is my first "multimedia keyboard". I got all those keys, I assigned some basic functions in LinEAK (volume up/down, eject/close CD) but I still have a bunch of unassigned keys and no real idea what to assign to them.
Of course I could assign launching different apps, but that's not very creative.
So... what would be your idea on that? A real geek config for "multimedia keyboard"?

Re:Okay, an offtopic question.

[temojen]

An answer vaguely on topic...
You might also link one of these to multiple failed xlock passwords.
don't forget to make it run nohup.

#!/bin/bash

su <<EOF
(rootpassword)
wall "Ack! someone's breaking in the door!"
dd if=/dev/urandom of=/dev/hda

EOF

----------------
or, more realistically,

#!/bin/bash
# this script does not assume that it will run to completion
# so it tries to prioritize. It also has never been tested.
su <<EOF
(rootpassword)

wall "Physical Security Compromized!"

# Kill encryption keys.
killall -TERM\
/usr/bin/gpg-agent /usr/bin/ssh-agent /usr/local/bin/speakfreely\
/usr/bin/kgpg /usr/bin/ssh /usr/bin/sshd
umount -f -d (any cryptoloop filesystem)

# Dispose of accidentally saved data
# Comment out the first two lines if you don't use TmpFS
rm -rf /tmp/*
umount /tmp
swapoff /dev/hda2
dd if=/dev/urandom of=/dev/hda2

# Warning: if you don't use TmpFS for /tmp,
# you need to do something here to clean & scrub /tmp

# make sure we can start up cleanly.
mkswap /dev/hda2

# Shut it down

/sbin/shutdown -h now

EOF

Consider the Jihad

[Anonymous Coward]

Are you tired of slashdot's editors? Check out anti-slash!

While you're there, check out the database tool here. With the database tool, you can quickly gain karma by reposting highly-moderated slashdot posts, and secure the +1 bonus for future jihad operations.

By decreasing /.'s already low signal to noise ratio, you can force /.'s editors to come clean about their ethical lapses, and have a great time doing it!

Thank you for your support,

jihadi_31337

Reasons are various?!

[uradu]

He hates NAT and that's pretty much it. Oh, the software has also degenerated into spaghetti code over the years, but if he didn't hate NAT so much it almost sounds like he would rewrite it from scratch. Now please, everyone, could we kill off NAT so Johnny Walker starts speaking freely again?

Re:I WANT TO PUT MY PEE PEE IN YOUR POO POO HOLE

[Anonymous Coward]

You remain the most boring Slashdot troll ever. Even the ascii goatse guy has a better gimmick than you. EVEN THE IN SOVIET RUSSIA TROLL IS BETTER THAN YOU.

Wait a second..

[T9D]

I thought Ashcroft already eliminated the right to speak freely? Oh, nevermind, this is a dupe. Sorry.