some ideas extensions index

[w-e-w]

I have some ideas about extensions index

1. as we started to collect metadata of extensions, it is possible that we can Implement a opt-in feature that can automatically check for updates without fetching from individual repo
2. we can add an extra field in the extension entry that allows extension author to specify a specific branch to install
3. we should use repo username as a prefix or suffix by default for the clone path this would prevent any potential conflict for extensions that have the same name, and allow fork to be installed there is extension in particular bad name https://github.com/catppuccin/stable-diffusion-webui.git
4. add a new tag fork used by fork of extensions to differentiate, the name branch is not maintaining in the fork has taken over you it can have the fork tag removed

[ClashSAN]

5. Only show extension with tag option in webui
6. Remove Dropbar tag, too much to check them all, they are already the script

what is meant by 1 ? 2, 3, 4 all sound very good

[w-e-w]

fot (1.) see the master branch, it has last commit time of the master branch of the ext repo

[w-e-w]

if an ext is listed on the index webui doesn't need to fetch the ext repository individually instead it can just query this index,json and compare the update time and hash all at once they might be a 24-hour delay because matadata is only updated once every day but I think in this use case it's acceptable

the idea is to have maybe an option to automatically check this index on launch or when loading index.json

[light-and-ray]

7. Add field special_branch_for_gradio_4. If it's empty, use the regular branch. If it's not empty, use it for gradio 4 further release