News for hackers. Stuff that matters.
Re:Try to not play with these sliders by Tick2Time on Monday May 22, 2017 @04:32AM (#14391929)
It's quite easy not to play with them on iPhone :/
Re:Try to not play with these sliders by semi-extrinsic on Monday May 22, 2017 @04:53AM (#14392009)
On Android, pulling sliders from left to right bring out some type of index/menu drawer that obscures 90% of the screen, and I have to hit a narrow strip to dismiss it; if I miss that strip, I navigate away from the page.
Re:Try to not play with these sliders by dismantlethesun on Monday May 22, 2017 @02:52PM (#14396010)
It doesn't so that on my Goole Pixel phone.
Re:Try to not play with these sliders by Matt3o12_ on Monday May 22, 2017 @04:53AM (#14392011)
It is quite difficult to do that on iOS since the "hit box" of the slider is rather small. You need to exactly hit the little point or it won't register (if you are used to iOS's native sliders, they are quite unsual).
Re:Try to not play with these sliders by josephg on Monday May 22, 2017 @04:42AM (#14391972)
Huh? The demo seems to be working fine on my iPhone. I'm using a 6s+ / current version of mobile safari.
Re:Try to not play with these sliders by samhamilton on Monday May 22, 2017 @04:47AM (#14391985)
Also having troubles, iPhone 6 with latest mobile safari
Re:Try to not play with these sliders by sleepychu on Monday May 22, 2017 @04:31AM (#14391923)
Had to enable 3 different external JS sources to get the page to work. I don't mind sites using CDNs but please try and reduce the surface for external threats!
Re:Try to not play with these sliders by lucideer on Monday May 22, 2017 @04:54AM (#14392015)
In case it's of any help to you, I use https://github.com/Synzvato/decentraleyes which had 2 of these 3 CDNs cached. And the 3rd (unpkg - an npmjs.com mirror) seemed not to be a hard requirement as far as I could tell.
Re:Try to not play with these sliders by therealmarv on Monday May 22, 2017 @04:35AM (#14391936)
are people doing this? What's the attack surface of a private hosted JS library vs. a well known TLS/SSL secured CDN for JS libraries? Threats are not restricted to CDNs.
Re:Try to not play with these sliders by stupidcar on Monday May 22, 2017 @04:40AM (#14391958)
Security theater, nerd-style.
Re:Try to not play with these sliders by raverbashing on Monday May 22, 2017 @04:36AM (#14391939)
CDNs are much more reliable than your avg. 'stuff.com' hosted js. It shouldn't be an issue
Re:Try to not play with these sliders by SchizoDuckie on Monday May 22, 2017 @05:15AM (#14392095)
This is a falsehood i've seen repeated over and over.

CDN's fail. You already have a connection to the 'stuff.com' self-hosted js. If your site is up but the cdn breaks you have another problem.

Also the perf win for using a shared cdn version of for instance jquery is totally overstated. See discussions here too: https://news.ycombinator.com/item?id=11549131

Re:Try to not play with these sliders by raverbashing on Monday May 22, 2017 @07:37AM (#14392676)
Thanks, I stand corrected
Re:Try to not play with these sliders by martinknafve on Monday May 22, 2017 @04:41AM (#14391965)
That would depend on what CDN you use and how it works. If the CDN is just a caching CDN in front of your own site then the CDN typically won't be any more secure than your own site.
Re:Try to not play with these sliders by ibotty on Monday May 22, 2017 @05:02AM (#14392049)
You have subresource integrity. If in use, that only leaves the privacy implications of using a CDN.
Re:Try to not play with these sliders by mirekrusin on Monday May 22, 2017 @04:54AM (#14392016)
It's actually fun trying to sync it with the music...
Re:Try to not play with these sliders by loco5niner on Monday May 22, 2017 @12:02PM (#14394651)
A less clck-baity title would be appreciated.