posting here because I don’t want to draw attention to myself

these don’t save, the save button does nothing:

  • [they/them]
  • [they|them]
  • [they\them]
  • [they-them]
  • [they_them]
  • (they/them)
  • (they|them)
  • (they\them)
  • {they/them}

even foreign brackets fail

  • 【they/them】
  • 〈they/them〉
  • 《they/them》
  • 「they/them」
  • 『they/them』
  • 〔they/them〕

non-brackets also fail, and look stupid

  • !they/them¡
  • #they/them#
  • Othey/themO

this one “saves” but never appears, and when I go back to settings it’s gone:

  • <they/them>

this one saves and appears, but I want brackets!

  • they/them

meanwhile, variants of he and she both work

it’s like they have some kind of regex filter lol

  • motherfucker [they/them, she/her]English
    5•2 years ago

    Edit: I have no idea where the 20-character limit is set in upstream Lemmy apparently, so you can ignore all of this.

    The database constraint on display names is in the persons table

    diesel::table! {
    person (id) {
        id -> Int4,
        #[max_length = 255]
        name -> Varchar,
        #[max_length = 255]
        display_name -> Nullable,

    Meanwhile, SaveUserResponse struct is here and doesn’t contain any annotations that would suggest the serialization or deserialization is doing anything funky.

    And the actual regex used on the client is ^(?!@)(.+)$. Nothing that should be negatively impacting your display name choice.

    Blind guess is it’s either a false positive on the slur filter or you hit a rate limit after an initial anomaly, but I’m not super familiar with the codebase (it’s laid out in a way that seems nice to work on, though).