All of this user’s content is licensed under CC BY 4.0.

  • 26 Posts
  • 244 Comments
Joined 2 years ago
cake
Cake day: October 20th, 2023

help-circle








  • […] I wasn’t reacting to being questioned, though, I was reacting to being singled-out for being questioned. You marked this as “Solved” based - also - on a test from you, and an answer from TootSweet, but it didn’t look like to me that you ever questioned whether those answers deserved a follow-up. Neither of those, in my opinion, are really good enough, but I’ll say why in the answers to your individual comments about them.

    This isn’t to discredit how you have internalized the exchange, so I apologize if I made you feel this way, but I want to assure you that it wasn’t my intent to single you out. I was simply looking for clarification because I felt that I might’ve found a potential ambiguity that I personally wasn’t sure of.





  • […] Lemmy distinguishes between ‘name’ for username, and ‘display_name’ for the display name. A better link for this is arguably https://github.com/LemmyNet/lemmy/blob/main/crates/db_schema/src/schema.rs#L735 but whatever. It’s these fields that are relevant to Lemmy’s API, not the terminology that ActivityPub uses. A client might reasonably want to know the limit for a username (as provided in the Site response), because it’s this that’s used for Signup and Login. Display name is set elsewhere, once that’s done, so it doesn’t make sense for actor_name_max_length to refer to this.

    Within ActivityPub, the distinction between username and display name is ‘preferredUsername’ and ‘name’, but AP also uses ‘name’ for a bunch of other things (including but not limited to what becomes a post title, a choice in a poll, or the alt-text for an image). There’s some overlap with how Lemmy’s API refers to stuff (e.g. a post title is a post name), but it not a 1:1 match. […]

    Thank you for providing this information.