tsuraan

How do these federated forges deal with spam? If merge requests and issues are federated, does that mean that anybody running a radicle node (or interacting with one) can open issues or merge requests on all the repositories that you've made public? Or is there a whitelist (or something fancier?) to allow interaction only with specified nodes?

Okay, good to hear on both counts. Thanks!

Oddly specific question, but can anybody confirm whether the AX210 (no vPro) wifi works with the AMD motherboards? I've seen some pretty bad reports about the realtek chip they're defaulting to on the AMD systems, and I already have the AX210, so if I could just keep using it, that would be ideal.

Okay, good to know it's being considered. For a non-optimized diff then (zfs-diff, which just prints which files have changed, not what about them have changed), it would be the same approach? Scan all the metadata looking for keys with versions between the two snapshots, and print out the associated file names? Would that simple approach be likely to be faster than whatever rsync does to find updated files when doing a backup?

Speaking of snapshots, are you planning to have analogs to ZFS's send/recv and diff? I didn't see any mention of them on the snapshots page or the roadmap, but I could be looking in the wrong place. Already having reflink support is exciting though; a ZFS replacement that can also do reflinks would be amazing.

I've personally seen as low as 30ms, but also up to 60ms. I also have a bit of packet loss, but my dish is just sitting on the ground in my wooded back yard right now. Once the weather turns back towards just being cold, I'm going to move the dish to my roof and see if that helps the packet loss. Maybe being able to see more of the sky will help get a more consistent latency too, but I'd guess more satellites are really going to be the fix there.