One start would be to disable smartphones from operating when linked to a car system, massively increase enforcement of smartphone use while driving, and increase penalties.
None of that would be popular, but it would be effective.
Not all cell phones being used in cars are used by drivers. I wouldn’t want my cell phone disabled in an Uber, or to get a ticket because my uber driver was speeding.
I vastly prefer on screen keyboards. I'm faster with them, it requires a lighter touch, and the auto correct is good enough.
What I miss about blackberries is that they were messaging devices, with OS level integrations around messaging that went beyond the notification system of today.
For 90% of messages i send, i could simply use a generic sms style interface through a system-wide messaging app, only jumping into the apps themselves from time to time. I think palm had that, but it was too little, too late.
unihertz makes a blackberry clone btw, check it out
I think you're spot on about the keyboard being rubbish, but overall bbm was great.
Everytime I upgrade my iPhone I find myself removing more and more apps. At this point all I really want/need is google maps, iMessages and... yaknow a phone. idgaf about anything else.
Which message services are you referring to? The most popular modern messaging apps wouldn’t work with the single interface nowadays. FBM, WhatsApp’s. I don’t know if third party integrations would be allowed so other apps could get integrated.
> modern messaging apps wouldn’t work with the single interface nowadays
The notification system on my phone already lets me reply. All I need is to be able to see text, emoji reactions, and a thumbnail of any photos. It's extremely reasonable for any advanced features to require me clicking the message and opening it in the app.
Not quite - many of their customers are paying $$ a month for medium to large marketing sends. Their biggest customers probably count for 30% of the overall revenue.
It's unusual seeing a company that sells goods and services for money be valued highly in silicon valley ;)
If you're interested in infosec/appsec, DND is a great place to get started. The host packages up stories in a well put-together way, has no qualms about breaking to explain a concept or term, and does it all within an hour.
My intuition is right with you. They will actively avoid anything that the end user thinks is a camera while packing it full of sensors that allow interactions with (mapping/object recognition of/etc) the world around them.
I don't particularly agree with the parent comment, but you are being oddly aggressive over something that is a real problem - communicating things is hard and it's a useful topic to consider in a world that increasingly runs on text-based communication.
None of the vulnerabilities are WAN side, which means that the average home user won't be affected by them. However, it also surprises/depresses me that there is no auto-update functionality.
Vulnerabilities happen. Architecture and secure design is critical. However, your patching and remediation strategy is what counts in the field.
I should add "the average home user 'likely' won't be affected by them". There's a couple of reasons for this, but it's still not a good enough reason to warrant allowing this kinda thing to continue to ship
The Lightning-to-HDMI adapter is also an insane miniaturization. It runs a (very) stripped down version of iOS/darwin (not sure what apple counts it as) that is loaded in about a second when you plug in the phone, establishes a network connection, and streams compressed video frames over the network over USB to the HDMI.
That's why when you use the iPhone HDMI adapter, everything looks a little bit compressed. Because it is.
Yup. It's actually an incredibly clever piece of tech that lets the iPad/iPhone get around the fact that lightning doesn't have enough bandwidth to transmit HDMI.
For regular home/app views, it does hardware compression of the iPad's screen, outputs that over lightning, then the adapter decompresses it to raw HDMI.
While for Netflix/etc. streams, it outputs the stream directly to the adapter to decompress, without quality loss. (And at full size as well, rather than double-letterboxed.)
I still haven't figured out the magic of how apps like Netflix are able to do overlays of subtitles on top of the compressed video stream. Best I can tell, there must be a separate API for that, that gets sent in parallel.
As far as working within the constraints of USB 2, it's a solid way to do things.
And I'll even leave aside the issue of running a whole OS just to decode video.
But this is dealing with 1080p output. That's not very intensive. A lightning port has two high speed data pairs. You don't even need USB 3 speeds to transmit HDMI over one of those data pairs, and then put in like a $2 redriver.
If you set up double-sided output I think you could even have a passive lightning to HDMI adapter. But that's a side issue, my main point is the bandwidth available that makes these tradeoffs unnecessary.
I'm not sure what point you're trying to make? Basic 1080p is 3.96 Gbps. Lightning is 480 Mbps. The bandwidth isn't there according to how lightning was designed.
Yes. (Well technically you need 3.20 or 3.33 for 1080p60, and HDMI 1.0 supports 3.96)
> Lightning is 480 Mbps. The bandwidth isn't there according to how lightning was designed.
Not true. Lightning has two differential data pairs. The port can do much more than 480 Mbps.
If your response to that is "oh, but it's only connected to pins that do 480", they would have to reconnect it to video pins anyway to do HDMI out. And nothing else in the lightning ecosystem would limit it, because this is a directly-attached adapter.
Also some of the iPad Pros have actual usb 3 support on their lightning ports.
I've been riding for a long time. I definitely spent effort understanding risks and safety.
Motorcycle fatalities are mostly similar to factors that cause car fatalities, but extremely exacerbated.
For example, about 40% of motorcycle fatalities involve alcohol. One drink before riding a motorcycle is about equivalent to 4 before you drive.
Riding at night accounts for a significant amount of fatalities, as does unprotected left turns. Oversteering is another major factor, usually because you went too fast through a turn.
Also, motorcycle fatalities are currently rising. This is largely due to older people who have wanted to ride but couldn't or were afraid to. A 65 year old man on a 800lb 1.5L engine bike who's a new rider is going to take a bad situation a lot harder than a younger person on a smaller bike.
Motorcycles are more dangerous than cars, but if you understand the risks and employ constant self-improvement in your skills, you really begin to reduce your exposure to risk. Unfortunately, it does somewhat select for a group that likes to take risks.
None of that would be popular, but it would be effective.