Remember last used publishing aspect
Faldrian
Public
Seen by 100
Hi!
I need some opinions on this one, so I thought this could be the place. ;)
I often hear people - especially new users - ask about where the default aspect for new posts could be adjusted. They have understood what "all aspects" and "public" means, but don't want to switch to public all the time if they primarily post public content.
There were already discussions about switching to "public" as new default, that idea has turned down and I totaly agree with that.
So there are a few ideas how to implement a less static default choice for the publishing aspect:
- Change nothing. The user must choose a different aspect than "all aspects" every time to make sure the user does not post public by accident.
- Create a default setting on user preferences where the default aspect can be chosen.
- Let diaspora remember the last choice and make this the default for the next time the publisher is shown to the user.
The following publisher-occurences would be affected by the default setting: on stream, on activity, on bookmark. If you are viewing your aspects, there are other controls influencing what the selected aspects are.
Choice 1 is status quo today and I think 2 is quite good, but also the difficult one to implement (but as I come to think more of it... now harder than choice 3, you only have to add a aspect-selector control to user preferences). Choice 3 may adjust to the behaviour of the user, but there is a risk the user does not check the aspect selector before posting, accidentially posting something public. This would also true for 2 if set to "public" in user preferences, but that change must be made by the user, so the user should be aware of the default. In constrast the remember-feature would select "public" by default if the last post was sent public.
Any thoughts on this?
Jason Robinson Mon 17 Nov 2014 8:20AM
I'd go for 2.
Create a default setting on user preferences where the default aspect can be chosen.
Number 3. is usability, but it also causes users to possibly forget to change the last choice, thus posting something publicly which was intended as limited. I was annoyed by this in Facebook before they changed it (I think).
Linus “Igby” O'Neill Mon 17 Nov 2014 10:05AM
@jasonrobinson agreed, it does make it a bit "dangerous"
I have posted wrongly before because of that too, awesome would be, being able to change visibility later on
don't know if that is technically possible though
Jonne Haß Mon 17 Nov 2014 12:11PM
And next we'll get complaints again why you can't set public as default.
I'll just refer to my old idea for my part: https://github.com/diaspora/diaspora/issues/2577
goob Mon 17 Nov 2014 6:08PM
I agree with 2) - see Github #4319.
3) would open the risk of someone not realising the visibility had been changed after posting publicly, and might lead to them posting something sensitive to public by mistake. At least in 2) the user has actively chosen for all posts to be public by default.
Juan Santiago Tue 18 Nov 2014 9:41AM
I agree option 2, because if the user is who sets it is less likely to make a mistake at the time of posting, the option 3 is also good, but I prefer the 2, option 2 is something I hope makes long time :)
Perig Gouanvic Sat 13 Dec 2014 9:14AM
I agree with 2)
I think that the issue of posting publicly by mistake should be solved once and for all by changing the color of the 'Public' option. The Public option could be blue like the share button, but a different hue. Just to remain elegant.
But just doing something else then gray would definitely solve the security issue, regardless of the setting we chose to adopt concerning the default aspect of posts.
Perig Gouanvic Sat 13 Dec 2014 9:15AM
A proposal for this color idea? That is a relatively easy code change, I suppose : a slam dunk, right?
Mikaela Suomalainen Sun 17 Apr 2016 12:03PM
I prefer the option two as I mostly publish public content, but when I do publish private content, I often forget to change it back to public.
I have had to repost some posts that I have first accidentally sent to just "my ascpects" instead of public.
Miko Sun 17 Apr 2016 2:37PM
@Faldrian I do not get the question ?
Linus “Igby” O'Neill · Mon 17 Nov 2014 7:50AM
I second version 3 and also maybe 2
But I am more than used to version 3 from google+
I think it's an essential usability feature, to have something like that. If that is too much effort, I'd also be happy with version 2
As far as I am informed, it is possible at the moment to change the settings globally, so everyone defaults to public, or all aspects
which is not really satisfying for me, because I don't want to force anything on users
Usability is the key to success
or at least one ;)