What does "Published by Teradek" mean?
The "Published by Teradek" text means that the stream was created using Teradek's direct integration with Facebook's API through one of our hardware encoders (e.g. Cube, VidiU, Slice, T-RAX), software encoders (e.g. Live:Air or Live:Air Solo), or streaming services (Core or ShareLink).
Why does this identification text appear?
The "Published by Teradek" identification text is required by Facebook as part of having access to their API and creating streams through a customer's account.
Any third party publishing tool must identify itself as part of Facebook's rules for API use.
For example, if you were using Hootsuite or other apps to manage content within Facebook, you would see the name of the tool as part of the post:
Who is able to see the "Published by Teradek" text?
This identification text isn't visible to the public viewing the stream, it's only visible to page administrators who are logged in and viewing the page.
This is mentioned if you click the [?] at the end of the "Published by Teradek" text, as shown in the screenshot below:
This post on Facebook's community support also states that the visibility is limited to managers on a Page, and further links to Facebook's help center which mentions that this identification text is only visible to Page admins:
Is Teradek claiming rights to my stream?
Teradek is not claiming any ownership, copyright, or any other rights to the stream.
Can I change the text shown from "Published by Teradek" to my own name or something else?
It's not possible to change that text because it relates to the tool used for publishing the stream, and not to the company or individual that was responsible for the stream using Teradek hardware, software, or services.
Can I not have the "Published by Teradek" text appear at all?
You cannot use Teradek's built-in integration with Facebook and not have this text shown for the reasons listed above.
The only way to not have the "Published by Teradek" identification text listed on a post is if you use manual RTMP configuration for each stream.
However, if you use manual RTMP configuration you run into all the caveats that Facebook places upon stream key generation, expiration and non-reuse, as described here: