brendoncarroll

7 ms·

1.
by brendoncarroll 3mo ago
No Nonsense Containers: a simple Linux containerization tool, secure by default, with support for presets. https://github.com/brendoncarroll/nnc I use it for running agents locally. nnc run /usr/bin/
2.
by brendoncarroll 5mo ago
Thanks for the link. It looks like this treats files as blobs just like Git, and trees as single objects which fit in memory. Assuming that is a correct understanding, this core abstraction would need to change to handle large files and di
3.
by brendoncarroll 5mo ago
I've heard that jj has support for non-git backends? Can anyone comment on how difficult it would be to add support for another backend, any docs or examples? I have a project[0] that does the large file thing well, but is missing most
4.
by brendoncarroll 7mo ago
I'm working on Got, version control like Git, but for files and directories of any size and E2E encrypted. https://github.com/gotvc/got Got is built on Blobcache, which is a general-purpose transactional storage l
5.
by brendoncarroll 8mo ago
Yes the author reached out. There has not yet been a confusion among real users that I am aware of. https://github.com/gotvc/got/issues/20
6.
by brendoncarroll 8mo ago
> The problem is when you move beyond text files it gets hard to tell what changes between two versions without opening both versions in whatever program they come from and comparing. Yeah, totally agree. Got has not solved conflict reso
7.
by brendoncarroll 8mo ago
Me too. Version control is great, it should get more use outside of software. https://github.com/gotvc/got Notable differences: E2E encryption, parallel imports (Got will light up all your cores), and a data structure
8.
Show HN: Blobcache(blobcache.io)
1 points by brendoncarroll 8mo ago|0 comments
9.
by brendoncarroll 8mo ago
I also wrote a tool for doing this[0], after one of these agents edited a config file outside of the repo it was supposed to work within. I only realized the edit because I have my dotfiles symlinked to a git repository, and git status show
10.
by brendoncarroll 8mo ago
https://brendoncarroll.net
11.
by brendoncarroll 9mo ago
I personally think that this is the future, especially since such an architecture allows for E2E encryption of the entire database. The protocol should just be a transaction layer for coordinating changes of opaque blobs. All of the complex
12.
by brendoncarroll 9mo ago
I recently released Blobcache v0.0.2. https://github.com/blobcache/blobcache Blobcache is a content-addressed data store for holding application state, and buiding E2EE applications. This most recent release includes a
13.
by brendoncarroll 9mo ago
I'm a happy bcachefs user. Haven't had any issues on a simple mirrored array, which I've been running since before it was in (and out) of the kernel. It's the best filesystem in 2025. Thank you for all your work. What
14.
by brendoncarroll 10mo ago
I work on a project Blobcache, a content addressed store for exposing and consuming storage over the network. It supports full end to end encryption, and offers a minimal API to prevent applications from leaking data. https://gi
15.
by brendoncarroll 1y ago
The same API part isn't surprising, content addressed stores are the most natural way to accept encrypted data. The public storage networks are targeting a different use case than Blobcache though, which I think of as a private or web-
16.
by brendoncarroll 1y ago
I couldn't find an email in your bio. You can reach me via the email at the bottom of my website (in my HN bio). Looking through the docs on Peergos, it looks like it's built on top of IPFS. I've been meaning to write some d
17.
by brendoncarroll 1y ago
I work on a FOSS project in this space, Blobcache. https://github.com/blobcache/blobcache Trusting a server to store an application's state is a different thing from trusting it to author changes or to read the da
18.
by brendoncarroll 1y ago
I'm working on Blobcache. https://github.com/blobcache/blobcache Blobcache is content addressed storage, available over the network. Blobcache allow nodes to securely produce and consume storage. Configuration in
19.
by brendoncarroll 1y ago
All of those issues can be solved by doing an import of the changed file into the build system's content addressed store, and creating a new version of the entire input tree. You also don't need to choose between cancelling, wait
20.
by brendoncarroll 1y ago
I'm not sure which paradoxes you are referring to. Type systems are used for a lot of things, in Mycelium a Type is an encoding strategy for it's Values. And just like I could explain the encoding strategy to you in text, the Ty
21.
by brendoncarroll 1y ago
The serialization format solves a similar problem to Protocol Buffers or JSON. If you haven't heard of either of those, then Mycelium might not solve a problem that you care about. Just after your quote the README mentions things lik
22.
Show HN: Mycelium(github.com)
40 points by brendoncarroll 1y ago|8 comments
23.
by brendoncarroll 1y ago
The Want Build System https://github.com/wantbuild/want https://doc.wantbuild.io Want is a hermetic build system, configured with Jsonnet. In Want, build steps are functions from filesystem snapshots, to fi
24.
Show HN: The Want Build System(github.com)
3 points by brendoncarroll 1y ago|0 comments
25.
Show HN: The Want Build System(github.com)
2 points by brendoncarroll 1y ago|0 comments
26.
by brendoncarroll 3y ago
I don't think you need to go quite so far as checking gigabytes of executables into version control. If you download some dependencies at build time, that's fine as long as you know exactly what they are ahead of time. "Exa
27.
by brendoncarroll 3y ago
I'll throw in INET256 https://github.com/inet256 It's a specification for identity based networking. There is a meshnet and a centralized implementation. You can layer IPv6, IPv4, or application traffic on top o
28.
by brendoncarroll 3y ago
> no need to exchange the key during authentication The public key does need to be exchanged, along with a signature relating it to the current session. This is all handled by TLS, there is no need for the client to send the key in the
29.
by brendoncarroll 3y ago
It's amazing how far adrift the industry has gone with authentication. This post is saying to avoid OAuth and use bearer tokens because OAuth is too complicated. I agree with OAuth being too complicated, but I don't really think
30.
Dan Bernstein's Libmceliece Now Available(twitter.com)
3 points by brendoncarroll 3y ago|0 comments

More ›