Hi! I did a search on Canny for "API" and anything else in this vein, and came up with a bunch of messages from around a year ago saying you'd consider working on a programming interface in your 2026 docket. Since it's been about twelve months since you closed those messages... would now be a good time to ask? The simplest API that would be useful would just be the ability to make a post under your own account (using a revokable API token, the same way other modern web services do it.) I'm particularly keen on this one as I'd like to develop a HUD application that allows posting to Primfeed from inside SL. Beyond that, you might want to take a look at the APIs for the major microblogging platforms: - https://docs.bsky.app/docs/category/http-reference - https://docs.x.com/x-api/introduction - https://docs.joinmastodon.org/api/ - https://developers.facebook.com/docs/threads/reference These have varying levels of complexity, and functionality, but they're all pretty mature, so many of the use cases and sharp corners have already been sorted out. Of course, there's an inherent danger in going too far with any programmatic interface—most of the problems on Twitter are enabled by bots and scrapers using the API, after all. Fortunately, the insular nature of SL and the use of SL logins already keeps out most of the crap. If you decide to leave out major features from the API like scraping contact info from replies or browsing the main feed, that is 100% understandable; it'll appease privacy-paranoid people and lower the overall server costs of supporting third-party tools. But I really would urge you not to discount the idea entirely. The more Primfeed grows, the more users will want to extend it with apps. Already you have a planned giveaway tool, https://feedback.primfeed.com/feature-requests/p/giveaway-tool-and-automatic-winner-picker — this could easily be implemented by anyone with API access to see their own followers list and make posts. In general, offering an API will allow you to offload this work onto third parties rather than having to scale the Primfeed dev team (such as it is) to keep up with demand, as well as saving you the time you'd otherwise inking agreements and shaking hands to enable collaborations you might actively be interested in pursuing.
