| ▲ | Tharre 3 hours ago | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
No it shouldn't. You don't break everyone's workflow just because some people refuse to take basic security advise seriously. > New API should have infrastructure for informing users and making sure they've read the message before proceeding. How would that even work? AUR packages are just git repos, everything that AUR helpers are doing or not doing is not under the control of the arch maintainers. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | harvie 2 hours ago | parent [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> How would that even work? Are you seriously asking how would sharing short text notes over internet work? If you need to be 100% git-centric, you can have git repo for messages. Client will then remember last commit displayed to user and refuse to continue unless latest message was displayed. BTW some AUR clients displayed ArchLinux RSS feed before... Too sad the issue is not even mentioned in the RSS feed... | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||