#youtube api

[ashtonfei]

Automate The Boring: Easily Update YouTube Titles and Descriptions in Multiple Languages

Easily Update YouTube Titles and Descriptions in Multiple Languages

google apps script, google sheets, google docs, google slides, google forms, google workspace, add-on, automation, google blogger, web app,

[cai-tan]

YouTube Integration Update

TL;DR: It ain't happenin', folks.

Standard Greeting Protocol, Toaster Frickers! So far, using Restream to multi-stream to YouTube has been functional enough for the sake of providing an additional watch vector as well as VOD backups. During this testing process, I did outline several potential functionality upgrades to integrate YouTube API stuff into KT-1632, namely subscriptions, monetization events, and a very limited embedded chat. Unfortunately, after reviewing the API documentation, I have decided to hold off on doing so indefinitely.

And, by "hold off indefinitely", I mean… Guys, it's bad. It's real bad. I'll put a more in-depth technical explanation of how bad it is somewhere else (probably the Discord and/or on Tumblr), but in short: It is literally impossible to have a real-time representation of stream chat, or literally any channel event on YouTube.

As such, I will likely not be spending any resources on making the YouTube streaming experience more interactive for YT watchers, and will instead focus on reminding YT watchers that Twitch is the main focus for stream interaction. I'd like to also mention I am working on some new stuff to try and help with audience interaction on Twitch as well, so look forward to that!

That's all in terms of important stuff for layman's terms, so let's get down to brass tacks.

When it comes to Twitch integration, it's pretty simple. Stream chat is handled via an IRC (Internet Relay Chat) protocol, a well-documented connection-based asynchronous realtime message system. KT-1632 easily connects to this via a standard greeting protocol (heh) over an ongoing connection that is authenticated using similar methods to the rest of the Twitch API. Meanwhile, other events, such as follows, channel points, subscriptions, etc. are all handled using either PubSub (publish/subscribe messaging protocol, also over an async connection) or the Websockets-based EventSub endpoint. This is all great, because all we have to do to maintain this is an occasional exchange of incredibly small keep-alive packets; we simply wait for Twitch to give us the good news in all these scenarios, and then handle those events as they arrive.

YouTube's API has… literally nothing.

Okay, it's not nothing nothing, obviously they have a series of REST (representational state transfer) API calls. I make an HTTP GET request, posting a ton of authentication information as well as the details of exactly what I want YouTube to do -- such as "give me the names of all public subscribers on the channel", or "create a Community post with the following text" -- and YouTube gives me some sort of response with the results of the request, generally in a big glob of JSON data. This is fine for an entirely passive system to generate a number somewhere on initialization of a webpage, or making some sort of administrative action.

So, you find yourself asking the exact same question I am: How do you get stream chat?

YouTube's own documentation, as well as every single resource I could find on the matter online, only have one answer: You (the developer) make one REST API call at a time, at some sort of polling rate, and process the result yourself, in order to find out if there's anything new to process. You drive out to YouTube, knock on YouTube's door, ask them if there are new chat messages, they give you a piece of paper that you need to process in a machine back home, you drive back home, and you run that piece of paper through the machine, and it tells you "Nope, no new messages." And, you have to do that every time you are ready to read a new chat message, whether there was one or not.

And guess what? That drive to and from YouTube costs gas. The REST API has rate limits that are entirely unreasonable for the sake of streaming. YouTube gives you a "quota" (worst choice of word for it, by the way) of 10,000 points per day, and every single REST call costs at least 1 quota. Let's say I wanted the absolute bare minimum of 1000ms "response time", I.E. one full second between polling calls, meaning messages can take up to a full second to show up on stream, which is already pretty egregious. Let's do the math! A full four hour stream is 240 minutes… which is 14,440 seconds… at one request per second, that's already 144% the daily "quota". And that's just for stream chat. It's a shared pool if I also wanted subscriptions, memberships, superchats, etc.

There is no websocket endpoint. There is no PubSub. There is no IRC. It's just REST calls, and you do not get enough REST calls (without paying Google, that is) to run a full stream at realtime, even with 1000ms latency.

This is incredibly ridiculous, especially given how easy and efficient it is to set up any sort of publish-subscribe endpoint over an exclusively RESTful API. Google's a massive corporation with insane technologies with more than enough manpower and machine-power to make this happen. Twitch's API is a bit jank and annoying to learn, but it fucking works. I feel like I'm screaming at Google, "JUSTIN KAN WAS ABLE TO BUILD THIS IN A CAVE! WITH A BOX OF SCRAPS!"

But yeah, in conclusion, no YouTube chat integration or notifications for now. The streams themselves aren't going away, but I will be paying even less attention to the chat moving forward, outside of moderation duties as required of me.

