Maybe its time to boycott Conservancy and #fosdem until such time as they're no longer promoting GAFAM. I understand that the history is complicated, but in 2020 we now have a very clear picture of how toxic those companies are in a multitude of ways.
The oldies like me need to remember why they originally resisted Microsoft, and not end up rationalizing away similar or worse abuses coming from Google and Facebook. In a lot of ways the problems created by those companies are much more existential than a sweating Ballmer hurling lawsuits and office furniture.
We were not aware that @conservancy is financed by Google. Thanks for pointing this out!
The choice of including the Software Freedom Conservancy (SFC) in the paper was inspired by the role of Bradley M. Kuhn in the creation of the Affero GPL (https://sfconservancy.org/blog/?author=bkuhn).
Since an involvement of Google conflicts with our standards (as stated in our statute https://wiki.f-si.org/index.php/F-Si_Statute), we have removed the SFC from the white paper. Anyhow, they have not provided any feedback to it.
Just got proxy fall-through to Express middleware chain on 404s working in node-http-proxy and http-proxy-middleware… now working to implement it properly in forks of those packages to include in the next version of Site.js. This is going to open the door to a couple of very exciting new abilities ;)
If you’re already running Site.js, just use:
To update it to the latest version.
If you’re running it in production, it will automatically update within the next hour.
If you haven’t tried it yet, you can install it and have it up an running in the next 30 seconds from https://sitejs.org
Just a quick update in case you miss my other toots: this fix has now landed in apt and it’s now safe to upgrade to Pop!_OS 19.10 again.
w00t! Cooking on Pop!_OS 19.10 gas.
(Once the System76 folks fixed the bug I reported with the installer and released an update in record time and once and I figured out how to revert my packages to stock 19.04 – hint: aptitude is your friend – the actual upgrade process was buttery smooth. Great job on pop-upgrade, folks.)
Any idea why I’m getting this error while trying to compile pop-upgrade (it’s a Rust app): https://github.com/pop-os/upgrade/issues/81#issuecomment-576454277
Anything obvious I’m missing? (still in trying to upgrade my Pop!_OS machine from 19.04 to 19.10 hell).
@aral And yet people buy it. The one I've talked to about it do not seem to care about theire privacy. I don't get it.
@aral The answer from Amazon's spokerperson is priceless: "We’ll continue to invent more privacy features on behalf of customers.". You don't need to "invent privacy features" if you're not spying on people in the first place!
Amazon Echo’s privacy issues go way beyond voice recordings
Warning: if you haven’t updated Pop!_OS 19.04 to 19.10 yet, wait until this bug fix lands before you do: https://github.com/pop-os/upgrade/pull/82
I’m currently running some sort of half-broken Frankenstein 19.04/19.10/half-Pop!_OS/half-Ubuntu hybrid.
Issue, with details: https://github.com/pop-os/upgrade/issues/81