selfup
Joined 10 years ago
Karma
103
Submissions
25
Member since
Jun 19
Recent submissions
Comment · 4 years ago
Fixture data (for testing) is fine. Sometimes a few lines is the minimum viable to test, sometimes a hundred or so lines of JSON. As long as the data is being optimized for testing and you aren't just storing a GB because it's easier.
I was replying to a comment asking why PII data shouldn't be stored in git vs a database. Just tried to give a general rundown of how to think about the tools.
Totally agreed that the data should have been synthetic/scrubbed and that a small sample set (large enough to validate) would be ok.
Sometimes a PDF or a few pictures are necessary (or just much simpler). I get that. I have seen some repos with an unreasonable amount of PDFs/Docs/pictures/etc.. and that's when a script that copies them into a gitignored directory from someplace (Dropbox/S3/etc..) is a better fit.
Comment · 4 years ago
The idea is that git is for source code/configs. Not data. Data gets stored in databases. Secrets/Tokens are stored in secret stores/vaults. Blobs like PDFs/etc should be stored in blob storage.
If a diff is not useful, don't store it in git. Doing a code review on PII is not useful.
You also shouldn't add packages in a git repo if they can be downloaded immutably in CI/locally. It adds a lot of space. Every commit is a snapshot + new code. Commits are not diffs.
Comment · 4 years ago
Yea CA certs are the first pain point I hit. Worth the hurdle. Noted on the timezone. Never really thought about that one. Thanks!
Comment · 4 years ago
Good to know. `FROM scratch` is such a breath of fresh air for compiled apps. No need for Alpine if I just need to run a binary!
Comment · 4 years ago
Had no idea about squash. Using cached layers can really save time, especially when you already have OS deps/project deps installed. Thanks!
Comment · 4 years ago
If you don't have an edge proxy (additional compute) you then accept all requests, or accept that a simple header is telling the truth.
Comment · 4 years ago
I am on latest FF for Android (95.2.0) and it works.
Comment · 5 years ago
I have had great luck using rayon for distributing CPU intensive work across available cores. If you are doing I/O I can see why async is preferable but rayon is an excellent library for parallel work.
I have found that async or even in Go with goroutines, a large amount of small threads are not faster even if they should be in theory when it comes to CPU intensive work.
I use it to generate a 3D universe (at the atomic level) but store the data as enums.
Here is the repo: https://github.com/selfup/oxidizy
Big help from rayon:
1) https://github.com/selfup/oxidizy/blob/master/crates/unigen/...
2) https://github.com/selfup/oxidizy/blob/master/crates/unigen/...
3) https://github.com/selfup/oxidizy/blob/master/crates/unigen/...
Example perf generating an obscene amount of data on a 32GB machine with 16 threads (3800x):
Atoms: 110592000 Baryons: 26099712000 Quarks: 78299136000
real 0m12.779s user 0m0.000s sys 0m0.000s
Comment · 5 years ago
You can set this in the OS itself.
Comment · 5 years ago
This comment isn't constructive at all. Keep it on topic and don't blame the messenger.
Comment · 5 years ago
There's a chance it's using Tauri (rust) https://tauri.studio/en/ if it's truly not using Electron but a similar concept. However WASM builds in Electron would make more sense if they use the term Electron.
Comment · 6 years ago
The end game is to switch to a post-quantum algorithm.
Essentially something that both quantum and classical computers cannot crack/brute force.
I would look into lattice-based crypto. It is one of the strongest candidates under review by NIST for post-quantum public/private key mechanisms.
Comment · 7 years ago
Is there some kind of test harness for this? What does generic streaming engine mean here?
Comment · 7 years ago
I read up on their blogs and as much technical explanation as I could find, and by far 1Password seems to be the best with a cloud offering.
Also Apple buying into using 1Password company wide helps gain some trust (I am sure there was some serious auditing): https://medium.com/enrique-dans/apple-and-1passwords-deal-sh...
https://selfup.me
https://github.com/selfup
https://gitlab.com/selfup
https://codeberg.org/selfup
[ my public key: https://keybase.io/selfup; my proof: https://keybase.io/selfup/sigs/zeb7OPc4pQ6U2r7tM07W7uCSu54nzt6bnF6-gJ9onPE ]