Sreyanth

I see a CAPTCHA opportunity here. Show the line item and ask people to type both the dish name and price in two boxes. Or may be give a couple of options that the end user must confirm before they can proceed.

If only they can read my dotfiles and create the theme just for me! ;)

Two things that drive product value & growth insanely:

    1. Dogfooding your own product
    2. A free-tier pricing that actually helps one-time users

You nailed both of them. Congrats on the launch. Using it right away. :)

On the contrary, the question I had while building my product was - “Am I infringing someone else’s patent?”

That was years ago. Now, I focus on value creation first and let the product succeed before venturing into patent research.

Hardware might be much tougher though. Would be interesting to see someone with hardware experience to share their real life experiences.

Hey folks - I’m a product manager at BrowserStack. Thanks @pulkitsh1234 for the shoutout!

SpeedLab is a free tool that our team built to help you test website speed across multiple browsers and real devices. You’ll get a cumulative score of your website’s speed across desktop and mobile browsers, so you can identify browser-specific or device-specific page speed issues.

We encourage you to take it for a spin. Questions and feedback are welcome!

EDIT: added that it is a free tool. No need to create an account too!

Am I the only one or is anyone else thinking about what the angle here could be?

Pretty impressive software though. Finally one strong open-source alternative for reverse engineering.

Might be an unpopular opinion, but I think H1B should slowly move to something like an EB1, where candidates can file a self-petition (but without immigration intent, and apply for a regular GC after a few years if they really want to immigrate). They can set some criteria for testing 'high skills'.

This way, a candidate can choose a company based on their interest and skill set match, rather than filtering by whether a company sponsors a H1B.

Sure, even EB1 is being gamed, but at the very least this is a fair chance to candidates.

- Eliminating the not-so-random 'lottery'

- Avoiding the body shops or the so-called fake consulting companies where students go for their OPT

- Eliminate the need to succumb to the whims of employers just to get a visa sponsorship

- Companies, big or small, need not worry about not hiring skillful employees, just because 'it is a looong and random process'

- Not entirely based on higher salaries. Sure, a high salary is a pseudo metric to indicate high skill, but what about early stage startups? This eliminates that unfair advantage

Just cracked your challenge. Should I apply? You will get a package of a developer & PM :)

I believe I might have a strong case for an O-1.

AFAIK, there are two ways in which the tones can be sent.

1. In the regular audio stream (AKA in-band) so anyone who can listen to the phone call, can also listen to these tones. These tones can be mapped to the digits pressed.

2. In a separate RTP payload (AKA out-of-band) so not everyone can read / listen to this stream of signals / tones. RFC 4733 (earlier it was RFC 2833) specifies the format of this RTP payload. This is what the payment via phone systems might be using.

There is a secure RTP with encryption support, but I am not sure if it can be implemented end-to-end to avoid anyone in middle (not a man-in-middle attacker, but a genuine carrier / network) to see these DTMFs. Just unable to imagine how this works :)

Never knew that. I assumed VoIP based telephony comes under PCI view.

I know they do pull it out to a separate band but many VoIP providers log the DTMF sent as digits to debug things - most evident in IVR use cases.

So, if attackers wants to get card details, they need not attack the business or Twilio (because it might redact these when they see <Pay>, but they can simply access logs of the middlemen for DTMFs. Concatenate all those per call, and there we should have all card numbers, expiry dates and CVC/4DBC.

Not sure how Twilio is doing it though. Unless they use some awesome encryption method to encrypt all these numbers so no one in middle can see them.

I don't completely understand how they do this without exposing the DTMF tones / digits pressed to the carriers.

For example, when I key in my card number, my phone carrier will know it, the routing carriers know it before it reaches Twilio. How is my card information safe? I guess I'm missing something here.