AkshitGarg's comments

AkshitGarg | 4 years ago | on: Competitive programming is useless

So much of this. In my CS class, I could hardly find anyone who actually had some curiosity to learn. Everyone does their homework by sharing answers on the class chat. And in team projects, either there is one person who does all the work, or they end up copying from google and stackoverflow.

AkshitGarg | 4 years ago | on: Facebook hacker beat my 2FA, bricked my Oculus, and hit the company credit card

It certainly recognizes the domain, but thats more of a convenience feature than a security feature. Nothing is stopping you from putting your example.com code into legit-example.com manually. Sure the extension won't do it automatically, but if the user is convinced to put the password into the fake website, user could also put in the TOTP code

AkshitGarg | 4 years ago | on: Why WebAssembly is innovative even outside the browser

WebAssembly in the browser currently can't manipulate the DOM directly. Neither can it make HTTP requests. You need to use a JS bridge to do that. That has some overhead. So I don't think webassembly will replace JavaScript anytime soon. It might be reserved for high-performance compute, or maybe canvas based rendering for the time being.

AkshitGarg | 4 years ago | on: Ask HN: How did web development become so bizarrely complex?

> we now have a generation of programmers who think a GET request only returns JSON, and were never taught it can also return HTML

Can't relate more to this. I sometimes find it difficult to accept that some of my peers in the college thought that fetch is the only way to submit a form. Those were the same people who fetched json to render a static blog post

AkshitGarg | 4 years ago | on: Google is capping Meet’s group video calls to an hour for free accounts

> I don’t understand what is difficult with WebRTC videos.

It is difficult to scale a pure p2p model to multiple participants. Each participant would need to create multiple WebRTC streams, one for each participant. So if some call has 10 participants, each one of them would need to broadcast 9 streams and receive 9 streams with the assumption that each one of them have their microphone and cameras turned on. This would consume a lot of CPU and bandwidth. There are alternate models where you send your stream to a central server, and that server distributes the stream to other participants. This reduces the CPU and bandwidth required per participant, but requires a central server. This looks like the model google follows. So I don't think keeping such a service unauthenticated would be a good idea.

AkshitGarg | 4 years ago | on: Brave, the false sensation of privacy

That still doesn't hide the IP you are connecting to unless you are on a VPN. They still know that if you are connecting to 209.216.230.240, it _could_ be hacker news. With the widespread use of CDNs, and hosting of multiple services on a single IP, this won't be 100% accurate, but the ISP can still connect the dots I guess
page 2