paveloom-f fork of LBRY client and updates OK?

[yeehi]

1. If you install this fork of the LBRY client, and you are subsequently notified that updates are available, will the "updates" prevent the client from seeing masked content?

2. So that we can try to verify that this fork works as intended, can you provide a link to an example of some masked content which:

a) is masked by LBRY Inc. on Odysee
b) is still seeded and visible using this forked client?

3. What is the name for this forked client? the paveloom-f fork?

[paveloom]

Hello, @yeehi.

1. If you install this fork of the LBRY client, and you are subsequently notified that updates are available, will the "updates" prevent the client from seeing masked content?

Yes, self-updating the client will reset the lbryinc module, and the blacklist will become functional again. When a new update is available, one can download the patched version from here and install it over the current installation.

2. So that we can try to verify that this fork works as intended, can you provide a link to an example of some masked content which:
   a) is masked by LBRY Inc. on Odysee
   b) is still seeded and visible using this forked client?

Usually, any recent DMCA takedown can suffice. The takedown notices are stored here, so one can check any of these. Since they're not backed up by LBRY, Inc. anymore, these tend to die out pretty quick, since the upload authors leave them behind.

Here is an example of a still hosted one (at the moment of writing):
odysee.com/@BootyControl:3/Sanya-Twerks-Like-That-Booty-Isolation-Twerk:9.

The related notice is here.

Proof

3. What is the name for this forked client? the paveloom-f fork?

Well, it isn't supposed to have a name (technically, the name is paveloom-f/lbry-desktop). It's just a fork that changes a few lines of code, so I don't think it's necessary to have a distinct name for that.

[paveloom]

Just a heads-up: since v0.51.1, self-updating the client will not reset the blacklist anymore.