You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
General feedback on Private BOT Network on Public Blockchain Testnet. Some are nits while others are a bit more important. Thanks for making this!
Unclear Title
The title of the article itself doesn't suggest that it is a tutorial.
O/T Terminology for New Members
Members of the community frequently refer to O/T/B for Orchestrator/Transcoder/Broadcaster. As someone new to the community, that was not immediately apparent to me. I'd suggest either explicitly stating the mapping between acronyms or remove them entirely.
Beyond running the broadcaster
If this is truly for testing your orchestrator E2E, you should include instructions on transcoding an arbitrary dataset and viewing it (similar to the livepeer docs).
Expansion of "become an orchestrator"
I'm aware this section is not complete yet. When it is, I'd suggest fully expanding on each input (what it is/why it's necessary). When it gets to setting your URI, there should be very clear instructions stating this needs to be your public IP (and potentially link to whatsmyip). In the current list of registered orchestrators, there are still a few with local ips as their registered uri.
The text was updated successfully, but these errors were encountered:
General feedback on
Private BOT Network on Public Blockchain Testnet
. Some are nits while others are a bit more important. Thanks for making this!Unclear Title
The title of the article itself doesn't suggest that it is a tutorial.
O/T Terminology for New Members
Members of the community frequently refer to O/T/B for Orchestrator/Transcoder/Broadcaster. As someone new to the community, that was not immediately apparent to me. I'd suggest either explicitly stating the mapping between acronyms or remove them entirely.
Beyond running the broadcaster
If this is truly for testing your orchestrator E2E, you should include instructions on transcoding an arbitrary dataset and viewing it (similar to the livepeer docs).
Expansion of "become an orchestrator"
I'm aware this section is not complete yet. When it is, I'd suggest fully expanding on each input (what it is/why it's necessary). When it gets to setting your URI, there should be very clear instructions stating this needs to be your public IP (and potentially link to whatsmyip). In the current list of registered orchestrators, there are still a few with local ips as their registered uri.
The text was updated successfully, but these errors were encountered: