fenollp
Joined 13 years ago
Karma
294
Submissions
180
Member since
Nov 4
Recent submissions
Comment · 1 year ago
> The asteroid mass needed to support one astronaut for one year is between 160 000 metric tons and 5000 metric tons.
Even these orders of magnitude are correct, this is still 14t-438t of material to process /per day/ just for one person.
Comment · 2 years ago
Yes!
I'm on this route myself, trying various things out at https://github.com/fenollp/reMarkable-tools
Handwriting (in and out) support is very important IMO. Also being able to draw DAGs.
I'd like an e-ink device with high frame rate and HW powerful enough to run some models locally or with good enough connectivity and sensors that e.g. Computer Vision tasks can be offloaded to the users' smartphone.
Feel free to expose your ideas on there :) I welcome Open Source discussion!
Comment · 2 years ago
What do you mean by "adding rootless"?
Comment · 3 years ago
From the article:
> Nothing in this diatribe argues that encryption at rest is creating a net negative, outside of it being represented as a be-all and end-all security measure. When I say encryption at rest is a scam, I’m talking about it from the eyes of the purchaser. And given that it’s their data at risk, this is the standpoint that matters.
Comment · 3 years ago
I love seeing work in this space! I made a collaborative whiteboard app for the reMarkable a while ago: https://github.com/fenollp/reMarkable-tools
It is packaged in the homebrew Toltec repo https://toltec-dev.org/
Comment · 4 years ago
Comment · 4 years ago
ESC freezes it on Chrome on Linux.
Comment · 4 years ago
We use K-Sortable Globally Unique IDs: https://github.com/segmentio/ksuid
Some differences:
128 bit strongly generated payload (instead of 80 bits for ULIDs).
Only 32 bit time precision but that's wall clock time anyway.
Base62 encoded.
Comment · 5 years ago
> I needed something that would manage all the containers without me having to ever log into the machine.
Not saying this would at all replace Harbormaster, but with DOCKER_HOST or `docker context` one can easily run docker and docker-compose commands without "ever logging in to the machine". Well, it does use SSH under the hood but this here seems more of a UX issue so there you go.
Discovering the DOCKER_HOST env var (changes the daemon socket) has made my usage of docker stuff much more powerful. Think "spawn a container on the machine with bad data" à la Bryan Cantrill at Joyent.
Comment · 5 years ago
Here's the video with timestamp https://youtu.be/kIFjDV_zHaQ?t=1168
You mention different goals (from GA) and a will to open source (RK). The parent user seems to have found a way for you to publicize your business efficiently: a Starlark syntax on top of github actions through your runtime, maybe brought in by the OSS community, giving you ample opportunity to capt this market of developers.
People looking for better Developer UX would pay for faster processes, right?
Oh and long live Starlark and so long YAML.
Comment · 5 years ago
Then you'd be interested by https://github.com/denzp/cargo-wharf
And DOCKER_HOST, and BuildKit!
And if any of this makes sense: https://fenollp.github.io/faster-rust-builds-docker_host
Comment · 6 years ago
While this seems good to have a more efficient transport, I can't make sense of this
> Since the subsequent IETF drafts 30 and 31 do not have compatibility-breaking changes, we currently are not planning to change the over-the-wire identifier.
On another note:
3. optionally, the trailer field section, if present, sent as a single HEADERS frame.
I'm divided: I'd be glad to get rid of grpc-gateway and websockets but isn't proto-encoded communication bad for the open Web /in principle/? Maybe it's only a tooling problem.
Comment · 6 years ago
If you want to upgrade your Bazel dependencies using pinned semver constraints and a lockfile I've made this [0] for you.
It superseeds http_archive and falls back to git_repository if needed. Just run `bazel sync`. See it working at [1]. Note: there's an open (and somewhat long standing) issue WRT Bazel fetching from gitlab.
[0]: https://github.com/fenollp/bazel_upgradable [1]: https://github.com/voidstarHQ/voidstar/blob/master/WORKSPACE
Creator of https://fuzzymonkey.co
https://fenollp.github.io/
Maintainer of https://erldocs.com/
Traveling through https://github.com/voidstarHQ/voidstar
Look, I've merged Fuzzing and Property-Based testing: https://github.com/fenollp/coverage_targeted_property_testing#prop_03_coverage_targeted