initial discussion on discord: https://discord.com/channels/1397975064254877718/1401026702553120779/1401026702553120779
dish: As a developer, one of the things I focus on as a dev is a good API for interacting with the service. For instance, patreon's is terrible(and half-abandoned afaik), while other sites(no examples otoh) have much better APIs that make sense and are intuitive in their use. They can also help when it comes to having other software that can interface with this(discord bots, custom dashboards, custom droplet impls, sites that add more metadata on top of the existing product metadata, etc). Therefore, I would like to see a focus put on ease of use for an API. Preferably the spec would also be documented as an OpenAPI document(and I'm sure theres an elixir/phoenix library for auto-generating this) so that developers can use tools that enrich their editors with automatic API documentation, or automatic client library creation, etc.
Kat: The plan right now is literally to make the entire stack be based on RSS + WebMentions + microformats
TL;DR so far: The API would be these three formats, and when new products are made, an external site could send a WebMention with a URL, formatted with microformats, to the droplet, which would then add to its RSS feed, and that would get syndicated to indexes, which would have their own meta-RSS feeds and such. There maybe isn't a need for an explicit API, but something I brought up would be some way of accessing the platform via the API specifically for sellers, so that they could create chat platform bots or custom dashboards and the like to monitor their stores. Something for further discussion!
initial discussion on discord: https://discord.com/channels/1397975064254877718/1401026702553120779/1401026702553120779
> **dish**: As a developer, one of the things I focus on as a dev is a good API for interacting with the service. For instance, patreon's is terrible(and half-abandoned afaik), while other sites(no examples otoh) have much better APIs that make sense and are intuitive in their use. They can also help when it comes to having other software that can interface with this(discord bots, custom dashboards, custom droplet impls, sites that add more metadata on top of the existing product metadata, etc). Therefore, I would like to see a focus put on ease of use for an API. Preferably the spec would also be documented as an OpenAPI document(and I'm sure theres an elixir/phoenix library for auto-generating this) so that developers can use tools that enrich their editors with automatic API documentation, or automatic client library creation, etc.
> **Kat**: The plan right now is literally to make the entire stack be based on RSS + WebMentions + microformats
TL;DR so far: The API would be these three formats, and when new products are made, an external site could send a WebMention with a URL, formatted with microformats, to the droplet, which would then add to its RSS feed, and that would get syndicated to indexes, which would have their own meta-RSS feeds and such. There maybe isn't a need for an explicit API, but something I brought up would be some way of accessing the platform via the API specifically for sellers, so that they could create chat platform bots or custom dashboards and the like to monitor their stores. Something for further discussion!