51–60 of 218 posts
Like some others here, Firefox is my daily driver and would look forward to anything you could bring our way.
Is this basically Greasemonkey 2.0?
I think the word "de-enshittify" is probably the least elegant piece of slang ever uttered. I know linguistics is descriptive not prescriptive, but it's truly amazing to me the lengths people will go to swear.
Blame Doctorow for swearing, not me!
Earlier quoted context omitted.
Oh great point! We do have the privacy policy included directly on the site but I cut out a lot of the onboarding content if you don't have the extension installed. Working on it now! Edit: The site is an entangled mess of state machine and I don't want to break anything right now (+ I'm trying to keep up with all the comments + traffic) so I can just put it here for now: https://www.tweeks.io/privacy We care a lot a…
> Definitely open to feedback here! Sure. Know your audience. HN users are going to be focused on two things: how the your browers data is used and how you stop an agent from taking account numbers, inputted passwords, etc. From the linked privacy policy: > Share data with third parties except our API service It would be helpful for you to share the privacy policy of the API service as well. > When you use our script…
We have standard data processing agreements with any and all LLM providers that we use. These include do not train/retain provisions (whether you trust them is another question entirely).
> Anything you make is or can become public. I would revisit this decision and prioritize keeping users' data private.
Totally valid. We haven't acted on this clause (scripts are not shared unless your yourself enable sharing) so probably best to remove it. To be clear though, your page data is your own. That will never be shared (not even you yourself can opt to share that because the privacy concerns are too great). The generated scripts are much safer (generally boils down to a bunch of static CSS selectors, styles, etc.). Nonetheless, a valid point.
> Also, I would encourage you to understand your technology, even your marketing site, to be able to add a link to Privacy Policy and ToS in the footer without the burden of "an entangled mess of state machine" and the risk of breaking anything. If the marketing site technology is outside the scope of your expertise, consider how much worse would a static page would be?
Fair comment, fwiw we did ship it in the footer already :) For the standard site, when the extension is installed, there are 6 steps. Each step dynamically progresses based on your install state (installed, pinned, permissions granted, first generation, etc.) We put a lot into the onboarding experience and it is pretty complicated (happy to geek out over the details!), but we hide all this if the extension isn't actively installed. Unfortunately, my blunder was that one of those steps that was hidden includes the privacy policy.
Thanks for all the feedback!
[flagged]
"Don't be curmudgeonly. Thoughtful criticism is fine, but please don't be rigidly or generically negative."
Earlier quoted context omitted.
Oh great point! We do have the privacy policy included directly on the site but I cut out a lot of the onboarding content if you don't have the extension installed. Working on it now! Edit: The site is an entangled mess of state machine and I don't want to break anything right now (+ I'm trying to keep up with all the comments + traffic) so I can just put it here for now: https://www.tweeks.io/privacy We care a lot a…
> Definitely open to feedback here! Sure. Know your audience. HN users are going to be focused on two things: how the your browers data is used and how you stop an agent from taking account numbers, inputted passwords, etc. From the linked privacy policy: > Share data with third parties except our API service It would be helpful for you to share the privacy policy of the API service as well. > When you use our script…
> Instead of digging through selectors and hand‑writing custom JS/CSS
Some of us like that or at least the exact control it gives us Vs installing an extension that has access to my entire browser infrastructure and those terms.
I suspect many HN readers aren't the target market for this.
Looks great, and a brilliant idea to bring back the Greasemonkey way of doing things. Also, perhaps the first practical use case for LLM-In-The-Browser I've seen in the wild (sidebars or AI startpages are very half-posterier'd ideas for what AI in the browser should mean imo). Like some others here, Firefox is my daily driver and would look forward to anything you could bring our way.
So we built this to hopefully make browsing the web more enjoyable for us humans that remain :)
And I'm with you on Firefox. I'd love to be able to go back to Firefox as my daily driver. Will try to prioritize it!