3 ms·

The problem: I don't trust extensions one bit.

• notepad0x90 7mo ago
  auditing the code is fairly straightforward if it isn't obfuscated. so long as it doesn't execute dynamic code that is. but the big issue is you can't control when the extension itself gets an update (to my knowledge). and it isn't uncommon to sell browsing data, or the extension itself to someone more shady than the original author down the road.
  • amelius 7mo ago
    Yes, this exactly.
• quarkcarbon279 7mo ago
  The reason we open our client side code is to bring in the trust in putting rtrvr's DOM intelligence in your web apps - https://github.com/rtrvr-ai/rover/tree/main https://github.com/rtrvr-ai/rover/tree/main . Our monetization is super straight forward with subscription - https://www.rtrvr.ai/pricing https://www.rtrvr.ai/pricing . The experiences of some extensions shipping anything or selling user data comes in when people build them as side-gigs not when we pour more than year in building the highly accurate automation engine. We have cloud sandboxes too if you prefer executing with the same intelligence on cloud and not on your own device. PS: Also, our data policy if you are interested: https://www.rtrvr.ai/blog/rtrvr-ai-privacy-security-how-we-handle-your-data https://www.rtrvr.ai/blog/rtrvr-ai-privacy-security-how-we-h...
  • deleted 7mo ago
    [deleted]
• arjunchint 7mo ago
  We don't sell user data, and we are in it to build a generational company. We already have 25k+ users and have an opensource extension as well: https://github.com/rtrvr-ai/rover/tree/main/apps/preview-helper https://github.com/rtrvr-ai/rover/tree/main/apps/preview-hel...