Wildcard domain matching support

[niltonfrederico]

Details

Hello! How are you doing?

Loved the extension, it is saving a lot of minutes daily!

Is there any plan to add a wildcard domain matching feature? I'd like it very much. I saw an earlier issue that had some discussions, but I think it never got implemented, is that right?

If it is part of your backlog, I can give it a go on implementing it!

[smashedr]

While I do want to add the feature, I have not personally had a need for it yet, which is the only reason it does not yet exist.

Personally, I wont have time to do this anytime soon; however, I do plan on re-writing this extension in TypeScript and Vue3 using the WXT framework. This will allow me (and anyone else) to easily make updates, and add locales for other languages.

I wrote a web extension for a friend as a test and so far so good: https://github.com/cssnr/geo-image

Current Re-writes:
Finish Cache Cleaner (almost done): https://github.com/smashedr/cache-cleaner
Hopefully Finish Link Extractor: https://github.com/smashedr/link-extractor

---

If you want to give this a go, feel free, and I will support you; but I do want a solid solution as I use this every day personally (even tho I never notice it), and it surprisingly already has over 5k DAU.

All the processing happens in 1 massive function: https://github.com/cssnr/auto-auth/blob/master/src/js/service-worker.js#L33

const creds = await Hosts.get(url.host)

But I wrote a custom class to store credentials to get around the Snyc storage size and key limitations. So credentials are gotten via 1 function: https://github.com/cssnr/auto-auth/blob/master/src/js/export.js#L26

My thoughts are, maybe add a setting to allow wild card hosts, which would have to disable hostname validation (and allow a wild card character, like *). Then, if a host has a * in it, call a getWildcard function, vs a get. But I just looked at this at a glance while writing this, don't use these as hard instructions.

EDIT: Also, its important I note how I hacked the sync storage. I store every host under a letter/number key of the start of the hostname since you are limited to 512 keys, and each key has a max size of 128kb, this splits all the hosts up somewhat evenly across 36 keys. So if we did do wild cards, we would probably want a wildcard key to store all wildcard hosts in. But ive not looked at this in detail, just brainstorming here...

[niltonfrederico]

I'll take a closer look and get back to you! Thanks for the pointers!

[smashedr]

Sounds good, feel free to ping me in discord: https://discord.gg/wXy6m2X8wY

I was actually thinking about it today, I will probably see about porting this to TypeScript + Vue3 this afternoon. It wont be done this afternoon, I just want to see how hard it will be and how far I can get. I will keep you posted on the progress.

That being said, I don't plan on changing any of the logic. I will let you know how it goes...

[smashedr]

Just a heads up, I was able to make good progress on the TS+Vue3 conversion. I got authentication fully working and added the hosts table. I just need to finish adding all the options.

I will make a roadmap when i get a chance. The source code is currently in this repo:

• https://github.com/smashedr/auto-auth

[smashedr]

Quick Update. I made good progress on the new version. Its almost done and ready for testing.

I am currently using it. I exported my credentials, disabled the live one, and installed the new one, then imported them. It is also fully localized and currently supports English and Portuguese (Brazil).

You can download the latest release here: https://github.com/smashedr/auto-auth/releases/latest

I also added you as a contributor to the development repository.

[lxiange]

Super helpful project. I was planning to vibe code a similar plugin, but this extension is definitely well fit my use case.
I also want the Wildcard domain matching support. The background is, i'm hosting a couple (~20) sub-domains at home, and they are using same credentials. It will be helpful if I don't need to type them one-by-one.

If you don't have time on this feature, maybe I can contribute a bit.

[smashedr]

I will take a look at this tonight or tomorrow and see how much effort it will take.

[smashedr]

@lxiange I drafted a PR with the help of everyone's best friend to see what it would look like.
I still need to do some more testing, but what testing I did worked quite well.

At least check out the matching pattern and let me know I am on the right track...

We can continue the discussion on my PR Draft #25