Record the API endpoint and instance URL in the post metadata

[nikclayton]

Since the user can change the API endpoint and instance URL, it's not sufficient (I think) to record the post ID in the metadata about the post,

The user can post to one instance, and then update the instance URL / API endpoint -- when they do that, anything that operates on historical posts (update, delete, get the link, etc) will fail.

[dangom]

True. It does make sense to store the endpoint info in the org file (or as a property) as well. I'm somewhat busy with my work right now, but I should be able to tackle this when things calm down a bit.

[sch1z00]

my instance doesn't have an api directory, so I've tried to set "Instance Api Endpoint" with write.as and "Instance Url" with my instance url, but when I publish my posts are on write.as; is it possible this kind of customization (publishing on a different instance using api directory on write.as)?

[dangom]

I don't think that is possible. The API is just where we send our requests to. The URL is only used to open and visualize the posts. Unless you provide an API for us to speak to, we cannot manage your posts programmatically.
The write.as API only updates posts on the write.as instance.