Skip to content

Self-Destruct Monographs are not removed [Self-Hosted] #8171

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

Open
ibaraki-douji opened this issue Jun 4, 2025 · 1 comment
Open

Self-Destruct Monographs are not removed [Self-Hosted] #8171

ibaraki-douji opened this issue Jun 4, 2025 · 1 comment

Comments

@ibaraki-douji
Copy link

What happened?

When enabling the self-destruct in the Notesnook client, i'm expecting to only be able to see the monograph once.
Tho after multiple access, i can still see the monograph.

Steps to reproduce the problem

  • Create a note (if not done already)
  • Publish it as a monograph
  • Make it Self-Destruct (creating the monograph or updating it with self destruct is the same)
  • Access it
  • Try again and you should still be able to access it, and in the client, the monograph is still present.

Version

Client v3.1.1 | Monograph v1.2.4

Platform/OS

Windows, Linux

Relevant log output

@ibaraki-douji
Copy link
Author

Also, the root cause of the issue is that, inside the monograph post component, you directly call api.notesnook.com instead of using the self-hosted host for the /view endpoint.

https://github.com/streetwriters/notesnook/blob/master/apps/monograph/app/components/monographpost/index.tsx#L230

Since the self-hosted API is waiting for /view to be called to remove the monograph, and the monograph call it on api.notesnook.com, then the monograph will never be deleted on access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant