obsproject
rtmp-services: Add hakuna live RTMP service
Description
Adding Hakuna Live's RTMP Ingest server address
Motivation and Context
Hakuna Live is one of the global live streaming service platforms. To make it easier for streamers to access Hakuna Live, add this address.
How Has This Been Tested?
I followed service submission guidelines and confirmed streaming's working.
Types of changes
New feature (non-breaking change which adds functionality)
Checklist:
- [x] My code has been run through clang-format.
- [x] I have read the contributing document.
- [x] My code is not on the master branch.
- [x] The code has been tested.
- [x] All commit messages are properly formatted and commits squashed where appropriate.
- [x] I have included updates to all appropriate documentation.
Hello, can you please confirm that you are a representative of Hakuna Live?
We are also unable to validate the service as is appears to be blocked in the US.
Hello, can you please confirm that you are a representative of Hakuna Live?
Hi, I'm working at hyperconnect which is devloper of hakuna live service. (https://hakuna.live) service provider is movefast company. My email address ([email protected]) indicates that I am an employee of hyperconnect. see https://www.movefast.company/company find family site. Is it enough or should I prove myself in other way?
We are also unable to validate the service as is appears to be blocked in the US.
We don't block any access but only registered users can stream to our server with streamKey. Now, We just run a streaming server for south korea and japan. What should I do in this case?
The service is indeed blocked in the US. Loading the page loads the front page completely, and the redirects with an error:
https://hakuna.live/en/unavailable-location
Can you provide any public details on current userbase? From what I was able to briefly see before the website blocked itself, there were under 50 active users.
You're right, I forgot that access from the U.S. is blocked. We operate a service in several regions, and when we consider all regions combined (Asia, Europe, MENA, etc.), there are around 1,000 to 1,600 users streaming simultaneously.
Our service offers both WebRTC and RTMP ingestion. The majority of our users utilize WebRTC, including WHIP, while a few continue to use RTMP.
I've fixed the merge conflicts and the commit message. Is the added service ingest really identified as "Republic of Korea, Japan"? It would be helpful from our point of view if we could check/verify the site and/or ingest list from US-based IP addresses.
Unfortunately, I have no control over allowing access from the US. However, I can try to speak to the department which has the authorization to open U.S, although it's difficult at the moment.
For my comment about the ingest name, I mostly just find "Republic of Korea, Japan" confusing, as a comma in this format usually indicates the first location is inside the second location. I would have expected "Republic of Korea / Japan" or something else. However, as I said, if your official documentation refers to it as "Republic of Korea, Japan", we aren't in the habit of mandating what you name your ingests. I just wanted to confirm that this isn't a mistake.
About opening to the US, I don't even need the ability to stream. I just wanted us to be able to easily verify the service is live/active. That said, we can probably waive this concern.