all 10 comments

sorted by: hot top controversial new old
[–] 12 points 5 months ago (1 child)

Instead of running on every page, could you have it be triggered manually? For example, visit page, click extension > run.

  • source
  • hideshow 1 child comment
  • [–] [S] 1 point 5 months ago

    That's a valid option. The whole thing in my head was that it was supposed to be automated, and eventually figure out how to narrow down the pages where it runs. I know seeing the permissions to collect data on every page just sounds scary lol but I was hoping the fact that the extension isn't touching any kind of backend or anything external would balance it out. I will think about that though, thanks for the input!

  • source
  • parent
  • [–] 10 points 6 months ago
    [–] 8 points 6 months ago*

    That's going to be very useful! Can you post a link to your github/Codeberg repo so I can verify I'm able to run it securely?

  • source
  • [–] 6 points 5 months ago* (last edited 5 months ago) (2 children)

    not a customer, but you'd do well to state front and center whether or to what extent this was vibeshat. same should go for every "I built" post, imo.

    edit: typo

  • source
  • hideshow 2 child comments
  • [–] [S] 3 points 5 months ago

    So to play devils advocate about it all, is this just for anyone that doesn't want to support anything that uses any amount of AI, or is there a certain threshold that acceptable (would vary between people I assume)? I released the code to show that no data is sent or collected anywhere else, does it actually matter how the code was written?

    To be completely upfront, as I said in another comment I'm new to extensions as I only have worked on one before that is super super simple. So I did use cursor to get a boilerplate template started so I could figure out what I needed and what I had to work with. Then I used it to bounce ideas off of and had a couple different versions of how it worked before getting to what I have now. Was some of the code ai generated? Yep. Was some of it written by me? Yep.

    If the question was really, did I vibe code this over a weekend and just tell the agent "build me an extension" then no that's not what happened. I probably worked on this over a month or so in my free time, using cursor to figure out stuff I didn't know, and save some time of looking things up the old school way.

    If that turns anyone off to the extension, it's all good. This isn't a business venture where I expect any money to come in from it. I wanted to work on something useful and hope it proves helpful to anyone who tries it out

  • source
  • parent
  • [–] 5 points 5 months ago*

    Also, fuck js forms. Browsers can save form content, except on dynamically loaded/or named ones. And they are more brittle to boot. User experience, lol, what's that? Hurry and bolt the site out, using a dotzend frameworks to be faster.

  • source
  • [–] 3 points 6 months ago (1 child)

    Haven't browsers been able to store and recall form fields for decades at this point? How is this different from the built-in browser functionality?

  • source
  • hideshow 1 child comment
  • [–] [S] 4 points 6 months ago

    True, and I've used the browser auto fill for name/email/number or the extension Simplify that can build a profile to auto fill things like LinkedIn URL, GitHub URL, things like that. But I haven't had either save an answer for things like salary range, "name a project you worked on/proud of" things like that, plus a lot will ask the same question worded differently. Maybe the browser can save those, or premium Simplify, but I haven't seen it or done it so why not build something that helps me out and I can show off on my resume.

    I'm new to extensions so I'm open for any feedback I can get, just a broke dev trying to find a job in this job market lol

  • source
  • parent