Hello.

I've added a new feature to time-to-stable that lists experimental APIs across browsers using BCD. This helps developers track experimental APIs, understand their stability, and consider the implications for website integration. It helps answer questions about cross-browser compatibility and potential deprecation, informing decisions about using these APIs.

Feature Policy is a powerful web platform tool that allows developers to control the behavior of APIs and features, similar to CSP. It helps manage third-party content by enabling or disabling functionalities like autoplay, geolocation, and sensor access within iframes, giving embedders more control over their page experience. Additionally, Feature Policy assists in maintaining performance budgets during development by flagging potential violations, such as excessive image downscaling, as demonstrated with the 'max-downscaling-image' policy used during Chrome Dev Summit. Developers can explore more about Feature Policy, code samples, and demos at featurepolicy.rocks, submit feedback at https://bit.ly/2B3gDEU, and learn about the Reporting API at https://bit.ly/rep-api. For the latest Chrome implementations, visit Chrome Status.

Feature Policy is a new web platform API designed to help developers maintain control over their web app's performance, security, and user experience. It allows developers to define policies that restrict access to certain features or modify the browser's default behavior. Examples include controlling autoplay, access to sensitive APIs, usage of fullscreen, preventing use of outdated APIs, and managing image sizes. Policies act as a contract between the developer and the browser, ensuring the developer's intent is followed even as the project grows and evolves. While adoption is a concern, its potential benefits for performance, security and privacy are substantial, especially if tied to incentives like app store listings.

I finally got a Windows Live Writer plugin working after starting from scratch! Stay tuned as I'm planning to integrate my Ajax Tagger into the Windows Live Writer framework soon. This will be a cool experiment combining Web 2.0 APIs with Windows Live Writer.

I've always struggled to find good directories of companies offering web services. I finally stumbled upon ProgrammableWeb (http://www.programmableweb.com/apis), which has a pretty good list of major web APIs. However, it also highlights the disappointing scarcity of companies providing decent APIs for developers.

MSN is launching APIs on Tuesday, September 13th, allowing developers to access their search results. More information will be available on the MSN developer site. I plan to explore these APIs and discuss my findings on this blog and on tagger.kinlan.co.uk. I hope they offer innovative features beyond basic search result access, similar to Yahoo's related searches, contextual searches, and term extraction.

In this part of my series on my AJAX application, I'm discussing the impact of external APIs. My use of APIs has made me realize how much more API access I want! I'd love to see broader API availability from feed/blog companies for statistics, retail companies for catalogs, news corporations for news feeds, and search companies for both results and more interesting APIs (like Yahoo's). Essentially, I want a central directory of companies offering these services, recognizing that I'm a consumer of their data. I'm also realizing how many APIs (REST and SOAP) are out there that I could leverage. I envision adding more dynamism to my apps, like analyzing blog post keywords to see their popularity, potential ad revenue, and related keywords. I could then cross-reference this with other sources to give viewers more feedback, such as related blog importance, link counts, and other connections. I could even offer localized product information, best buy deals, or second-hand options based on keywords. This isn't revolutionary, but I need help finding lists of companies that offer web APIs and useful RSS feeds. Readers, please share your knowledge!

I believe retailers need to embrace open APIs to their product catalogs and ordering systems to reach a wider audience. While I agree with Robert Scoble's view on the transformative potential of developer APIs in retail, I'm concerned about the slow pace of change. Costly per-call charges for APIs like eBay's hinder experimentation and development, especially for independent developers like myself. It's also difficult to find retailers who openly offer APIs. Amazon's free access model is a good example of how APIs can drive revenue. Are there any UK retailers offering cool, accessible web services?

In this third part of my series on my first AJAX application, I'm diving into the power of the Yahoo! API. It's been a learning experience, and I'm incredibly impressed with how much it offers compared to Google's. I've been exploring the Term Extraction and Related Searches APIs, and I'm starting to think about how to use the Contextual Search API. The Term Extraction API is great for pulling out keywords, while the Related Searches API helps me find relevant search queries. My app combines these to analyze blog posts and generate related searches. I'm hoping to use the Contextual Search API to add targeted search results. Future versions will incorporate more APIs, possibly from Technorati, to enhance functionality. Stay tuned!