Yes.

Nah OSS models ftw

Yh. They seem to have dealt with the routing issue with a DHT, but I’m sure there are other methods of doing the routing.

I was thinking the other day that we could replace IP addresses with public keys if we made something like BGP and you signed your announcements/connections with peers. I.e. peer A could announce “peer A is connected to peer B” and attached would be peer A and B’s signatures. Scale that up a bit and you have a sort of validating mesh network. The problem as you said is scaling the routing table. If you had random keys then you couldn’t really optimise using primitive methods. BGP announces IPs in blocks, not individual IPs. So something like 1.1.1.1/24 would cover 1.1.1.1 through 1.1.1.255. The 24 is the “prefix” bit length that doesn’t change.

That is great for efficiency, but obv this is more difficult to do within a mesh network. Maybe I’ll post some more if I think about it any more

Wait until he learns about kanal and the thread per core model (just wait until u need more than 8 cores)

I mean his points were valid and mostly correct, but it makes me upset that good accurate takes have to come from a furry before someone else. Is this discrimination? Yh i guess

Good post but shame he’s a furry 💀

I wouldn’t worry about it, the girls that’re worth it will want to work so you don’t have to spend your bitcoin. Plus, I haven’t seen many ugly girls in the industry icl…

hurrah.

it does (but go ahead, garbage collect all you like)

based

rust is Solana but it wasn't premined and it doesn't have downtimes

(what are we on about at this point)

JavaScript moment

I got out of my comfy bed at midnight to find this for y’all. epub and pdf here. Enjoy.

I highly doubt 100+ soon

Secure enclaves don’t support secp256k1 so this won’t be possible unfortunately

YESSSS IVE BEEN WAITING TO USE THIS FOR YEARS LFGGGGGG

Agreed 100%.

Not sus, just likely they haven’t finalised it yet. Power consumption certainly they won’t know until they finalise their designs