Agreed about Cupertino but San Francisco is very walkable!
8 karma · joined December 27, 2020
There are issues which arise from restricting the hologram to a real valued grid, like limited FoV and noise, but these are not impossible problems to solve and existing technology is already quite good in terms of image quality.
VividQ is a VC-backed, deep tech software company with world-leading expertise in 3D holography: the next generation display technology. Our expert engineers, mathematicians and computer scientists out of the Universities of Cambridge, Oxford and St Andrews have solved key technology barriers in the adoption of holographic display for mass commercial application. VividQ powers devices developed by OEMs across the US, China and Japan, establishing a new standard of display.
Details: https://vividq.com/careers
Using my NAS for sharing photos and files with family/friends opens up security holes that encryption at rest wouldn't help with, and I accept the tradeoff of potentially leaking data. What is less acceptable to me is any risk of data loss.
These are the threats I have considered and would like to mitigate against, in no particular order:
1. Physical damage or theft to the NAS and supporting hardware (e.g. backup drives in my home). 2. Accidental deletion or corruption of files through user error. 3. Ransomware which targets my NAS. In particular a sophisticated malware author could target common cloud backup destinations by looking for credentials stored on the NAS, and delete any backups, although I have not heard of any such attacks in the wild.
The first threat seems simple enough to mitigate: make regular backups backed by cloud storage, and keep offline credentials for accessing the backup in multiple geographical locations as well as a cloud based password manager.
The second is also not troublesome: use a filesystem which supports versioning and take regular snapshots.
The third is where I have been somewhat disappointed by the options. An effective strategy is to keep an external hard drive which is plugged into the NAS regularly and keeps a clone of the data. However, an extremely cunning malware author could still pre-empt this by corrupting data on plugged in drives. This is extremely unlikely, but here's where I was hoping for better options in cloud backups: effectively all the pieces are in place for immutable backups, except for the tooling.
Options such as restic and rclone don't have good (if any) support for targets which support immutability, such as AWS S3 and BackBlaze B2. My current solution is to use a version of restic which I have patched to not require delete permissions when targeting B2, and very carefully manage API keys so that deleting backups would require compromising my BackBlaze account. In case a script does try to corrupt the backup repository, there are few if any supported ways of accessing a past version of a B2 bucket, although rclone comes very close and could support this very nicely with some minor tweaks to the B2 backend.
I will be keeping a close eye on this, and hopefully if I have the time I can make some PRs to push the open source tooling in this direction.
I am not sentimental about text messages but I did have photos which I had received from other people and wanted to keep. The only way to do this in the iOS -> Android case was to go through all of my threads in WhatsApp and Signal, save the photos I wanted to keep to my Camera Roll (??) and then copy them to my computer.
On Android, WhatsApp stores its data in the data partition, and Signal can either save photos to its own folder or export a backup, although I did not look into how to decrypt the backup.
Ultimately what drove me back to Android was that iOS did not give me control of my data in the way I am used to, despite some of the much touted privacy advantages.