Editing LBRY (section)

= FAQ =

== Why Upload to LBRY/Odysee? ==

Several reasons:

* Because it's on-chain, uploads cannot be censored in any meaningful way barring a gigantic actor pulling a very visible 51% attack on the LBRY blockchain
* LBRY can be accessed without Odysee, allowing greater anonymity
* Even if a file is removed from Odysee, it can still be downloaded over LBRY Desktop if someone's mirrored it
* LBRY allows GunCAD Mirror instances to seed content transparently
* We're all here already
* It's battle-tested
* GunCAD Index integrates tightly with it -- we can only parse LBRY/Odysee releases

Additionally, other websites (like Printables, Makerworld, etc.) may have policies that result in the removal of firearms-related content.

== How are Claim ID Collisions Handled? ==

So say you've got two claims for the <code>@bro</code> channel handle, and they start as follows:

* <code>abc123...</code>, claimed first; and
* <code>abd51f...</code>, claimed afterward

In this circumstance, it looks like the naiive qualifier of <code>@bro:a</code> is ambiguous. However, per LBRY spec, there is no ambiguity. The '''earliest claim gets the shortest ID''':

* <code>abc123...</code> - <code>@bro:a</code>

Then, subsequent claims, in order of claim time, append as many characters as it takes to disambiguate:

* <code>abd51f...</code> - <code>@bro:abd</code>

This algorithm minimizes length as much as possible. If someone comes along and makes another claim that doesn't quite collide as hard as the second, they're allowed to take a shorter qualifier:

* <code>a99881...</code> - <code>@bro:a9</code>