> And I had to explain that it’s probably not possible, except if ios or Android implemented it directly (more so iOS, I’m not up familiar with android).
PDFs with embedded bitmaps can actually do that (and are currently supported widely, but PDFs are a terrible format with way too much attack surface). Same for any other composite html+whatever formats like epub. Standardizing a non-book format name and a spec that mandates nothing more than bare xhtml & image support with no JS or CSS interpreters would probably be quite sufficient.
> duckduckgo
Duckduckgo caches/proxies the images on its desktop site, which is useful when it gives results for sites that are since dead. Often at a lower resolution, but that's what reverse image searching is for.
That sort of malware already exists. This does simplify making it by a lot, because now it can much more easily ensure its portability without external communication.
The python script/program ultimately depends on a Python interpreter which currently has to be distributed as a different binary for every platform.
So in the end, the difference is purely where the platform-differentiated compilation happens for VM & interpreted languages like Java & Python.
This would instead allow you to ship a single Python executable that simply works everywhere. Whether with a bundled-in script/program, or just the interpreter.
> Well, another reason is because TLS (and formerly SSL) wasn't (weren't) just about encryption, but about a "web of trust." Encryption alone isn't trust.
Which is a nice principle, but given corporate and government incentives, the trust provided was lackluster at best. The PKI is pretty much broken because of it.
In the end, all it did is incur an unaffordable cost for hobbyist bloggers and other netizens.
You used to be able to simply install a Firefox extension[1] or Android app[2] and automatically steal the accounts of everyone on your wifi network on every website. https stopped that.
Widespread https did that. Firesheep motivated the big players to stop cheaping out and go fully https unlike approaches which did https for login pages only but it took let's encrypt also for https to become truly widespread
Yeah, in the end it’s silly that we ended up with “trust” meaning only you’re connected to someone that controls the domain” which doesn’t actually need PKI to accomplish if we just supported a SRV record with the public key(s) and verifiably authoritative DNS queries.
Which fair it’s trading one PKI for another but web servers vastly outnumber authoritative DNS servers. But DKIM gets along fine without it so we probably could too.
I've yet to watch the video, but it seems weird to see praise for steam heating systems to me when I've had literally nauseatingly overheated apartments due to it.
Was I just unlucky enough to have to cope with lowest-bidder systems?
There's nothing particular about steam heating that will cause overheating on its own; it works identical to any other heating or cooling system; there's a thermostat where you set the temperature and it turns the system on and off to maintain the temperature at its set point. You change the set point if you are uncomfortable.
Sometimes for multi unit buildings the landlord or super controls the heat for the whole building, that can be a case of the heat being set hotter than the occupant prefers, or perhaps just due to poor maintenance the system isn't maintaining temperature properly. I'm not sure why they couldn't just turn off individual radiators in this case though.
A properly set up and maintained steam heating system keeps temperature properly and doesn't overheat the occupants.
In NYC, the typical way this works out is that apartments on the lower floors get cold, because the buildings are uninsulated and hot air rises to the higher floors. They complain to the super, who cranks up the thermostat for the building until the lower floors are comfortable, and the upper floors are therefore stiflingly hot. Many people leave windows cracked open or even run their AC in the winter to overcome this.
I looked at an apartment that had steam heating via radiators in every room. The landlord was very adamant that the tenants were not to adjust the radiators. My guess as to why is that turning one off/down could make the others hotter.
Reading up on some of the links provided in this thread, I think that would indicate a badly maintained system/too much pressure.
And I'm now quite sure I had to deal with a single-pipe system modified to not have individual valves. Quite insane, but I guess that's what cheap owners will do.
PDFs with embedded bitmaps can actually do that (and are currently supported widely, but PDFs are a terrible format with way too much attack surface). Same for any other composite html+whatever formats like epub. Standardizing a non-book format name and a spec that mandates nothing more than bare xhtml & image support with no JS or CSS interpreters would probably be quite sufficient.
> duckduckgo
Duckduckgo caches/proxies the images on its desktop site, which is useful when it gives results for sites that are since dead. Often at a lower resolution, but that's what reverse image searching is for.