orbisvicis
Joined 3 years ago
Joined 3 years ago
Best I can do is some high-school mumbo-jumbo about farming and specialization furthering wealth acquisition.
But to truly comprehend the situation I'd have to study economics and current events and sociology and even then I think it's a lot of theories and sometimes when I hear economists talk I wonder that it may not be coming out of their mouth.
The motive seems to be a naive process that enqueues a message and then commits to a database - two independent actions. But a well-behaved process would commit to a database, and then only if successful enqueue a message. That's better but still not atomic - commit, crash, and no message queued.
So the solution is a two-table write - the outbox pattern. But the process that reads the outbox must commit both a query and delete before sending the message. That's the same risk as the agreement well-behaved program - commit, crash, and no message queued. Except now you introduced another pipeline element so your overall complexity increases, and so too risk.
What if you never delete messages from the outbox? Well, what you have now is no longer an outbox nor a database nor useful for large volumes. What if you implement a database to track procesed messages. Return to square one - that's the same problem you were initially trying to solve.
What if you fetch, enqueue, and then delete? Ohh... that works. In case of a crash the message remains in the outbox. It may be processed in duplicate, but eventually if successfully it will be deleted from the outbox.
The message broker then receives a possibly duplicate message. It must consult its internal database, and if the message is unique, route it. So right back at square one. Can't have atomicity and uniqueness.
Don't go putting people into boxes. That's the path of persecution.
You have the inalienable right to say what you want on a plane, limited by what the government is allowed to prosecute. In a confined space, that is a bit riskier. That's a solely personal choice - no laws are being broken. The Captain has the right to ask you to conform or leave, but that's a separate issue.
People are being overly sensitive. A wifi name is not a protest. It does not disturb personal privacy and tranquility. It's about as offensive as an article titled "We’re All Gonna Die!" from your favorite news outlet - which by the way, is not an uncommon headline.
What if my wifi name was "peanut butter for all!" but unbeknownst to me and by some rare cosmic coincidence everyone on the plane was deathly allergic to peanut butter. Does that make me a terrorist? No! But I swear someone would try to drag me through decades of litigation regardless. These people seem to have divorced words and meanings from the mechanics of how the world works. Like, "this piece of paper says you shouldn't say this, so off with your head".
For supported devices, which include Pixel 8, Pixel 9, and Pixel 10 series, the Find Hub network can locate your phone for several hours even if the battery runs out or the device is powered off. """
https://support.google.com/android/answer/3265955?hl=en#zipp...
Couldn't find any official documentation from Apple, but there's this:
https://www.howtogeek.com/805624/what-does-iphone-findable-a...