[mrhairybrit]

YouTube Channel ID and User ID [What is it? & How to use it]

YouTube Channel ID and User ID [What is it? & How to use it] #youtube #socialmedia

A YouTube channel ID is a string of letters and numbers that uniquely identifies a YouTube channel. It is used to distinguish one channel from another and to associate a channel with its owner. To find your YouTube channel ID: Go to YouTube and sign in to your account. Click on your profile picture in the top right corner of the screen and select “My channel” from the dropdown menu. Your…

View On WordPress

[jendhil]

How to Create Youtube Data Api V3

[mobil13com-blog]

YouTube'dan Yuvarlak Hesaplar!

Yeni haber paylaştı! https://www.mobil13.com/youtubedan-yuvarlak-hesaplar-18465.html

YouTube'dan Yuvarlak Hesaplar!

YouTube Abone Sayısı Değişikliği 

YouTube, kanal abone sayısını görüntüleme mekanizmasında bir değişiklik olduğunu açıkladı. Şimdi bazı arayüzlerde yuvarlak bir sayı gösteriliyorsa, diğerlerinde ise kesin bir sayı olsa da, Ağustos 2019’dan itibaren her yerde yaklaşık bir değer gösterilecektir.

Kanal 4237 aboneye sahipse, sayaç 4300 aboneye ulaşana kadar sayaç “4.2k” gösterecektir.

Kanal 133.033 aboneye sahipse, kanal 134.000 aboneye ulaşana kadar cihaz “133K” gösterecektir.

Kanal 51,378,232 aboneye sahipse, sayaç 52.000.000 aboneye ulaşana kadar sayaç “51M” gösterecektir.

Kesin abone sayısı yalnızca kanalın 1000’den az olması durumunda görüntülenecek. İçerik oluşturucular YouTube Studio‘da tam sayıyı görmeye devam edecek.

Bu değişiklik aynı zamanda aboneleri saymak ve kanal büyümesini hesaplamak için YouTube API‘sini kullanan üçüncü tarafları da etkileyecektir. Blogcuların popülaritesini ölçen Social Blade şirketi Twitter’da, yeniliğin veri gösterimini etkileyeceğini söyledi.

[mobil13com-blog]

YouTube'dan Yuvarlak Hesaplar!

Yeni haber paylaştı! https://www.mobil13.com/youtubedan-yuvarlak-hesaplar-18465.html

YouTube'dan Yuvarlak Hesaplar!

YouTube Abone Sayısı Değişikliği 

YouTube, kanal abone sayısını görüntüleme mekanizmasında bir değişiklik olduğunu açıkladı. Şimdi bazı arayüzlerde yuvarlak bir sayı gösteriliyorsa, diğerlerinde ise kesin bir sayı olsa da, Ağustos 2019’dan itibaren her yerde yaklaşık bir değer gösterilecektir.

Kanal 4237 aboneye sahipse, sayaç 4300 aboneye ulaşana kadar sayaç “4.2k” gösterecektir.

Kanal 133.033 aboneye sahipse, kanal 134.000 aboneye ulaşana kadar cihaz “133K” gösterecektir.

Kanal 51,378,232 aboneye sahipse, sayaç 52.000.000 aboneye ulaşana kadar sayaç “51M” gösterecektir.

Kesin abone sayısı yalnızca kanalın 1000’den az olması durumunda görüntülenecek. İçerik oluşturucular YouTube Studio‘da tam sayıyı görmeye devam edecek.

Bu değişiklik aynı zamanda aboneleri saymak ve kanal büyümesini hesaplamak için YouTube API‘sini kullanan üçüncü tarafları da etkileyecektir. Blogcuların popülaritesini ölçen Social Blade şirketi Twitter’da, yeniliğin veri gösterimini etkileyeceğini söyledi.

[vetripandi]

Android Search Play Youtube Videos API

Android Search Play Youtube Videos API

Android Search Play Youtube Videos API – In this tutorial i will show how to create Android Search and Play Youtube Videos using YouTube Player Data v3 API. Most of developers used YouTube player API for their personal android application or company based projects. YouTube Player Data V3 API used for search and get the accurate results of the videos and play from YouTube android application or…

View On WordPress

[vetripandi]

How Play YouTube Videos Android Application

How Play YouTube Videos Android Application

How Play YouTube Videos Android Application – Here i will give the detailed explanation about YouTube API and how to used for our android application. Let’s see how to play the YouTube videos in your android application using YouTube official API. When you have get videos from YouTube just give permission from YouTube. I mean first you have to get API and then get the YouTube videos from server.…

View On WordPress