You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder how much resilient SeqBox is to different "corruption vectors" e.g. in comparison with https://github.com/ttsiodras/rsbep-backup (which shall need just an approximate offset of the file and corrects up to 65280 consecutive bytes including all metadata)?
Some typical issues with FEC (forward error correction) schemes are outlined in https://www.thanassis.space/rsbep.html (especially metadata FEC is often flawed or the number of consecutive errorneous bits/bytes/chunks is very limited - typically to 1 or 2 or the ratio between errorneous parts and the whole data size is highly insufficient for long-term storage etc.).
The text was updated successfully, but these errors were encountered:
I wonder how much resilient SeqBox is to different "corruption vectors" e.g. in comparison with https://github.com/ttsiodras/rsbep-backup (which shall need just an approximate offset of the file and corrects up to 65280 consecutive bytes including all metadata)?
Some typical issues with FEC (forward error correction) schemes are outlined in https://www.thanassis.space/rsbep.html (especially metadata FEC is often flawed or the number of consecutive errorneous bits/bytes/chunks is very limited - typically to 1 or 2 or the ratio between errorneous parts and the whole data size is highly insufficient for long-term storage etc.).
The text was updated successfully, but these errors were encountered: