YouTube JavaScript Player API deprecated - youtube-javascript-api

I found the following link https://developers.google.com/youtube/youtube-api-list where "YouTube IFrame Player API" and "YouTube JavaScript Player API" are in the list of "YouTube API Subject to the Deprecation Policy".
Does it mean I cannot embed YouTube video on my site via JavaScript?
Thanks,

The deprecation policy explains whether Google will announce changes to the YouTube API and what they might change:
see https://developers.google.com/youtube/terms section I item 7.
It does not mean that the current YouTube Javascript API is obsolete.
Instead, it says that they will keep various APIs working for a year after announcing a need to shut them down, or until April 20, 2015.
Here is a shortened excerpt:
Google will announce if it intends to discontinue or make backwards
incompatible changes to this API or Service. Google will use
commercially reasonable efforts to continue to operate ... until the
later of: (i) one year after the announcement or (ii) April 20, 2015,
unless... The above policy is the "Deprecation Policy."

Related

API for sending closed captions to a Microsoft Teams meeting

Since August 25, 2021, Microsoft Teams has support for CART captioners to send text (captions) to the meeting. This is great!
See https://learn.microsoft.com/en-us/officeupdates/teams-admin
On this page
https://support.microsoft.com/en-us/office/use-live-captions-in-a-teams-meeting-4be2d304-f675-4b57-8347-cbd000a21260 is described how to obtain the CART caption link, to which my software need to connect.
But this is where the information ends. I cannot find the (Graph?) (REST?) API how to make this work.
I have searched the API reference https://learn.microsoft.com/en-us/javascript/api/overview/msteams-client?view=msteams-client-js-latest as well as SDK sources on GitHub. Nothing about CART or captions!
I hope someone can point to me to the documentation on how to feed Closed Captions to a MS Teams meeting... some Sample code is even better ;-)
Thanks
We have discussed with engineering team and get to know that GET API development is in-progress. There will never be a POST API for it.
We do not have exact ETA to share for now.
There is a CART API endpoint that you can use to push captions to Teams. This is the same URL that you get when you enable CART in the meeting options for your meeting . The details are available on the Teams Meeting Apps API reference page.

Is Using Deprecated Google Infographics API a Good Idea

