Block / Report User
If this user/feed is violating this Pod's (twtxt.net) community guidelines as set out in the Abuse Policy, please report them immediately!
You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.
@cvshumake does not follow you (they may not see your replies!)
Recent twts from cvshumake
@prologic (#tgmogmq) this is to say, FEC & data duplication solve different problems. Disaster Recovery is possible with data duplication, but a bug in your FEC code and no duplication will prevent it. Use case matters because is your def of HA going to be 99.99% or 99.999%? The first can be single-instance mysql. The second, a cluster. More, and you start stepping into things like TiDB or Spanner.
@prologic (#tgmogmq) my read on reed-solomon erasure encoding is its the generalized implementation of raid 5, that replication factor is about the data stored’s complete replica count ignoring any capabilities of recovery through FEC. If you’re trusting your FEC, then you’ll be happy with replica-counts of 1. HA, of course, is dependent on use case. CAP teaches us to sacrifice Availability, but you can make very HA systems and keep C & P.
Block size? I assume that’s about compression’s effectiveness - you’ll get better compression with more data.
pi-hole up and running :D
todo: learn about DHCP, use dns-over-https, expand raspberrypi responsibilities to route all traffic through it and have it use a vpn, ensure I can switch what endpoint I’m using from my phone.