Wouter Verhelst has posted a retaliation idea on his site:
start adding their "private" email addresses to some database and, rather than throwing away mails which are so obviously spam, start forwarding them to random addresses from that poolI think it would need doing very carefully, so that you don't put too much cost on your ISP - ultimately, you pay for your ISP's costs - or get yourself booted for sending tons of spam. If you do it, check your AUP, watch your network stats and good luck!
From: foo@bar.baz To: wouter@grep.be Subject: PLEASE HELP Date: some_date_in_the_future Hi, My name is <the name of a relative of someone rich who died>. I have <some problem involving an amount of money that I cannot get at>. Could you please <do something which will cost you a lot of money>? Thanks. PS: please, reply on my private email address <scammer@scam.com>.The important phrase is the last one: if you could please be so kind as to reply to their "private" email address. Obviously that email address is a throwaway one; but one would expect that they must read it and hope someone replies to it before the amount of spam on that address gets too high to reasonably be able to read it. Which is the catch. I wonder how those spammers would react if I would start adding their "private" email addresses to some database and, rather than throwing away mails which are so obviously spam, start forwarding them to random addresses from that pool...
scheme48 -cl packages.scm -o mystructurewhich is equivalent to typing:
,config ,load packages.scm ,open mystructureat the Scheme48 prompt.
.
Of course, I didn’t in fact start from scratch, but had a look at the various logging libraries available; the Scheme ones being:
.'(conjure cc) is a child of the logger named '(conjure).
This may all sound overly complicated, but getting started is very straightforward:
;; ,open spells.logging
(define log-info (make-log ‘(test) ‘info))
(configure-logger ‘())
(log-info “hello world!”)
make-log creates a logging procedure. Logging procedures take a single argument to be logged; the argument may be an arbitrary object; it is up to the handlers on how to go about formatting this object. The argument passed to the logging procedure is wrapped in a log entry, which additionally contains the log level.
The name of the logger that is to be used is '(test), and 'info is the log level. If the logger '(test) doesn’t already exist, it is created on the fly with no handlers and the root logger as a parent; it can be configured later. This separation of logger creation and configuration is important: In a real application, the logging can be configured from the command line or a configuration file; you don’t want to (hard-)code it into the same module that uses the logger.
(configure-logger '()) configures the root logger (which has the empty list as name) with a default configuration. configure-logger also has an optional argument in which you can provide a custom configuration, but I won’t go into this now, since this part of interface is most likely to change. The default configuration amounts to logging everything on (current-output-port).
Finally, we log a simple string through the logging procedure log-info. The output looks like this:
(test: [info] hello world!)
"Es un salto adelante, que no renunciamos a completar en a os futuros"Lamentable.
Your Inner European is Dutch! |
 Open minded and tolerant. You're up for just about anything. |
![[info]](http://stat.livejournal.com/img/userinfo.gif){kind=small}
ndusart is coming for the weekend! Haven't seen her in two months, so I'm understandably, ridiculously excited. Better lend mricon my earplugs.
|
Your Social Dysfunction: Paranoid You show pervasive and unwarranted suspiciousness, and mistrust of others. You are overly sensitive and prone to jealousy. |
||||
|
||||
|
Take this quiz at QuizGalaxy.com
Please note that we aren't, nor do we claim to be, psychologists. This quiz is for fun and entertainment only. Try not to freak out about your results.
|
sfllaw hasn't blogged about it, we're having a little get together on Saturday at Hurley's at 5:00. In the spirit of "the more, the merrier" (hope that's ok with you Simon), if you're a wannabe Debian developer come buy us drinks. I promise to sign the key of anyone who buys me a pint (how's that for a web-of-trust?).
mricon won't have to look for a new roommate come August.
mricon, seems to have a nice blog, so my competitive spirit has been awakened. I'm hoping this won't be the first and last post.
lsusb output for Google to parse, other people might be searching for this info:
Bus 003 Device 003: ID 0c45:602a Microdia Meade ETX-105EC Camera
| Your Inner European is Irish! |
Sprited and boisterous!You drink everyone under the table. |
# find "foo" followed by whitespace and "bar", even across lines $ vim $SOMETHING 'g/foo\_s*bar/' # words ending in "bar" $ vim $SOMETHING 'g/bar\>/' # words starting with "foo" $ vim $SOMETHING 'g/\<foo/'... and more. What does $SOMETHING have to be set to? Update: Neil Moore suggests the following shell function:
vgrep () local S="$1"; shift vim -es +"argdo g/$S" +':q!' "$@"This works. I shall be posting any improvements I make over the next couple of weeks in another blog post. If there are any. But I suppose options like -i and -v might be good to have.
Next.