Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
User Journal

Journal Journal: Best slashdot comment ever encountered 1

Best slashdot comment, ever:

Russia's Biggest Spammer Brutally Murdered

Posted by timothy on Monday July 25, @11:48AM
from the but-what's-the-motive-detective-columbo? dept.
Karellen !-P writes "Vardan Kushnir, a notorious russian spammer who headed the English learning centers, the Center for American English, the New York English Centre and the Centre for Spoken English, was found dead in his Moscow apartment on Sunday, Interfax reported Monday. He died after suffering repeated blows to the head."
----------------------------------------
Should have opted out. (Score:5, Funny)
by Tackhead (54550) on Monday July 25, @11:54AM
(#13157866)
> He died after suffering repeated blows to the head.
From a hidden microphone at the scene of the murder:

"You are receiving *WHAM* this blow to the head *WHAM* because you are part of a *WHAM* specially-selected list of *WHAM* people who agreed to receive *WHAM* blows to the head *WHAM*.

To stop *WHAM* receiving these *WHAM* blows to the head, please *WHAM* email us at no-more-please@optout.blowtothehead. com and *WHAM* we will remove you from our list of *WHAM* blow-to-the-head-club members *WHAM* (heh, we said "club"!) *WHAM* within 24 to 48 hours.

Businesses

Journal Journal: Workplace absuridities as phone support for a DSL ISP. 16

This journal entry isn't about customers that call in, despite the numerous ijits out there that deserve to be mocked.

No, it's about the company I work for, specifically the bosses.

Yesterday, I recieved an email saying that "Firefox is on the list of banned software, and there will be disciplinary repercussions if anyone is caught using it."

Nevermind that all our webapps suck ass, or that I've spent time on and off the clock for the past 3 months, in between calls, trying to make it work with them. Bless you, greasemonkey.

Don't even consider, that on average, my calltimes have to be at least 1 minute shorter because of firefox. I have a single window open, not 20 IE windows. I've not only fixed the webapps, but extended them... when I pull up your phone number, I see all the information that I'd spend the next few minutes (and in a few select cases, the next 15-20 minutes) looking for in a mix of shared drive documents, webapps, and even printed out documents. That one CO location with the abbreviation that doesn't match its name, and since everyone on night shift has only been there 2 months, they can never figure out which... our main webapp now sports a button that I click, to log into it. 15 minutes reduced to 3 seconds.

If you've wandered through our phone menu and gotten lost, I can see immediately if you have our dialup or dsl, or if you're just a telephone only customer... I don't waste the next 60 seconds figuring this out before I transfer you.

So, why would this be a problem? Well, apparently, I let the wrong person test an older version of the greasemonkey script that even makes the webapp work at all. And it opened a ticket, but didn't save the comments. Now mind you, you only have to re-edit the ticket, add them again (and the guy should have noticed, it doesn't whisk you away to another page, it shows the saved ticket there after saving it). Also, consider this: we screw up alot of tickets. On average, a dozen a day, I'd think. Someone using IE forgets to put his comments/notes in, or schedules the wrong person to work on it, or doesn't send it back to the company that wholesales the phone lines when its their problem.

We screw up hundreds of tickets every year. The first one ever screwed up by firefox, because I didn't quite fix the webapp perfectly on one of the earlier beta greasemonkey scripts, and firefox simply can't be tolerated.

So, I go and ask my boss (think her title is Director, never spoken to her before) if she could spare a few minutes to talk to me.

I'm polite, I don't start screaming, or spouting ideological rhetoric. I simply state that this would be a hardship, and would impact my productivity. I explain how the enhancements I've made improve my calltimes, how I've got literally dozens upon dozens of saved passwords in firefox (that IE doesn't save), that I'd spend the next couple of months having helpdesk change for me, or that I'd have to look up in documents no one can find.

What do I get? Do I get anything like the minimal respect that a 30 yr old man is entitled to? That a human being is entitled to? How about because I'm a worker making shit wages who took it upon himself to actually try and improve things there, even just a little? No. I'm treated like a child in grade school. This from a woman that can't be 5 years older than I.

"Now I hate to do anything that would decrease your productivity, but I can't very well let you use it and prohibit it for everyone else."

This is ridiculous. She can say that. She's not giving out candy to kindergarteners, she is saying which workers can use which tools. At construction sites, do you have one guy whining that he wants to use the crane today, that Jimbob got to use it yesterday? Fucking ludicrous.

Side note: She thinks that "E" is the name of the web browser we are supposed to be using, because of the icon...

Finally, I somehow manage to pour more on, without whining (imo). She relents, and I won't be written up as long as "there's not another single incident of it creating a bad ticket".

So, I investigate a little further, after our talk. Seems it was just as I describe, it didn't save the comments (if indeed, he simply didn't forget to type them in). It didn't create some invalid ticket that fucked up the database, and it was caught that very same day.

