jof

SSL was developed by Netscape in the 90s and evolved into TLS. Netscape Navigator essentially evolved into Mozilla.

"They've" been at it from the beginning, so it somehow seems understandable that Mozilla has a lot of "SSL" momentum or carryover.

It seems to me like the underlying issue was ignoring HTTP semantics and making a state-changing link like a logout link a plain <a> (HTTP GET) and not something like a form submission (HTTP POST).

Having intuition for the foundational layers of our tools saves so much time and future headaches.

Make an LED blink.

Then, connect an RGB LED and experiment with PWM signal generation.

Then, experiment with network programming, accepting a UDP packet to the ESP32 that sets the color of the RGB LED.

Could it also be, with the advent of Satellite SOS, that Apple is starting to explore non-conventional mobile RF protocols, and that Qualcomm's product offerings are only really geared towards generic, standards-based mobile networks.

The GPS P(Y) and Military codes exist to (hopefully) prevent spoofing.

This probably leads to a great user experience.

However, if this catches on, SMS sniffing over the air is going to really pick up! :p SMS messages are often carried over GSM control channels, generally unencrypted over the air.

Even when they are encrypted, it's only A5/1 (already broken).

Recall that Visa and Chase are major investors. It's rather difficult to "eat their lunch" with them on your board.

As one of the volunteers operating the existing Market St. WiFi and the housing project WiFi, I can say that this is definitely being discussed and evaluated, but I don't have a lot of hope for the Department of Technology making anything happen.

They have deeply-rooted relationships with large telcos and utilities that have granted them good deals on easements to lay their existing fiber and copper paths. If the city started offering competing services for money, it would throw those relationships in jeopardy.

It's really too bad, as a lot of the dark fiber resources are already in place to build a decent backbone that could support radial paths out different neighborhoods. However, there's very little technical clue (if you're a competent network engineer in the Bay Area, why would you work for a city? ick.) and political capital/gumption towards making this happen.

The layer 0 - 7 stuff is easy. It's layer 8 and above (money, politics, humans) that make this hard to accomplish.

If you're an SF resident, call or write your supervisor. Let your opinion be heard and demand proper infrastructure!

Fiber is becoming the new roads; how you get your product to market. Municipalities need to step up and get building, because the big utilities and ISPs sure as hell aren't.

Well, let's just say it's an architecture Square knows well. :)

Jekyll? There's not much more than a repo and text files on the admin side, but enables super-fast blogging on light hardware.

This is _exactly_ what Aircell does in the US. I'm not sure what spectra they're using, but the bandwidth would likely be quite variable, as planes with non-directional antennas will interact with one another over wide areas. Weather could also play a part, depending on the frequency.

I haven't run across or know of any tutorials on this exact problem, but I think you're right that you'll end up doing a lot of the synchronization yourself.

You might check out PubNub and other messaging services. PubNub is a stackmob partner product that can be added in their marketplace. That would provide for a component to handle transporting messages and state information between your document editors.