It might surprise some developers to learn that the 4 official apps for Micro.blog — the iOS and macOS apps, Sunlit, and our microcasting app Wavelength — don’t actually share very much Objective-C or Swift code. To minimize dependencies and so that we could more easily develop each app quick...
I saw Snippets and thought about micro.blog’s predecessor. This post turned out to be about something related but much different.
Great to see pieces of micro.blog opening up like this.
For some time, we have been considering how we could open up compatibility between Micro.blog and Mastodon. Any feature that could be disruptive needs to be approached carefully. In this post I want to talk about how Micro.blog supports Mastodon, why I think it’s useful, and anticipate some questi...
There’s some awesome new functionality in micro.blog now. It looks like it’s still got some work to come, but, ideally, this is how most websites will work in the near future.
In order to make it easier to track activity in Hypothes.is, I created a program called Hypothes.is Collector. The idea is that you can type in user name, a URL, a tag, or a group ID and click the button to see all of the related annotations. The program will create a new sheet with an archive of up to 200 annotations based on the search terms. It will then create a third sheet that will count how many of these annotations were made on each URL in the set by each user.
This seems like it could be an interesting tool for annotations in a classroom setting and is related to some of the broader Hypothes.is API tools.
cc: Greg McVerry, W. Ian O’Bryne
The #IndieWeb community has been working on this for a while. There’s even a service called Brid.gy to help enact it. At the same time, as Ben Werdmüller indicates, we need to be careful not to put too much reliance on silos’ APIs which can, and obviously will, be pulled out from underneath us at any moment.
As any kindergartner can tell you, “It’s difficult to play ball when the local bully owns the ball and wants to make up their own rules or leave in a huff.”
One of the things I love about IndieWeb is that we’re all trying to create a way for balls to be roughly standardized and mass manufactured so that everyone can play regardless of what the bully wants to do or what equipment people bring to the game.1
And as Nikhil Sonnad has reminded us very recently, we also need more than just connections, we need actual caring and thinking human interaction.2
I announced recently that Bridgy Publish for Facebook would shut down soon. Facebook’s moves to restrict its API to improve privacy and security are laudable, and arguably ...
This is so disappointing. Facebook is literally killing itself for me. So much for their “connecting everyone” philosophy.
Brid.gy was the last thing really keeping me connected to Facebook at all. Now that Facebook is shutting down its most useful functionality from my perspective, perhaps it’s time to deactivate it and move toward shutting it all down?
APIs (application programming interfaces) are a big part of the web. In 2013 there were over 10,000 APIs published by companies for open consumption 1. That is quadruple the number available in 2010 2.
With so many companies investing in this new area of business, possessing a working understanding of APIs becomes increasingly relevant to careers in the software industry. Through this course, we hope to give you that knowledge by building up from the very basics. In this chapter, we start by looking at some fundamental concepts around APIs. We define what an API is, where it lives, and give a high level picture of how one is used.
I found this downloadable e-book a while back at Zapier’s resource page, which has some other interesting things, but this overview and layout of APIs seemed fairly simple but powerful for folks interested in the topic.
Some say to get independence from silos, users have to run servers, but that's not true. A small new connection can break the logjam.
Continue reading “Break the logjam with a simple API”