#introduction time! I'm Oskar, and I spend most of my time online talking and writing about #programming, including but not limited to #Haskell and #FP, #testing, #architecture, #FOSS, #Linux, and #web. I have a blog at https://wickstrom.tech and I produce screencasts at https://haskell-at-work.com when there's time.
See you around!
Obviously I'd have to give up Signal, but sms and calls would be fine.
Being able to bundle JSON and image files in an archive would remove the risk of partial uploads and file name mismatch, but I'm not sure about archive unpacking in the browser?
I looked at BSON a bit, which can be used from the browser. Images could be represented as Binary fields. Inspectability would suffer somewhat, having to use `bsondump` or something.
So far I've tried JSON with b64-encoded images, which works OK and is easy to consume, but clumsy to inspect and rather slow in the browser (I haven't done proper measuring, just feels).
I'm on the bandwagon here, perhaps late, and prototyping in Rust. We'll see where it goes...
OK, whatever, here's a comment.
This feels like a WWI machine. Extremely simple and brute force.
It gets stuck on stumps though, so I'm paying for my sins of sloppy clearing last year. And the blackberry vines tangle up and make life difficult.
Other than that it's nice.