It's interesting reading articles about Level 2 and how it can adversely affect driver attention. I was concerned when I started driving a Tesla for the same reasons. Would I grow complacent? Stop paying attention?
The opposite happened. I'm more focused on the road since I can relax and not multi-task. On long road trips, I'm not feeling that ache in the knee or the tension in the shoulders/back from constantly keeping the car aligned in the lane. In fact, I wish Tesla would just introduce a touch interface into the wheel so it knew your hands were on it, but not require constantly resisting the wheel to trigger the sensor.
The conclusion I've come to: Level 2 can make good drivers safer and make bad drivers more dangerous. I don't look at my phone when I'm driving. I don't text at red lights. I don't constantly fiddle with the screen. If you do these things, you're a dangerous driver. If Level 2 increases this because you feel a false sense of safety, it'll make you more dangerous.
People just need to take driving a 2 ton heap of metal 70mph seriously and we'd all be much safer.
> In fact, I wish Tesla would just introduce a touch interface into the wheel so it knew your hands were on it, but not require constantly resisting the wheel to trigger the sensor.
We recently rolled out capacitive steering wheels in several Mercedes-Benz models for that reason. It's pleasant.
> I wish Tesla would just introduce a touch interface into the wheel so it knew your hands were on it, but not require constantly resisting the wheel to trigger the sensor.
Morons will use devices that clamp to the steering wheel to defeat this sensor. Actively turning the wheel is harder to spoof.
edit: looks like we went through this process already.
Why is this a problem? My car is at a complete stop and is not legally allowed to proceed. What's the threat? Doing things while moving (even creeping along in stop/go traffic), sure, I'll agree, but stopped at a light?
If your head is down in the car, you lose track of what's going on outside and have to reaquire situational awareness from scratch when you 'wake up'. That takes longer at best, and you may miss something important at worst.
Small things like bikes and pedestrians are frequently occluded and you may miss the glimpses of them you needed to predict their future trajectory.
We could argue about the absolute importance of this effect, but it's definitely real.
Especially when you don’t notice the light has changed, someone honks at you, and now you have half a second to reacquaint yourself with what’s going on in front of you before stepping on the gas. I see many drivers looking down (presumably at their phone) at a red light who get honked at and almost immediately take off without any safety checks. If, say, a child had run out in front of the car, that child would get run over.
The problem is not texting itself, it's not paying attention to your surroundings, while moving or standing still.
If you're sitting at a red light fiddling with the stereo, the light turns green but you missed it, so the person behind you honks, chances are you'll start moving forward without actually being fully aware of the scene in front of you. And if there is someone in front of you, you could hit them. So why take the chance? Always pay attention to your surroundings.
Man, this is why self-driving cars can’t come soon enough. Everyone else’s replies to this already sort of answer your question, but for me this hints at the bigger issue: people don’t take driving seriously. My counter is: why do you need to be looking at your phone in a car? What text is so important that you can’t pull over and read it? Why give up the situational awareness that is absolutely required to safely operate a machine that can kill people?
Life is about trade offs and constant cost/benefit analysis. How is reading/responding to a text message slightly sooner worth the decrease in situational awareness and possible accident involving a 2 ton vehicle?
I think we have normalized the dangers of driving a vehicle to the point where we sort of just shrug at the monumental number of vehicular deaths. I’m confident that when my kid is an adult, he’ll look at us with astonishment when we say we used to drive vehicles around, poorly trained, staring at phones, half-drunk, kind of paying attention sometimes, a bit sleepy and it was not only legal but _normal_. It’ll be like us hearing about how our great-grandparents had a 2 year old work dangerous farm equipment alone. You think “How the hell did anyone survive?”
> It’ll be like us hearing about how our great-grandparents had a 2 year old work dangerous farm equipment alone. You think “How the hell did anyone survive?”
This reminds me of a old news article from Sweden I came across some weeks ago. The headline was something like "Driver crashed into house, judge released him without any fines because he was drunk so couldn't properly control the car"
In the context of the modern world, it's hilarious. But one could wonder how that news headline was reacted to back in the day.
> In 1928, a materially serious car accident occurred on the national road between Örkelljunga and Åsljunga.
> It was an Örkelljunga resident who drove over a merchant from Skånes Fagerhult.
> At the subsequent trial in Klippan, it was said that Örkelljungabon, who was the cause of the accident, received a mitigating sentence because he had drunk brandy and therefore had difficulty controlling.
That was the conclusion in the article too. The editor chose to highlight the less likely (in the real world) situation where the user is new to their L2 equipment.
Yep, I was just highlighting the fact that most articles about Level 2 or, in general, < Level 4, are written with a concern for situational awareness. In my experience, it was the opposite: it improved it.
Some of these have unfortunately been the fault of Apple's own iCloud drive sync problems in the past. I've noticed many apps that use it struggle to maintain consistent data across multiple devices in the case of conflicts / offline devices coming back online and having to catch up.
I changed to CloudKit and changed the extension as well to ".md". I was able to add a calendar event once or twice, then the same issue came up again where it could not add event and asked me to email support. I've deleted the app and reinstalled a few times. Anything else I can try?
Zettelkasten has to be the least explained concept I've discovered online. Sure, they'll explain the _technique_ of it, but I've almost never seen any solid examples of it in _use_. I was so excited when I first heard of it, but I'm a person that learns by seeing examples and I couldn't find any good ones anywhere.
Any wiki is basically an example, isn't it? Or if I'm not quite ready to defend that statement, I can at least say, you could use (or maybe misuse) any wiki-builder to build a Zettelkasten. Just impose a length restriction on each page's content.
But I don't know how much of the advantage of the Zettelkasten is tied to its being in the physical realm. On the one hand, the more physically rich an experience (of browsing or traversing or entering info for example), the more it will tend to stick in memory. On the other hand one of the things computers are good at is remembering indexes and linking them to other places where that index was mentioned.
Gordon Brander's pattern wiki is probably the best contemporary example I can think of that implements the Zettelkasten pattern: http://gordonbrander.com/pattern/
I think part of what can make the concept hard to see in practice, is that it's both the Zettelkasten artifact, and your methodology for adding and linking concepts when you're learning
I’ve kept a personal wiki since about 2007 for my notes on medicine and pathology. The “structure discovery” function it enables is very similar to Zettelkasten. I would submit the affordances of physicality can’t be replicated in software without AR.
Exactly the same thing happened to me. I was reading hours into this topic and nobody was able to explain this topic in a convenient way. I even read the German sourced.
Trust me, I've read every page of Zettlelkasten.de. It's a nice site (and I like their software) but there is no fleshed out examples that I've seen on it.
Again, I get the concept, but I want to see examples in use.
Could you clarify what specifically you have questions about, and/or what docs are perhaps slightly better (or worse). Or documentation for other concepts you've found useful?
Regards Zettlekasten itself: the key notion to me is simply capture and reference. Those are the dual-natured heart of the system.
The rest is just mechanics. Important mechanics, in cases, but mechanics all the same.
Everything I’ve read on Zettelkasten has been the equivalent of trying to learn to program by reading a reference book. Sure, I could technically learn Python by reading an exhaustive list of methods, classes and operators, or I could pickup a book which explains key concepts through an example project and examines the syntax through a specific context.
I learn best by example, personally, and I’ve never seen good examples on this topic myself.
I think the point most guides overlook consists of the internal semantics of using a Zettelkasten, Luhmann essentially used it to create a paragraph (Zettel) & subchapter (Zettel Sequence, but note they of course sometimes he'd not manage to fit an entire paragraph on one Zettel due to margin limitations) branching & branchable, recursively self-referential choose your own adventure hypertextbook, from which he'd then generate regular textbooks. Hence why he said that his books basically wrote themselves — to write a book, he'd 'just' enter the Zettelkasten, and copy out everything he'd already written there on the topic, picking between branches & branchings as he went back, forth & side-to-side within it. Hence why if one looks close, one can find Luhmann seemingly self-plagiarising paragraphs from books he'd previously written. I suspect a similar mechanic sits behind the (in this sense very ignorant) accusations of self-plagiarism against Slavoj Zizek.
As such, one might wish to instead consider using Hypertext Fiction tools for creating a Zettelkasten, such these two (proprietary software, Mac OS X only, unfortunately):
And secretly use the patching patches feature of pijul.org in the background so version control actually becomes sanely doable, throw in elastic tab stop support, and maybe an entire kitchensink in which someone let a mixture of ChrysaLisp, SmallTalk, Hazel, Scala 3, /r/nosyntax, Inferno, RINA, GNUnet, & every single proof assistant and theorem prover sit for a tad bit long, and then MAYBE we can stop living in the dark ages of computing.
Tinderbox was something I paid for (and wanted to love) but it was just too bloated and buggy. The creator's stance on "artisan software" is intriguing, but frankly the software doesn't put him in a good light. I'm willing to pay good money for good software, but $180 for software that feels like it's an open source alpha project is annoying, especially software that is meant to contain massive amounts of connected data.
I sat in the same boat as OP and that page wasn't that helpful. It's starts backwards with
- How many of things I know nothing about should I have.
- Don't use this aspect in the thing, use the other.
…
And every article is a text wall of minutia addressing questions which are going to be relevant later on, but are just information overload if you try to understand What is it?
I've had precisely your reaction, and am stoked to share my enthusiasm for Roam (https://roamresearch.com) -- a graph-based system for codex / memex / personal knowledge-base / zettelkasten++
I checked out Roam (thanks for the rec!) and though I REALLY love the concept, I'm a little nervous to keep a massive interconnected knowledge base with a SaaS. Currently, I use Devonthink and though it's not perfect, I'm just so relieved I can have data on my machine with the storage system I choose. I miss the days of software storing data on my computer or where I want.
As a backend engineer, I just think: "Man, this data is just sitting in a db somewhere for any engineer to grep." Until we get to a point where everything is just encrypted by default, I just can't see myself trusting software like this.
I've recently started using Roam, and I'm really enjoying it so far. Probably the easiest information capture and reference tool I've used to date--it makes it very simple to get things down without slowing you down. Only major downside so far is no mobile app, but I know they are working on one.
Tbh, I haven't seen a real-life example that perfectly clones this method but I've adopted parts of the system that makes sense for my own workflow. I think that's how it should be approached. Luhmann developed this in a non-digital world after all.
This kind of method used to be very common among scholars, before computers.
You can probably still find some in use among retired professors who started their careers 60 years ago and already had a system in place when computers started to replace physical organization systems.
Nowadays there are still many people who use digital equivalents.
ha, yeah very muich in the same boat. been following some of the zettel blogs for years and have read an ungodly number of posts, but it still hasn't entirely clicked — that said, I've moved entirely to plain text for note-taking and it's been a godsend moving out of evernote.
That's incorrect. HIPAA compliance only requires consent between patient and provider. Provider can choose to share that data with other providers. This is how Google purchased medical records by partnering with Ascension.
If you are covered under 42 CFR Part 2, then it would not be allowed because the patient has to give consent to ALL parties.
> Provider can choose to share that data with other providers
Not without express consent. The default is 0 hops. Same rules applies for banking info.
You want to share with someone else? You have to ask for consent again. A lot of people did unknowingly sign up to have their data shared like you say though, which I think is a regulatory failure more than anything else.
In the US, HIPAA allows your medical data to be shared without your express consent as long as certain conditions are met. Generally, they are that the data must be used to help your provider meet a legitimate medical or business need, and they have to have a contract with the entities they share with that constrains their use of that data.
HIPAA compliance has a lot of ambiguity. You are correct if, say, your employer requested medical records from your doctor. However, any entity that works with your provider that is facilitating its business can still get your data without your consent.
JohnFen's comment is correct. This is why 42 CFR Part 2 was created; HIPAA was too loose with patient data.
This is true! But when I last talked with them, I couldn't figure out a disaster recovery plan. They had no way for me to back up my users' mail aside from IMAP syncing. Which means I'd have to know my users' passwords. Which seemed slightly more ridiculous than just continuing to host my own mail.
1. share everyone's mailboxes to an admin user who does the backup via IMAP.
2. create an app-password for each user which can be used to backup that user. This can be done as an admin user on your account.
Neither of them require knowing the user's password - an admin can override into each account unless it's specifically locked down to deny that. It does require a separate app password per account, we don't have a way to create a single password which can view each user's account without them explicitly sharing the folders, but I'm not sure how you reasonably do anything else without it being a backdoor behind all the privacy settings on each account.
Ah, interesting! Yes, I'd be fine with either of those. Right now I'm just backing up via rsync of the maildir tree, so it's not like these are any worse. I just didn't want to a) know my user's passwords, and b) have to have them give it to me any time they changed it.
Thanks for the tip. Maybe my Christmas present to myself will be to murder my mailserver!
Sorry - busy at IETF this week, didn't get to reply before. I would recommend the per-user app passwords over sharing all the folders to an admin account - because that way you see the \Seen flags as the user when backing up.
You mean you can send emails to <user>-<tag>@<domain> and it'll be delivered to <user>@<domain> account (assuming MX for <domain> is pointing at fastmail)?
Is there anything you need to enable to allow this? I just tried, and the email got bounced back.
Or are you talking about email aliases? As in, you register <user>-<tag>@<domain> first before sending emails to that address?
The opposite happened. I'm more focused on the road since I can relax and not multi-task. On long road trips, I'm not feeling that ache in the knee or the tension in the shoulders/back from constantly keeping the car aligned in the lane. In fact, I wish Tesla would just introduce a touch interface into the wheel so it knew your hands were on it, but not require constantly resisting the wheel to trigger the sensor.
The conclusion I've come to: Level 2 can make good drivers safer and make bad drivers more dangerous. I don't look at my phone when I'm driving. I don't text at red lights. I don't constantly fiddle with the screen. If you do these things, you're a dangerous driver. If Level 2 increases this because you feel a false sense of safety, it'll make you more dangerous.
People just need to take driving a 2 ton heap of metal 70mph seriously and we'd all be much safer.