We could pick a company car in my previous company (it's a tax thing). We could pick any color, apart from red, because the insurance forbade it - red cars get into more accidents. Somehow that must have made it all the way to the policy without someone asking "is it the red car or the kind of person that picks a red car that causes more accidents?"
And yet the root comment claims the opposite (the US is very stretched out, so it’s harder to connect all of it).
In my country, fiber is run to my apartment building and through the technical shafts. Very easy for the telco: to connect a unit, they only need to branch off from the technical shaft. I imagine the total cost to connect 200 apartment units is much lower than connecting 200 farms or 200 houses in the suburbs, even with the red tape.
The physical barcode reader is long gone in Belgium. Instead, you scan the QR code with your banking app (or on mobile, click a link to open the banking app), and either verify directly for amounts under €250 (?), or verify big amounts with ItsMe, another app, using Face ID.
> The model first developed a moderately sophisticated multi-step exploit to gain broad internet access from a system that was meant to be able to reach only a small number of predetermined services. [9] It then, as requested, notified the researcher. [10] In addition, in a concerning and unasked-for effort to demonstrate its success, it posted details about its exploit to multiple hard-to-find, but technically public-facing, websites.
> 10: The researcher found out about this success by receiving an unexpected email from the model while eating a sandwich in a park.
Here in Belgium too. Somehow they don’t properly work if you have other Bluetooth devices connected, so the app forces you to disconnect other devices. Then it needs access to precise geolocation, and not just because Bluetooth requires it - I have to turn on location services.
In the old system, I could just punch in the code or scan the QR code, but now I have to do this dance of “why won’t it connect?” every time
The concern was related to being able to know where emergency vehicles were. If you build a system that announces to traffic light “I’m police/fire/EMS, coming through”, you also build an early warning system for criminals and terrorists who either want to avoid or target you.
That's not how it works - the idea is your navigation app signals the lights in advance. If you will reach red lights in 1km, the app signals this and the lights will be green before you're there, so you don't need to slow down.
Flemish EMT here. There were a lot of privacy concerns for emergency services when this came out, and my service is in fact not using it on most ambulances. The same concerns were hand-waved away when it came to apps for regular drivers. It would not surprise me if that played a role for Google Maps/Waze not to support it. Or the market is too small here to be worth implementing.
This is my brother's job, testing for contaminants. He says it can be very boring. For example, they always test for lead, and it's always negative. But it's a necessary precaution when you're making medicine.
This is absolutely fantastic! I have been looking on and off for something like this for years (some of the things I have used are CouchDB, command/event sourcing, and ditto.live).
I have not been able to read the docs fully, but some questions:
* How do you handle state that is too big to send to the client fully? In a chat application, does the client need to have the whole channel history, or is syncing a subset of that supported?
* Does permissioning support partial CoValues? For example, "You can edit the contents but not the title of the 'blog post #11' object"
* Do you have resources about the suggested data modelling? Things like how granular should a CoValue be and what the trade-offs are.
* How do you handle deletion? Do you tombstone? Is there a way to fully scrub a value from history (to support, for example, GDPR's right to erasure)?
Events like this are much more common than you may think, though rarely as severe as this shooting. From fires at retirement homes and even at an ED once, bus crashes, WWII bombs surfacing during construction, floods… it almost becomes routine. I can assure you the plans are not built not academics but are refined through experience. And in a weird way, disaster response almost becomes routine.
Can't say for Las Vegas, but we do here (in Belgium). There's a dedicated responsibility during mass casualties to distribute leaving ambulances over hospitals, also taking into account hospital specialties and facilities, such as a burn unit. The closest hospital is usually skipped because victims who self-transport will usually go there.
Interesting that he had to do so much thinking and improvising. I'm an EMT in Belgium, and every hospital here has to have plans for mass casualty events. Ambulance bays are built to be transformed into a triage ward, spare beds are kept close, often there's a dedicated command room, ...
I wonder if OpenStreetMap has historical information easily available and easily queryable. It'd be interesting to see the evolution of the number of benches in cities and parks. My feeling is that they have been disappearing in my area, and it feels harder to find good spots to sit and read a book.