There are several problems here:

1) A director managing a technical department that knows so litte, she can't name the web browser she uses.

2) The applications department isn't giving us the tools we need to do our job.

3) Making your own tools isn't praised as resourcefulness, it's punished for a single instance of a flaw that is so trivial that the triviality can not be over-emphasized.

4) This proclamation/rule/policy implies that my calltimes aren't important, and the corollary that our abandonment rate is not important either. That has a corollary too, which is that helping our customers isn't important... if they hang up before I can talk to them, then I'm not helping them.

5) It suggests that the managerial groupthink tends towards something I would describe as "militaristic", that is, it is more important I do what I'm told, rather than I've given a problem and left to my own devices to solve that problem.

6) It never ocurred to her that if it can reduce my calltimes, with as much experience as I have (seniority in just 6 months, kind ridiculous eh?), then it might also improve calltimes all-around, especially for the new guys. Not only would I not have to put a customer on hold every 30 seconds to answer them when they ask which CO an abbreviation is (they'd just click that button), they wouldn't have to put a customer on hold to ask me.

7) They're (by this, I mean the director and 2 supervisors) concerned with calltimes and abandonment rates, but only have managerial talents at their disposal to solve those problems. Not only do they not have the technical talent to solve these problems, they can't even recognize technical solutions when they see them.

I don't work here by choice, I'm paying down 5 figure credit card bills from when I was unemployed. Last payment is this month, after which my girlfriend and I will be debt free. My other job pays better, is telecommuting, and I can work in my underwear if I so wish. I don't know if I will continue to work the second job (would be nice to actually put away some savings for once), but the real question is, how can I?

Next time you're on hold for an hour because your DSL is down for the third time in a month, remember that your ISP chases away workers like myself.

Slashdot.org

Journal Journal: Day Three: Apathy 1

Well, I wonder if temporary bans last this long, or if my sarcastic email managed to get me an editor pimpslap.

Strangely, I don't miss it as much as I would have thought.

Slashdot.org

Journal Journal: Day Two: Bannination.

Well, it's been well over 24 hours. May have to wait til I get my DSL before I can comment again. So all you losers that think you won our arguments... wrong, you've been protected from my stinging sarcasm and subtle wit by none other than the editors. They can't protect you forever. One day, you'll say something stupid on fark, or k5, and my vitriolic rebuttals will tear your wimpering souls to shreds. That, or you'll just ignore logic and continue blabbering on.

On DSL: It sucks. I work for the DSL company. I'm figuring that it will be down 5 days a month. About on par with my cable modem. That said, I plan on keeping both of them, and praying to the Gods of Networking that the 5 day periods never overlap. Yet another reason why a consumer broadband router is a poor substitute for a linux machine with quad port nics...

Slashdot.org

Journal Journal: After getting a few flamebait mods.. 1

I recieved the:

Due to excessive bad posting from this IP or Subnet, comment posting has temporarily been disabled. If it's you, consider this a chance to sit in the timeout corner . If it's someone else, this is a chance to hunt them down. If you think this is unfair, please email moderation@slashdot.org

So I decided to email them. Here is the gist of it.

Robert Rozeboom wrote:

> So, I'm lumped in with all the GNAA trolls?: No you'll get the ability to post again after a timeout period. You were banned because you have been downmodded too many times.

I apologize, obviously something I wrote mistakenly led you to believe I was a retard. I respectfully submit that I am indeed of normal intelligence and that I suffer from no chromosomal abnormalities or other birth defects that cause me below average intelligence.

