Hey,

This is planned, and there's already basic support to process Update from other instances.

Handling the addressing of update activity is a bit tricky, and I haven't got time yet to work on it, but it will definitely end up being implemented.

Thanks!

I don't know if this is the right place, but I'll give it a shot:

It would be a nice feature to be able to work on a note/article and being able to save it without publishing it, yet.

Does that fit here? Having a place to start writing, add to it, work on it, save it to go on working on it later - all without publishing.

Later at some point it should be possible to hit the publish button.

I think that's another discussion, it would be "draft support".

I am not sure it will be implemented, I will have to give it some more thoughts. I see how it can be useful, but I want to keep the number of features small/only essential stuff (and there's already a lot of stuff in my todo list to stabilize existing features).

For my use case having this feature would be really important as well.

I'm evaluating to run my blog (non micro) with microblog.pub and not being able to edit posts is almost a showstopper.

To me it would already really helpful to be able to edit only the markdown part, such that the website shows the corrected posts. And for the activitypub part, as long as there is no update support implemented, maybe it would be possible to decouple the activitypub publishing from the markdown editing, eg via a separat button that says "publish" next to an article. So that one can fine tune the markdown a bit before publishing to activitypub.

Also interested in both "editing published posts" and "saving a draft." If the project owner is interested in the draft-saving functionality, I would like to take a look into it and suggest an implementation.