Just because people use the app doesn’t mean they like the name.
Just because people use the app doesn’t mean they like the name.
They are not telling the author they can't call his app whatever they want. They are saying they will not sell it in their app store under that name.
And that's the bargain you enter into when you sell in a walled garden ecosystem.
But they were indeed selling it under that name for 6 years!
How would you like it if you spend a lot of money to advertise your company or product and create a brand value to it, to one day Apple telling you that they would like you to change the name or they will not distribute it on their store?
Yes, the app store is a closed environment where they can dictate some terms. But don't forget that the developers PAY THEM to use it, and as such their terms cannot trump the consumer laws that exist to protect against such abuse. (By the way, "my shop, my terms" have already faced legal scrutiny some of which were found to be illegal - popular ones include refusing to serve people of colour or gays.)
So they are in fact telling the author that he can't call his app whatever he wants. Because if he does, they will do everything they can to prevent anyone else from ever using that app.
People keep saying that but nothing on my Mac has ever stopped me from installing whatever software I want. I wish people would stop repeating this lie.
I remember Apple revoking Epic's access to Apple's developer tools because of a disagreement over their developer program TOS, but that only stops Epic from using Apple's tools. It does not prevent me from installing any software.
I have a ton of software on my Mac that's not part of the Apple developer program and the developers have never asked Apple's permission nor given Apple any money for the software and Apple has never once tried to block those developers from creating that software or me from installing and running it.
You might be able to bypass the notarization requirement as an end-user, if you have enough technical know-how, but good luck explaining that to your customers. Especially when all the dialogs are calling your software malicious, untrustworthy, etc.
This is not exactly true and you know it. For example:
>if you have enough technical know-how
You right click the app and then click open.
>Especially when all the dialogs are calling your software malicious, untrustworthy, etc.
Another lie. The dialog says "this is from an unidentified developer" and does not say anything about being malicious or untrustworthy. What is your beef with Apple that you're so willing to say so many outright lies on a forum filled with people who know better and can call you out on it?
Windows does this with UAC. Many Linux distros require executables to be explicitly set with the +x flag. macOS is not unique in this, and like with the other OSes it's a security feature.
Check out the warning and "bypass" for yourself: https://www.macworld.com/article/3140183/how-to-install-an-a...
> Beginning in macOS 10.14.5, software signed with a new Developer ID certificate and all new or updated kernel extensions must be notarized to run. Beginning in macOS 10.15, all software built after June 1, 2019, and distributed with Developer ID must be notarized
GateKeeper will also flag your app as malicious and having the potential to damage your Mac if Apple revokes your certificate, which they have done in the past by mistake.
This isn't unique to Apple. Debian and other Linux distributions have also had similar discussions when considering the distribution of packages with obscene, morally repugnant or inappropriate names, as well as the package contents themselves.
Whether it's a commercial entity or a volunteer organisation, there are considerations regarding image and reputation. People can and will push the boundaries of what is acceptable, and somewhere you're going to have to draw a line.
Edit: This keeps the computer awake until 6 PM each day.
caffeinate -u -i -s -t $(($(date -j -f "%a %b %d %T %Z %Y" "$(date +"%a %b %d 18:00:00 %Z %Y")" "+%s") - $(date +%s)))If a thing isn't bad, then it isn't, and if someone is ignorant and makes associations and assumptions that are wrong or unsupported, then I'd rather add my tiny influence against that rather than help it.
Or do you yourself do the same thing to your clients? What features of your clients do you use to prejudge them and make unfounded assumptions about them? Should your clients worry what clothes they wear in case you think it means they are gay, which maybe you associate with having Aids... Personally I woukd think things like that are none of my business but apparently you don't think like that.
Please don't smooth the way for the wrong things. I can't demand, obviously, that's why it's a request with the word please.
It seems to be a small thing but big things are made out of small things, and you and I can only do small things. All we have is the choice of which kinds of small things we do.
There is a command line tool called caffeinate that ships with Mac OS. Maybe Apple didn’t like somebody using something so similar their system utility name.
Originally I thought it was the same name, so this seems much less likely now that they're merely similar.
I removed Caffeine from the App Store when Apple started complaining that a click on a menu bar icon for an app without a dock icon must always show a menu (offering a Quit option). I wanted it to toggle the active state instead and show the menu on right-click/cmd-click.
> Amphetamine updates have been rejected by Apple on numerous occasions. One time, Apple’s App Review Team did not like my “Preview” screen shots. Another time, Apple objected to the default behavior when clicking Amphetamine’s menu bar icon, saying it must open the menu by default and not start a session.
It's a neat idea but that is just not the use case the menu bar was designed around and I don't think it makes sense for individual apps to go against the current in that way
Good for you! That is exactly what everyone needs do when Apple starts being pointlessly petty. Yes, operating systems have UI guidelines. But they are guidelines - sometimes a developer may come up with something better, especially for power users, and no such developer should have to waste time trying to communicate and convince some committee of this, and worse, wait for an approval from them to launch the product.