Could you please make an Android version...

[ghost]

that removes the blacklist?

[paveloom]

Maybe when I have an Android phone.

[paveloom]

Heads up! The Android fork is here. Some testing would be appreciated, though.

[ghost]

Hello, @ismail6172. Thanks for the report!

There are indeed two lists:

• api.lbry.io/file/list_blocked
• api.lbry.io/file/list_filtered

Both should by bypassed by my patch in the Android version:

Here's the patch:

https://github.com/paveloom-f/lbry-android/blob/29b66c3d42e7c4fc76fa6847f8d5d2a6d9687955/.github/scripts/build_a_release.bash#L18-L19

Here's the diff:

diff --git a/app/src/main/java/io/lbry/browser/MainActivity.java b/app/src/main/java/io/lbry/browser/MainActivity.java
index 5bee4b9..835faf2 100644
--- a/app/src/main/java/io/lbry/browser/MainActivity.java
+++ b/app/src/main/java/io/lbry/browser/MainActivity.java
@@ -2935,12 +2935,12 @@ public class MainActivity extends AppCompatActivity implements SdkStatusListener
 
                     JSONObject blockedObject = (JSONObject) Lbryio.parseResponse(Lbryio.call("file", "list_blocked", context));
                     JSONArray blockedArray = blockedObject.getJSONArray("outpoints");
-                    Lbryio.populateOutpointList(Lbryio.blockedOutpoints, blockedArray);
+                    // Lbryio.populateOutpointList(Lbryio.blockedOutpoints, blockedArray);
                     startupStages.set(STARTUP_STAGE_BLOCK_LIST_LOADED - 1, new StartupStage(STARTUP_STAGE_BLOCK_LIST_LOADED, true));
 
                     JSONObject filteredObject = (JSONObject) Lbryio.parseResponse(Lbryio.call("file", "list_filtered", context));
                     JSONArray filteredArray = filteredObject.getJSONArray("outpoints");
-                    Lbryio.populateOutpointList(Lbryio.filteredOutpoints, filteredArray);
+                    // Lbryio.populateOutpointList(Lbryio.filteredOutpoints, filteredArray);
                     startupStages.set(STARTUP_STAGE_FILTER_LIST_LOADED - 1, new StartupStage(STARTUP_STAGE_FILTER_LIST_LOADED, true));
                 } catch (Exception ex) {
                     // nope

You can check if either of the lists is ignored by doing the following:

1. Take a hash ID from the list, removing the :0 part in the end
2. Query the blockchain to get metadata (change the hash in the SQL query)
3. Check the name of the claim on Odysee.com to see if it's actually blocked / filtered
4. Check the name of the claim in either of my forks to see if it's accessible

Here's an example from the blocked list:
@GIRLSMUSIC (1441007a20747b1b9f92dfac620089308268be23afe99b35d8c410dfd3aaeeb6)

You can check the filtered list yourself (lots of NSFW content, so I won't post it here).

I can confirm that claims from the filtered list are not accessible with the Android fork, despite the patch above. That's weird, because the snippet above is the only place where the list_filtered endpoint is queried.

What's also weird is that I don't see the transaction hash ID of the channel you mentioned in either of the lists.

I will investigate it further.

I forgot to mention that the videos/channels do show up on search results but when you click on them it does it says nothing found as if the claim was abandoned or never existed. I hope that helps.

[paveloom]

Correction: I can see the filtered content from the filtered list. Not sure why I couldn't before. So, both lists are bypassed.

Looking at the code, the There's nothing at this location message is only rendered in these two components:

FileViewFragment:
https://github.com/lbryio/lbry-android/blob/master/app/src/main/java/io/lbry/browser/ui/findcontent/FileViewFragment.java#L941-L988

ChannelFragment:
https://github.com/lbryio/lbry-android/blob/master/app/src/main/java/io/lbry/browser/ui/channel/ChannelFragment.java#L485-L510

Both will render this text after failing to resolve the claim using https://api.lbry.tv/api/v1/proxy. Perhaps, this is where censoring (or a serch error) happens.

Do you have other examples of channels or files you don't see in the Android app, besides @WebmPoster?

[ghost]

Correction: I can see the filtered content from the filtered list. Not sure why I couldn't before. So, both lists are bypassed.

Looking at the code, the There's nothing at this location message is only rendered in these two components:

FileViewFragment:
https://github.com/lbryio/lbry-android/blob/master/app/src/main/java/io/lbry/browser/ui/findcontent/FileViewFragment.java#L941-L988

ChannelFragment:
https://github.com/lbryio/lbry-android/blob/master/app/src/main/java/io/lbry/browser/ui/channel/ChannelFragment.java#L485-L510

Both will render this text after failing to resolve the claim using https://api.lbry.tv/api/v1/proxy. Perhaps, this is where censoring (or a serch error) happens.

Do you have other examples of channels or files you don't see in the Android app, besides @WebmPoster?

I will try to find more. I found one more so far.

lbry://@WeWuzKangz

[ghost]

Correction: I can see the filtered content from the filtered list. Not sure why I couldn't before. So, both lists are bypassed.

Looking at the code, the There's nothing at this location message is only rendered in these two components:

FileViewFragment:
https://github.com/lbryio/lbry-android/blob/master/app/src/main/java/io/lbry/browser/ui/findcontent/FileViewFragment.java#L941-L988

ChannelFragment:
https://github.com/lbryio/lbry-android/blob/master/app/src/main/java/io/lbry/browser/ui/channel/ChannelFragment.java#L485-L510

Both will render this text after failing to resolve the claim using https://api.lbry.tv/api/v1/proxy. Perhaps, this is where censoring (or a serch error) happens.

Do you have other examples of channels or files you don't see in the Android app, besides @WebmPoster?

You think you could release an Android fork with video optimization disabled? It's just transcoding but rebranded. You can't disable it when uploading videos. Not really needed as I can upload on Desktop but would be more convenient so I would appreciate it.

[paveloom]

Aight, I can confirm that this channel is also inaccessible in the Android fork.

These two channels (lbry://@WebmPoster and lbry://@WeWuzKangz) aren't in the public list_filtered and list_blocked lists, so the origin of blocking is unknown to me. At the moment, though, I do believe that these claims aren't being resolved on the server-side (the app queries https://api.lbry.tv/api/v1/proxy, as described above, which is an older version of the API). Since it happens on the server, I can't change it.

Disabling the optimization is out of scope of that repository. Some trickery with paths could be applied by someone interested.