-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Support for foreign user #737
Comments
i suppose that would be a big work but meanwhile meaningful one |
I will also help translate some content, but I think the translation of this repo may take a long time. |
yep, currently i work on bilibili clone (SEA version)
It's okay if it takes a long time since the project I'm working on is only for my hobby and learning new stuff. I fully understand that this will be difficult to do because of the existing structure and it will definitely be a big work, so I will not force anyone and while waiting I will try to understand it using the existing translation tools 😸 thanks for your response @cxw620 @MineCreeper86 |
We'll go ahead and try to support i18n, and the project will be completely refactored to facilitate the use of a parser that can generate code in a variety of languages. At that point, I think it will be easier to add i18n support. |
Awesome! I'm looking forward to it 🐈 |
Well, Bilibili SEA is separated and independent from Bilibili now, you have better to pay attention to the difference between their APIs. For example, Bilibili SEA service doesn't make use of gRPC, and playurl API has many unique params to determine users' location (Bilibili SEA only offers its service in South East Asia). You may need to determine API's request parameters by decompiling the Bilibili SEA offcial app or by network capture. This repo currently only collects and focus on Bilibili(China version, service area includes CN Mainland, CN HK, CN MO and CN TW)'s API, not Bilibili(SEA version). This's what I want to call your attention to. But I don't know if we would also collect Bilibili(SEA)'s API in the future (that's not difficult, I think, for the APIs are similar), for Bilibili Corp is increasingly focusing on business in SEA. If needed, I may contribute to the repo adding some playurl |
Naruhodo, if I look at it, indeed the API seems similliar. If I may, why the playurl need many unique params to determine users' location btw? is that for algorithm purpose to manage recommended videos or something like that?
Okay, I will try to observe the network traffic on chrome devtools then.
If you are interested, you can contribute to building a public collection API via Postman. Thanks for your information and advice! |
For applying area limitation, I think. Bilibili SEA's offcial app will verify both your phone's SIM card and geographic location of access IP. But we only need to simply imitate the network request of the official APP. Web API only requires that your geographic location of access IP is SEA.
When I'm free I'm happy to help to do so :) |
the documents are too large, i think translating them will spend a long time. |
I'm not a Chinese person, and I try to understand this documentation through translation tools, but sometimes the translation results tend to be stiff and become difficult to understand.
It would be nice if someone who doesn't mind volunteering to make a translated version of it, I would appreciate it very much.
Thanks for the great repository!
The text was updated successfully, but these errors were encountered: