Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show error message when content is blocked by ISP #460

Open
10 tasks
kekkyojin opened this issue Oct 16, 2023 · 1 comment
Open
10 tasks

Show error message when content is blocked by ISP #460

kekkyojin opened this issue Oct 16, 2023 · 1 comment

Comments

@kekkyojin
Copy link
Collaborator

The Issue

Steps to reproduce

  1. Ensure you are using the app from a Spanish IP address
  2. Go to any livestream

Expected behaviour

Content is played. As some ISPs will block any content from odysee.live, user should be warned that somebody is blocking that content. Showing the page content message would be OK; see "Anything Else" section to know which 'page content' I am talking about.

Actual behaviour

Player opens, but never plays. Related content is forever loading

Anything Else

Try opening the VideoURL on a browser (for example, https://cloud.odysee.live/content/fdd11cb3ab75f95efb7b3bc2d726aa13ac915b66/master.m3u8 NFW, this is RT International livestream). After ignoring the certificate warnings, an error page will show you that content is blocked. I was lucky. Until no so long ago, this kind of blocking were simply returning a 4xx HTTP error code without further explanation.

Likely, at some time, odysee.live domain was added to Telefonica list of blocked domains. Major Spanish ISP providers tend to sync their own list with Telefonica's.

Trying to access the same VideoURL using a Japanese IP via a VPN will play the stream without issues.

Screenshots

Internal Use

Acceptance Criteria

Definition of Done

  • Tested against acceptance criteria
  • Tested against the assumptions of the user story
  • The project builds without errors
  • Unit tests are written and passing
  • Tests on devices/browsers listed in the issue have passed
  • QA performed & issues resolved
  • Refactoring completed
  • Any configuration or build changes documented
  • Documentation updated
  • Peer Code Review performed
@kekkyojin
Copy link
Collaborator Author

By the way, of course this is also a problem on Odysee iOS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant