Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

85%
+10 −0
Q&A Future planning: what user preferences would be useful?

I am starting to think about user preferences. This won't happen for a while, but I'd like to gather input so we can start thinking about a functional design. Currently a user has a single account...

19 answers  ·  posted 2y ago by Monica Cellio‭  ·  last activity 2y ago by fedorqui‭

#3: Post edited by user avatar Canina‭ · 2020-10-13T17:52:35Z (about 2 years ago)
have default license as an answer here, aiding prioritization, linking to the question for details
  • I am starting to think about user preferences. This won't happen for a while, but I'd like to gather input so we can start thinking about a functional design.
  • Currently a user has a single account across our network. When you edit your description or your display name or your blog link, those changes apply on all communities where you have a presence. Similarly, when you link a Stack Exchange account (on communities that support data import), what you're really linking is your SE *network* account -- you only need to link it once.
  • User profiles have a very small preferences section now -- there's one preference, to turn keyboard shortcuts on or off, which I believe is a global preference. We've had a request for a *per-community* preference for a default license -- you might ask why per-community, but it makes sense to me that if you are hobbyist photographer but a professional writer, you might want different settings on those two communities.
  • The possibility of per-*category* preferences has also been raised, again with licenses.
  • We need to understand the potential use cases before we design something. Knowing whether there are 3 or 30 things, for instance, or knowing whether preferences are mostly global with a few exceptions or mostly local or all over the place, makes a difference.
  • My question to y'all is: what kinds of things should be settable as user preferences, and with what scoping (global, community, category)? Some suggestions I've heard (please feel free to develop these in answers) include:
  • - [default license](https://meta.codidact.com/questions/278458) -- per community, maybe per category
  • - whether your votes are public or private by default (assuming we implement optional public votes; we don't have this now) -- per community
  • - enable keyboard shortcuts - global?
  • - just to acknowledge it before deferring it: dark mode :-) (yeah maybe someday, not now, presumably global)
  • What else should we be considering?
  • I am starting to think about user preferences. This won't happen for a while, but I'd like to gather input so we can start thinking about a functional design.
  • Currently a user has a single account across our network. When you edit your description or your display name or your blog link, those changes apply on all communities where you have a presence. Similarly, when you link a Stack Exchange account (on communities that support data import), what you're really linking is your SE *network* account -- you only need to link it once.
  • User profiles have a very small preferences section now -- there's one preference, to turn keyboard shortcuts on or off, which I believe is a global preference. We've had a request for a *per-community* preference for a default license -- you might ask why per-community, but it makes sense to me that if you are hobbyist photographer but a professional writer, you might want different settings on those two communities.
  • The possibility of per-*category* preferences has also been raised, again with licenses.
  • We need to understand the potential use cases before we design something. Knowing whether there are 3 or 30 things, for instance, or knowing whether preferences are mostly global with a few exceptions or mostly local or all over the place, makes a difference.
  • My question to y'all is: what kinds of things should be settable as user preferences, and with what scoping (global, community, category)? Some suggestions I've heard (please feel free to develop these in answers) include:
  • - [default license](https://meta.codidact.com/a/278490/278506) -- per community, maybe per category
  • - whether your votes are public or private by default (assuming we implement optional public votes; we don't have this now) -- per community
  • - enable keyboard shortcuts - global?
  • - just to acknowledge it before deferring it: dark mode :-) (yeah maybe someday, not now, presumably global)
  • What else should we be considering?
#2: Post edited by user avatar Moshi‭ · 2020-10-13T01:57:45Z (about 2 years ago)
Added [preferences] tag
#1: Initial revision by user avatar Monica Cellio‭ · 2020-10-13T01:48:12Z (about 2 years ago)
Future planning: what user preferences would be useful?
I am starting to think about user preferences.  This won't happen for a while, but I'd like to gather input so we can start thinking about a functional design.

Currently a user has a single account across our network.  When you edit your description or your display name or your blog link, those changes apply on all communities where you have a presence.  Similarly, when you link a Stack Exchange account (on communities that support data import), what you're really linking is your SE *network* account -- you only need to link it once.

User profiles have a very small preferences section now -- there's one preference, to turn keyboard shortcuts on or off, which I believe is a global preference.  We've had a request for a *per-community* preference for a default license -- you might ask why per-community, but it makes sense to me that if you are hobbyist photographer but a professional writer, you might want different settings on those two communities.

The possibility of per-*category* preferences has also been raised, again with licenses.

We need to understand the potential use cases before we design something.  Knowing whether there are 3 or 30 things, for instance, or knowing whether preferences are mostly global with a few exceptions or mostly local or all over the place, makes a difference.

My question to y'all is: what kinds of things should be settable as user preferences, and with what scoping (global, community, category)?  Some suggestions I've heard (please feel free to develop these in answers) include:

- [default license](https://meta.codidact.com/questions/278458) -- per community, maybe per category

- whether your votes are public or private by default (assuming we implement optional public votes; we don't have this now) -- per community

- enable keyboard shortcuts - global?

- just to acknowledge it before deferring it: dark mode :-) (yeah maybe someday, not now, presumably global)

What else should we be considering?