Skip to content

Site is banned - on a local instance of encoder #395

@VWarte

Description

@VWarte

Hi,

I need some clarification on the privacy policy of AVideo and the AVideo-Encoder.

I run my own instance of AVideo and my own instance of AVideo-Encoder on local hardware. In the last days, I wasn't able to access my locally run AVideo-Encoder instance because "Your site is banned".

Yes, my site is on the blacklist now ( https://search.youphptube.com/blackListed ), and yes, I've read what content is not supported by AVideo. But the question here has a global character, since both Streamer and Encoder aren't accessible by the public, there should have been no way to even review what content was being used here.

That raises the question, how is that even possible? Does AVideo or AVideo-Encoder has a callback function or a backdoor, that exposes private content without user's knowledge to WWBN? Or is there some kind of a local "crawler" that has a certain word-blacklist?

If I would host an AVideo-Stream-Site and AVideo-Encoder-Site for corporate usage, with content that is only meant to be seen internally by employees, would the content still be exposed to WWBN, just to "validate" it's not "porn" or similar?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions