ALL CAPS, SpOnGeBoB cASe, clap emphasis, and others carry specific meanings in colloquial written language, the use of other letterlike symbols can also. These should be presented in an accessible form to the user, rather than demanding that people refrain from using them.
And then there is Apple who pack everything I want in a sleek 14" or 15" device, plus a very fast CPU and battery life that is years ahead of anything else ... Why is there no competition here? I'm willing to compromise on battery life, and I don't need the fastest CPU, just a good quality work laptop where I can run `cargo build` / `docker pull` without worrying about filling up the disk, and mostly just a browser aside from that. Why is the gap so large?
I know many people still love MacOS, but it lost me a few years ago. I've also, frankly, had much better milage out of Dell machines than Apple ones over the last ten years.
On top of that, this isn't just a design that a person hasn't seen often, it's a denomination. Think of the 500 EUR notes, they were unfamiliar to many people.
Here is their full response from back then:
> Thanks for the submission! We have reviewed your report and validated your findings. After internally assessing the finding we have determined it is a known low risk issue. We may make this functionality more strict in the future, but don't have anything to announce now. As a result, this is not eligible for reward under the Bug Bounty program.
> GitHub stores the parent repository along with forks in a "repository network". It is a known behavior that objects from one network member are readable via other network members. Blobs and commits are stored together, while refs are stored separately for each fork. This shared storage model is what allows for pull requests between members of the same network. When a repository's visibility changes (Eg. public->private) we remove it from the network to prevent private commits/blobs from being readable via another network member.
> After some internal discussion, we have determined this is a known low risk issue. We may make this functionality more strict in the future, but don't have anything to announce now. As a result, this is not eligible for reward under the Bug Bounty program. Below is a reference to our instructions for users to remove sensitive data from a repository. https://help.github.com/articles/removing-sensitive-data-fro...
Are there different tax implications for settlements? Is this basically a stock buyback without being a stock buyback. Is it a more friendly dividend?
Is there any party directly harmed by this?
I'd say that Apple are directly harmed, by the court order to pay £385 million. I haven't seen any suggestion that there has been a transfer of shares as part of the settlement, so it wouldn't align with a stock buyback. Equally, this seems like the opposite of friendly, and the money involved here is tiny compared to Apple's dividend payments.