This has been my domain where I studied the technology, business, and politics of APIs from 2010 until 2024. It was kind of a PHD into how much of the web, mobile, and connected device works, as APIs drive almost everything today. I worked with startups, small business, enterprise organizations, and government agencies to understand how they were putting APIs to work. Spending time in Silicon Valley, New York, Washington DC working for the White House, and in Europe working with banks, the European Commission, and others to understand the world of APIs.

In 2024, I've decided to step away, and put my skills to work at 菜鸟加速器官方 as an API architect. While I thoroughly enjoyed doing API Evangelist, I was getting weary of the independent hustle, and I was in need of some change. At some point in the future I may come back to this work, but for now I've worked to clean up the site a little, and just leave up as a resource for others to learn from. I won't be publishing any new blog posts, or engaging with the community, but I'm happy to continue sharing my research and hard work, as it was my passion for some time.

You can access everything I've written via the archives page, and I've recently added a Google Search page to make things easier to find my keyword and topics. You can also access my API lifecycle research spanning almost a hundred stops using the links below. Each area of the API lifecycle is its own repository with stories I've written in each area, curated links, and companies and tooling that I've discovered along the way. You may come across links that are broken, as things change often in the space, and startups come and go. I will work to clean up from time to time, but for now, it is what it is. I hope you find something of value here.

I’m working to define APIs at the Department of Veterans Affairs (VA) on several fronts right now. I’ve provided not just one, but two detailed reponses to their Lighthouse API platform RFIs. Additionally, I’m providing guidance to different teams who are working on a variety of projects occurring simultaneously to serve veterans who receive support from the agency.

As I do this work, I am hyper aware of the privatization machinations of the current administration, and the potential for APIs to serve these desires. APIs aren’t good, bad, nor are they neutral. APIs reflect the desires of their owners, and the good or bad they can inflict is determined by their consumers. Because APIs are so abstract, and are often buried within web and mobile applications, it can be difficult to see what they are truly doing on a day to day basis. This is why we have API management solutions in place to help paint a picture of activity in real time, but as we’ve seen with the Facebook / Cambridge Analytica, it requires the API provider to be paying attention, and to possess incentives that ensure they will actually care about paying attention, and responding to negative events.

By re-defining existing VA internal systems as APIs, we are opening up the possibility that digital resources can be extracted, and transferred externally. Of course, if these systems remain the sources of data, VA power and control can be retained, but it also opens up the possibilities for power to eventually be transferred externally–reversing the polarities of government power and putting it into private hands. Depending on your politics, this could be good, or it could be bad. Personally, I’m a fan of a balance being struck, allowing government to do what it does best, and allowing private, commercial entities to help fuel and participate in what is happening–both with proper oversight. This reflects the potential benefits APIs can bring, but this good isn’t present by default, and could shift one way or the other at any moment.

Early on, APIs appeared as a promising way to deliver value to external developers. They held the promise of delivering unprecedented resources to developers, thing they would not normally be able to get access to. Facebook promised democratization using it’s social platform. While silently mining and extracting value from it’s application end-users, executed by often unknowing, but sometimes complicit developers. A similar transfer of power has occurred with Google Maps, which promised unprecedented access to maps for developers, as well as web and mobile maps for cities, businesses, and other interests. Over time we’ve seen that Google Maps APIs have become very skilled at extracting value from cities, business, and end-users, again executed unknowingly, and knowingly by developers. This process has been playing out over and over throughout the last decade of the open data evolution occurring across government at all levels.

ARM处理器、X86处理器和AI处理器的区别 - 菜鸟-传奇 - 博客园:2021-11-2 · ARM处理器、X86处理器和AI处理器的区别 目前主要的处理器架构有： X86: Intel, AMD, 海光, 兆芯 ARM: 华为，飞腾，华芯通，Cavium，Ampere，富士通，亚马逊 POW

I have no way of testing the political motivations of people that I am working with. I also don’t want to slow or stop the potential of APIs being used to help veterans, and ensure their health and insurance information can become more interoperable. I just want to be mindful of this reality, and revisit it often. Openly discussing it as I progress in my work, and as the VA Lighthouse platform evolves. Sometimes I regret all the API evangelism I have done, as I witness the damage they can do. However, the cat is out of the bag, and I’d rather be involved, part of the conversation, and pushing for observability, transparency, and open dialogue about the realities of opening up government digital resources to private entities via APIs. Allowing people who truly care about serving veterans to help police what is going on, maximize the value and control over digital resources into the hands of people who are truly serving veteran’s interests, and minimizing access by those who are just looking to make money at veteran’s expense.

• Read The Blog

• Environment
  • Editors -
  • 菜鸟加速器 -
  • Forms -
  • GIthub -
• Formats
  • Web Concepts -
  • Specification -
  • Schema -
• Tooling
  • 免费科学上外网 app -
  • 菜鸟加速器 -
  • Validator -
  • Converter -
  • Command-Line -
  • 菜鸟加速器官方下载 -
  • Aggregator -
  • Translator -
  • Merging -
  • Diff -

These building blocks are constantly being added to and reorganized. If there is something you think should be here feel free to let me know. Remember that this represents my living research, and will evolve, expand and actually seed new research areas as I find the time to pay attention to API definitions.

SunPma'Blog - 一个菜鸟的记录:2021-6-4 · HTML5 Player视频播放器源码API接口P2P加速支持MP4 M3U8 介绍支持MP4和M3U8格式支持M3U8 P2P加速支持画中画和投屏支持MP4直链下载支持顶部悬浮条广告播放器JS本地化截图使用将压缩包放置到网站目录解压即可使用如果不需要广告,修改

In 2024, I've decided to step away, and put my skills to work at F5 Networks as an API architect. While I thoroughly enjoyed doing API Evangelist, I was getting weary of the independent hustle, and I was in need of some change. At some point in the future I may come back to this work, but for now I've worked to clean up the site a little, and just leave up as a resource for others to learn from. I won't be publishing any new blog posts, or engaging with the community, but I'm happy to continue sharing my research and hard work, as it was my passion for some time.

You can access everything I've written via the archives page, and I've recently added a 菜鸟加速器 to make things easier to find my keyword and topics. You can also access my API lifecycle research spanning almost a hundred stops using the links below. Each area of the API lifecycle is its own repository with stories I've written in each area, curated links, and companies and tooling that I've discovered along the way. You may come across links that are broken, as things change often in the space, and startups come and go. I will work to clean up from time to time, but for now, it is what it is. I hope you find something of value here.