# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 15
# self = https://watcher.sour.is/conv/tgmogmq
I don't usually ask the community on Stackoverflow questions, but here we go: https://stackoverflow.com/questions/65737814/reed-solomon-erasure-encoding-and-replication-factor 😀
I don't usually ask the community on Stackoverflow questions, but here we go: https://stackoverflow.com/questions/65737814/reed-solomon-erasure-encoding-and-replication-factor 😀
In the past I've _normally_ answered them! (_but I haven't been active on SO for some years now, too busy!_)

In the past I've _normally_ answered them! (_but I haven't been active on SO for some years now, too busy!_)\n\n
In the past I've _normally_ answered them! (_but I haven't been active on SO for some years now, too busy!_)\n\n
In the past I've _normally_ answered them! (_but I haven't been active on SO for some years now, too busy!_)

@prologic 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.\nBlock size? I assume that's about compression's effectiveness - you'll get better compression with more data.
@prologic 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.
OH wow! Chris you’re amaIng! Can you just answer the SO question , link here too and I’ll just accept it? 🤣
OH wow! Chris you’re amaIng! Can you just answer the SO question , link here too and I’ll just accept it? 🤣
OH wow! Chris you’re amaIng! Can you just answer the SO question , link here too and I’ll just accept it? 🤣
@prologic :D don't have an account
@cvshumake Get one 🤣
@cvshumake Get one 🤣
@cvshumake Get one 🤣