-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Post as draft #6
Comments
For previewing I submit posts anonymously. Provided you don't share the link, they are invisible and don't get federated. You could use write.as just for previewing, I guess: (defun my-writefreely-preview-post ()
(let ((writefreely-auth-token nil)
(writefreely-instance-api-endpoint "https://write.as/api")
(writefreely-instance-url "https://write.as"))
(writefreely-publish-or-update) ;; Updates run async, so you may have to refresh your browser.
(writefreely-visit-post))) And once you are done you can call |
Yeah, there are a couple of subtle differences between write.as and writefreely, this is indeed one of them. (another one for example is the Another workaround I have been using is creating a 'Draft' collection which does not federate and post to that collection initially and once done moving it to the 'real' collection. |
After checking with Matt, on writefreely, 'drafts' are the same as 'anonymous' except you need to be logged on O_O |
How about recognizing if we are connecting to write.as or "the rest", where the text for "anonymous posts" collection on the latter is reworded as "-- drafts collection --" or something similar? |
Perhaps we could call it |
Hmm, wouldn't that make it more unclear for both situations? Neither the word 'anonymous' nor 'draft' is then in the text. |
If documents could be posted as drafts that would be very helpful. Both as a way to preview how things will get rendered, I find that I need to correct little things to get the rendering intended, and to have a bit more control on when the post goes federated.
I've looked in the write.as API, but it didn't seem obvious how to do that, perhaps I'm missing something.
The text was updated successfully, but these errors were encountered: