80 karma · joined June 2, 2012
My 4yo child recently received a $10 digital camera at a generous birthday party and independently has figured out how to take videos (in addition to photos). Some self interviews, some videos of his sibling, his family. It really is amazing to see things from his eyes.
After seeing a friend with young kids post candid photos of his family for the last few years, I decided to give it a try. Purchased a Retina IIIc rangefinder camera (from the 1950s, preceded SLRs) and it's one of the most amazing purely mechanical, consumer-focused engineered products I've held in my hands. Got a scanner, successfully booted the Nikon Scan abandonware on a virtualized Windows XP environment, and saw my first roll of photos appear last weekend. Wife and extended family absolutely loved it. I've reviewed those 36 photos (standard roll length) more in the past week than the 1,000 family photos of the past 2 years on my cell phone. Excited for more.
Question - your privacy policy is fairly robust. Curious how you tackled this. Hire an attorney, skill set of yours, outsourced firm that does this for a nearly fixed price?
https://podcasts.apple.com/us/podcast/planet-money/id2907834...
Incredible website that is both feature rich and succinct to the content. As far as marketplaces go, there are some known platforms (e.g. ShareTribe) and payment options (e.g. Stripe Connect) - did you all "build" from the ground up or "buy" in putting this together?
To add additional info on the subject, the US employs a similar concept (and name) to "sentinel events." Relevant to surgery, this includes:
"Invasive procedure, including surgery, on the wrong patient, at the wrong site, or that is the wrong (unintended) procedure"
"Unintended retention of a foreign object in a patient after an invasive procedure, including surgery"
More broadly, sentinel events are generally defined as:
"a patient safety event...[that] results in any of the following:
Death
Permanent harm
Severe temporary harm" (1)
Outside of surgery, there are around a dozen additional, specific events that are always deemed to be "sentinel events." This includes forms of assault, abduction, unauthorized departure (i.e. the medical team has not yet discharged the patient) leading to patient death/harm, and specific, highly avoidable outcomes due to standardized procedures such as blood transfusions, too much bilirubin in newborns, and prolonged radiation. (1)
These sentinel events policies are guided by the Joint Commission in the US, a not for profit organization that guides many patient safety initiatives and accredits health facilities in the US. At least for hospitals, site visits are unannounced around every 3 years. (2) Failure to gain/maintain accreditation, among many outcomes, threatens a hospital's ability to participate in Medicare/Medicaid as the Centers for Medicare & Medicaid Services (CMS) considers the Joint Commission a national accrediting organization. (3) Revenues from Medicare + Medicaid are generally essential for the solvency of a high majority of hospitals in the US - in 2013, the national average was ~58% of hospital revenues (4).
Hospitals are "strongly encouraged" to report sentinel events to the Joint Commission but it remains voluntarily. Thus, the Joint Commission's data is available but explicitly not "an epidemiologic data set and no conclusions should be drawn about the actual relative frequency of events or trends in events over time" (5)
However, hospitals are "required" to respond to a sentinel event through a comprehensive analysis and planning to prevent future occurrences. If the Joint Commission becomes aware of an event during a site review or other means that was not addressed in compliance with the lengthy review policy required, then the facility will risk its accreditation status. (1)
(Post often references "hospitals" but applies to many health facility types.)
(1) [PDF] https://www.jointcommission.org/assets/1/6/SE_CAMOBS_2016Upd..., from http://www.jointcommission.org/sentinel_event_policy_and_pro... (2) http://www.jointcommission.org/mobile/faq.aspx (3) http://www.jointcommission.org/faqs_ccn/ (4) [Point 27] http://www.beckershospitalreview.com/hospital-management-adm... (5) http://www.jointcommission.org/sentinel_event_data_general/
The one thing you give up, of course, is the guarantee of future compatibility. That said, there is some security in hardware working in 10.9, likely working with 10.10+ (or w/e Yosemite is) just as old Mac's working with future OSX versions, with the additional ability to easily swap/upgrade components.
Apparently "plate pickle, bento pickle" (or reverse order) isn't correct. Would love to see a hint/solution manual.
This is often faster than "click[ing] on three tiny dots."
Like many people considering using DigitalOcean, I did some research over the weekend on "droplet" management. My results came up with the following resources (many already shared on hacker news):
1) Tugboat (today)
2) Fog - https://github.com/fog/fog - digital ocean support just recently added (https://github.com/fog/fog/pull/1525)
3) Vagrant DigitalOcean - https://github.com/smdahlen/vagrant-digitalocean
Both #2 and #3 are well established technologies that are allowing DigitalOcean plugins whereas TugBoat seems to be a specific tool for DigitalOcean.
Could someone with more extensive sysops experience comment on when/why you'd use one of these tools over another? (particularly relating to system provisioning options/interplay after droplet management...)
Given the likelihood of similarly positioned friends on my social networks, I shared the Economist article here ( http://www.economist.com/news/21567340-governments-squabble-... ) as a set up for the link to the petition, should people agree w/ Google's efforts.