You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want it to default to the same visibility level when replying (but being able to over ride it with -v). I seem to recall it worked like that up to very recently.
The text was updated successfully, but these errors were encountered:
So, I think I found the cause of this regression in commit 125626d where I missed the fact that it sets the default value for visibility to public. I have corrected it so that visibility is not sent to the server when posting, unless the --visibility option is used explicitly. That way the server decides what's the visibility, e.g. if user has a default visibility set to something other than public.
That being said, this does not fix the issue for me on Mastodon. It seems that Mastodon sets the visibility to public by default, even when replying to a post which is not public. Please test on your server and see if it fixes it for you.
This could be fixed by first fetching the post we're replying to, reading it's visibility, and then posting using that visibility. I kinda don't want to do this because it means we need two requests instead of one. But it might be the right long-term solution.
I want it to default to the same visibility level when replying (but being able to over ride it with -v). I seem to recall it worked like that up to very recently.
The text was updated successfully, but these errors were encountered: