First of all, It's great that users can set personal priority levels for websites. This helps in organizing and accessing frequently visited sites more efficiently.
I think Kagi can be benefit from introducing more detailed priority levels to improve the granularity of website prioritization. Maybe something like:
- Pinned
- Higher
- High
- Low
- Lower
- Blocked
Consider a scenario where you're searching for documentation on a specific library, such as the Golang's Echo web framework. This is not a site you will always look up, so it doesn't make sense to pin it, especially when there's limit on the number of pinned websites. Currently, with github.com set to a higher priority, a lot of the documentation website may require several scrolls to access, which is definitely not the end of the world, but still is few extra keypress.
If I set github.com to high but not higher, I want to see it being upper than other general search results but not higher than the official documentation page, which is the most relevant search result as a user. Since I don't really understand how Kagi's prioritization works, I understand this sort of decision may be impossible to be made Kagi side but still, I think it's worth a consideration.
