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

Anon posts can appear in fediverse feed #79

ejheil opened this issue Feb 27, 2019 · 1 comment


None yet
2 participants
Copy link

commented Feb 27, 2019

Describe the bug

When a blog post has been made anon, it is still visible to subscribers in the fediverse (but not on the site itself)

Steps to reproduce (if necessary)

Steps to reproduce the behavior:

  1. Post to a blog.
  2. The post is now visible in subscribers' fediverse feeds
  3. Change post to anonymous
  4. The post does not go away from subscribers' fediverse feeds. Though if they click through to see it they can.
  5. How to resolve: change the post back to a blog post, then delete. (I have not investigated whether or not you can resolve it by just deleting the anonymous post directly, because if it doesn't work, I don't want that anonymous post stuck in the fediverse.

Expected behavior

The same thing that happened after it was actually deleted: it should disappear from the fediverse.

Application configuration casual account (edh)

@thebaer thebaer added this to the 1.0 milestone Feb 28, 2019


This comment has been minimized.

Copy link

commented Feb 28, 2019

Thanks for reporting this -- definitely something we want to fix. I confirmed that the post isn't removed from the fediverse when it's deleted as an anonymous post.

As I mention in this task, sending out a Delete activity upon the post being moved from a blog to Draft/Anonymous would fix this. But then we're unable to later federate the post again if someone moves it back to the same blog.

We'll need to figure out what Mastodon, Pleroma, etc. need in order to accept that post again in the case of re-federating it. I assume something like a new ID might work, but I'm not sure if there's an easier solution that would involve fewer changes on our end.

@thebaer thebaer modified the milestones: 0.9, 1.0 Apr 4, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.