Why do you not provide active data on realm populations

[Iqgap-kromcrush]

this is literally what you meant

This is what I mean by “bad faith argument”.

After 15 years of people on the forums claiming “WoW is dying” I can hardly blame them.

[Tln-herod]

this is literally what you meant

You’re deliberately misrepresenting my statement in order to troll.

Hence “bad faith argument”, and “grow up”.

[Iqgap-kromcrush]

ya just because you cant come up with a valid explanation i must be trolling

[Tln-herod]

you cant come up with a valid explanation

I already did.

Keep trolling tho.

[Iqgap-kromcrush]

could you link it i cant seem to find one from you

[Tln-herod]

could you link it

I can.

/10char

[Iqgap-kromcrush]

oh sorry, will you pretty please link me to your valid explanation on why blizzard is hiding census numbers

[Tln-herod]

will you pretty please link me to your valid explanation

I have no reason to do so, and thus won’t.

[Iqgap-kromcrush]

ya thats what i thought, see ya

[Tln-herod]

see ya

Oh I’m sure you’ll definitely leave and not come back.

[Crackore-arugal-775847]

Because the greed of corporations don’t care. They will take your money and keep taking it until you unsub.

Your just a number in a spreadsheet.

[Holymary-fairbanks]

why blizzard is hiding census numbers

Is Blizzard hiding census numbers?

[Tln-herod]

Is Blizzard hiding census numbers?

Kind of. They don’t release the data, and have recently broken addons that have existed for a long time to collect such data by tracking characters.

[Holymary-fairbanks]

have recently broken addons

AFAIK, they removed the being able to use automated /who() API calls, which isn’t exactly the same as breaking addons.

WowClassicPopulation uses the CensusPlusClassic addon, which works and is still in active development, with the developers being accessible through their discord.

They don’t release the data

Which is different from hiding it. I would not accuse you of avoiding mowing my lawn, simply because you do not do it.

[Tln-herod]

AFAIK, they removed the being able to use automated /who() API calls, which isn’t exactly the same as breaking addons.

The function was SendWho(), and that’s what “breaking addons” actually means.

Blizz can’t change the code of the addon. All they can do is disable whatever feature the addon is using.

WowClassicPopulation uses the CensusPlusClassic addon, which works and is still in active development, with the developers being accessible through their discord.

It’s not the same anymore, with the addon having to piggyback off of the UI calling /who, it now requires the user to click.

Which is different from hiding it. I would not accuse you of avoiding mowing my lawn, simply because you do not do it.

It’s a requirement of hiding the thing, which is why I brought this up. In order to interpret this argument as “simply because they did not do it”, you have to ignore the context I provided in the rest of the comment. Please don’t start that nonsense.

And you probably would accuse me of avoiding mowing your lawn if I didn’t do it AND I threw out the wheels of the lawnmower. Sure, you could replace the wheels with sled runners, but I’ve made it more difficult and annoying to actually get the job done.

[Holymary-fairbanks]

It’s a requirement of hiding the thing, which is why I brought this up. In order to interpret this argument as “simply because they did not do it”, you have to ignore the context I provided in the rest of the comment. Please don’t start that nonsense.

I certainly wasn’t trying to start any nonsense. I did not know there was any reason to believe that disabling SendWho() was related to intentionally breaking census data addons.

I had assumed it was related to the LFG addon, but I suppose I don’t have any particular reason for that assumption either.

[Tln-herod]

I did not know there was any reason to believe that disabling SendWho() was related to intentionally breaking census data addons.

That’s basically all that uses it.

I had assumed it was related to the LFG addon, but I suppose I don’t have any particular reason for that assumption either.

A lot of people were claiming it was supposed to break ClassicLFG… but it didn’t break anything related to that addon as far as I can tell.

[Goodie-ashkandi]

Even at 40 60 thats a huge number difference when talking about 1000s. Its not 3000 as we all know its what double that and more on some servers is it not? Anyways pretty lame for pvpers no matter the factions

[Ceeyoo-aegwynn]

I totally agree. Its density. But people want to turn it into “ltp” or “pvp happened”

They do Blizz a favor being so…dense about it.

[Holymary-fairbanks]

@Tln-herod

That’s basically all that uses it.

From some CensusPlusClassic dev issue comments for the source code:

“it seems Blizzard disabled the sendWho() API call in a hotfix yesterday. Addons can no longer use this function. This breaks all Census addons. There’s speculation that this was done to limit LFG addons, Census is just collateral damage. Damn shame. I’m not aware of a workaround atm.”

reference: https://github.com/christophrus/CensusPlusClassic/issues/17

@Bornakk

we believe the nature of ClassicLFG is incompatible with our social design for Classic. Thus, in an upcoming patch (in the weeks following launch), we will be adding restrictions to the Classic add-on API that will significantly limit this add-on and others like it.

---

That doesn’t clearly show a direct connection between breaking SendWho() and the ClassicLFG addon, and I could not find any mention of SendWho() in the ClassicLFG source, except for here: https://github.com/DomenikIrrgang/ClassicLFG/blob/10fad93d5c33d05edb577373cd5f674d0e3420ad/src/util/util.lua#L89

I’d be curious as to whether there is any compelling information that would point to reasons for disabling SendWho() as a public API call that are related specifically to preventing consensus or population data collection.