Over the past month I’ve been working on a tool called Browserhub, and it’s a way to automate browsing actions without coding. You can use it to perform end-to-end testing, web scraping, and much more.
And as we may know, there are many edge cases and technical hurdles to automate browsing actions. Solving captcha, rotating proxies, you name it.
That's why I'm reaching out to you. I’m eager to hear about your most painful process of coding your own browser automation solutions. If you have a magic wand, what would you change from the process?
> With that in perspective, the figure of 5k / 10k synonyms mentioned on your website doesn't seem that 'groundbreaking'.
I only generated it once in a go. The number will grow as the time goes by. Imagine the multiplier then.
> Just wanted to understand what value GPT3 brought to your product.
Thanks for your intent, appreciate it :) So I used GPT-3 to train all emojis, not only the new ones. That means a particular emoji will get more and more synonyms as I hire GPT-3 over and over again.
I use GPT-3 to generate synonyms for all of the emojis.
And yes, it’s simple to have a list of synonyms. But is it easy? Calculate the time anyone takes to write synonyms for a particular emoji, and multiply it by the number of emojis (thousands). Not to mention the energy that people spend for it.
For the 2nd question – it’s a limited price deal, and it’ll go up in a few hours.