-
Banned
What specific data is collected by TH for Dashboard?
Subj.
Untill detailed answer with proofs I recommend all users block dashboard ip in firewall (137.74.12.51).
-
Member
Mostly internal stuff for function between HUD and client. Wouldn't get paranoid.
A banana a day keeps the doctor away!
-
Active Member
You're not going to get "proofs" because TH is not an open source project, period. You either trust or you don't.
-
I am happy that your first post on the forum is so thankful, positive, and comforting. Have a nice day
Do not send me private messages unless it is absolutely necessary or the content is sensitive or when I ask you to do that...
-
Post Thanks / Like - 3 Thanks
-
Banned
Originally Posted by
KillerJohn
I am happy that your first post on the forum is so thankful, positive, and comforting. Have a nice day
So no answer? Ok, I'll keep this ip in firewall then.
-
Banned
- fixed: HUD terminated when pastebin.com was unaccessible
- fixed: the "Unable to retrieve latest version info for TurboHUD." message was not displayed when pastebin.com was "hacked" in hosts file AND dashboard was forbidden on firewall
Why you trying to "fix" that users don't wanna be spied by you? btw, the fiddler (TurboHUD was Hacked and Has been Discontinued) trick is still works, and TH still works even if your spy-board ip is blocked, but now message is longer then "can't connect to spy-board":
-
Member
This is a project he does on his spare time, 100% free, to help the community.
So how about you go f**k yourself ?
You are entitled to nothing, you like it, you use it.
You don't like it, then don't use it.
And stop whining and making demands you can't make.
-
Originally Posted by
xiya1
well, it is by-design what I did with the fix you quoted: I display the text if dashboard is unaccessible.
BUT NOW... Just because of you, in the next version HUD will be disabled as well when it can't communicate with dashboard
/grabs popcorn/
Do not send me private messages unless it is absolutely necessary or the content is sensitive or when I ask you to do that...
-
Contributor
Originally Posted by
KillerJohn
well, it is by-design what I did with the fix you quoted: I display the text if dashboard is unaccessible.
BUT NOW...
Just because of you, in the next version HUD will be disabled as well when it can't communicate with dashboard
/grabs popcorn/
My God, I hope the dashboard will be stable! It used to be very unstable and often crashed
-
Member
Ohh, xiya1, ffs...
SeaDragon is right - dashboard is too unstable
KillerJohn, put that popcorn down, don't let innocent people suffer because of one stupid troll
-
Banned
Originally Posted by
KillerJohn
well, it is by-design what I did with the fix you quoted: I display the text if dashboard is unaccessible.
BUT NOW...
Just because of you, in the next version HUD will be disabled as well when it can't communicate with dashboard
/grabs popcorn/
Why you so toxic and can't just say to users of your indian-code what are you trying to collect from us?
-
Member
Originally Posted by
xiya1
Why you so toxic and can't just say to users of your indian-code what are you trying to collect from us?
I hope he collects usage data on how many turn off paragon captura and greyed out items so they get disabled by default
And yes, why not write something about what data you collect and why?
-
Member
Can we please have this troll banned ?
He's toxic, doesn't help and mistakenly thought he was awed something....
Moron...
-
FYI
- salted hash of the battletag (salt is the sender computer's name so there is no way I could brute-hash all known battletags and match those with your hash, because I don't know the sender's machine's name)
- salted hash of the current hero ID (salt is the sender computer's name)
- hero info: sc/hc, hero class, gender
- realm
- server IP
- the stat trackers
Do not send me private messages unless it is absolutely necessary or the content is sensitive or when I ask you to do that...
-
Member
Originally Posted by
KillerJohn
FYI
- salted hash of the battletag (salt is the sender computer's name so there is no way I could brute-hash all known battletags and match those with your hash, because I don't know the sender's machine's name)
- salted hash of the current hero ID (salt is the sender computer's name)
- hero info: sc/hc, hero class, gender
- realm
- server IP
- the stat trackers
Even with that kind of shit talk, you delivered.
Thanks