VWR-1735 might fix this.

Torley, thank you for looking in at this problem. I look foward to the revamped notifications. May I suggest the revamp moves all the "where from and who from" information to the END of the notice. it is very anoying when the object and/or avatar sending the notice has a long name. Especialy when the notification is a llDialog or some other dialog that accepts a text to display via LSL. Often this text scrolls off due to the "where from and who from" information.

Darling.

I've been lucky enough to have some more reputable Content Creators log in as Alt's to IM me and tell me to remove them from my Mute list... grrr...

When the user normally encounters a "MUTE" option, it is either in the circle menu, or in local chat, or on a person's profile, one of the following happens:

1. When you select an object, and right click, selecting "mute" will mute "the object". (though this has been buggy, this is the intended function). When you select a person and mute through the circle menu, it mutes the person.

2. When you select a "name" in the local chat window, it mutes the person. If you select an object (which has been speaking) it mutes that object.

3. When you select MUTE in a profile, it mutes the person.

Here's the problem.

When an "inventory offer" (or other blue dialog) is muted, it mutes the owner of the object, not the object. People are going around muting greeter bots, landmark givers, all the usual inventory noisemakers.. and in the process are populating their mute lists with shop owners, not objects.

If the giver is an object, this mute button should mute the giving object, not the owner

Can this one now be closed?

I just spend over 30-40 minutes trying to re-delivery a product to someone who had me muted by mistake.

It is a painfull problem to fix because you need to get other people to pass on messages to help the customer unmute the creator.

I suggest option 3 be implemented immediatly. It is an easy fix and will remove the pain and frustration involved in gettng someone to unmute you when you cant tell them they have you muted.

3) If you send an IM to someone you have on your mute list the mute should be removed automaticly, so they can reply to your IM. (This would solve 100% of product redelivery issues caused by accedental mute.)

With the 3rd option the customer still muted the original object delivery, however when they IM the creator to complain about not receiving the product the creator can immediatly give them one as the mute will have been automaticly lifted by them sending the IM.

Darling (frustrated shop owner) Brody

If you hit the mute button, you need to look up at the screen before you click.

However, making it a yes/no option would be a less destructive way to go at it.

Inventory offers from objects, produce "mute button dialogs"
Inventory offers from avatars producte "mute button dialogs"

Pressing mute in either case, mute the avatar involved.

When a notecard giver presents a "Accept, Decline, Mute" dialog.. it is counter-intuitive to have THAT MUTE BUTTON mute the owner of the store. That mute button SHOULD mute the object giving the notecard.

This, combined with the fact that the "Mute" button suggests something closer to "ignore" than "silence forever" in other languages, actually encourages people to press "mute" to "make these annoying blue dropdowns go away".

This Mute button was added as a kneejerk reaction to a greifing attack, and should be either retracted, or reconstructed in such a way that, at the very least, when a customer mutes a notecard offer, they mute the notecard giver, and not the owner of the store.

Linden Lab is now having to run the gauntlet to try and make it easier to UNMUTE people.. because this one button makes it far too easy to mute someone unintentionally.

Winter Ventura is right.

We have two differnt types of MUTE in SL. Mute the owner, and mute the object.
When you mute from the PIE menu you mute the avatar/object you clicked on.
When you mute from the dialog box you are muting the owner and not the object. <--- This is inconsistant behaviour as it is the object, not the owner who is offering inventory.

If this inconsistancy was removed it would at least let the creator reply to the customer's IM's about the "failed" product delivery. However it is still only half of the solution.

It is still important for an auto-unmute to be applied when you send an IM to someone so they can reply.
To avoid accedental unmuting someone we could have a warning message in the IM window saying "<name> has been removed from your mute list so they can reply" when you sent an IM to someone on your mute list.

The auto-unmute should also be applied to the TOUCH events as customers often touch again after they accedently muted the original notecard they were given on the first touch.

The same goes for the PAY event with customers paying a second time because they think the first one failed when it was really muted by mistake.

I am sure some people who are carefull about which buttons they press or not involved in SL commerce may say they see no value in these changes. Those of us who are abused daily by people who accedently muted us while shopping in our store do not consider it trivial. I am sure the customers who spend weeks trying to get the products they paid for do not consider it trivial either.

The typical accedental muting goes like this:-

Customer pays for item
Customer mutes instead of accepting object.
Customer sends IM to creator complaining they didnt get their product.
Creator logs into SL. (Often days later)
Creator sends a reply asking them for the transaction details. (If the IM gets thought)
Customer logs into SL. (Often days later)
Customer sends another frustrated IM demanding to be given what they paid for.
Creator logs into SL. (Often days later)
Creator sends a reply asking them for the transaction details a second time in case their first IM didnt get through.
Customer logs into SL. (Often days later)
Customer starts to abuse the creator calling them a theif and threatoning to file abuse reports. Often they do file abuse reports!

At some point either the customer or (more often) the creator relizes there may be a "mute" problem and involves a 3rd party to relay messages.
Depending on the language skills, and the computer literacy of the customer and the 3rd party helping, the un-mute process is often dificult.

