Just to be clear, WordPress has the update servers hard coded. If they wanted you to use a different server, making it easily configurable by an end user would seem like the first step before cutting of access to a whole swath of IP addresses.
It is Open Source, right? It means everyone is free to change the source. Oh wait, but that’s hard. Much easier to just point your control panel at the original distribution and start the money printing machine while someone else is footing the bill.
There is no "control panel" to point. api.wordpress.org is hardwired into the source, and the implementation of that API is not open source. Matt has personally informed us that he is perfectly happy with this setup and has no plans to change it: https://news.ycombinator.com/item?id=41675671#41678014
So it's WPE's fault for not forking the ecosystem earlier?
Comments
Just to be clear, WordPress has the update servers hard coded. If they wanted you to use a different server, making it easily configurable by an end user would seem like the first step before cutting of access to a whole swath of IP addresses.
It is Open Source, right? It means everyone is free to change the source. Oh wait, but that’s hard. Much easier to just point your control panel at the original distribution and start the money printing machine while someone else is footing the bill.
There is no "control panel" to point. api.wordpress.org is hardwired into the source, and the implementation of that API is not open source. Matt has personally informed us that he is perfectly happy with this setup and has no plans to change it: https://news.ycombinator.com/item?id=41675671#41678014
So it's WPE's fault for not forking the ecosystem earlier?