Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
How does a website (or podcast) send out notification of updates?
How does a website (or podcast) send out notification of updates?
I have subscribed to a sample podcast and see that I do get alerts (upper right corner of screen) on my MacBook. I have not yet verified those alerts only show up when I have Chrome opened, but that because I always have Chrome open.
Here is what I see under Settings as the Allowed sites.
What is port 443?
Does this mean my port 443 is open to alerts from these two websites?
Please let me know how this works, since I am considering using this for my podcast. Or, if you give me the name of this type of communications, I can look for solutions which I can adopt to have this behavior.
Thanks.
I have subscribed to a sample podcast and see that I do get alerts (upper right corner of screen) on my MacBook. I have not yet verified those alerts only show up when I have Chrome opened, but that because I always have Chrome open.
Here is what I see under Settings as the Allowed sites.
What is port 443?
Does this mean my port 443 is open to alerts from these two websites?
Please let me know how this works, since I am considering using this for my podcast. Or, if you give me the name of this type of communications, I can look for solutions which I can adopt to have this behavior.
Thanks.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Mostly it doesn't... a method called RSS is used:
https://en.wikipedia.org/wiki/RSS
See also chapter 6 in there: https://en.wikipedia.org/wiki/RSS#Podcasting_and_RSS
The client regularly check this "RSS"-feed which hold a list of "new" items.
if the RSS Summary changes the actual content is fetched.
Port 443 is a HTTPS protocol port. (normal web access).
https://en.wikipedia.org/wiki/RSS
See also chapter 6 in there: https://en.wikipedia.org/wiki/RSS#Podcasting_and_RSS
The client regularly check this "RSS"-feed which hold a list of "new" items.
if the RSS Summary changes the actual content is fetched.
Port 443 is a HTTPS protocol port. (normal web access).
Hi !
Is not a real "push" mode. A simple extension for Chrome scan for changes on target website (or page or specific part of). Podcasts and RSS cannot work in push mode.
Is not a real "push" mode. A simple extension for Chrome scan for changes on target website (or page or specific part of). Podcasts and RSS cannot work in push mode.
So, the website adds its URL:443 to Chrome so it can be allowed?
I also notice different types of alerts. Some flash up, then disappear. The ones from Bongino.com stay in the upper right until you close the alert.
That makes the alert more noticeable, but makes it more likely to end with an un-subscription.
How does that delay thing work? Can it be tailored so only certain ones force the user to Close it?
Thanks.
I also notice different types of alerts. Some flash up, then disappear. The ones from Bongino.com stay in the upper right until you close the alert.
That makes the alert more noticeable, but makes it more likely to end with an un-subscription.
How does that delay thing work? Can it be tailored so only certain ones force the user to Close it?
Thanks.
Basically it's just ca call to a page element with refresh every 5,10...X seconds. The server are responding with an alert (a very little "webpage") in JavaScript that can have any "face". Usually, the programmer decide the actions available.
Some extensions can be tailored, some not.
Some extensions can be tailored, some not.
A better way to think about this may be to just consider an RSS feed to be what it is... a passive setup of updates, published on your Website at some interval... some RSS feed updates are generated by a give action, like a page/post update...
Other updates occur via system CRON or WordPress CRON. These are clock updates.
This is all your site does.
For external sites, like iTunes or other Podcast directories, you register your site RSS feed link with these sites, then they scan your RSS feed at some interval (you have no control over this interval) to generate what you're calling an update.
Normally all this is handled for you, if you use something like WordPress + the Power Press plugin.
Other updates occur via system CRON or WordPress CRON. These are clock updates.
This is all your site does.
For external sites, like iTunes or other Podcast directories, you register your site RSS feed link with these sites, then they scan your RSS feed at some interval (you have no control over this interval) to generate what you're calling an update.
Normally all this is handled for you, if you use something like WordPress + the Power Press plugin.
Ow that could be notifications using an javascript style thing:
https://www.w3.org/TR/notifications/
That would require you "being active on the site" where RSS can be used without continously having access to the site and just query once in a while.
https://www.w3.org/TR/notifications/
That would require you "being active on the site" where RSS can be used without continously having access to the site and just query once in a while.
I assume if I start my channel using Podbean, I have no control over such updates. But, if I decided to move the podcast hosting to my Wordpress site, I would have the ability to insert unique Javascript for different types of ads.
But, when sent to iTunes or SOundCloud, I would have no control.
True?
But, when sent to iTunes or SOundCloud, I would have no control.
True?
Most probably.
If ads get served over notifications then for me that would mean end of notifications period.
Notification are the new pop-ups ajax style. And the authorisation of those can also be revoked.
This time with controls for allowance up front, not as an afterthought.
If ads get served over notifications then for me that would mean end of notifications period.
Notification are the new pop-ups ajax style. And the authorisation of those can also be revoked.
This time with controls for allowance up front, not as an afterthought.
> And the authorisation of those can also be revoked.
I assume you mean it's simple for a recipient to be disgusted by the ads and remove the URL from the "Allow" list. (I am about to do the same exact thing for this podcast.)
OR, do you mean there is some advisory board which revokes such privileges?
I would only consider using ads for my podcast when they were specifically to advertise an appearance I was going to make, personally, like in New York City, or where there are tickets available. Or to promote an download opportunity where I am providing premiere programming, of my own making, for a small fee.
But, even that could result in cancellations.
Thanks.
I assume you mean it's simple for a recipient to be disgusted by the ads and remove the URL from the "Allow" list. (I am about to do the same exact thing for this podcast.)
OR, do you mean there is some advisory board which revokes such privileges?
I would only consider using ads for my podcast when they were specifically to advertise an appearance I was going to make, personally, like in New York City, or where there are tickets available. Or to promote an download opportunity where I am providing premiere programming, of my own making, for a small fee.
But, even that could result in cancellations.
Thanks.
Sounds like you may be new to Podcasting + how Ad Networks work (behind the scenes).
If you try serving Ads using standard Ad Networks, very unlikely anyone will see an Ad Unit, the way you'd like to have them see the Ad Unit.
This has to do with how Podcast feeds work + how Ad Networks serve Ad Units.
The only way to know 100% your Ad Unit is reaching your audience, is to embed the Ad Unit in your audio track.
This means you'll be embedding Ad Spots just like an old school radio show.
Only your audio track reaches your audience, intact. Any other tech will likely be stripped along the way.
If you really are new to this game, likely best to reach out to folks who've been doing this a while + have a few short conversations with people about Podcast monetization strategies.
If you try serving Ads using standard Ad Networks, very unlikely anyone will see an Ad Unit, the way you'd like to have them see the Ad Unit.
This has to do with how Podcast feeds work + how Ad Networks serve Ad Units.
The only way to know 100% your Ad Unit is reaching your audience, is to embed the Ad Unit in your audio track.
This means you'll be embedding Ad Spots just like an old school radio show.
Only your audio track reaches your audience, intact. Any other tech will likely be stripped along the way.
If you really are new to this game, likely best to reach out to folks who've been doing this a while + have a few short conversations with people about Podcast monetization strategies.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial