-
Notifications
You must be signed in to change notification settings - Fork 0
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
Ability to set annotation privacy setting to 'Public' by default. #27
Comments
+1 to defaulting to public |
Our newest branch does this. |
Great. How to make it so in our own. See updated description. |
@dwhly no, it doesn't. |
@tilgovi, do you know how we can do this? Renoir found this line of code that he thought might help: This doesn't seem like it should be hard to do. |
That line does not help. That line is about determining when the drop-down says "Public" and when it says "Only Me". The way to do it on the version of h you're using would be to change the line here to On our current master branch, the approach is different, but also cleaner, and doesn't require forking. After next week, or maybe late next week, I should be able to help you move to our latest code and make these changes. |
@tilgovi, thanks for the fix. Which line do we change, and will that still let people make private annotations if they choose? |
Oh, sorry. I forgot to hit paste. |
yes |
Thanks! i’ll do that! |
I promise you that's not the case :-D. Copying my message from the email thread:
|
Holy mother of god did I think I had you on that one. :) |
Deployed and running. |
As a W3C spec contributor, most of the work is in the open. Some users asked why they can’t see their own annotations when not logged in.
Could it be possible to set as "Public" by default for our annotations.
Some notes
In
hypothesis/h
version@84c6283
Around this section or in
annotation.coffee
aroundvalue.permissions
.Current
hypothesis/h @master branch
After some code reading, it feels like its not configurable. Closest to making it default might be to change directives/privacy.coffee at line 67. Set
VISIBILITY_PUBLIC
instead ofVISIBILITY_PRIVATE
.The text was updated successfully, but these errors were encountered: