News for hackers. Stuff that matters.
Re:Qt for WebAssembly by d33 on Tuesday June 19, 2018 @03:59PM (#17349846)
What are the implications?
Re:Qt for WebAssembly by chaosite on Tuesday June 19, 2018 @04:21PM (#17350001)
After 5 seconds of looking at it, I'm noticing that my scroll wheel doesn't work and that typing in Hebrew results in Unicode boxes. Meaning, it is acting different enough from my browser that I'm noticing it.
Re:Qt for WebAssembly by 0x4f3759df on Tuesday June 19, 2018 @04:52PM (#17350214)
Somebody is going use a technology similar to this to defeat ad-blockers.
Re:Qt for WebAssembly by spiritcat on Tuesday June 19, 2018 @08:41PM (#17351489)
damm you, cold hard truth!

but it is really cool

Re:Qt for WebAssembly by 0x4f3759df on Tuesday June 19, 2018 @09:30PM (#17351719)
People argue that we will just block ads at the transport level, but I don't see why the site won't just add an extra hop and serve the ads from their server.
Re:Qt for WebAssembly by chii on Wednesday June 20, 2018 @02:15AM (#17352996)
> serve the ads from their server.

because ad networks don't trust their own clients to not spoof the traffic numbers.

Re:Qt for WebAssembly by spiritcat on Tuesday June 19, 2018 @09:42PM (#17351788)
On the bright side, punch the monkey in 3d/vr could be cool.
Re:Qt for WebAssembly by dmitriid on Tuesday June 19, 2018 @03:59PM (#17349855)
Most likely, accessibility.