|
|
| Author |
Message |
| 25 new of 63 responses total. |
remmers
|
|
response 12 of 63:
|
Jul 13 17:47 UTC 2007 |
If you look at the history, being "long time buddies of all the current
staff members" has never been a criterion for staff appointment here.
The problem is finding qualified volunteers. Occasionally there have
been calls for such, with little success. If you have some names to
suggest, I'm sure the board and staff will be all ears.
(And of course, a volunteer would have to be taught that the way to
disable an account is *not* to put an "x" in the password field. The
actual process is just about as simple, though...)
|
mcnally
|
|
response 13 of 63:
|
Jul 13 22:12 UTC 2007 |
"Long time buddies" isn't the right way to phrase it, but John is
right -- our staffing issues are seriously complicated by control
issues some of the senior staff have. When they had time in their
lives to respond quickly to whatever problems arose it didn't matter
whether they were willing to delegate authority or not. But now
they've moved on, but haven't let go, and it's causing problems for
the system.
I think the best thing that Grex could do about staff would be to
thank Steve and Marcus, warmly and sincerely, for years' worth of
unpaid work that they have selflessly contributed to the system,
and then to ask them to retire to advisory-only positions, making
room for a new generation.
One HUGE impediment to this is that hardware unreliability problems
have frequently necessitated intervention from staff who are physically
local to Ann Arbor. We need to change that somehow, either by arranging
a system which allows remote console access or through some other
mechanism (such as perhaps virtualizing Grex and giving admins the
ability to relaunch the whole system from a login on the host machine.)
|
unicorn
|
|
response 14 of 63:
|
Jul 13 22:22 UTC 2007 |
#12:
> The problem is finding qualified volunteers. Occasionally there have
> been calls for such, with little success. If you have some names to
> suggest, I'm sure the board and staff will be all ears.
I don't know what else is involved, but I'd be willing to volunteer if
it meant being able to stop things like the current ongoing abuse from
spin.
|
scholar
|
|
response 15 of 63:
|
Jul 13 23:14 UTC 2007 |
Who are you?
|
slynne
|
|
response 16 of 63:
|
Jul 13 23:25 UTC 2007 |
Thanks unicorn!
|
glenda
|
|
response 17 of 63:
|
Jul 14 00:47 UTC 2007 |
If you do a !finger on STeve, you will find our home number and while we
screen all calls, we do listen to the messages. I told STeve about this jerk
and he is looking into it.
|
slynne
|
|
response 18 of 63:
|
Jul 14 03:54 UTC 2007 |
Thanks glenda!
|
unicorn
|
|
response 19 of 63:
|
Jul 14 04:36 UTC 2007 |
Who am I? I'm not sure what kind of a response you're looking for.
I'm not some pseudonym of someone else you know on here or m-net, if
that's what you're wondering. The name you see at the top of all of
my posts is my real name. Although I've been registered here for
several years, until recently I've only popped into the bbs on rare
occasions, and rarely said much when I did.
I'm not local to Ann Arbor, but I am in Michigan (Mt. Morris, to be
exact, up by Flint). I used to do a lot of BBSing in the Flint area
when it was more popular. I'm no Unix guru or sysadmin or anything,
but I've been running Linux on all of my computers exclusively since
1994. I've been running Slackware from the beginning, which requires
a bit more knowledge than many of the Linux distros, and is much more
similar to the *BSDs than most of the Linux distros, too.
I also do a little programming (I'm the current maintainer of sc, the
text-based spreadsheet calculator for Unix/Linux) and scripting (mostly
shell, a little perl), so I'm not a complete dummy when it comes to
staff-type activities. Vim is my editor of choice, and zsh is my shell.
I've also used bash for years. What else do you want to know?
|
keesan
|
|
response 20 of 63:
|
Jul 14 07:27 UTC 2007 |
Can you autograph my copy of sc at the grex picnic? Wow, a local celebrity!
Sc is one of the things I included in the 61MB of Slackware that I am putting
together for people who don't know linux (the biggies are Opera and Abiword,
which I rarely use myself). I have not found a small simple enough database
program.
|
mary
|
|
response 21 of 63:
|
Jul 14 11:12 UTC 2007 |
Thanks, Chuck, for volunteering to help out.
|
slynne
|
|
response 22 of 63:
|
Jul 14 16:10 UTC 2007 |
Indeed. Thanks very much.
|
cmcgee
|
|
response 23 of 63:
|
Jul 15 01:27 UTC 2007 |
Joe Gelinas blocked the user 'spin' this morning. Since 3 o'clock
'pins' has spammed Agora 5 times.
I telephoned and left a message for STeve around 9 tonight, after
talking with Gelinas.
During the conversation with Gelinas, he brought up the fact that spin
had apparently come in from several different ISPs, and therefore we
could probably not block him that way.
Any new ideas, other than fix your twit filters?
|
krj
|
|
response 24 of 63:
|
Jul 15 03:06 UTC 2007 |
Develop the capability to add writing-to-conferences to the
list of privileges one needs approval for. Leave a switch on this so
it can be turned on/off as needed.
|
mcnally
|
|
response 25 of 63:
|
Jul 15 03:18 UTC 2007 |
I'd prefer to see fronttalk and backtalk modified so that the filtering
system works a little better. The problem that "spin" ("pins", etc.)
is exploiting is that even if you twit-filter their response, it's
still aggravating to go through the conference because the twit filtering
occurs after the fact -- i.e. after the conferencing software has decided
which items to show you as "newresponse" items.
If that's too much to bite off, then I suggest we try to work on an
alternative "fixseen" command that will mark as read any items where
the *only* new comments are from a person identified on your twit list.
Used in conjunction with existing twit filtering mechanisms such a
command would take most of the pain out of the "spin" vandalism,
at least for regular conference readers experienced enough to know
how to use twit filtering.
|
unicorn
|
|
response 26 of 63:
|
Jul 15 03:59 UTC 2007 |
How about if something was written into the system to detect if someone
is typing faster than is humanly possible, and reading/replying faster
than is humanly possible, and automatically logging them off the system?
|
mcnally
|
|
response 27 of 63:
|
Jul 15 04:08 UTC 2007 |
No.
For one thing, people might have good reasons for doing that
(I can think of one user (no longer active) who used to run a
script which went through agora and downloaded all newresponse
items, then read them off-line, composed responses, and logged
back in with the responses.)
For another, it doesn't really address the problem and is
simple for the vandal to circumvent. I can write an expect
script in 10 minutes to do what "spin" (etc) is doing, and
furthermore if I set a variable, expect will happily mimic
the typing speed of a real human for me. You could spend
hours or days writing such a countermeasure and it could
be circumvented in 10 minutes. And you might break other
(worthwhile) scripts in the process.
I think it's a flawed approach.
I like my approach (though I'm sure someone can come up with
a better idea) because it improves the functionality of the
conferencing system and gives users additional control over
blocking people they want to block. I would prefer some sort
of solution that left people the option of still reading
every single response in a conference, however worthless some
of those comments might be.
|
slynne
|
|
response 28 of 63:
|
Jul 15 05:23 UTC 2007 |
I am thinking about abandoning agora in favor of other conferences for
a week or so. I mean, I wonder how long they are likely to keep this
up. Alternately, I wonder if we could temporarily shut down newuser? I
suppose this person might just choose to wait us out though. It is
hard to say.
I dont like any of the above as a solution really. Like Mike, I would
prefer to see improvements in the filtering or fixseen or both. But
realistically, I dont see that happening in any sort of timely mannar.
|
cmcgee
|
|
response 29 of 63:
|
Jul 15 12:21 UTC 2007 |
ok, I'd like the board to call an emergency meeting, with two agenda
items:
1) appoint unicorn to staff
2) discuss appropriate strategies for keeping Grex from being totally
shut down by this twerp.
I'd be glad to host the meeting at my place, if necessary. Clearly
STeve doesn't have enough time to deal with this; Gelinas and cross are
out of action for the moment, and janc hasn't signed on recently enough
to recognize there is a problem.
Board needs to make a temporary decision about keeping people interested
in reading Agora.
One idea I have is from trapping stalkers with email. You leave the
email account funtional, and let everyone but the stalker know the new
address. We could leave Agora functional, but start a new summer agora
that we privately emailed people about. Then he could spam Agora all he
wanted.
It doesn't seem that he's actually reading anything, so we might be
under his radar.
|
cmcgee
|
|
response 30 of 63:
|
Jul 15 12:22 UTC 2007 |
The other thing I'd do is unlink any linked items, and relink them to
AgoraII
|
cmcgee
|
|
response 31 of 63:
|
Jul 15 13:27 UTC 2007 |
Also, we'd have to make sure Walter doesn't reset the automatic roll-over
mechanism when he opens the new cf.
|
nharmon
|
|
response 32 of 63:
|
Jul 15 13:34 UTC 2007 |
Folks, I'm willing to bet money this person is using TOR, and that every
single one of the hosts he is coming in from is a TOR exit.
http://tor.eff.org/faq-abuse.html.en
TOR was never intended to be a way for people to evade bans, etc. And as
a result, it provides a python script that will give a list of current
TOR exits. That would provide us adequate protection.
|
cmcgee
|
|
response 33 of 63:
|
Jul 15 13:40 UTC 2007 |
So all we have to do is get ONE staff member to spend a little time?
|
mary
|
|
response 34 of 63:
|
Jul 15 14:01 UTC 2007 |
There are lots of proxy servers out there. I suspect this is not as easy
as blocking a known list of IP addresses.
I like Mike's solution although the immediate response should be to close
newuser, temporarily.
|
slynne
|
|
response 35 of 63:
|
Jul 15 14:21 UTC 2007 |
re: shutting down newuser. Yeah and then we have to hope that this
user doesnt already have a bunch of accounts created. But that clearly
seems to be the thing to try. There are tons of proxy servers out
there and new ones get added all of the time.
Our staff situation is such that I am willing to take a risk with
unicorn, even though I dont know him well. He seems like a nice enough
fellow.
Another possible temporary solution would be to grant several trusted
people fw powers in agora so that they could delete any inappropriate
responses as they get entered. Would that prevent items from showing
up as new?
|
cmcgee
|
|
response 36 of 63:
|
Jul 15 15:42 UTC 2007 |
I'd prefer not to shut down newuser.
It would give this guy feedback that he had indeed gotten a strong
reaction from his harassing tactics. If we leave the current Agora open
for his attacks, and start a version II, he may never change his
tactics.
If we shut down newuser we've given him a lot of information and made
ourselves a more interesting target.
|