I think it is a bit my own fault, for not explaining in a clear way, what the difference is between WordPress.com and WordPress.org .
WordPress.com is a specialized blog-hosting site, on which members can write their blogs, but which runs on professionally-maintained servers, by WordpRess.com .
But, the people behind this service have also made the PHP Scripts available for free, that run on the server, and that cause the HTML to be generated, which causes proper WordPress blogs to appear on the browser of the reader. People may download those, and may upload them to whatever Web-server they have access to, provided that that Web-hosting service, also supports the running of server-side scripts, by the Web-hosting service members. Some Web-hosting services put a lot of restrictions on what their members may publish, such as static HTML Pages only, or such as no access to any MySQL server, the latter of which WordPress.org uses actually to store the blogs.
And so, because this support-factor is the main part of the expenses incurred by WordPress.com, I will assume that sharing their core scripts poses no perceived threat to them. Their main expense is not, that core set of PHP Scripts. But, because an individual may have problems setting all this up as well, there is an associated Web-site, namely WordPress.org, where independently-hosted WordPress users can go for tech support, and to download plug-ins.
In addition to that, the early years of networking were such, that each computer on a network was able to have its own statically-assigned IP address, which means that I am referring to the years of networking before DHCP was invented. In those years, just like today, it was switches and routers that would act as the infrastructure to which all these computers connected. But unlike how it is today, whether any of those IP addresses had a Web-server running on them, was more or less an accidental feature of one computer.
It was never an accidental feature though, whether an individual could own a domain-name, which when true would also imply that when a browser is asked to open a URL that belongs to a registered domain name, the DNS servers subscribed to will be able to retrieve the IP address being referred to, and thus to access that Web-server openly.
And for this reason, it has always been easy for Linux users to install a Web-server on any computer. It remains easier to do so under Linux than it is under Windows. Further, it is also easy to install WordPress.org under Debian / Jessie, straight from their package manager, that depends on the Web-server being installed. When I wrote This Earlier Posting, I did not clarify what the difference was between WordPress.com and WordPress.org. There, I only wrote about ways in which the version obtained from the package manager, needed modification at the time, to run properly, as that version is also not the same as the version which people could just download as ‘a bundle of PHP Files’, and then upload to some hosted Web-server as such.
I can voluntarily disclose another oddity about Linux. Certain Linux users – one of whom I know – May Have instructed their package manager to install some software of interest, that happened to depend on some Web-server also being installed, for which reason those people may not be keenly aware, of the possibility that some of their computers do have Web-servers running.
This possibility is compounded by the fact, that under Debian, not every package that provides a Web-server – equally according to the package-manager – needs to be The fully-equipped Apache server. The package manager can sometimes list a series of alternative dependencies, any one of which will allow the package of interest to run.
So if certain Linux users were actually just installing a Web-server because that was being pulled in as a dependency, then theirs might be some minor, vestigial daemon that also hosts HTML Pages, but which I would not call a full-fledged Web-server either.
For myself, I tend to scan my package manager, against the risk of such a thing happening to me. If I see that a certain package I am interested in, depends in some way on one other package out of numerous available ones, I will try to think ahead of the package-manager, and do a full install of those other packages – of the packages of my choice – before proceeding with the install of whatever it was I was first interested in installing. And so I will also know that one machine should obtain a Web-server down the road, and I will make sure that it receives a powerful one.