Hi,

The package’s defaults and configs are intentionally general and aimed at common, widely used setups. Users who need something different can easily adjust them.
As mentioned before, I plan to keep updating it with more features, but I don’t live my life around this single package — still, both I and people I know find Hyde-Ext useful.

It is intentionally designed to install a prebuilt binary to speed up installation. If someone prefers building from source, they can get the source from GitHub and build it themselves. I also plan to publish a -git AUR variant, similar to what’s done for hyprproxlock. The binary is built using a GitHub Actions workflow.

The missing description was due to a prior workflow issue. In my opinion, most users check the project’s GitHub or website before installing from AUR, rather than relying solely on the PKGBUILD description. Everything is still in line with AUR rules.

Lastly, I could be mistaken, but it seems like matthewq337 has been submitting nearly identical reasons for multiple packages, often with very brief and generic justifications.

Regards,