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
{{ message }}
This repository has been archived by the owner on Feb 4, 2022. It is now read-only.
The timeline is blocked already by this setting but a post can still be accessed directly with its UUID, we must add a check there to make sure it isnt if the profile is set to private and the person is not a follower.
The text was updated successfully, but these errors were encountered:
Actually a UUID is perfectly fine for this type of thing. UUIDs are not guessable, the risk is negligible really. Just make sure that when using the web app you add the noindex header and/or tags: https://developers.google.com/search/docs/advanced/crawling/block-indexing. This will prevent indexing when someone accidentally shares the link on a public site.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The timeline is blocked already by this setting but a post can still be accessed directly with its UUID, we must add a check there to make sure it isnt if the profile is set to private and the person is not a follower.
The text was updated successfully, but these errors were encountered: