Closed tzarebczan closed 6 years ago
@nikooo777 is aware of this one and it requires some type of decoding of claim data.
From Jack: jack [2:56 PM] not without building lbryschema into lbrycrd to decode them [2:56] lbrycrd returns protobuf claims as some kind of escaped unicode (edited) jack [2:58 PM] it probably wouldnt be terribly difficult to include lbryschema.go for decoding/validating them to json text (edited)
I have a feeling chainquery could work some magic for the claimbot @tiger5226
yeah chainquery can provide the decoded json data of a claim or channel. For example @fillerino
All claims are stored in the claim
table and to get the decoded json data the column is value_as_json
all decoded and waiting for you :) . Also to determine the difference between a stream and a channel just use claim_type
column. 0 is stream and 1 is channel.
Fixed in #210
If content is posted under a channel, it should show the URL as lbry://@jiggytom#232131231231231/claimname
actual example from recent content post: lbry://@humblegoddess#7d00b2935e6f508bf5e2cbef609571f96495bedb/twitchstream91120171