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
Community Proposals
Community Proposals
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 See all your notifications »
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.

Comments on Future planning: what user preferences would be useful?

Parent

Future planning: what user preferences would be useful?

+10
−0

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 -- 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?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?
+10
−0

status-completed Favorite tags It's an idea I was thinking about since a while ago, but wouldn't it be nice if use …

4y ago

+9
−0

Sort posts in one's own profile by score or age The profile main page includes a selection of posts (currently top 15 …

4y ago

+8
−0

whether your votes are public or private by default I would probably use that, but it also shouldn't be a big deal to …

4y ago

+7
−0

status-completed Enable/Disable Autosave Self-explanatory, let users choose whether they want to turn the autosavi …

4y ago

+6
−0

status-partially-completed: can now set per community (but not per category). Allow users to select their own default …

4y ago

+5
−0

Enable/disable display of Hot Notable Network Questions. [If we ever have the Notable Network Questions at all.]

4y ago

+5
−0

status-completed Be able to not have default licenses This is related to being able to pick a default per category …

4y ago

+3
−0

Use a monospace font in the editor (enable/disable) For those like me who want to use a proportional font when writin …

4y ago

+5
−1

Some way to track the votes you are receiving. Some kind of "reputation timeline" that explains which posts were voted u …

4y ago

+2
−0

I would enjoy having a network profile, where I could see all the posts and comments I have posted over time.

4y ago

+4
−1

Assuming the favourite tags per community feature gets implemented, then how about some manner of social media-like "fee …

4y ago

+4
−1

With respect to licence types per category: the Photography & Video site default is CC BY-SA 4.0, but the Contests/Criti …

4y ago

+5
−2

Show/Disable last seen time This is a pretty standard preference for those sites that do have "last seen" tracking, f …

4y ago

+1
−0

Choosing the language of the interface. In my experience in non English sites from SE, not having a user interface in …

4y ago

+1
−0

Currently, the user profile has these fields: - Avatar - Username - Profile description - Website URL - Twitter a …

4y ago

+1
−0

A succinct list of posts, the time they were posted and its current score, as well as the last time they were active. (a …

4y ago

+0
−0

It would be great to have a way to define where the preview is showed: above, below, or next to the text editor

4y ago

+2
−4

Title before body in post editor There has been much discussion about the fact that the title is put after the body o …

4y ago

+2
−4

status-declined I would like a way to disable Markdown by default in posts I write. The HTML formatting is richer, …

4y ago

1 comment thread

General comments (3 comments)
Post
+1
−0

Currently, the user profile has these fields:

  • Avatar
  • Username
  • Profile description
  • Website URL
  • Twitter account

When in a community, I sometimes feel like sharing some of my personality with those in the community: who am I, what I like, etc. However, what refrains me from doing it is the fact that anyone will be able to see it, no matter if they are registered in the site or not. That is, any passer-by will see the same information about me.

For this, I think on having a way to chose how public is every item in your profile: just you / just registered users / everyone.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (3 comments)
General comments
Monica Cellio‭ wrote almost 4 years ago

Would being able to limit the profile description to people who are signed in, versus anybody, meet your need? This would give you a place to put whatever you want that you don't want in Google results etc, while not making the user interface complex.

fedorqui‭ wrote almost 4 years ago

@Monica Cellio that is a good idea! Say "basic description" vs "extended user info". I had thought on a toggle for every item (twitter account, etc), but your solution seems easier and to me it would be very useful (twitter account can be put in the extended characters, etc).

Monica Cellio‭ wrote almost 4 years ago

Right, if you want to tell people about your blog or Twitter account or whatever else, but you don't want it to be publicly linked, then you could put it in the not-completely-public block. You'd just have to do it manually -- type "Twitter: " or whatever, instead of filling in a form.