Apple/macOS removed from official Unix registry
opengroup.org
opengroup.org
Traditional UNIX is does not mean having an open source core you're intended to tinker with. Traditional UNIX was entirely proprietary, connected with well-defined text-based interfaces. This is entirely orthogonal to user control and manipulation of the OS.
AT&T was forbidden by its consent decree from productizing Unix. Licensees received the source code, on an as-is basis, with no official support from AT&T.
As a non corporation end user with a sublicense from one of the above licensees (which is the apt analogy for an individual user in my opinion) you most certainly did not receive the source or have the rights to it.
You then likely hacked the source code to make it work on your machine.
I can understand that others might include the commercialization of the 1980s and the Unix wars as part of "traditional Unix", but even then, my IRIX system ca. 1990 supported end-user kernel extensions, to handle new types of devices. Our imaging hardware was not "connected with well-defined text-based interfaces".
It doesn't mean end users had access to the source code.
In fact, vendors would have been prohibited from distributing AT&T source code to customers who weren't themselves AT&T licensees, just as CSRG was prohibited from distributing BSD to customers who weren't licensees before 4.4BSD-Lite.
The same goes for most other proprietary source-available products. For example, game developers can't open source Unreal Engine projects even though Unreal Engine source licenses are available to end users for free.
At a bare minimum, you would almost have to have source to the vast majority of the kernel because there was no kernel modules. Sysgenning for a particular system involved compiling the kernel for that set of hardware.
I'm literally working on an early sun system emulator right now, heavily assisted by the standard sec tape that came with the standard software distribution of sunos, which has plenty of AT&T code.
As jeremyjh wrote at https://news.ycombinator.com/item?id=50032733 , "A system that the hardware owner cannot modify is not really on the same wavelength as traditional UNIX.". Since traditional Unix was source-available, with the expectation that people would hack on the source, I fully agree with jeremyjh's characterization.
I think you are talking about a later era in Unix history? The early Unix licensees were educational institutions and commercial sites, not vendors or resellers.
Every one of those academic and commercial end users got the source code.
From https://en.wikipedia.org/wiki/History_of_Unix :
> "In 1973, AT&T released Version 5 Unix and licensed it to educational institutions, and licensed 1975's Version 6 to companies for the first time, ... Anyone could purchase a license, but the terms were very restrictive; licensees only received the source code, on an as-is basis. ... Unix was entirely unsupported by AT&T"
From the same link, "Perkin-Elmer began distributing Wollongong Unix for Interdata as Perkin-Elmer Edition 7, the first version supported by a computer company". That was in 1980.
So while yes, "Traditional UNIX was entirely proprietary" and could not be redistributed to non-licensees, it was also provided with "full user control and manipulation of the OS", and not merely "connected with well-defined text-based interfaces", quoting jdiff at https://news.ycombinator.com/item?id=50033080.
SIP is as much defense from the likes of Adobe and Google as it is from more traditional malware.
I think that piece by piece Apple wants to go into direction of making macOS just a desktop version of iOS, that is closed and impossible to modify. They will use of course security as an excuse, the practical thing is that with iOS they succeeded because they went to the market with an OS that was already closed, but making users accept that in new version downloading a software from the internet and installing it it's no longer possible takes time. But they are getting there soon to me.
The reason why that won't happen (but more and more warning prompts all the time because of this modern world...) is because macOS is a self-hosted platform.
Apple _needs_ macOS as an unlocked OS at the very least as a development platform to develop their operating systems on. Not having the self-hosting requirements allows to tighten the security model a lot.
Notably, with a Unix terminal, a huge problem for sandboxing is how to determine permissions granularly, whereas a UI flow has significantly better answers to that.
Btw, MacOS 27 (the current version) still has UUCP.
the netbsd gallery (https://netbsd.org/gallery/) had a picture of somebody using that on windows xp (iirc) in order to compile pkgsrc packages in a "posix compliant" environment. the picture seem to be gone now :(
"1.12 Threads
1.12.1 Cancellation Points
Question 31: Which C stdio functions have cancellation points that occur when a thread is executing?"
https://www.opengroup.org/csq/repository/noreferences=1&RID=...
- The Linux kernel also has timer coalescing
- Linux also has lazy atime ('relatime') by default
- No Linux distro installs uucp by default, and certainly not suid
- Desktop distros will also run a file indexer of some sort
etc.
First, Linux was never GNU - the GNU ecosystem has always been a significant part, but if you were obstinate enough, you could get away without using any GNU tools (which is even easier today).
Second, you give just two examples. A few years ago we had a trend to rewrite everything in Rust with these newer tools usually not being part of the GNU project. Sure, you can replace everything now. However, most GNU tools are here to stay for a long time especially in enterprise distros where backward compatibility is important.
So no, Linux has never been GNU, and whatever fluctuations we had over decades with innumerable fights like egcs vs gcc etc., the GNU ecosystem is and will long be part of Linux distros.
25 years ago it was reasonable to say the typical Linux machine was “gnu/linux”. Today it’s not.
So legally at one point a Linux was Unix.
They were:
Inspur K-UX (expired on 3 February 2019)
Huawei EulerOS (expired in September 2022)
https://en.wikipedia.org/wiki/Inspur_K-UX
https://en.wikipedia.org/wiki/EulerOS
These were both based on Red Hat.
So, if you want your installation of macOS 15.0 to pass the UNIX® 03 certification test suites, you need to disable System Integrity Protection, enable the root account, enable core file generation, disable timeout coalescing, mount any APFS partitions with the strictatime option, format your APFS partitions case-sensitive (by default, APFS is case-insensitive, so you’ll need to reinstall), disable Spotlight, copy the binaries uucp, uuname, uustat, and uux from /usr/bin to /usr/local/bin and the binaries uucico and uuxqt from /usr/sbin to /usr/local/bin, set the setuid bit on all of these binaries, add /usr/local/bin to your PATH before /usr/bin and /usr/sbin, enable the uucp service, and handle the mystery issues listed in the four Temporary Waivers.
Then, and only then, is your macOS 15.0 actually UNIX® 03-certified.
This is batshit insane. I can guarantee you with 100% certainly not a single macOS installation in the entire history of macOS – let alone when just counting macOS 15.0 – has implemented even half of these changes. I’m sure there is a small number of people who have System Integrity Protection disabled permanently, and an even smaller number of people who have enabled the root account, and an even smaller number of people who have done both of those things – but that’s it. All the other changes are far too obscure and specific to be of any use to anyone.
> This is batshit insane. I can guarantee you with 100% certainly not a single macOS installation in the entire history of macOS – let alone when just counting macOS 15.0 – has implemented even half of these changes.
Well, maybe that means it doesn’t really matter and especially not to the extent that the author seems (?) to be making it out to be. If no one disables System Integrity Protection in order to be UNIX® 03-compliant, maybe that means that to the extent that people care about macOS being “a UNIX”, they don’t care specifically about the parts of the specification that are incompatible with System Integrity Protection.
There were (are?) companies and especially parts of the government where it was pretty difficult/impossible to purchase anything that wasn’t on an official pre-approved list. Trying to get anything new added was a massive problem.
One of the things that was on the list was something like “a computer running Unix“. Tada. Macs now run Unix so you can easily buy them.
Like other people here, I really don’t think true compliance mattered to basically anyone for their actual use. The idea that it was just box checking so they were easier to buy in some institutional environments makes much more sense to me.
I'll bet all kinds of government contracts needed some way to compare vendors bidding on a contract
for example:
- These ran UTX-32, Gould's version of Unix based on a BSD 4.2 kernel developed by Gould's UNIX development centre in Urbana-Champaign (IL) to support multiprocessor systems
- AIX is based on UNIX System V with 4.3BSD-compatible extensions.
- DG/UX 1.00, released by Data General in March 1985, was based on UNIX System V Release 2 with additions from 4.1BSD.
- HP-UX (from "Hewlett Packard Unix") is a discontinued proprietary implementation of the Unix operating system developed by Hewlett Packard Enterprise
- Xenix is based on the operating system UNIX System V, which Microsoft licensed from AT&T Corporation in the late 1970s.
So OS X continuing that strategy early on would make perfect sense.
Perhaps Golden Gate simply hasn't yet passed certification.
It takes several months for the certification to appear on the site. What would be newsworthy is if we see a release next year without this release getting certification.
Even better, last year's 26 releases are still undergoing the process.
Looking now, I see almost no uses of the word UNIX on the website except the docs archive, so I guess they’ve decided to abandon both the certification and the use of the UNIX trademark in macOS.
So Apple's use of UNIX in marketing was to make sure they never ran into that as a disqualified on a government contract. My impression is that those contracts largely no longer require that (one small measure of common sense has caught up).
Developed WSL and discontinued SFU (Windows Services for UNIX), which they had since NT 4 days.
The original POSIX Subsystem (psxss.exe) was Cutler's team who implemented a minimal POSIX.1 subsystem server alongside Win32 and OS/2. This was done primarily to satisfy US Federal Government procurement requirements (FIPS 151-2).
In these efforts they also tried to create successor languages to C, Alef and Limbo (for userspace), and never cared that much about anything past C89.
He has settled with Linux because that is the winner of UNIX wars, which predated Linux wars on Distrowatch.
As for the original UNIX,
"Using Unix is the computing equivalent of listening only to music by David Cassidy"
-- Rob Pike
Today? It's all Linux or Windows (of course, now also Web/SaaS). All these different Unices have fallen by the wayside in favor of Linux. Yes, some are still around but the mindshare has been in Linux for the last 20 years.
I suspect you could rip out a ton of autoconf rules and no one would notice.
If they are in fact dropping it, that’s why. But… Apple often “finishes” the enterprise features with a point release.
It is hard to find, unless one knows the technical details.
Then in WSL2 they just switched to using a VM, which is way more boring but probably less work to keep up with (I’m sure the Linux kernel has a lot of stuff that needs translating/implementing and it’s simpler to just use a hypervisor)
WSL 1.0 was a Drawbrige picoprocess.
Your confusion is natural among those that aren't into Windows programming.
Here are the links for the related information,
https://www.microsoft.com/en-us/research/project/drawbridge
WSL 1.0 architecture,
https://learn.microsoft.com/en-gb/archive/blogs/wsl/pico-pro...
What I care about, at least, are experiences of ease, convenience, compatibility, control, order, and freedom around a programmable system that invites the blurring of the lines between user and developer, between quotidian use and automation, and between decoration and reshaping. Such experiences still involve many of the same elements as they did two decades ago: a composable language of commands, commonly observed conventions, well-organized hierarchies of files, formal software freedom, powerful package management systems, great in-band/offline documentation, etc. But Unix certification isn't the center of gravity around which such experiences revolve, if it ever was. And for that matter, neither is macOS.
Was it delisted from a different “product standard”, or is this submission about macOS 27 not being listed?
Which is a damn shame, because AI dev is going to result in a massive influx of new software right when Apple makes it ever more difficult to do so on its platform.
I still make Mac builds, but it is more of an afterthought on a secondary Mac build machine now.
You know something has peaked when they become less open and more “clawbacky”; that is basically collecting interest on an investment (marketshare) instead of remaining more open (at the cost of some things). “Increased security” is always the rationale.
If the platform I use is an afterthought for you then your software becomes afterthought for me as well.
For those that don't know how to use a filter drop down, check UNIX 03 version.
The story behind macOS UNIX certification.
I just wonder if macOS will stop being UNIX like.
That is, whilst it still has home brew and a BSD core it’s great. If that goes away it’s no longer a viable alternative to Linux.
lima does, not colima (well it does because it's lima under the hood)
Imagine the only scriptability you get for the OS is Automator or Shortcuts, https://github.com/apple/container is at best an API at worst a GUI app and certainly not a CLI, and that's it. macOS is MacOS (pre-X). Or iOS-like. Terminal.app spawns a sandboxed Linux microvm. You never see the host from a shell. Dear colima can't even _exist_.
Neither Apple nor NeXT had a UNIX culture, and efforts like A/UX and mkLinux were never that much serious.
Had they acquired Be, BeOS was even less UNIXy than NeXTSTEP.
Edit: love how I get downvoted for facts?! They literally broke Cocoa so it was throwing hopeless useless exceptions at the bottom of the stack when they changed the native file open boxes to run in another process. Two bits of software I use couldn't raise an open file dialog window any more.
It’s insanely common.
Given that Windows made WSL in an attempt to capture developer mindshare, that tends to support his comment
The remaining differences are related more to systems stuff - managing daemons with launchd for example. These aren't really a distraction day-to-day.
The fact that someone who didn’t grow up at the time when open source was an idealistic concept instead of free support to corporations needs to learn about the gnutils and how to install them with homebrew is what makes me sad.
Why do we seriously not have a command-line package manager on macOS yet? Windows has one by now. It’s just sad to me that you need a manual checklist of post-setup steps to turn a Mac into a useful machine for software development.
At Apple, if you even use GPL tools in your workflow you have to seek approval, and most often there’s pushback of “why won’t this (alternative that isn’t GPL) work ?”
Their lawyers aren’t stupid, they understand the GPL and its limits, but they’re simply doing a risk assessment- which one is less risky, the GPL variant or the BSD. For a corporation, that’s generally BSD.
Apple is highly incentivized to keep devs on Macs, even if it turned out to be a loss leader for them.
Developers and operations people are already starting to move to Linux. More and more I see colleague either switching to Linux, or have a mac laptop for administrative tasks and then a Linux workstation, or VMs, where they do their actual work.
I’ve been in this industry for a long time now. Linux always had more credibility among devs and ops folk. This “starting to move” view is weird.
My view is that OS X was acceptable by these teams because it was close enough to Linux and corporate could deal with it.
When I worked in corporate IT Linux was simply not an option for a primary workstation because there was no standard configuration or management tooling that made everyone happy. Macs were an easy compromise.
https://wccftech.com/apples-private-cloud-compute-server-m5-...
I don’t think it makes business sense for them to mass produce these for a consumer market but a data center of M5 chips sounds amazing for the workloads they’re running.
I don’t think the open source model will ever make an Apple quality UI because that’s the result of highly opinionated executives like Steve Jobs who don’t need to compromise or allow customization.
I’m glad both exist. I use them both and my life is good
[1] https://blogs.windows.com/windowsdeveloper/2026/09/29/wsl-co...
Be mindful of living in an echo chamber. HN is one. There is a startup/SV-oriented culture here, which selects for a specific niche of people that is not representative of the general population. Going by this forum, you'd also think Java and especially C# were dead languages by how many votes and comments their threads get. Yet in the real world, Windows dev environments dwarf Linux, and Java/C# are everywhere in enterprise.
You might wanna look into that because that’s not how it works at all. I frequently switch between terminal and GUI apps and have not once noticed Finder failing to catch up with whatever it is I’m doing in the terminal.
And yes, they are different even at the user end on the shell.
In practice, anyone seriously developing Linux software on either macOS or Windows is using VMs or containers running the actual Linux kernel, at least for testing, and the difference is that Microsoft has put far more effort into integrating specific support for these things into the OS.
Writing on Mx Mac and deploying on Intel Debian is a little harder in the beginning, but spares you oh, so many footguns down the road. Eventually you might want to deploy to a different OS or arch for cost or convenience reasons. That's a really bad time to find out that your project can't be made to work there without heroics.
macOS as a more Linuxy-friendly place to work on Linuxy-type software, sure. Definitely true compared to Windows. But no one cares if macOS is blessed as Official UNIX.
How many people are writing software that they need to be able to run on Linux, Solaris, AIX, and HP-UX in 2026?
They probably also buy MacBooks since they’re reliable, performant, high-endurance (battery life) general purpose business laptops that employees like using and see good productivity with.
People care that macOS has a lot of compatibility with Linux/BSD, but most don't care that it's UNIX® - just as people don't care that Linux/BSD aren't UNIX® compatible. Yes, Linux/BSD are very similar to UNIX® and mostly compatible, but they don't conform to the specification.
You (probably) don't care about the UNIX® specification. You care that your MacBook has good compatibility with Linux/BSD infrastructure. Many people assume that Linux/BSD are UNIX® and just don't pay for certification. They aren't UNIX® compatible. They are extremely similar, but they don't follow the spec 100%.
Sorry for putting the ® everywhere, but people often use UNIX when they mean nix-like operating systems and when we're talking about whether people care about macOS as a UNIX® or not, it matters whether were saying "people want macOS to be UNIX®" vs "people want macOS to have good compatibility with nix-like operating systems such as Linux and BSD like it does today." People usually care a lot about the latter and not about the former.
Also the suggestion Apple was entirely removed is false; see https://www.opengroup.org/openbrand/register/apple.htm
It was Tahoe, it’s since been removed.
The UNIX03 page still lists it, but I believe that’s a mistake.
macOS has been removed from the main register/list.
Perhaps Golden Gate simply hasn't passed certification yet? It's less than a month old.
This is just a site rendering issue. Rather than silently removed, it's more like some bug was introduced. macOS 26 is still Unix 03 certified.
APFS is mandatory now. I recently used OCLP to coerce macOS 15 "Sequoia" onto my now-elderly 2015 27" Retina iMac. It's a capable machine: 4 cores, 32GB RAM, 1TB SSD as the system drive and 8TB HDD for data.
I kept my home directory on the HFS+ HDD. So, fast OS, slower but very capacious personal drive. It was a very simple hack and everything automatically obeyed. Worked fine up to Monterey (macOS 13), the last supported version.
Not now.
Lots of apps wouldn't run and the OS couldn't save lots of settings. I had to go through the first-login wizard every single time.
In the end I moved my home directory to the system volume on the SSD, and then moved all the big folders back out to HFS+ HDD (Documents, Downloads, Pictures, Music, Videos, etc.) This took 2 days of work but it did the job. Everything works now and the machine is noticeably faster, but now, I'm using 2x more SSD space and less HDD space.
The point being that the POSIX texts require setting classic Unix values on HFS+ drives, and I am not sure all of those still work on APFS, and that will make passing harder.
I think they might do it anyway, and soon, macOS 27, on Arm64 only, might pass... but in an even more wildly nonstandard config.
It was Stallman who came up with the name POSIX by the way.
They were CentOS Linux derivatives.
https://retrocomputing.stackexchange.com/questions/27095/why...
https://www.quora.com/What-goes-into-making-an-OS-to-be-Unix...
This is UNIX 03 certified OS with OSS alternatives from I gathered on internet :
- Apple OS X 10.7 - Apple macOS 26 , provide OSS Darwin 9 - Darwin 26
- Oracle Solaris 10 / 11 , provide OSS OpenSolais , then Illumos
- EulerOS 2.0 , based on RedHat Enterprise Linux / RHEL 7 and 8
- Inspur K-UX 2.0 , based on RedHat Enterprise Linux / RHEL 5
- Inspur K-UX 3.0 , based on RedHat Enterprise Linux / RHEL 7
At best a distro could be certified. But that certification would not automatically extend to other distros.
More than 1 Linux distributions have been tested, passed, and listed in the past... But you need to pay again every year, and recertify every new version, and they didn't bother keeping it up.
I described them and what this meant in some depth in this 2023 article:
https://www.theregister.com/software/2023/01/17/unix-is-dead...
https://www.opengroup.org//openbrand/register/xy.htm
I imagine that the cert will be listed for Golden Gate soon.
We just ssh/http to the real Linux machine that runs our things anyway. These days with commoditized VPN and symmetric residential Gigabit internet, that Linux box does not have to be in the cloud either (specially with LLMs guiding the sysadmin tasks).
Any thin client with a browser, an ssh client and an internet connection will do the job.
Sometimes just having a local machine that you can do everything on is what you need
https://web.archive.org/web/20261007103902/https://www.openg...
This suggests that different parts of the website aren't necessarily in sync with other parts, information wise...
And I'm not sure why it would be non-silently/loudly removed: is there an expectation of a press release or weblog post about non-certification?
Is this Apple just not wanting to pay for the certification anymore or does it actually change anything for us devs?
> Is this Apple just not wanting to pay for the certification anymore or does it actually change anything for us devs?
It's probably not about paying and more about tiny differences. Will it change anything for you? Almost certainly not. In fact, it might make things better for you. If anything, Apple's adherence to the UNIX spec can sometimes mean subtle differences in tools between macOS and BSD/Linux. Do you want things like grep or sed that conform to the UNIX spec or that work like grep and sed work in the real world?
And these differences are often small edge cases that don't come up much, but a spec is a spec.
The money is inconsequential for Apple, but at this point it probably makes more sense to just stop calling it UNIX and not worry about shipping a version of a tool exactly meets the UNIX spec - it'd be more useful for their users if it matched the behavior on Linux/BSD.
That grep/sed difference on mac caused me issues so many times, always thought it was just Apple doing their own thing. I didn't realize it was a spec thing.
Both aim to conform to the POSIX, but POSIX is a very spartan spec, people routinely use non-POSIX features without realizing it.
Tahoe, Sequoia, Ventura, and Monterey were in main list until October 7.
Can't figure out the reason.
Anyway, who cares. FreeBSD is Unix no matter what some standards organization says.
Standards are useful and the fact that these have lasted this long is IMHO evidence of that
For example, I once got in to an argument about how to handle code like this:
#include <stdint.h>
uint32_t rotate(uint32_t i, int bits) {
return (i>>bits) | (i<<(32-bits));
}
Whether this should return i if we rotate by 0 bits (like it does in GCC) was a discussion I had with the clang developers, and, lo and behold, we get this:If the value of the right [shift] operand is negative or is greater than or equal to the width of the promoted left operand, the behavior is undefined.
As an aside, this works:
#include <stdint.h>
uint32_t rotate(uint32_t i, uint32_t bits) {
return (i>>(bits%32)) | (i<<(-bits%32));
}
Because, as per the C99 standard:If the quotient a/b is representable, the expression (a/b)*b + a%b shall equal a
And:
a result that cannot be represented by the resulting unsigned integer type is reduced modulo the number that is one greater than the largest value that can be represented by the resulting type
Likewise, POSIX also means that every system call my open source code does, with the exception of chroot() and setgroups(), is defined in POSIX [1].
The entire environment to make my open source software only depends on POSIX utilities to build, and, indeed, it can build in both a Busybox based and a GNU based environment. For example, none of the filenames in my project have a `-` (dash) in them because, until POSIX 2024, one could not have a `-` or `/` in a filename used by Make, and yes my code builds with a strictly POSIX Make.
I no longer use Python for any of my open source because Python doesn’t have a stable standard to develop against; namely the Debian team got on my case I was using a Python2 script in 2020 when Python2 was made unsupported and I’m not going to play catch up should Python3 (or Perl) ever encounter the same fate Python2 has.
Instead, I write my scripts in Lua 5.1 these days. While Lua 5.1 isn’t a formal standard, the original implementation of Lua 5.1 (or a later version of Lua) has been implemented many times in many languages. There are two independent C implementations of Lua 5.1 in C, and there are also implementations in Go, C#, Javascript, Rust, and so on.
[1] /dev/urandom is also not defined in POSIX, but this is a runtime, not compile time issue, and writing a separate utility to put random bits in a normal file called /dev/urandom is one way to solve the issue.
linux compatibility is way more relevant now.
Given the amount and volume of software that mac has, the fact that almost all new interesting stuff are released for mac first or even mac alone, I also don't think it needs to attach itself to bigger names for platforms.
I think the financial burden of Ubuntu Mobile, Unity 8, and Mir; and the immediate rise of docker and WSL made canonical fully shift to server, so much so that their website no longer is about a better os for people, but what can it do for your cloud. Other distros also followed its path and Linus became all in on servers and IoT. I see windows as the biggest pile of trash in the world. Infinitely inconsistent, buggy, patched worked, visionless and rotting. Honestly that is one piece of software that is worse that AI slop.
And so what is there for Apple to compete with honestly? Haiku? Solaris?
I mean I don't disagree with that, but you're in dire need of a reality check wrt Apple's dominance
It's not even the most used OS. It's userbase has certainly grown over the last 20 years, but it's still at <30% on desktop...
There are however some demographics in which it's more represented, and that's probably just such a bubble where you're coming from
And if you're honest, macOS has sadly dropped in quality too...
But the reason why I wrote my comment was just that you gave off the feeling that you consider macOS to be the only relevant desktop operating system, which seemed like a very strange view to have given the reality of it's userbase.
Apple wants it to be more like iOS (so they can control what you do on it) while users want a normal computer they can do computer things on without it spewing ads or applying political pressure when someone tries to hold Apple accountable (e.g. the EU trying to make Apple stop abusing their market position).
You mean the second most used desktop OS with about 15% of the global consumer OS market? About 30% of consumer desktops in the US alone? That “irrelevant” macOS?
$ cat test.sh
var=
echo "${var+{\}}"
cat <<EOF
${var+\"foo\"}
EOF
$ /bin/sh test.sh
{\}
\"foo\"
$ /bin/dash test.sh
{}
"foo"
Note that they even ship dash as a much better /bin/sh...When it's about the fruit company, is there a difference? Unless it's for the eyes of the beholden i.e., le iFans.
(*) My lawyers have asked me to point out that the case of Regina vs Sex Pistols (1977) established that this term refers to a priest in Old English (https://en.wikipedia.org/wiki/Never_Mind_the_Bollocks,_Here%...).
> oh maybe using a Mac
If that’s what you get reading that comment then maybe ask your lawyer to pump some grey grease into the upper few inches next time you two are at a petrol err gas station.
> usually only needed for applications like FreeTube
No, looks like that won’t be sufficient. Pumping grey won’t be sufficient. Ask the lawyer to also do a “recent top posts on hn” search for you, assuming their marbles don’t yet melt at first sight of fruit company criticism/rant.
> you will struggle to find a need to do so.
Right. A member of the “you are holding it wrong” + “this is how it’s supposed to be used” genus spotted. Not your fault then. Here you go: yeah, you are right. Consider yours truly enlightened and in your immense intellectual debt.