HN2new | past | comments | ask | show | jobs | submit | Zeebrommer's commentslogin

In the North Atlantic most paths are slightly curved to take the most efficient route (taking curvature of the earth into account). There is one prevalent route from Gibraltar to Florida that is straight as an arrow though. What is up with that?


I know it does for a small Dutch setup :) https://www.kalamatakarma.com/ Marketing is still completely word of mouth afaik, but the webshop makes it easier for total strangers to tag along.


Or ending it with the same salute involving the name of the leader, for that matter.


Standard US cryptographic protocol during the same time period was to begin and end every message with a few random words specifically to thwart such attacks.


Which accidentally caused a bit of a rift in the US Pacific Admiralty: https://en.wikipedia.org/wiki/The_world_wonders


Seems like an interesting conundrum. If you encrypt all transmissions, you end up having a lot of boring repetition, like weather and sign offs to just fill space. But if you don't encrypt the boring stuff, then the transmission itself is a nice signal of something interesting about to happen. But if you try to just pad with completely random noise, the other end might worry they've decoded something wrong and ask for a new cipher pad increasing the chance of interception. So maybe they should have tried to find something almost random but with known structure instead of sending the weather? Seems similar to how we now know that choosing a random password from the dictionary adds encoding redundancy without reducing security. Or similar to the goal of getting ordinary people to use Tor for ordinary things?


In modern crypto it’s solved by using random nonce to star with and by using (encrypted) hash of data at the end. Random nonce gives you different cypher text for same inputs, hash tells you if you actually decrypted what was intended.


Isn't that why we have PFS now?


No, PFS is to ensure communications aren't compromised even if the server's private keys are compromised afterwards. It has nothing to do with mitigating known plaintext attacks. That's already mitigated with techniques like randomized IVs.


So-called perfect forward secrecy uses temporary keys so that eavesdropped logs can't be decrypted after those keys are discarded. To prevent known-plaintext attacks and/or statistical analysis, data entropy must be equalized so that patterns won't be apparent even before encryption.


No - our actual encryption primitives work better, and don't suffer from this problem. (Other comments give an explanation of what PFS is actually for).


A bit like Anathem.


Is someone even trying to open source that type of content (routes, pois)?


Open Street Map.

But otherwise this is really something that tourist organisations could champion, in combination with national mapping services. It's not like the routes are somehow obscure, or user-generated they're often national trails strung together. Switzerland Mobility is a good example of this. You can also hook official weather providers. The fact that we need private apps is bizarre.

https://schweizmobil.ch/en/switzerlandmobility-app


I know of this eu effort for long distance bike routes: eurovelo.com, but it's government afaik, not open source. I don't think anyone is doing it.


From experience, the bread has a better rise when I feed my starter for three or more cycles/days after storing it in the fridge. As if it needs to "wake up" and increase its speed of metabolism.


I agree that most leaders will now they are fallible, and also have some idea of which things are problematic. As an inexperienced leader, I still valued getting "known feedback". It gave me a better idea of which problems were growing too large, and which ones remained minor annoyances. In addition, acknowledging the points that were brought up and explaining why I hadn't gotten to addressing them (besides being human) usually gave the person giving the feedback a more positive outlook.


Rust is getting there, but I don't think it's production ready yet: https://github.com/esp-rs


That's an interesting idea, you'd probably be able to know ip addresses via wireguard. Protocols like CoAP or SenML can be used to keep payloads small.

MQTT, aside from being pubsub, has more functionality that is especially useful in IoT though: robust sessions with LW&T to monitor onlineness, and retained topics to deliver messages as devices come online again


I'm curious which lost land you are referring to.

Building skyscrapers on former swamps is indeed difficult.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: