hexbear

10308 readers

1 users here now

Hexbear Proposals chapo.chat matrix room.

This will be a place for site proposals and discussion before implementation on the site.
Every proposal will also be mirrored into a pinned post on the hexbear community.

Any other ideas for helping to integrate the two spaces are welcome to be commented here or messaged to me directly.

Within Hexbear Proposals you can see the history of all site proposals and react to them, indicating a vote for or against a proposal.

Sending messages will be restricted to verified and active hexbear accounts older than 1 month with their matrix id in their hexbear user profile.

All top level messages within the channel must be a Proposals (idea for changing the site), Feedback (regarding non-technical aspects of the site, for technical please use https://hexbear.net/c/feedback), or Appeals (regarding admin/moderator actions).

Discussion regarding these will be within nested threads under the post.

To gain matrix verification, all you need to do is navigate to my hexbear userprofile and click the send a secure private message including your hexbear username.

founded 4 years ago

MODERATORS

Ryaina@hexbear.net

ella@hexbear.net

CARCOSA@hexbear.net

sweet_pecan@hexbear.net

So it seems like people have started noticing Hexbear/Lemmy's "backend" (corpo term) doesn't actually enforce that you have pronouns and that you don't change your username (hexbear.net)

submitted 8 months ago by PaX@hexbear.net to c/hexbear@hexbear.net

75 comments fedilink hide all child comments

There are a few users on the site without pronouns now (other than "none/use name", I mean like there is no pronoun field at all)

Was considering writing a no-fun-allowed patch for this unless this is intended behavior now? I would have submitted a diff but I can't build lemmy on my system to test any changes :(

It seems like the patch would be pretty easy, there is already pronoun validation code it just needs to be applied when people try to update their username

This seems like a deviation from the path laid out for us by comrade TC69

What do you think?

you are viewing a single comment's thread
view the rest of the comments

[–] chickentendrils@hexbear.net 18 points 8 months ago* (last edited 8 months ago) (1 children)

I know there are clients like Jerboa, are those guaranteed to support custom data fields that instances may add? Might be something one of those is doing but it'll never be enforceable for federated users as things are currently.

[–] PaX@hexbear.net 18 points 8 months ago (1 children)

In this case Hexbear's web UI actually just puts your pronouns in your username (display name is the Lemmy term). All that has to be done is enforce that there are pronouns in your selected username in the server code

[–] RedWizard@hexbear.net 6 points 8 months ago* (last edited 8 months ago) (1 children)

There is a difference between Username and Display Name. You can't "change" your username and it has different character requirements and is used for authentication. Display Name can be changed at any time using the Default UI and can be what ever you want and is not used for authentication.

Hexbear replaces the text field for Display Name with the pronouns drop down. It then combines your username with your pronouns and saves it in your display name field.

If you have API access you can update your display name to whatever you want because the UI is what enforces the pronouns not the server (as you identified).

The display name is used externally by other instances so it needs to remain compatible for federation. That way pronouns are displayed for users on other instances.

I'm not really sure if you can add validation to the field without breaking external users display names.

[–] PaX@hexbear.net 7 points 8 months ago* (last edited 8 months ago)

It's doesn't seem so difficult to me, we just have to check if local users have valid pronouns (valid in the sense of it's in a list that can be checked by a computer lol, not ideal but yeah) in their requested display name when they try to use the save_user_settings api. According to makotech222 elsewhere in the thread we actually used to have validation like this but the code got lost in an update