Resonant Information - Announcement - Comments

Logging in

Zed — Sun, 31 Dec 2006 14:38:48 -0500

... to the web interface isn't (currently) the same as logging into the server directly. You originally set up a web account as "japplegate", and if your e-mail address is still good, you should be able to retrieve your password if necessary.

(Sorry for the long response time -- I'm currently travelling.)

D'OH!

Anonymous — Fri, 22 Dec 2006 23:18:59 -0500

I just realized that in my previous post, I failed to identify myself. Sorry about that. It's Jared.

Yay!

Anonymous — Fri, 22 Dec 2006 23:15:37 -0500

I'm glad to see you made it okay. Of course, last I heard (about a year ago) you were moving up there in March or April.

Now that it's been a couple months, have you settled in okay? Did Lynne make the move with you? How are you two doing, anyway?

I'd call you this weekend, but I no longer have your contact info. Is it safe to assume you still have mine?

I'll talk to you later, old friend. Congratulations on the (relatively) successful relocation.

Take care!

- J

BTW - do I need to re-create my account on Resonant.org? I thought I'd logged in, but apparently I'm still posting as anonymous.

Venting vengefully

Lynne — Sat, 09 Jul 2005 13:22:41 -0400

... and alliteratively as well, it seems.

It's not really a policy

Zed — Sat, 09 Jul 2005 03:39:51 -0400

As far as I know, it actually only happened once, and I think there were additional considerations, such as the spammer using government equipment to do it. I unfortunately can't find a reference to the event on the net. And no, a substantial amount of spam still comes out of China. But I can still vent vengefully.

Spammer executions

Lynne — Fri, 08 Jul 2005 21:45:00 -0400

How long have they been doing that?

(And did it work?)

Or maybe not port blocking, but fixed now

Zed — Wed, 16 Mar 2005 11:18:28 -0500

Cox denies having done this deliberately, and whatever it was seems to have cleared up. I guess I can blame a freak router misbehaviour somewhere upstream of me.

Leak

Zed — Sat, 05 Mar 2005 20:18:28 -0500

The leak is either in Apache, one of Apache's modules, in PHP4, or in one of the PHP4 modules. I've arranged for Apache to restart itself automatically every hour, which should keep the damage contained, but I still don't know exactly where the problem lies.