Live data from Hacker News

Launch HN: Tweeks (YC W25) – Browser extension to deshittify the web

tweeks.io

101–110 of 218 posts

Re: Launch HN: Tweeks (YC W25) – Browser extension to deshittify the web

#101

Dumb question: why does each use cost tokens?

It looks like it's using an LLM agent to do the actual work of editing the site.

That's correct. The flow is 1) user requests some change e.g. "change to dark mode", 2) a snapshot of the page is sent to an LLM, 3) the LLM generates and returns a deterministic script that handles the page editing.

And just to further clarify: "each use" means each generation. Applying the modification after generation doesn't cost tokens

Re: Launch HN: Tweeks (YC W25) – Browser extension to deshittify the web

#102
@jmadeano, i just wanna say this is the most inspiring post ive seen on HN, ever. The idea, execution and also your responses in the comments about just wanting to build cool stuff without really caring about the other stuff reminded me of why i started this journey, to have fun and build cool shit. This is genuinely soo inspiring man… lets gooo work, i really hope you win man lmao too much glaze but wtv y’all deserve it

Re: Launch HN: Tweeks (YC W25) – Browser extension to deshittify the web

#105

Man I love this, but this isn't a business. Facebook, Reddit, et al will almost certainly C&D you and eventually sue you for violating their policies. "Facebook does not have a specific policy against Greasemonkey like extensions by name, but it has banned users for creating or using scripts that interfere with Facebook's functionality, which can include those made with Greasemonkey. Such actions are against Facebook…

Grounds to ban someone from a service are not grounds for a legal dispute.

Re: Launch HN: Tweeks (YC W25) – Browser extension to deshittify the web

#106
What a positive application of AI. Refreshing to see a product which wants to reduce the amount of slop and noise in my life, instead of the opposite.

A bit disappointed that it doesn't work on Firefox. Since Google banned ublock origin I would think much of your core audience is on FF.

Re: Launch HN: Tweeks (YC W25) – Browser extension to deshittify the web

#107
post #75

Earlier quoted context omitted.

Can you answer question 7?

I doubt that they know. It's too early to figure something like that out.

Seems to me that the obvious business model here is that they will need to have their AI inject their own ads into the DOM. Overall though, this feels like a feature, not a business.

Re: Launch HN: Tweeks (YC W25) – Browser extension to deshittify the web

#108

Man I love this, but this isn't a business. Facebook, Reddit, et al will almost certainly C&D you and eventually sue you for violating their policies. "Facebook does not have a specific policy against Greasemonkey like extensions by name, but it has banned users for creating or using scripts that interfere with Facebook's functionality, which can include those made with Greasemonkey. Such actions are against Facebook…

"Ban" and "sue" are very different things...

Re: Launch HN: Tweeks (YC W25) – Browser extension to deshittify the web

#109

This looks cool and could be a much needed step towards fixing the web. Some questions: [Tech] 1. How deep does the modification go? If I request a tweek to the YouTube homepage, do I need to re-specify or reload the tweek to have it persist across the entire site (deeply nested pages, iframes, etc.) 2. What is your test and eval setup? How confident are you that the model is performing the requested change without b…

> 1. How deep does the modification go? If I request a tweek to the YouTube homepage, do I need to re-specify or reload the tweek to have it persist across the entire site (deeply nested pages, iframes, etc.) If you're familiar with Greasemonkey, we work similar to the @match metadata. A given script could have a specific domain like ( https://www.youtube.com/watch?v=cD5Ei8bMmUk ) or all videos ( https://www.youtube.…

> We could go to Z site and say, "Hey, you could probably make your users happy if you made this change". Maybe they'd even pay us for that insight?

My honest opinion:

1. No site would pay for that insight

2. Every site should pay for that insight

Part of the problem is that a lot of companies fall into one of two categories:

1. Small companies that don't have the time/energy/inclination to make changes, even if they're simple; often they're not even the ones making the website itself and they aren't going to way to pay the company who made the site originally to come back and tweak it based on what a small, self-selecting group of users decided to change.

2. Large companies who, even if they did care about what that small, self-selecting group of users wanted to change, have so many layers between A and Z that it's nearly impossible to get anything done without a tangible business need. No manager is going to sign off on developer and engineer time and testing because 40% of 1% of their audience moves the sidebar from one side to the other.

Also:

1. Designers are opinionated and don't want some clanker telling them what they're doing wrong, regardless of the data.

2. Your subset of users may have different goals or values; maybe the users more likely to install this extension and generate tweaks don't want to see recommended articles or video articles or 'you may like...' or whatever, but most of their users do and the change would turn out to be a bad one. Maybe it would reduce accessibility in some way that most users don't care about, etc.

If I had to pick a 'what's the value of all this', I would say that it's less about "what users want from this site" vs. "what users want from sites". For example, if you did the following:

1. Record all the prompts that people create that result in tweaks that people actually use, along with the category of site (banking, blogs, news, shopping, social media, forums); this gives you a general selection of things that people want. Promote these to other users to see how much mass appeal they have

2. Record all the prompts that people create that result in tweaks that people don't actually use; this gives you a selection of things that people think they want but it turns out they don't.

3. Summarize those changes into reports.

Now you could produce a 'web trend report' where you can say:

1. 80% of users are making changes to reduce clutter on sites

2. 40% of users are disabling or hiding auto-play videos

3. 40% of People in countries which use right-to-left languages swap sidebars from one side to another even on left-to-right-language websites

4. The top 'changed' sites in your industry are ... and the changes people make are ...

5. The top changes that people make to sites in your industry are ... and users who make those changes have a 40% lower bounce rate / 30% longer time-on-site / etc. than users who don't make those changes.

On top of that, you could build a model trained on those user prompts that companies could then pay for (somehow?) to run their sites through to provide suggestions of what changes they could make to their sites to satisfy these apparent user needs or preferences without sacrificing their own goals for the websites - e.g. users want to remove auto-playing videos because they're obnoxious, but the company is trying to promote their video content so maybe this model could find a middle-ground to present the video to users in a way that's less obnoxious but generates user engagement.

That's what I think anyway, but I'm not in marketing or whatever.

Re: Launch HN: Tweeks (YC W25) – Browser extension to deshittify the web

#110
post #90

Great idea, great execution on your landing page (the onboarding experience is really well done) and great job on answering questions in this thread. Also, +1 on building a Firefox version. Since I also have to use Chrome for an extension I'm developing, I pinned Tweeks and will likely reach for it every so often to actually test how well it does, but the demos definitely impressed me. Out of curiosity, how much, if…

> Great idea, great execution on your landing page (the onboarding experience is really well done)

Thank you! As others pointed out here, we admittedly didn't invest much in the "landing page" aspect, but I did work hard to make a great onboarding experience. Glad it shined through

> Since I also have to use Chrome for an extension I'm developing

We're in the same boat, I wouldn't be using chrome if not for this extension. Great to see HN has a strong cohort of Firefox users!

> Out of curiosity, how much, if any, of this did you vibe code?

A lot of the elements of the extension, backend, and even the onboarding page integrations push at the boundaries of what tools like codex and claude code can do right now.

We do believe in the tech (in some regards, the extension is powered by similar tech), and we are power users of both, but we also know when claude code has said "You're absolutely right" one too many times and we need to dig in and get our hands dirty.

Post reply on HN