@matheus23.com
Building iroh with the amazing folks at number 0 (n0.computer). Generally striving to increase user agency and excited about commons networks. Only works for Canadian CEOs, apparently. Rust, cryptography, CRDTs & more on my feed
I have a lot of worries, but one is that expectations of speed increase to the extent that I can't either take the time to handwrite it if I want, or take the time to do it in collaboration with an LLM at a level of quality that would have been prohibitively time consuming before.
A clean looking graphic with sharp lines and crisp colour
The same graphic, but muddy and blocky. The previously sharp lines are blurry.
I think it's often overlooked that AVIF is also really good at flat colour & sharp edges.
Don't go straight for a lossless format just because it's the kind of image that would look bad as a JPEG.
Here's an 11kb image as an AVIF, vs JPEG XL.
I love this! Was just looking through reverse dependencies of bevy yesterday.
No webrtc in iroh! And so no - no base64 overheads.
Virtual networked memory?
There's this account:
bsky.app/profile/auto...
which has an automated list for e.g. unverified accounts over 10k followers, so you can mute/block them all at once.
I'm strongly in team "any markdown field could have been a facet"
Many plates spinning right now, but I keep feeling like I need to port/rewrite some of the atjson tooling, because atproto facets really need better tooling.
Oooh my god this feels sooo hard to read after working in GitHub all day and dealing with buggy CI, slow page loads and various UI bugs.
making software that’s good and durable and solves a user problem remains hard
architecture remains an essential consideration and thinking through it is a job
while you can speed them up, you cannot replace an engineer with a robot
their skills and insights…
Remain special.
Two chat rooms next to each other showing the same thing, a new chat with a video ("I don't wanna do the work today") inline
need to figure out adding friends in an easier flow (right now you both have to have added each other to the friend list to start getting status pings) but p2p chat is very easy to build with iroh
We plan on integrating WebRTC eventually, but then we lose control over how exactly the holepunching works, so it all depends on how well the browser implements it again (i.e. you don't benefit from our tireless work of getting holepunching right).
so I personally like to think of this more like a "progressive enhancement" thing where you point people towards a native app that can actually do peer to peer stuff.
Yeah. We have examples in the iroh-examples repo that check whether stuff compiles to Wasm & runs.
The only downside is that you can only send data via relays in browser at the moment,
Well, I for one, am excited to read more 👀
Friendly folks wrote a great article about Privacy Pass, a way of cryptographically unlinking the issuance and redemption of auth tokens:
research.chainbound.io/private-api-...
inspired by CLAUDE.md, I’ve started putting markdown files named after coworkers into work code repos so I can remind them to stop doing shit to the codebase that annoys me
for some reason they’re all mad at me now, which means ill be adding commands to JEREMY.md for an attitude adjustment
Ah right. Thanks for clarity. For some reason I was thinking of the cases where one shows both the command and output.
Yeah for command only that 100% makes sense.
Why not? (Genuinely)
BTW, this may be uncharitable and ignorant of me but I totally interpret this arbitrary 16 GiB limit in the browser as "That one mistake—virtual mem is a proxy for real mem—that people keep making", which the entire smalloc project is kind of an attempt to dispel. github.com/zooko/smallo...
I should say: I suspect that was what made them slow. It's my experience *that* they were slow, but I haven't looked into why exactly.
The webcrypto API is async. IME that made it really slow compared to wasm hash function implementations on small inputs.
I was wondering if wasm runtimes do virtual memory well.
Ah, just seeing this in the readme to-do section:
> turns out web browsers still limit the virtual memory space to 16 GiB even after the new improved memory model, which kills smalloc in wasm in the web browser. What a shame! But non-web-browser-hosted WASM could still maybe use smalloc...
Cool stuff.
`cargo add smmalloc --rename smalloc` oof this is going to be confusing to tell others about 😬
Sounds like something particularly well suited for rust wasm crates, right?
It's actually a community contribution and based on a *draft PR* supporting custom transports on iroh! So yeah. Not really "shipped" but exists.
github.com/n0-computer/...
Kind of short notice today. But I'm in Brussels for #FOSDEM until this evening. So if anybody wants to link up and talk iroh, QUIC, CRDTs or cryptography, let me know :)
YouTube PM:
We need... More shorts...
MOORE
MMOOOORE SHOOORTS
Best description I've read so far of all the different levels of "self-hosting" there are on atproto.
At this point the only "missing" thing is being able to transfer said reputation in a transaction and operationally you've just built a cryptocurrency. I don't see how you could gain permissionlessness without inventing a cryptocurrency.
Seems like what they have in mind is a system that uses "reputation" which is obtained by solving proof of useful storage (I suspect proving that you're storing the PLC ledger, which, by the way, is extremely, and I can't stress this enough, extremely hard to do right).