As you may be aware, your warning message doesn't say "if you believe this to be in error", which if it did, I would think it might mean "if you believe a random slashcode math error caused this". It says "if you think this is unfair". My previous email should indicate that yes, I think it is unfair, even though I don't necessarily believe it to be in error.

That being the case, I am slightly confused that you would reply with an email that says in effect, "there is no error, you've been downmodded". I understand that the moderation system is a very tricky thing, and that you have little control over it even when gibbering idiots somehow get mod points and go running amok like chimps randomly clicking buttons. Perhaps you should change the wording, so that you no longer use the word "unfair" and instead use something like "in error" or maybe "by misktake". That way, people like me will be able to see that you and the other powers that be at slashdot don't care about fairness, or that you have no control over it.

Or you could just ignore me, and allow nature to take its course. Here in a year or two, when no attitude/sarcasm/strong opinions are left and the great slashdot groupthink experiment is complete, will it matter as long as advertising revenue is strong?

Respectfully,
John

Slashdot.org

Journal Journal: Slashdot needs some fixes

Slashdot is fun and useful and all, but there are some pretty annoying problems with the site. They constantly come up in an "off topic" manner, and consequently get (sort-of) appropriately modded down - this journal submission is intended to give them a legitimate home. I submitted it as a story, but - of course - it was rejected.

These are the things that seem most obvious to me, but I am sure there are others, given how annoying the issues I have in mind are to me. Please feel free to add your thoughts to all this, shoot my ideas down, whatever.

Moderation is anonymous

I say this is a Very Bad Thing. You can compare this to Kuro5hin, where you can easily see who did what to whom. Moderation with accountability allows anyone to see when a vendetta is being pursued, or when someone is systematically modding a subject down because they disagree, rather than because the issue is actually off-topic, a flame and so forth. I cannot begin to count the number of comments I have seen that have been modded down because they were contraversial, as opposed to offtopic, flamebait, or whatever else the down-mod claimed they were. The site's editors are also anonymous and that provides a hidden power structure which isn't a particularly good thing in any venue. I have read multiple claims that this poster or that poster cannot get mod points "because they modded something [a slashdot luminary] posted some time ago." If this is an illusion, exposing who did what to whom will in turn expose the illusion. If it is not an illusion, then exposing what happened should reduce the problem, because such action would rightfully be condemned by readers if it is inappropriate. I find the idea that the site's editors might be sneaking around and quietly muzzling moderators in a punitive manner more than a little disturbing.

So my first suggestion here is simply to lose moderation anonymity. My second is that if and when mod capability is removed from a user, the date of, and reason for, that action be posted right in their user page.

Many - perhaps even most - down mods are punitive or inappropriate

I suggest that the meta-moderation process be adjusted to include the ability to flag down-mods as obviously inappropriate, and to remove moderation privileges from those who commit such down-mods, as well as the down-mods themselves.

Up-mods don't need metamoderation

I suggest the outright removal of metamoderation of up-mods; if someone considers something interesting (or whatever) positive characteristic, who are we to say that this isn't so? That's the moderator's take on the comment, and up-moderation is a (very limited) opportunity for a moderator to "uplift" the story to the rest of us based on that perception. Upmods aren't harmful the way down-mods are - quite the contrary - and it seems to me to be a complete waste of time to metamoderate upmods for that very reason.

With mod points so scarce (and I agree they should be) we are forced to pick the things we really appreciate to up-mod. I rarely see an honest need to down-mod (obvious "first post" and gay/nigger trolls excepted), but I simply do not see a need to counter an up-mod. Someone thinks this, that or the other thing is insightful or interesting or sexy or whatever? Ok, that's at least notable - and that is exactly what an up-moderated and hence higher point comment does, it becomes more notable - not more interesting, not more insightful, but more notable. It might not actually seem that the applied moderation is accurate to us on reading the modded comment, but it is interesting that so-and-so (or at least "someone", if moderator anonymity remains preserved) thought it was worthy of a mod point. Comments can argue the issue if a poster is so motivated, and that seems like plenty of recourse to me. We see this all the time anyway; why not simply make it the official means of argument with an upmod?

Metamoderation is a scarce resource - put it where it does the most good

