Live data from Hacker News

React Armor: Protect your DOM from third-party tampering

github.com

51–55 of 55 posts

Re: React Armor: Protect your DOM from third-party tampering

#51
post #49

Earlier quoted context omitted.

Users have asked me how to change their icon, and then gotten mad at me when I say I don't know. How about explaining it better? Get them to show you a screenshot, and then you can point out the fact that it's not coming from code you served. For a while, there was some very common malware that rendered my website unusable. Perhaps that was a good thing, because it made you aware of its presence quickly.

> How about explaining it better? Get them to show you a screenshot, and then you can point out the fact that it's not coming from code you served. You presume users understand what the difference is. Not all users are technical enough for that sort of thing. Someone also points out a related problem: if the user complains on social media instead of directly to me. I don't always have the opportunity to explain at al…

Er...so if you didn't tell them it was malware, then what DID you tell them?

Re: React Armor: Protect your DOM from third-party tampering

#52
post #51
post #49

Earlier quoted context omitted.

> How about explaining it better? Get them to show you a screenshot, and then you can point out the fact that it's not coming from code you served. You presume users understand what the difference is. Not all users are technical enough for that sort of thing. Someone also points out a related problem: if the user complains on social media instead of directly to me. I don't always have the opportunity to explain at al…

Er...so if you didn't tell them it was malware, then what DID you tell them?

I didn't tell them anything. I just deployed a workaround where the tag the malware inserted was between .

https://github.com/Zarel/Pokemon-Showdown-Client/commit/95f2...

Re: React Armor: Protect your DOM from third-party tampering

#53
post #25

so many haters here... Make things that solve your problems. Have fun while doing it. Continue.

Widespread deployment of this will make a number of people's lives less fun. In response, pro-fun countermeasures will be created to solve their new problem. Or, to quote a comment on a technology discussion site about this project: "And so begins an arms race."

[deleted]

Re: React Armor: Protect your DOM from third-party tampering

#54
post #13

Earlier quoted context omitted.

broken user scripts and styles. f-up accessibility and screen readers. seriously. wtf.

But think of the ads! Can't get in the way of that!

not sure if you were joking, but ads messing up with page is a huge problem, and is in no way solved by this.

But the solution already exists for years: http://www.iab.com/guidelines/safeframe/

any publisher not using this is not worthy their salt!

Re: React Armor: Protect your DOM from third-party tampering

#55
post #30
post #26

Earlier quoted context omitted.

We handle over 1600 Japanese institutions at the company I am working for in Tokyo (Moneytree.jp), and we haven't arrived at a situation where we were defeated by what React Armor is trying to prevent.

I'm sorry, I've reread your sentence several times, and I still don't understand what it's trying to say. Does your company have the same goals React Armor has (this seems to be what your double-negative is saying), or is it the party React Armor is trying to protect against, or is it relevant to React Armor in some other way? What kind of Japanese institutions are these and what does handling them entail? Are you sc…

Sorry for the confusion, but Roritharr explained spot on! Thanks Roritharr
Post reply on HN