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 What information should be displayed on a network profile?

Parent

What information should be displayed on a network profile?

+9
−0

I want to design a network profile (and then possibly implement it). There was already discussion about that in Community dropdown and profile information, Understanding how posts were possibly received by the community --- network wide and there is an issue with when single site accounts should be created and a discussion about user preferences.

Here I want to present my thoughts on the network profile and ask you for your feedback on them. What would you like to have on a network profile?

  1. Ways to access the network profile: from each site profile and from codidact.com/users/12345

  2. Available tabs when it's another user: Profile, Activity, Vote Summary (as in the site profile)

  3. Additional available tabs when it's me: Account, Edit, Preferences

  4. Content of the Profile tab: top-left: a free text field and some links like for the site profile, below a list/table of all communities where the user has an account with links to their site profiles and statistics (number of questions, answers, edits, votes, reputation). Possibly sortable by name of community or stats mentioned above. On the right side the avatar and a summary (total number of questions, answers, edits, comments, votes across the whole network).

  5. Content of the Activity tab: same as for the site profiles only with content from all sites of course

  6. Content of the Vote Summary tab: same as for the site profiles only with content from all sites of course

  7. Content of the Account tab: I'm not sure, do we have site specific accounts here or is there only a network wide account, if so, that Account tab should vanish from the site profiles and only appear on the network profile

  8. Content of the Edit tab: I'm not sure, do we have the ability to have a different profile for each site?, if yes, maybe we could use the network profile as a way to copy text quickly to all site profiles if needed, but do we really need a unique profile text section/avatar for each site? If it's not unique, it should be moved from the site profile to the network profile.

  9. Content of the Preferences tab: The site profiles' preferences tabs have network preferences and local community preferences. Simply split them and put the network preferences on the network profile's preferences tab.

Some questions I asked myself while designing this:

  • Do Activity and Vote Summary need to be separate tabs? One could call it History instead and then have filters and sorting on it or expand the number of tabs into a larger list (questions, answers, ...).
  • Do you need to have a profile page text and avatar image that is specific for each community? Why not, I'd say, but then with potentially tens of communities this might be a nightmare to manage.
  • Is there one account (email/password) for the whole network or one account for each site?
  • What else would be nice?
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?

1 comment thread

Working on QPixel? (10 comments)
Post
+3
−0

Is there one account (email/password) for the whole network or one account for each site?

There is one account for the whole network. Profiles on individual communities are auto-created when you visit a community for the first time while logged in.

It would take some work to create separate profiles on each community, so before we do that I'd want to have a discussion about the benefits. It sounds like the main thing people would like to be able to vary per-community is the "about" text. Since we now have community-specific preferences (we didn't when profiles were first implemented), there might be a way to allow per-community "about" text without creating separate profiles. (I'm speculating; I haven't asked.)

As you surmised, the Edit and Account settings are network-wide. (Account is stuff like passwords and 2FA; Edit is to edit the stuff shown in the profile.) While these are network-wide and should be editable from the network profile, let's be careful about removing them from the per-community profiles. For someone who joins and participates in one community here, the experience should be coherent.

One possibility is to mirror those tabs (like they're mirrored on all communities now) on the network profile -- you can edit those fields from anywhere. Another is to provide paths from the community profiles to the network profile where those can be edited -- and also provide a path back. I suspect the redundancy of having them everywhere will be easier and less confusing than centralizing them, but that's just my gut feeling and maybe I'm wrong. (In other words: just my opinion, not a directive from the staff.)

We should probably add some text to those pages to the effect that the changes you make here apply across the network.

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

2 comment threads

Other (more important) reason to allow separate accounts (3 comments)
Don't split the "about" text by default. (1 comment)
Other (more important) reason to allow separate accounts
celtschk‭ wrote almost 3 years ago

I would see the main reason for separate accounts the ability to manage what publicly looks like several accounts with a single account.

For example, imagine you are a Jew in an antisemitic country. Then you might want to participate both on the Judaism community and on a community on a topic related to your job. And you might want your boss to know your account on the job-related topic, but not have him know about your activity on the Judaism community, for obvious reasons. Or you might want to publicly show your name on the site of your professtion (in order to build up a reputation) without publicly linking it to your Judaism account.

Currently the only way to do that would be separate accounts, which certainly is tedious, and moreover error-prone as you might accidentally post in a community while logged in under the wrong account, thus revealing the connection.

Monica Cellio‭ wrote almost 3 years ago

Using separate accounts requires more work, but on the flip side, protecting "hidden" accounts so they really can't be connected by observers is also complicated. SE has had problems with that for years, because "hidden" wasn't really but by having something called "hide", they gave people the impression you could. I'd like us to not repeat that mistake. But I'm not sure how we can support that without making everybody log in separately to each community, which is an even bigger hassle. This problem will require more thought.

celtschk‭ wrote almost 3 years ago

Monica Cellio‭ I think the best way would be to allow for each account to define several personas. A persona would look like a separate account for anyone but the account owner.