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

Ability to set annotation privacy setting to 'Public' by default. #27

Closed
renoirb opened this issue Dec 12, 2014 · 14 comments
Closed

Ability to set annotation privacy setting to 'Public' by default. #27

renoirb opened this issue Dec 12, 2014 · 14 comments
Assignees
Labels

Comments

@renoirb
Copy link
Member

renoirb commented Dec 12, 2014

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 around value.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 of VISIBILITY_PRIVATE.

@azaroth42
Copy link

+1 to defaulting to public

@dwhly
Copy link

dwhly commented Dec 12, 2014

Our newest branch does this.

@renoirb
Copy link
Member Author

renoirb commented Dec 12, 2014

Great. How to make it so in our own. See updated description.

@renoirb renoirb changed the title Ability to set to privacy setting to 'Public' by default. Ability to set annotation privacy setting to 'Public' by default. Dec 12, 2014
@tilgovi
Copy link
Contributor

tilgovi commented Dec 12, 2014

Our newest branch does this.

@dwhly no, it doesn't.

@shepazu
Copy link
Member

shepazu commented Dec 12, 2014

@tilgovi, do you know how we can do this? Renoir found this line of code that he thought might help:
https://github.com/hypothesis/h/blob/84c62837cda5d717870a4a0d5ca2d669cd01f531/h/static/scripts/directives.coffee#L10

This doesn't seem like it should be hard to do.

@tilgovi
Copy link
Contributor

tilgovi commented Dec 12, 2014

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 read: ['group:__world__', token.userId].

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.

@shepazu
Copy link
Member

shepazu commented Dec 12, 2014

@tilgovi, thanks for the fix. Which line do we change, and will that still let people make private annotations if they choose?

@tilgovi
Copy link
Contributor

tilgovi commented Dec 12, 2014

@tilgovi
Copy link
Contributor

tilgovi commented Dec 12, 2014

will that still let people make private annotations if they choose

yes

@renoirb
Copy link
Member Author

renoirb commented Dec 12, 2014

Thanks! i’ll do that!

@dwhly
Copy link

dwhly commented Dec 13, 2014

@dwhly no, it doesn't.

Yep. It does.

Create a new account-- the visibility defaults to public now. Just confirmed it again. I believe @aron made this change recently. Can't recall which pull request it was exactly.

@tilgovi
Copy link
Contributor

tilgovi commented Dec 13, 2014

Create a new account-- the visibility defaults to public now. Just confirmed it again.

I promise you that's not the case :-D.

Copying my message from the email thread:

No. It's not. The solution we implement with local storage isn't tied to your account, it's tied to your browser. Log in, even to your same account, with a private browsing window and you will see the default is private.

@dwhly
Copy link

dwhly commented Dec 13, 2014

I promise you that's not the case :-D.

Holy mother of god did I think I had you on that one. :)

renoirb added a commit that referenced this issue Dec 15, 2014
renoirb added a commit that referenced this issue Dec 15, 2014
@renoirb
Copy link
Member Author

renoirb commented Dec 16, 2014

Deployed and running.

@renoirb renoirb closed this as completed Dec 16, 2014
@renoirb renoirb self-assigned this Jan 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants