Right Click to Blacklist Sooner Rather than Later

[CielWulfe]

Look, the RMT issue is still out of hand. SE is trying, but the problem is every time they put one counter-measure into effect, the RMTs find another way to annoy and still spew their ads all over the screen, be it by /shout, /yell, or /tell. For me, usually, I see them by /tell and my blacklist has grown considerably just on the additions of RMT names.

Not every RMT ad gets reported by me, because the current process to report them takes too many steps and too much time, and there's enough RMT bots for it to become extremely tedious. Usually by the time I would get around to reporting them, chances are the same bots have been reported numerous times by other players anyway. And yet, somehow, despite several mass bannings by SE, I have seen very few of the names on my blacklist disappear or come up as (Deleted).

By names, too, I'm not just talking about variations on legitimate attempts at character names, but the random gobbledygook names which look more like a toddler sat on their dad's lap and bashed at the keyboard for a few seconds. For example: Gsgdsf Fgdsgdsfg is the name of an RMT bot which sent me a /tell this morning and promptly got added to my blacklist.

SE has said they're looking to implement the Right Click to Blacklist in 2.1 at least, but that's still well over a month away. This needs to happen now, not later. This should have happened already.

Also making it a Right Click to Report wouldn't hurt either. That way, it could Blacklist and also shoot a report to SE right away with the contents of the offending /tell, /shout, etc, so they can see how the RMT messages and names are changing to work around their hotfixes in much less time than it does with the current reporting process.

It all boils down to the old addage "work smarter, not harder". Right now we're all having to do too much work to help SE curtail a problem they should already have well in hand. If they can do an emergency maintenance to fix a market security breach within a matter of hours of it happening, then they can fix this before 2.1.

[yukikaze_yanagi]

should should should...well, not. They said there are technical reasons because they can't release it alone, and that's is enough.

[CielWulfe]

should should should...well, not. They said there are technical reasons because they can't release it alone, and that's is enough.

Evidently it's not "enough". If fewer people had been effected by the market breach, and if fewer had rattled SE's cage over it, you can bet they would have been slower to act. SE CAN fix this issue. There's no reason they can't build this in on a maintenance patch. If they can't, then they need better codemonkeys.

At the very least, let us set permissions on who can send us /tells. I would rather authorize people to send me /tells than get random garbage out of the blue from someone who isn't even really there.

[Tupsi]

Evidently it's not "enough". If fewer people had been effected by the market breach, and if fewer had rattled SE's cage over it, you can bet they would have been slower to act.

Uh...a few hundred (200?) is significantly small and they acted.

[kasei]

They said there are technical reasons because they can't release it alone, and that's is enough.

I'd say it's more "won't" rather than "can't". The only reason I can see holding this up is not wanting to release small patches for the PS3.

Any other reason would be pathetic. If they can't push out a single feature in a patch, then I'd hate to see the codebase they're working with.

[Naunet]

I'd say it's more "won't" rather than "can't". The only reason I can see holding this up is not wanting to release small patches for the PS3.

I'm not really familiar with PS3 stuff, so why would this be a legitimate reason? o.0

It really does seem like SE is sitting on an awful lot of simple stuff and pushing it off for two, three, or six months down the road...

[kasei]

I'm not really familiar with PS3 stuff, so why would this be a legitimate reason? o.0

It needs to go through Sony. It's much less time consuming and more cost effective to package a bunch of updates together and then send it to the PS3.

A quote on the subject.

Those systems as great as they are, they’re still closed. You have to jump through a lot of hoops, even for important stuff like patching and supporting your game. Those are things we really want to do, but we can’t do it on these systems. I mean, it costs $40,000 to put up a patch [...]

[Source Interview]

Assuming SE worked out some kind of deal with Sony, I can't imagine it being as efficient as using their existing infrastructure.

[Tubben]

It needs to go through Sony. It's much less time consuming and more cost effective to package a bunch of updates together and then send it to the PS3.

A quote on the subject.



[Source Interview]

Assuming SE worked out some kind of deal with Sony, I can't imagine it being as efficient as using their existing infrastructure.

Then they should patch the pc version fast and do their ps3 patches in batches. I dont really care. But the tell spam get's out of hand. I started to play /busy to not get annoyed by tells.

[Terius]

SE can't be bothered to do much it seems, always use 'technical reasons' as an excuse not to do something.

[Vittorino]

I just make a macro to blacklist people. Anyhow's what i'd like to see or a new edit-search info command rather than busy "only letting friends pm you" instead of the busy command. I'd like to have a damn collect call service; "would you like to accept this pm from (dklaskdn aslsdm?) This damn GoldCE=Om whatever that fruit is doing is entirely aggravating. I can't even keep my d@mn listing "online" anymore. Do something please! :>