Skip to content

Conversation

@fiatjaf
Copy link
Member

@fiatjaf fiatjaf commented Dec 17, 2025

Based on #2164.

@fiatjaf
Copy link
Member Author

fiatjaf commented Dec 17, 2025

Bringing in custom fields: #1593

@vitorpamplona
Copy link
Collaborator

Why are you adding everything in one kind? :)

Custom fields should use a separate kind, IMO

@fiatjaf
Copy link
Member Author

fiatjaf commented Dec 17, 2025

Why are you adding everything in one kind? :)

Because these are all things that are needed when rendering a specific profile as its own page/view/screen (and not when only fetching a user's name).

And they're related enough I assume the same client is likely to support multiple in the same codepath/flow/whatever it's called.

Do you think these things should be in separate events?

Custom fields should use a separate kind, IMO

I'm ok with that too.

@fiatjaf
Copy link
Member Author

fiatjaf commented Dec 17, 2025

There is an argument for having the preferred colors in a separate kind, as they can be used when rendering mentions/references to another user. I don't know, every decision we make is bound to have some negative effects.

@fiatjaf fiatjaf marked this pull request as ready for review December 19, 2025 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants