349 karma · joined May 5, 2018
[0] "real" as opposed to provider that has a great WP-related pitch but in-reality this is just a regular shared hosting with no actual wordpress oriented optimization/enhancements.
have you checked the REST endpoint?, namely site.tld/wp-json/wp/v2/users
By default all user names are exposed that way.
There actually was a change in Polish legislation - Telecommunications Act 172.1 (Ustawa Prawo Telekomunikacyjne art. 172 par. 1)
Users almost universaly don't care. This also applies to businesses, C-levels and managers. However, while they don't care it affects them indirectly as they end up using bloated sub-optimal software possibly with bugs and sometimes significantly slower than in could be. It then affects their productivity as well.
My point is that one could at least try educating the non-IT decision makers why it's important. My team has successfuly convinced the CEO that 2 month long refactoring project is really important and that while it won't directly affect the functionality it will increase productivity of the our team in future by making the team more productive and allowing for faster implementation of new features in the future. From my experience the "technical debt" metaphor is great for explaining such things to business oriented people. That metaphor is usefull because it is compatible with other debt related metaphors, like interest rate or refinancing. We could explain extra time needed to implement stuff in non-refactored bloated codebase as an interest-rate.
Also, the use of car-related analogies is quite effective.
My point is that while users don't care about the technological intricacies, the effects can be explained by the use of metaphors and concepts that they know well.
On the other hand given how sophisticated these things are , even if all the source code is available you can't be 100% sure to spot all the bugs/vulnerabilities/backdoors. I guess this applies to hardware equally well.
[0] For example,archive storage at OVH runs at 0.0026$ per GB, so having a backup of 4 million 1mb sites would cost 1.04$/month for three copies of data.
X-Unnecessary-Header-0: [random-string]
X-Unnecessary-Header-1: [other-random-string]
...
This could be enough to insert random-length noise without the need to invent any new protocol. Of course this would only be effective for smaller packages as I assume that headers size is limited and as a result this would significantly change the perceived download size only for smaller packages.you could imagine a situation where https would be optional for APT mirrors. Then the package manager would have a config flag to use any mirror or only https-enabled mirrors (probably enabled by default). This would allow to use https without creating any demands to organizations that host those mirrors - if they can they would enable it, but it would not be required. The https-enabled hosts could also provide plain http for backwards compatibility.