The removal of up-mod metamoderation could allow multiple meta-moderation of down-mods so that a reasonable, multi-user consensus that a down-mod is innapropriate can be reached. It seems to me that it should not be a light thing to say that someone is abusing the moderation system; you want to be reasonably certain. A meta objection to a down mod should cause that down-mod to immediately rear its ugly little head in a bunch of other meta-moderation queues so that consensus can be reached - and then corrective action taken if the mod is widely deemed inappropriate. This last point is important: It is a real shame that reasonable posts are permanently lost to the default view because some moderator was being a twit.

Fix the comment point system

There are several things wrong with this area of the site. The first is simply exposure, like authorship of moderation. Anyone who looks at the summary of points in a profile and tries to figure out what happened to a heavily moderated comment in a story is doomed to failure. It's Byzantine at best, and opaque and threatening at worst. Expose it.

Next, The math behind up/down mods is bizarre, to say the least. At a minimum, fix it so it is linear; or if not, then at least expose each and every mod point and show what it did to the story (along with the inflicting member - again, see Kuro5hin for a nice example of how this should be done.) Of course, if only this is done, an outcry will probably arise to fix the math, for the obvious reasons. :)

Expand the moderation choices

I have also seen lots of very good suggestions for additional moderation reasons. I'd like to see the readership discuss that here and perhaps a poll be subsequently created to see which new moderations should actually be added.

Story submission is entirely in italics

How is one expected to visually check the HTML of a story if the story preview enforces italics for the entire body? Why not use dark blue on white, and let italics flow according to the story tags so we can actually see what we're writing? You know, that radical new concept, "WYSIWYG"?

Sign the Polls

Stories are signed so we know who to thank (or blame) for the story. Sign the polls too. As I write this, there is a poll up for "favorite writing instrument" and the poll fails to include "keyboard" as an option. Somebody should have some digital egg on their face for that one. Maybe accountability will result in better quality polls. One can hope, anyway!

Linux

Journal Journal: Lwared lives! 1

Well, it turns out that Lwared hasn't worked since the early 2.0 kernels, ouch. Just got permission from the original authors to continue development, and will be releasing lwared-0.95-jo1 soon. Builds without a warning now, but still some issues with functionality... it's unable to recognize an interface's IPX addr. I have no explanation, as well as I can read the C code, it's not even trying, maybe I got ahold of a broken beta? Will have to check some of the pre 0.95 code to be sure.

Beginning to do prelimnary research on a VIP protocol stack for linux. (Banyan VINES, for those wondering). It won't be easy, I'm not that great of a programmer. Looks like I'm on my own though, no one else would even be interested.

Some friends and I are finally launching spalp.org. Society for the preservation of assembly language programming. Text book quality tutorials on asm for just about any cpu you can name, is our goal. At the moment, we have an intro to asm, and several 65xx chapters. Look forward to books on the z80, pic microcontroller, and motorola 68k before the end of the year. Contact us if you can help!

User Journal

Journal Journal: Unemployment still sucks.

Managed to hack the ipx utils and lwared enough to compile on 2.4.x. Mostly just incorrect includes, they must have switched alot around from 2.2 to 2.4. So I get the daemons to compile, and no segfaulting even... and still can't get the damn things to run right. When finished though, my home uberserver will be able to broadcast reboot messages via samba, netware's nsend, appletalk broadcast, and even pitou's onscreen messaging feature. Gotta get around to installing SNA on the thing too, but decnet didn't work very well, and I really want to get that working first.

Still need to work on PAMizing slackware, and getting my uberdirectory built... local accounts suck ass when you have close to 50 active boxen.

Of course, when I am employed, with the jobs I usually have, I'm given no credit whatsoever. Maybe I don't deserve any.

User Journal

Journal Journal: Journal entry, Febuary 4, 2002

Discovered there is such a thing as a journal. Wow. Got mis-moderated by a troupe of chimpanzees masquerading as slashdot readers. Some idiot accused me of cutting and pasting a list of OS's I claimed to use. Haha. The list would have been twice as big, had I been able to remember them all. Must find work, unemployment about to run out. Very uncool.

Slashdot Top Deals

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Working...