Skip to content
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

[bug] 0.18.0-rc3 : Why I need to approve my own reply #3815

Open
kuspoes opened this issue Feb 20, 2025 · 2 comments
Open

[bug] 0.18.0-rc3 : Why I need to approve my own reply #3815

kuspoes opened this issue Feb 20, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@kuspoes
Copy link

kuspoes commented Feb 20, 2025

Describe the bug with a clear and concise description of what the bug is.

Just upgrade to

0.18.0-rc3

I replied to my own toot, but GoToSocial gave an error stating that my reply is in a pending status and requires my approval.

Image Image

What's your GoToSocial Version?

v0.18.0-rc3

GoToSocial Arch

FreeBSD amd64

What happened?

No response

What you expected to happen?

I shouldn't need to approve my reply to my own toot.

How to reproduce it?

No response

Anything else we need to know?

No response

@kuspoes kuspoes added the bug Something isn't working label Feb 20, 2025
@kuspoes kuspoes changed the title [bug] Why I need to approve my own reply [bug] 0.18.0-rc3 : Why I need to approve my own reply Feb 20, 2025
@tsmethurst
Copy link
Contributor

It's a bug! Basically your first reply was still pending approval by the account you were replying to. So the second reply also gets marked as pending approval, but because it's a reply to your own status you get that message. We need to change the wording here basically.

@kuspoes
Copy link
Author

kuspoes commented Feb 21, 2025

well, My first reply got a boost from the account I replied to. The status should not be pending.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants