So People are getting silenced for using Rare Share Addons

That would only be true if the person using it is the person who authored it. In nearly every case, that isn’t so. The responsibility lies with the person who coded it. The fact that I download a given addon does not represent the fact that I control what it does.

Indeed. This is why we can’t have nice things.

Oh wait YOU are calling someone else a troll? With a post like

and

You are actually calling other people a troll? Incredible.

As far as what I am going on about is how he was saying other people are trolling, but kept liking your actual troll posts.

What? No it’s not. The responsibility is on the person who is using it.

The fact that you downloaded and installed an addon means you are responsible. Remember the people getting banned for using addons that changed cosmetics? Yeah, that wasn’t the creator that got banned - that was the user.

2 Likes

I’m sorry, I haven’t clicked like on any of your posts here. Nice try though.

So far, just you - because that’s what you’re doing.

Wikipedia, like any other wiki, can be made to say whatever one wants it to. That’s not proof of anything. Plus, I’m not correct.

Go enroll in a college course, write a paper on an assigned topic and cite Wikipedia as your source. Turn that paper into your professor and watch what happens.

That’s different. That addon changes things between you and the server. The addon here actually sends messages on your behalf. In this case it would fall with the author, because the user isn’t telling it to send those messages. It’s an automated process.

1 Like

But your link literally says that there is no such thing as an industry accepted definition of spam.

Are you dense?

3 Likes

Wrong again. Downloading apps becomes the responsibility of the user.

I created an app that said something profane in /yell command and you downloaded it knowing what it did. You’re responsible, not me. Yeah, my app will probably get banned from curse gaming’s website, but it’s your account that’s getting silenced for using those apps.

Where do you think the author is responsible for the app spamming and not the user?

1 Like

What a strange thing to take exception to. This thread shows that people view spam in different manners, why wouldn’t games also do so.

1 Like

… he literally sourced a Wikipedia page, saying that it gave the absolute definiton of spam.

The page he linked said that there is no absolute definition of spam.

Where is the part you’re not understanding?

This thread has gone so very far afield from any kind of point.

5 Likes

Because the user cannot know in advance what it does, or how it does it within certain operating environments. Suppose the addon was to say something profane in /yell whenever a specific action is performed, or when a certain command is typed. Okay, that’s what it is supposed to do - what if I then type said command and nothing happens? Or what if I type it and a completely different action occurs? The user cannot possibly know that ahead of time, therefore they cannot take responsibility for that. Not to say they can’t be actioned for that, because they can.

Yet here you are not only liking other people’s trolling, but doing it now yourself.

Ironic

Yes you are not correct and where are your links on the video game definition of spam?

Not the same thing, try again.

Try reading it again. The key part I was responding to was “flooding is spam” and “a violation of the CoC” which is a direct counter to who I was responding.

More insults from the person talking about “horrible people”? Try reading.

Actually It says varies from site “but usually this term applies to all forms of message flooding, violating the terms of service contract for the website” The key part here is what I quoted. If Blizzard is silencing people for it then it is a violation. It was also a direct counter to someone arguing that it is flooding and not spam.

1 Like

So are you going to give Wiki 100% endorsement about being correct now ?

Because if you are going to claim ‘what qualifies as spam varies from game to game’ is incorrect, you are going to go against common sense.

Just trying to determine what your position on this actually is, or whether you are just straight arguing anything now to insult and claim someone is wrong.

I am pretty sure I read in that link exactly what he said as well.

Yup - right in there.

What qualifies as spam varies from game to game,

That’s “buyer beware”. Because Blizzard does not openly police apps in a download center, it’s the user’s responsibility and accepting responsibility when downloading any 3rd party addon.

That’s exactly why they get actioned for it and not the author.

Blizzard created a new system of rare spawns using the old system - long respawn rares, with low chance of drops. We haven’t had that model for almost a decade now. There was zero reason to go back to it other than to deprive people of their time and make them spend more time in game.

While I’m sure the silences will be the thing most discussed here, I’m glad I’m not the only one who hates the return of the old rarespawn system.

Call me old fashioned, but I just type it out myself. Doing this also means I don’t announce rares that are so close to death that nobody stands a chance of getting to it… I also wont tell anyone it died if someone else’s addon already did.

Someone in my mechagon is using two addons for rare announces and if the rare takes longer than the built in 60 second spam filter Blizz implemented, we get double the “target has died.” spam too. Instead of taking the criticism of “do you really need both of them?” they chose to lash out about how ungrateful we are. So I reported em for spam. They’re responsible for downloading it and turning on the automatic feature, on in the case I gave… turning on the automatic feature of both addons.

Claiming it isn’t the users fault but instead the creator is a weak argument. Try that with a cop… “I didn’t know the car goes so fast, it’s clearly the fault of the creator, not mine!”

2 Likes

Well the main thing is I was trying to talk to someone who was arguing that it was flooding and not spam, but I was pointing out that in video game context it is the same thing. I had also mentioned that if Blizzard agreed it was spamming then it is spamming which they were also arguing against. The link I provided clearly supported what I said.

Proving you wrong is not trolling.

Indeed. Complaining about people correcting you when trolling. Oh the irony.

I don’t need links. Your link has been debunked multiple times over.

It is the same thing. Your source was Wikipedia, the source in the paper is Wikipedia. Go watch what happens.

1 Like

Yes, but if the author were doing their thing correctly in the first place, there should be no chance of getting actioned. The user doesn’t maintain the app - the author does.

Okay… but none of that is something Blizzard cares about. They’re going to punish the person using it - not the person who made it.

Why are you even arguing this?

There really isn’t much point in arguing with them because experiences on this will differ a lot and if I was playing on their servers/shards/time of day I might agree there is no problem. However, since I am not and since I have seen the effects of the amount of spam on my server I am not a supporter of these addons being used by people with little to no common sense.

In order for me to not view it as sometimes useful spam it would need the same filter applied to “target has died” as got applied (very quickly and rightfully) to the announce itself… it the addon detected someone else already said it, it should refrain from saying it again. I don’t need four people telling me that the rare died. It would also need a filter to not say anything if the mob is below a certain percentage. Right now, as I type this…

  • “Foul Manifestation 4.24% ~(64.41, 49.14)”

It isn’t useful to anyone because that thing will be dead by the time anyone even finishes reading it.

Otherwise though, it has some usefulness to it, but nothing that basic human decency can’t accomplish. :stuck_out_tongue: