Dang, you’re right! Thanks for clearing that up. So is the best way really to do something like:
for tag in event[1]['tags']:
if tag[0] == 'p':
pubkey_ref = tag[1]
if tag[0] == 'e':
target_eventID = tag[1]
\",\"display_name\":\"PABLOF7z\",\"about\":\"Other Stuff maximalist\",\"nip05\":\"_@f7z.io\",\"lud16\":\"pablof7z@ln.tips\",}",
Can I ask a stupid question:
Why are tags a list instead of a dictionary?
Makes it really annoying to parse through. Right now I have to create a for loop to with an if statement since the data is unordered.
Am I missing something?
Makes sense, I agree
At least one cool thing about comment bots is that they will work on all social clients since the communication protocol is standardized
Looking forward in seeing how clients evolve and new concepts surrounding DVMs 🤙
Yes, exactly a bot. Would you not say that DVMs are just bots with paywalls?
It takes an data input with a payment and then provides an data output.
The convenience of a simple comment bot that can be tagged is that it is a familiar interface that doesn’t require additional development from clients.
Curious on how you see DVM integration in the future
Interesting, I’ve been thinking about this too.
I wrote up a DVM standard for video translations and was trying to think of ways to integrate into clients, but the way it is structured currently would require the client developer to add features. Which is why dedicated DVM clients have been created like “Vendata”.
The path I am starting to go down now is to work within the constraints of existing clients by creating a DVM that “listens” for comments and then replies with invoices, which once paid would result in the desired content.
@lemon Turkish