Me: When you respond "guillotines" what do you expect the campaign volunteer reading the response to think you're advocating for?
Me: Whose murder do you expect them to think you are advocating for?
Them: The richest people in the US.
Me: 0.1%, 1%, 5%?
Them: I think billionaires is a good cutoff. There are 540 in the US. So, the richest 0.000164%.
Me: Is executing them your first choice? Or would you prefer to see non-violent redistribution?
Is your objection that having this much money is immoral when others need it so much more, that you can't be this rich without having committed serious crimes, or something else?
Them: I'd certainly prefer a non-violent solution. Redistribution sounds lovely.
My objection is that we do not have anything remotely resembling a democracy. And I think that having that much money is actually immoral, while 21% of the children in the US are below the poverty line. Putting them together, I think it's a fine solution to kill them off until they can figure out how to release their chokehold on our government.
And it seems to me, solutions within the system have been adequately tried.
The Facebook side of the discussion on the insulation post was very helpful, and got me thinking about putting closed cell foam panels directly against the concrete walls. Because it's both a vapor barrier and efficient insulation it reduces the risk of condensation happening between the concrete and the insulation.
I'm less sure about what comes next. Whatever I'm doing is not structural, and there are a lot of trade-offs. All of the options involve the layer of closed-cell foam directly against the concrete, but then they vary on how they're finished. Standard options:
I hired a mason to redo the cinderblock and a carpenter to replace the roof. The mason has finished, and I'm waiting for the carpenter to start:
Peter Snyder of Brave recently wrote a post on the proposed WebBundle specification arguing that it makes URL randomization easier and so is harmful to content blocking. The core of the post is incorrect, however, and based on a misunderstanding of what can be done today and what WebBundles make easier. Snyder and I discussed this some on HN and I wanted to take a step back and try to write up the issues more clearly.
A WebBundle (see explainer) allows you to serve a single file that the browser can treat as multiple files. This solves many long-standing problems, some of which I've been working around for a long time. A classic one is that many sites will have a large number of small files. Everyone who visits the site will need essentially all of these files, and you lose a lot of performance in individually requesting each one. When I worked on open source web page optimization software (mod_pagespeed) it could combine CSS, JS, and images so the browser could request a single 'bundle' for each, but it was not ideal:
|Code||Apartment Price Map|