My Gunt Across America channel on Odysee has been flagged for DMCA yet I don't see an actual DMCA complaint for it on the Lbry github so I think Tom may have done this one on his own:
https://odysee.com/@GuntAcrossAmerica:c
Tom unquestionably did it on his own.
LBRY's verbiage in describing their DMCA responses is distinct:
Since the message is displayed by the block explorer, it stands to reason that the block explorer is performing some type of check to determine when to show the message instead of the underlying content. To figure this out, I was able to search this phrase in their block explorer Github repository, which let me find the file where the software checks to see if this text should be inserted:
The new LBRY block explorer. Contribute to lbryio/block-explorer development by creating an account on GitHub.
github.com
The message is displayed instead of the claim based on the status of a variable, "claimIsBlocked":
I then searched for this variable in the same repository, and was lead back to the MainController file that I'd previously used to determine that Tom has been the one in charge of labeling staff accounts, as is described in my last LBRY post. Searching within this file reveals that "claimIsBlocked" is defined by parsing a file that is read in from the LBRY API:
The new LBRY block explorer. Contribute to lbryio/block-explorer development by creating an account on GitHub.
github.com
As it turns out, LBRY maintains a hard block list (distinct from the search blacklist) for all content that it deems unlawful or infringing. That list is not directly published anywhere but can be found via their API. It contains about 3500 entries, and anything on the list is hard-blocked from all LBRY applications, including the block explorer itself, meaning that the only way to interact with such a claim is using the Chainquery SQL API.
I was able to use the SQL API to determine that the transaction hash associated with @GuntAcrossAmerica is "cb0acfc45b182080c6737fb0c5d6eb82e6e97c80a27b5dca17491380e2f7006b" (note that this is a transaction hash, not a claim ID):
Lo and behold, when I searched the global block list...
There it is.
Tom added the channel to the global block list, blocking it and all of its content from LBRY Inc's services in the absence of any DMCA claim.
Be careful interacting with the claims in this list. It's likely that this is how they filter the truly heinous NSFL garbage that some people upload. I'd strongly recommend not using the API to do things like retrieving thumbnails associated with random claims on there or you might accidentally find seriously horrible content, and instead just check to see if known IDs you're interested in are on the list as evidence of illegitimate blocking.