in my spare time
音楽ソフトを開発中
| location | 東京 tokyo |
| location | 東京 tokyo |
developers working on cool p2p stuff, the new 0.97.0 update for @n0iroh is now out and resolves all of the latest connectivity issues i was having with the library. the custom transport stuff looks mad too.
https://www.iroh.computer/blog/iroh-0-97-0-custom-transports-and-noq
anyone have recommendations for alternatives to raspberry pi zero 2 w? i'm enjoying developing for it at the moment, but i hear spec wise, there might be better options.
something with at least 512mb, wifi, bluetooth, and bonus points for anything with good out of the box arch or alpine support (the rpi zero 2 w doesn't support arch so well, so i have to use the official headless rpi OS).
i bought a new one for 4300¥, so anything around that price point and roughly the same size would be nice.
https://worm-blossom.org/#y2026w11
This week, Aljoscha talks about repetition. Sammy ponders a 'cultural API'. Aljoscha talks about repetition. And in the comic, we find the bottleneck.
genuine question for anyone building p2p apps/libraries: how are you testing networking and sync code under real world conditions?
like, not two instances on the same machine, but actual different networks, latency, etc. spinning up a droplet/vps? something else entirely?
testing stuff that has a gui and isn't headless also kind of complicates things too..
I haven't written any p2p related code in about 7 years or so, but I decided to try and make something using @n0iroh for the first time on a whim, and was left incredibly impressed by how quickly I had two peers between berlin and tokyo connected together, swapping data with each other. i think i'd like to start making something useful with it.
i'm also excited to see what eventually comes of the iroh-willow implementation, but for now iroh-docs seems to work well.
that new smackos record absolutely smacks. quickest buy ever.
he’s the best to ever do it. i don’t care who else you throw at me. if you don’t say it’s danny, i don’t wanna talk.