Notifications are not instant?

[tonaltti]

If I understand correctly, PubSubHubbub is based on YouTube's RSS feed. In my experience, the RSS feed updates anywhere from 0 to 20 minutes after an upload, so the notification is far from instant.

Is there a way to get instant notifications about uploads?

[SeoulSKY]

I couldn't find a reference that YouTube's PubSubHubbub is implemented with an RSS feed on their server.

The difference between the RSS feed and PubSubHubbub is that the RSS feed requires a client to do periodic polling, whereas, for PubSubHubbub, a client gets a POST request from the server. So, in theory, the notification from PubSubHubbub should be instant, unless the YouTube server uses a mechanism that introduces some delay.

I haven't measured the delay for their PubSubHubbub, but if you want to control the delay, you can use their RSS feed with periodic polling with a short interval, although it will be less efficient than using PubSubHubbub

[SeoulSKY]

Check out the new update:

pip install -U ytnoti

[tonaltti]

Now I do not get any output at all. Maybe it's listening for new videos. I need to now catch an upload from some channel.

[SeoulSKY]

Great!

[tonaltti]

It works, I get notifications about new uploads.

And also the notifications are instant. The delay to published_at timestamp from Youtube API is only 3-4 seconds.

Interestingly the video is still added to the feed file https://www.youtube.com/feeds/videos.xml?channel_id=UC9EEyg7QBL-stRX-7hTV3ng with a delay. In my latest test the delay was over 5 minutes.

But this is not a problem to me. I get most of the details in the notification video object and the missing details (like getting the type of the video: normal, live (upcoming), live (currently live), live (completed)) I can then query from Youtube API.

Maybe a support (optional) to Youtube API to get all details about the video could be integrated to this library?

I'll be using this library and I will report if I find any other problems or if I have any further suggestions. Thanks.

[SeoulSKY]

I'm glad that you successfully received the notification!

I can add an option to fetch additional video information from YouTube Data API in the next version.

Thank you for the suggestion and feel free to open up issues whenever you encounter a problem!

[tonaltti]

I have my script running since yesterday. Yesterday it notified about the uploads. Twice about the same live stream, but at least I got the notification.

But today it has not been giving notifications. No errors, nothing. What is the best way to debug this? It's important that the library would be reliable and it should at least throw an exception if something is not right. This is my current script:

from pyngrok import ngrok
from ytnoti import YouTubeNotifier, Video
from datetime import datetime

channel_ids = [
    "channelid1",
    "channelid2",
    "channelid3",
    "channelid4",
    "channelid5"
]

ngrok.set_auth_token("mytoken")

notifier = YouTubeNotifier()

@notifier.upload()
async def listener(video: Video):
    timestamp = datetime.now().strftime("%Y-%m-%d %H:%M:%S")
    print(f"[{timestamp}] New video properties:")
    for key, value in vars(video).items():
        print(f"{key}: {value}")

notifier.subscribe(channel_ids)

notifier.run()

[tonaltti]

That makes sense. Ngrok provides a free static domain so I got one. But how do I use it with ytnoti?

I tried like this:

tunnel = ngrok.connect(
    addr=8000,
    proto="http",
    domain="mystaticdomain.ngrok-free.app"
)

notifier = YouTubeNotifier()

And it opens a tunnel with my domain. But later I see in the log that it opens a tunnel again without the static domain. So I guess ytnoti needs somekind of support for this?

[tonaltti]

Nevermind. I can do this:

tunnel = ngrok.connect(
    addr=8000,
    proto="http",
    domain="mystaticdomain.ngrok-free.app"
)

notifier = YouTubeNotifier(callback_url="https://mystaticdomain.ngrok-free.app")

Now lets see if it works for a week.

[SeoulSKY]

Great! Hopefully it works

[tonaltti]

Just an update that with static domain I didn't face the same problem anymore. But maybe the dynamic ngrok domain problem could be described in the documentation as that is something many users are likely to experience.

[SeoulSKY]

Yeah, I'll update the document so that they are aware it's for development only