Hacker Newsnew | past | comments | ask | show | jobs | submit | more ranger_danger's commentslogin

Source:

The source is Apple. They can access any phone if they want to. In this case, they didn't want to.

https://en.wikipedia.org/wiki/Apple%E2%80%93FBI_encryption_d...


I don't see anything written there that says Apple has a current capability to "access any phone" which I am assuming to mean personal info like SMS message contents... just a whole lot of reasoning why they haven't had that capability in years.

Why would they be forced to develop their own OS? They could just license this theoretical future proprietary Android OS.

The comment I responded to was:

> Not sure if the big manufacturers would want to depend on a proprietary Google OS.

If a manufacturer doesn't want to depend on a proprietary Google OS, licencing that Google OS is not an alternative.


They could still be given the sources, for a hefty license fee.

Pretty sure that Google sells the Android licence for as much as they think they can. Make it too expensive and the manufacturers will try to move away.

AFAIK it doesn't, by exactly-once I think they mean not-more-than-once, which would still include zero.

I thought JavaScript was originally called LiteScript?

"LiveScript" – all the proprietary Netscape technologies were named "Live…", as in LiveWire, LiveBridge, etc.


Tried 3/4 of the tools, and none helped me reattach neovim.

Ended up using dtach. Needs to be run ahead of time, but very direct and minimal stdin/stdout piping tool that's worked great with everything I've thrown at it. https://github.com/crigler/dtach


have you tried diss, shpool or abduco?

also vmux appears to be specifically tailored to vim/neovim

https://github.com/yazgoo/vmux


It has been 20 years since the REAL ID Act of 2005... I am more than OK with this fee, and I don't think it unfairly punishes anyone at this point.

Why?

Does the system update process still produce zero progress indications whatsoever?

I don't think this is true... a reverse proxy/CDN can see the full request URL even if the origin server is using TLS (unless you're using mTLS, which almost nobody is), and we don't even know if it's the proxy/CDN or the origin that is filtering based on keywords... but all of them could be doing it.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: