Inscription Replies #2467
shiftshapr
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Greetings!
I am building ordweb.io. Our premise is that, with Ordinals, Bitcoin can become the premiere repository for the world's most valuable -- bit for bit -- public knowledge. A modern-day Library of Alexandria that cannot be centralized, censored,sacked or burned to the ground. Of course, this would require ordinals to be a functional information ecology with much greater context and content discovery than currently.
In this vein, I have noticed that you are empowering creators with meta operations such as creating child inscriptions and adding metadata to inscriptions, which I think is great. But in the informational context, empowering creators only goes so far. Functional informational ecologies are also shaped by researchers who curate the data. I think that we need solutions for linking and labeling inscriptions by people other than the creator/holder. But I am getting ahead of myself.
As a first step, I propose an operation that enables anyone to reply to an inscription. We have seen through Ord.io conversations that people are eager to reply to inscriptions. See https://www.ord.io/31444286. While there is no fee to reply in this context, I am certain that some people will be interested in replying with inscriptions. This would be useful for me. Just as child inscriptions can be very useful for the creator, it will be also be useful to associate a new inscription with existing inscriptions for people other than the creator.
I think people will reply as an inscription for many reasons including for visibility, understandability, giving credit, sidestepping censors, and speculating on the future value of the reply as an inscription.
For me, only allowing the creator to "reply" to their inscription (via parent-child) is like only being able to use recursion with your own inscriptions.
I am thinking that replies can be implemented like parent-child but you don't have to send the parent as an input.
Whatdoyathink?
Beta Was this translation helpful? Give feedback.
All reactions