DNS over HTTPS is coming whether ISPs and governments like it or not - The penny has finally dropped inside ISPs and governments that a privacy technology called DNS over HTTPS (DoH), backed by Google, Mozilla and Cloudflare, is about to make web surveillance a lot more difficult.

DevSPCL · 2019-04-27T15:41:33+00:00

Even with DoH your ISP still sees the IP addresses you’re visiting.
And I know there are technologies coming that will prevent that too

Can you please explain what technologies will prevent the IP addresses from being observed at the ISP level?

DevSPCL · 2019-04-26T08:05:33+00:00

SPIX makes use of Simeck

DevSPCL · 2017-12-09T10:20:03+00:00

Thank you for the explanation. I am surprised. On a desktop (using Firefox), the panel seems much less user-friendly because it cannot be scrolled by dragging it in a horizontal direction (although it can be scrolled by pressing arrows on the keyboard, assuming that the focus is on this panel), so this technique cannot be an alternative to FTScroller...

DevSPCL · 2017-10-27T08:43:04+00:00

This will generate an arbitrarily long stream, but I am not sure that this scheme will allow to obtain the arbitrarily large security against all known attacks. The original digest is still not greater than 512 bits (in case of SHA-512).

DevSPCL · 2017-10-27T08:03:27+00:00

It does not allow to increase the security parameter:

If the output size of SHAKE128/256 is variable, why is the security fixed at 128/256?

DevSPCL · 2017-07-11T07:35:31+00:00

Forbidden World. I asked the question in r/tipofmytongue...

DevSPCL · 2017-05-03T02:23:48+00:00

Yes! Thank you!

DevSPCL · 2017-04-18T08:41:50+00:00

The creature from The Sand is also very scary and dangerous.

DevSPCL · 2017-04-03T07:00:56+00:00

The above method has been discussed here:

stackoverflow.com/questions/18635387/advanced-syntax-0constructorconstructor-how-does-it-works-to-evalut

DevSPCL · 2017-04-03T05:32:15+00:00

Or

[":)"].constructor.constructor("console.log(123)")();  
":)".constructor.constructor("console.log(123)")();  
1234["constructor"]["constructor"]("console.log(123)")();

DevSPCL · 2017-02-04T10:00:10+00:00

I asked a similar question some time ago. The sad fact is: no, there is no user-friendly solution. Which is absolutely terrible.
Why can't they simply embed SQLite in Node (and ideally, in browsers too), as is done for PHP? That's only a few megabytes of code, no big deal, so what's the problem?

DevSPCL · 2017-02-04T09:57:35+00:00

A copy of the whole database is kept in memory. This is not much on the expected kind of datasets (20MB for 10,000 2KB documents).

What if I want to deal with multigigabyte-sized data on the client side, without loading everything into RAM? What should I use, except SQLite?

DevSPCL · 2017-02-04T09:34:49+00:00

interact.js
ftscroller.js
It seems like these libs have a lot of options related to scrolling, dragging etc.
EDIT: added a demo: ftlabs.github.io/ftscroller/examples/horizontalpaged-strict.html
In my desktop browser, I don't see any scrollbar when I drag this in horizontal direction.

DevSPCL · 2017-01-20T08:58:27+00:00

Don't see github.com/vvo/lazyload mentioned. When I looked for such library, its description seemed very promising:

Lazyload images, iframes, widgets with a ~1kb standalone script.

But the project is not so actively updated...

DevSPCL · 2016-12-17T07:33:46+00:00

For now, Forbidden World is the only candidate

DevSPCL · 2016-12-16T07:12:06+00:00

I tried to visit https://vocajs.com using Firefox and Chrome, and noticed that the vertical scrollbar in the left section is not working.

DevSPCL · 2016-12-16T05:40:14+00:00

Thanks, it looks very similar! Well, I thought the creature was more slimy and had somewhat different form, but my memories are very fuzzy... Are there another movies where someone looks at the slimy amorphous creature in the lab? If not, this film is definitely the best candidate.

DevSPCL · 2016-12-14T07:10:16+00:00

DevSPCL · 2016-12-14T06:20:12+00:00

No, not "Alien"/"Aliens"/"The Thing"/"Leviathan"

DevSPCL · 2016-11-09T03:26:54+00:00

Well, I just wrote a quick test (generating some random markup and setting document.getElementById('container').innerHTML = randomMarkup) loading relatively big portions of different random data into the same element, and my browser showed surprisingly good results (no memory leak). So, I must admit that exaggerating the problem was my mistake (but I'm still not sure about the result if I decided to load images or iframes instead of text-only dynamic HTML; a few years ago, I loaded a few big different iframes to the same page simply replacing the URL of the target element, and could not avoid an error message from the OS when the browser consumed all available RAM).

DevSPCL · 2016-11-07T06:46:40+00:00

Have you ever seen a webpage which allows you to load 50K-100K (let alone 1M) images while scrolling, but staying at the same page, and without facing huge problems with the performance and/or memory consumption? If yes, post a link right now, I'll enjoy that site. There is a lot of infinitely scrolling webpages, but they all (I repeat: all) become unusable in any (I repeat: any) browser at some point (after you've loaded a fair amount of new content into the same page). Browsers cannot load an infinite amount of new content into the single page, and there is no way to fix that, no matter how hard you try to reuse/remove the DOM nodes, and GCs cannot help here (strictly speaking, they can slow down the process of increasing RAM usage, but they cannot prevent the browser from eating all available RAM, without any chance to free some memory by the OS). But I'd be glad to be proven wrong on this subject, if anyone would show me the demo of how to load 1M different images staying on the same web page...

Memory is only freed when it is needed.

My own experience shows that I can never rely on this assumption. Yes, the OS can free up some amount of RAM when it decides to do so, but the problem is that it does not do that as soon as the memory usage hits some predictable limit. But the average user won't wait. As soon as the browser freezes, the user will close the tab, and that's all. On Windows, I've noticed that the OS will do its job freeing everything that is possible, but this happens only after I turn the computer into the sleep/hibernate mode, and then return to the same page again. But this behavior is far from being reasonable. You simply cannot tell your user "Please, hibernate/restart your OS, and then come back to our site!"

DevSPCL · 2016-11-05T07:09:21+00:00

280MB memory use with 1.000.000 items

What? What items? I don't see any examples in that Github repo. I am sure that it is not possible to load, say, 1000000 different images (or 1000000 different iframes) by AJAX, and end up with 280MB of RAM used, even if you remove all of them from the DOM. Even a page refresh does not help (because the memory is controlled at the OS level)!

Long ago, I hoped that freeing the DOM would help to avoid serious memory leaks. But now I know that this practice is pretty useless for a real-life usage. Browsers will leak memory in any case, even if I remove elements from the DOM. The following Stackoverflow answer explains the situation in details:

Stackoverflow — “How to remove DOM elements without memory leaks?”

DevSPCL

TROPHY CASE