[jmadeano]

Could you share more about the dark pattern? That's definitely not my intent. No sign in is required for installing/managing scripts, sign up is only required to generate scripts (and that's because without it, there's no way to prevent abuse of e.g. spamming requests).

We tried to keep the setup process slim: Step 1 is install, step 2 is pin (I guess technically this could be moved later but in testing, without pinning it, users couldn't find it to do the other steps), step 3 is required to make it functional at all (blame chrome manifest V3). Would your preference be to sign up before that?

[brulard]

I had a simple scenario in mind: Hide annoying "shorts" section from youtube. It nagged me I have to sign in. I expected to be able to create a script for myself locally. Why would that lead to spamming requests?

[jmadeano]

> I had a simple scenario in mind: Hide annoying "shorts" section from youtube.

You can install the script above (copied here: http://tweeks.io/share/script/bcd8bc32b8034b79a78a8564) to remove shorts, no login required :)

> I expected to be able to create a script for myself locally.

When you click to generate a script, a (non-local) LLM assists with the generation. We have tried hard to make something work locally, but it isn't viable with current tech. I apologize if that wasn't clear from the post.

> Why would that lead to spamming requests?

The unfortunate truth of public launches like this is that there are always some bad actors/abusers. I've launched without auth in the past and been burned. Even today, I can see people spamming email sign ups, poking around different endpoints, etc.

Totally understand the friction that auth introduces, and I'm sorry for your experience.