> If you serve as a mere conduit for automatic transmission of user communications, there are no other qualifications or obligations you need to meet. If you serve a caching function, in addition to the two requirements above, you must maintain comply with the notice-and-takedown process.
Go look at the github commits for llama.cpp and read the actual code they're adding to support new model/quant types... to me at least it's some serious black magic, and the sheer number of genius developers and activity level in this repo is absolutely wild.
Imagine what could happen if other open source projects had this level of engagement and expertise at hand and eager to contribute... instead of arguing over politics and making yet another fork of something.
Besides the irony of a privacy-conscious user using facebook to buy a car... those "perfectly-serviceable vehicles" are 1. no longer manufactured, and 2. will not last forever.
Unless a new age of unconnected cars becomes a reality in the near future, I don't see this being a long-term solution.
"will not last forever" doesn't comport with observed reality to date. There are literally model A's still on the road. Barring true oddities there doesn't appear to be a model of production vehicle that has gone extinct at any point in automotive history. Anyway, three of my cars are older than I am, and I am not a young man. Buying into their shit is optional.
I think most people would not be on board with your solution, but in general to your point I would say everyone draws the line somewhere different.
Yes there are many (maybe most) who will not give up their comforts or risk modifying their vehicle in order to make it more private... but trying to play the judge in a made-up internet game of altruism olympics is not going to convert many people either.
But GrapheneOS relies on a proprietary, black-box security chip from Google... who pinky-promised to open-source it but never did, and that just doesn't sit well with me.
I think it's entirely possible that a compromised Titan module (whether such code ships with the device or is updated at a later point) could leak keys via some covert method, and possibly transmit via the baseband or through some other application/method where the OS is not really aware of what's going on.
I don't believe that they will use this against me. But I do believe in the right to use devices without backdoors for everyone, so I support something else instead.
> the surveillance networks can capture metadata - who talks to who and when
If this is part of your threat model then I would suggest a different tool such as SimpleX since it uses onion routing and can be configured to always use private routing/relays.
> If you serve as a mere conduit for automatic transmission of user communications, there are no other qualifications or obligations you need to meet. If you serve a caching function, in addition to the two requirements above, you must maintain comply with the notice-and-takedown process.
https://www.copyright.gov/512/
https://internetcases.com/2024/02/12/dmca-subpoena-to-mere-c...
reply