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.
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.
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).
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.
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.
In my favorite static analysis toolset (Radare, http://radare.org/), there's a nice feature similar to this. It "zooms" out on a big file by summarizing portions of it into chunks and displaying colored ascii characters in a chart to represent the block.
With the entropy and ASCII printable filters setup, it makes repeating patterns and TEXT sections pretty clear.
There are a couple of factual errors in this piece that I feel obligated to point out:
1. The root DNS server pool only hosts glue pointing TLDs to other pools of servers that administrate those TLDs. No amount of pressure on ICANN or the root server operators can debilitate a single non-TLD domain name.
2. Not all registrars and/or TLD operators exist in the US. All it would take is doing business with an international registrar that doesn't agree with the rules to circumvent DNS tampering laws.
3. In theory, ICANN already requires registrants to maintain accurate information in WHOIS. Registrants should be receiving annual notices from registrars to remind them of this fact. We can all see how well this is working. :p
The issue with providing "identity" to register a domain is that there's no portable, international way of doing so. What does an "identity" consist of? A name?
There's plenty of good discussion on this topic in the nymwars.
However, I do agree with SOPA being a red herring, and it's unfortunate that big. Players are still planning a blackout even though the legislature is already backpedaling on the worst bits of the language.
What if next month the DOPA (Decapitating Online Piracy Act) bill comes along and it's much worse. Would big sites be willing to continue shutting down their services for each crazy bill that comes around?
I feel like the endgame of the US futzing with the Internet will just result in other, international bodies taking on the operations of core infrastructure (a la The ORSN project; Vixie saw SOPA coming!), edging out US influence on this medium that the whole world enjoys.
There are a couple of factual errors in this piece that I feel obligated to point out:
1. The root DNS server pool only hosts glue pointing TLDs to other pools of servers that administrate those TLDs. No amount of pressure on ICANN or the root server operators can debilitate a single non-TLD domain name.
2. Not all registrars and/or TLD operators exist in the US. All it would take is doing business with an international registrar that doesn't agree with the rules to circumvent DNS tampering laws.
3. In theory, ICANN already requires registrants to maintain accurate information in WHOIS. Registrants should be receiving annual notices from registrars to remind them of this fact. We can all see how well this is working. :p
The issue with providing "identity" to register a domain is that there's no portable, international way of doing so. What does an "identity" consist of? A name?
There's plenty of good discussion on this topic in the nymwars.
However, I do agree with SOPA being a red herring, and it's unfortunate that big. Players are still planning a blackout even though the legislature is already backpedaling on the worst bits of the language.
What if next month the DOPA (Decapitating Online Piracy Act) bill comes along and it's much worse. Would big sites be willing to continue shutting down their services for each crazy bill that comes around?
I feel like the endgame of the US futzing with the Internet will just result in other, international bodies taking on the operations of core infrastructure (a la The ORSN project; Vixie saw SOPA coming!), edging out US influence on this medium that the whole world enjoys.
There are a couple of factual errors in this piece that I feel obligated to point out:
1. The root DNS server pool only hosts glue pointing TLDs to other pools of servers that administrate those TLDs. No amount of pressure on ICANN or the root server operators can debilitate a single non-TLD domain name.
2. Not all registrars and/or TLD operators exist in the US. All it would take is doing business with an international registrar that doesn't agree with the rules to circumvent DNS tampering laws.
3. In. Theory
"They've" been at it from the beginning, so it somehow seems understandable that Mozilla has a lot of "SSL" momentum or carryover.