So I have recently found out about Google Infographics QR Codes API which is very easy to use and I have yet to find a better alternative. Example: https://chart.googleapis.com/chart?cht=qr&chs=200x200&chl=Example:
However their documentation page (https://developers.google.com/chart/infographics/docs/qr_codes) says this: Warning: This API is deprecated. Please use the actively maintained Google Charts API instead. See our deprecation policy for details.
Also Google Infographics main page(https://developers.google.com/chart/infographics/) says the fallowing:
Deprecation notice
While the separate Google Charts service is actively maintained, the infographics service was deprecated in 2012 and turned off on March 18, 2019.
Go to Google Charts
About Google Infographics
This deprecated API serves static PNG images via URLs you can place in the src attribute of an tag.
As you can see eventhough Google says that it is turned off the API for QR Codes still works fine. Does this mean that I can still use this API with no worries? If not is there an equivalent API?
Using a deprecated anything is never a good idea. deprecation notices are there to tell developers that they need to move away from something because its due to be shut down.
If its deprecated that means they will turn it off. They start turning it off on "March 18, 2019". It can take a while for it to be completely turned off and some APIs continue to work for a year or so before they stop working all together.
I would not use this or develop with it as it is going to stop working soon.
Recommendations of equivalent APIs is out of scope for Stack overflow i suggest you Google it.

Workaround for new Instagram API restriction for tagged content

I built a module for my company's marketing team to fetch all the photos based on a hashtag. Such as #nofilter.
I was using the URL https://api.instagram.com/v1/tags/nofilter/media/recent with no problems until Instagram decided to change their API authentication to OAuth.
I followed the new guidelines but my client is still in sandbox mode and the API call doesn't return anything anymore. All it returns is:
{"pagination": {"deprecation_warning": "next_max_id and min_id are deprecated for this endpoint; use min_tag_id and max_tag_id instead"}, "meta": {"code": 200}, "data": []}
It seems like I need to submit my application to be reviewed before going live. But this doesn't seem possible, based on what i found from their submission guideline below. Is there any workaround for this?
====== UPDATE July 8th, 2016
I have found one of those 3rd parties that instagram mentioned, but the pricing is awful https://www.dialogfeed.com/pricing/
189 euros per month seem a bit steep
I had to deal with this. Their documentation is pretty unhelpful and doesn't seem to offer any solution for someone just wanting to collect relevant links, which should be no prob.
Fortunately, the script on an Instagram page provides easy access to their structured data. In my rails app I create a headless browser and just hit their url. I provided my solution as an answer to another question:
https://stackoverflow.com/a/38572893/4888422

Instagram API change without warning?

I know that as of June 2016, Instagram are going to vet who can use their API, but we've noticed something has changed early.
Does anyone have any information on how the vetting process is going to work?
Take a look at Instagram platform update.
Simplified platform policy
We’ve updated our Platform Policy to
explicitly list the use cases we will support moving forward. These
include apps and services that:
Help individuals share their own content with 3rd party apps, such as
apps that let you print your photos and import an Instagram photo as a
profile picture. Help brands and advertisers understand and manage
their audience, develop their content strategy, and get digital rights
to media. Established apps in this space may apply for our newly
announced Instagram Partner Program. Help broadcasters and publishers
discover content, get digital rights to media, and share media using
web embeds. You can read the full terms here.
New review process and sandbox
We will begin reviewing new and
existing apps before granting full API access starting December 3,
2015. Existing apps have until June 1, 2016 to submit and be approved.
We are also launching Sandbox Mode, which will let you privately build
and test your apps using Instagram’s APIs as your app is being
reviewed.

Is the myspace streaming subscription API still functional, and if so, how can I tell?

In an effort to get music-related events for an app we're building, we've mulled through Myspace's decidedly clunky authentication process and managed to set up a subscription and endpoint.
Using all this fun stuff:
http://wiki.developer.myspace.com/index.php?title=Category:Real_Time_Stream
http://wiki.developer.myspace.com/index.php?title=Stream_Subscription_API
http://wiki.developer.myspace.com/index.php?title=Stream_Subscription_Example_Walkthrough
The Myspace GET request verifies the existence of our subscription. So all we were hoping to do was sit back and wait...
...but even with no query filtering set whatsoever (i.e. we should get EVERYTHING that happens!), we seem to get no data pushed our way.
Most worrisome is that I don't see anyone talking about this on the web anytime recently. Does it still exist? It's still on Myspace's Developer homepage. Did they forget to take it down? Is their sense of self-esteem so low at this point (for obvious reasons) that they've stopped caring about whether their services work?
A boolean answer with conclusive supporting evidence would be most appreciated.
Links to resources and discussions less than a year old would be an awesome bonus.
Myspace has a very inactive MySpace Developer Team News and Announcements that lists various API modules designed to work with the ActivityStrea.ms standard and has a dedicated Activities API webpage with examples.
Once you view that page, you'll see they work within the depreciated OpenSocial API v1 Platform.
In reference to the Stream Subscription method your using, the History Log has the last entry at January 2010. It's safe to say that method has been abandoned. Reference screenshot:
I visited Wikipedia Myspace Page to discover what Developer API is currently used and was greeted with the same outdated information that you already have. The last API used was in 2010.
There still is hope for your goal of getting music related events via a current API method: The above Wikipedia page has a section titled Decline: 2008–present which links to footnote 71 for a January 2012 article: MySpace is Reborn at Panasonic Press Conference, Unleashes Justin Timberlake
That Wikipedia announcement reads:
In January 2012, the company announced at CES that it would introduce MySpace TV with Panasonic.
While Myspace is currently under the radar for developers and your goal is to get Music Related Events (from music artists?) via API, consider using YouTube API that has a powerful search feature to find such events from artists with legitimate YouTube ID's.
If that's not an option perhaps Myspace TV / Panasonic venture will come into fruition soon.
As this is not a happy answer, it's only fitting to Cry Me A River until a new API is realized.
Edit: As your looking for a Boolean Answer, MySpace API is false.
To complement that Boolean state, these other JavaScript values are considered false too: 0 -0 null "" undefined NaN.
WordPress for MySpace API is abandoned with last blog entry April 2010.
The MySpace Stream Subscription API is a component of MySpace RESTful API that is abandoned.
Finally, the MySpace Developer Home Page was last updated on December 2010.
Even to this day, Google Groups for MySpace API has no activity since July 2010.
The above links is Further Evidence that the MySpace API is dead.