chadscira

5 ms·

1.
by chadscira 10y ago
Yea but when using promises with async/await its very beautiful. await asyncFuncOne(); await asyncFuncTwo(); No more weird water-falling, and finally proper exception handling. The only gotcha is the fact that we cant awai
2.
by chadscira 10y ago
If they don't have X-Frame-Options the attacker can also just use a 1x1 iframe on a popular website or shitty ad network to trigger that page to load
3.
by chadscira 10y ago
I don't know if I agree with this. Even with paper ballot we still have to trust the people/devices counting the votes. As an American citizen theres no website I can go to and check my vote. How do I know it was even counted, or
4.
by chadscira 10y ago
Yeah, but its a pain in the butt to iterate when doing that, especially when you just want to dump off clipboard, or drag & drop. Also wanted an excuse to play with a few browser features :P.
5.
by chadscira 10y ago
This was made to make playing with Data URI's much easier. I find myself often needing a quick way to generate a Data URI when playing with files on jsfiddle, or codepen (due to CORS). So I thought it would be nice to have a website th
6.
Show HN: ICanHazData – Data URI Swiss Army Knife(icanhazdata.com)
257 points by chadscira 10y ago|5 comments
7.
by chadscira 10y ago
I made this because I was getting upset with the lack of a solid solution that did everything. It locally stores the files as well, click on the hamburger menu to see them. - drag & drop - manual upload - paste - custom file creation -
8.
Show HN: Data URI Generator(icanhazdata.com)
4 points by chadscira 10y ago|2 comments
9.
by chadscira 10y ago
Oh, awesome. Hopefully they drastically reduce it.
10.
by chadscira 10y ago
They are charging us too much for time! We need the gates foundation to donate a billion, that should get us 31 years on the clock.
11.
by chadscira 10y ago
Awe, hey we end up with more than a empty hole! What about all of the dead code!
12.
by chadscira 10y ago
Also those jobs wont be around that long. Every year we have quite a bit of progress on Self-Driving Cars.
13.
by chadscira 10y ago
Seems like in chrome you can go much higher! Here is a example of 5M data:text/html,<script>window.location='data:text/html,<script>document.
14.
by chadscira 10y ago
I did data:text/javascript;base64,YWxlcnQoMSk= I didn't know you could do stuff like this (not for XSS) data:text/html,<script>alert(window.location)</script> Cool, you can store a whole web
15.
by chadscira 10y ago
We currently just rent a few big boxes on OVH, and manage them via Rancher. You should checkout ranchers channel for some videos: https://www.youtube.com/channel/UCh5Xtp82q8wjijP8npkVTBA It's mind-blowing that the
16.
by chadscira 10y ago
Because theres no perfect solution at the moment we have opted for a 4 disk setup, and mirror them all using ZFS. We also do 10 minute snapshots, and incremental snapshot backups (to S3). Feels safe enough for our needs. Before this we didn
17.
by chadscira 10y ago
We have been using Rancher as well... It allowed us to move away from DO and AWS. Now most of our infra is from OVH :). It's been smooth sailing. Because of massive costs savings we were able to just reinvest it in our own redundancy.
18.
by chadscira 10y ago
Yep thats what it looks like. So the take away is Go is better at handling massive amounts of open outgoing network calls. In Node.js you want to restrict this to prevent the server from choking. If they did that I bet performance would be
19.
by chadscira 10y ago
I would like to know more about the implementation. I have had node do 12000 requests a minute with no problem (on a single core). In this case they had 4 two core boxes, so they needed each one to at least perform 42 requests a second unde
20.
by chadscira 10y ago
This could have been solved with a simple addition of another queue. Don't spawn off heavy requests without a throttle / queue, or else you will overload your single core. We normally don't think about this because most req
21.
by chadscira 10y ago
Not really understanding the down votes (maybe the double question mark??), but oh well. This is a valid comment considering that the EC2 instance mentioned is a 2 core box, and there is a possibly that the node implementation didn't t
22.
by chadscira 10y ago
No mention of Cluster?? https://nodejs.org/api/cluster.html#cluster_cluster
23.
by chadscira 10y ago
The email verification was easy when they provided gravatar ids, which used to just be MD5(email).
24.
by chadscira 10y ago
Doesn't github already make majority of this data public? With the exception of emails... Previously they used gravatar hashes which allowed email brute forcing (since removed). Then they also were not omitting emails from commit messa
25.
by chadscira 10y ago
We also should remember that most react apps are single page apps, and usually this .js file is aggressively cached on a CDN. Most interactions are close to instant. Server-side rendering fixes the issue of time to first pixel. I think we d
26.
by chadscira 10y ago
Its not just something me, and you disagree on. I would say it's me, plus a good amount of other, and also most browsers. If the browser is locked over X seconds it will actually tell you that the script is unresponsive, and ask if it
27.
by chadscira 10y ago
Good catch. From my experience though there is a small overhead in terms of workers, also the message cost. But still even if it was 300% slower it's justified because it is unacceptable to lock the browser. Too many commenters here ar
28.
by chadscira 10y ago
Life before WebWorkers was fun :). Another way was to create multiple iframes, and use a form of hacky message passing to use more cores, but i think this may have depended on the browser implementation.
29.
by chadscira 10y ago
In response to your last comment, you should check out https://github.com/icodeforlove/task.js . It will do that and much more.
30.
by chadscira 10y ago
If you wanted to go crazy you can use transferables to get around the memory copy cost. It would be a fun experiment to figure out at what point does it make sense to use multiple workers considering the initial cost of worker distribution.

More ›