search for: disqus

Displaying 5 results from an estimated 5 matches for "disqus".

Did you mean: disque
2015 Jun 12
1
C5 : Firefox 38 bug
...'safe browsing' from > Google either. Yeah. I never enable google-analytics. When I want to see a website that's got a ton of inclusions, I selectively temporarily enable only what I think I'll need (which of those stupid things has the text? which the pic?), and when you enable disqus, for example, *then* you have to reopen noscript, because only then in disquscdn visible. Annoyances, but... and I never enable the ads. mark
2013 Jun 12
1
Instant search for R documentation
Hi, I just wanted to share with you that we made a website over the weekend that allows "instant search" of the R documentation on CRAN, see: www.Rdocumentation.org. It's a first version, so any feedback/comments/criticism most welcome. Best regards, Jonathan [[alternative HTML version deleted]]
2015 Apr 22
3
[Bug 90145] New: [NV94] Corruption on very long (vertical) pages in Firefox
...0.0-1.fc22.x86_64 , xorg-x11-drv-nouveau-1.0.11-2.fc22.x86_64 , xorg-x11-server-common-1.17.1-9.fc22.x86_64 , mesa-dri-drivers-10.5.1-1.20150314.fc22.x86_64 , libdrm-2.4.59-4.fc22.x86_64 . If I view a page with a lot of vertical scroll in Firefox - say, a long article, or just a page with a lot of Disqus comments - after I scroll through quite a long way, the display of the page starts corrupting. http://www.avclub.com/article/surely-you-cant-be-serious-oral-history-airplane-218043 is a good example: it starts corrupting around the "Into The Cockpit" section. I can scroll up to any poin...
2015 Jun 13
6
C5 : Firefox 38 bug
On 06/12/2015 11:57 AM, Jonathan Billings wrote: > On Sat, Jun 13, 2015 at 10:55:47AM -0600, jd1008 wrote: >> The most offensive problems of using browsers is that >> they do not tell you nor ask your permission when javascripts >> spy on your entire storage contents. > Huh? You've been misinformed. Certainly there have been exploits > against browsers to bypass
2013 Nov 28
74
Remove :js responder
https://github.com/rails/rails/issues/12374#issuecomment-29446761 Here in discussion I proposed to deprecate JS responder because this technique is insecure and not pragmatic way to transfer data. It can be exploited in this way http://homakov.blogspot.com/2013/05/do-not-use-rjs-like-techniques.html i find this bug very often so i know what i''m talking about. With it attacker can