All of this can take days or weeks depending on how often the Customer and Creator login, and on how fast their offline IM's are capped.

LL make a lot of money from the commerce in SL, so it is in their interest to make sure it runs smoothly.

--------------------------------------------------------------
Personal note:

• I remind people that the JIRA is a place that ONE person has the right to suggests a change / fix for SL.
• Other people can vote in agreement, or they can leave a message to help refine the suggestion.
• Comments apposing the suggestion should be limited to technical or logical reasons why the suggestion can not or should not be implemented.

• • Personal vendettas have no place in the JIRA and will result in an AR being filed each and every time.

Check out what Whispering Hush has been up to :-

http://jira.secondlife.com/browse/SVC-1462
http://jira.secondlife.com/browse/VWR-4185
http://jira.secondlife.com/browse/SVC-2114
http://jira.secondlife.com/browse/SVC-2336
http://jira.secondlife.com/browse/SVC-2336
http://jira.secondlife.com/browse/SVC-1533

This is another example of Product Griefing, and why unverified accounts that do not own land should not be in the JIRA at all.

–
Darling Brody

[10:20] Curmie Burner: (Saved Fri Jan 09 00:27:21 2009) do not see the boat yet
[10:22] 7Seas Sass: Hrm, that's odd. I'll ask her server to send again. If it doesn't work this time either, I bet you may have Jen Shikami or her item server accidentally muted.
[10:23] Curmie Burner: I am searching for Dragonfly boat - could I be missing it ?
[10:24] Curmie Burner: I am sorry to be sucha pain
[10:25] 7Seas Sass: You didn't get the dialog box even offering it, correct? (I already sent the command, at 10:20)
[10:25] Curmie Burner: yes - no box
[10:27] 7Seas Sass: OK, well just in case, let's check your mute list again... here's how. (it's easy to mute accidentally, it's an SL usability bug). To check that, click the up-arrow next to your Communicate button (which is on the lower left) and go to the mute list. Check for these names and if they're there, remove them: Jen Shikami (it's probably her), Meissa Thorne, Seven Shikami, 7Seas Master Server, Jen's 7Seas Item Server, Meissa's 7Seas Item Server.
[10:28] Curmie Burner: I just got a master server Seven Shikami data base blue print
[10:29] 7Seas Sass: Yeah, that isn't really relevant because he's a different person.
[10:29] Curmie Burner: oops
[10:30] Curmie Burner: you are right he was on my mute list
[10:30] Curmie Burner: I unmutes
[10:30] Curmie Burner: unmuted
[10:30] Curmie Burner: I din'd even know how to mute

Now we just need to stop them from doing it by mistake!

Priority raised to Critical, because I have never met someone who paid $2500 to me who didnt think delivery of the product was critical!

Darling Brody

http://jira.secondlife.com/browse/VWR-1735

That does help, but only when they are IMing the creator directly, and it still doesn't help after the fact; we still get irate customers IMing "why are you ignoring me?!" and leaving bad feedback on all our XSL items, et cetera. The IM unmutes the creator, but by then it's a bit late, eh?

Doing it by mistake or in circumstances where they're not interacting is still an issue, definitely. I consider this a major usability issue, since most people don't seem to even realize they've done it. The momentary appearance of the mute list doesn't seem to even register its significance, nor does the "you decline X from John Doe" note that they see in chat.

In addition, I often suspect (and tell my customers) that lag may make a difference here – perhaps that's what caused the wrong button-click to register. Who knows?

Our business delivers around 100,000 items in SL every day. That's 100,000 chances for people to click wrong or get affected by lag or whatever it is, and accidentally mute. I guess I should be glad people don't do it (or notice they did it) even more often...

Regardless, they need a better confirmation that explains itself thoroughly. Something like
"Are you sure you want to mute John Doe? If you do, you will not be able to hear them or receive any objects from them again."

Here's another example from many recent similar incidents...

[2009/01/13 4:42] DeathFate Burnfield: (Saved Tue Jan 13 07:38:44 2009) hello this is a list of fish that i caught but dident recieve...
(Editor's note: list removed)
[2009/01/13 4:43] 7Seas Sass: I'll replace them for you. But you know, it's interesting that they're all made by the same creator. I wonder if this is an unintentional mute issue.
(Editor's note: I proceed to explain how and why that can happen, how to check, etc.)
[2009/01/13 4:45] DeathFate Burnfield: i am now looking to see if i did mute any one by mistake
[2009/01/13 4:46] 7Seas Sass: See, what happens is, in that blue box SL gives you every time you're offered a fish, there's three buttons... Keep, Discard, Mute.... It's a very common problem.
[2009/01/13 4:49] DeathFate Burnfield: tyvm i found out that i did some how mute Meissa Thorne by mistake ty for the help
[2009/01/13 4:49] 7Seas Sass: Ahah! Yeah, that would do it. Thank you for checking!