Our great sponsors
-
arttime
arttime is a CLI application that blends beauty of ASCII / text art with functionality of clock / timer / pattern-based time manager in terminal ⏰
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
So! I developed and published a software https://github.com/poetaman/arttime. Thinking it would be beneficial for users to be able to install it from home-brew, I published a package on homebrew. Recently I realized that there is problem. Unlike when a user runs install.sh from the GitHub repository, they don't get a crucial installation note that user need to manually take for software to correctly run. The only installation message homebrew's installer print from developer is called "caveats". But they won't let me add a note for new users to take a crucial step before trying to run arttime. Because of a legalism of what "caveats" stand for in home-brew's lingo. The lead of home-brew stepped in steered the conversation to irrationality. I requested them to remove my software till a satisfying solution is found. Then they started using "law", and because it is not written in law that they won't remove my software. And I have been told to add bloat code to notify the users from within the application to change their computer settings. This is definitely one instance where open source software publishing platforms have failed us. An open source developer should have freedom to stop publishing a software from a platform that is forcing them to add bloat code.
