Avatar
HoloKat
1bc70a0148b3f316da33fe3c89f23e3e71ac4ff998027ec712b905cd24f6a411
Kat
Replying to Avatar HoloKat

nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s if you guys create 2 custom emoji slots then I can use Shaka and zaps again just like it used to be prior to Apple crap šŸ˜‚

Or just make the custom emoji take up the empty space

I can’t seem to. Paste doesn’t paste šŸ¤·ā€ā™‚ļø

nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s if you guys create 2 custom emoji slots then I can use Shaka and zaps again just like it used to be prior to Apple crap šŸ˜‚

Gotta run the water to clear the gunk before the good stuff comes out

Damus update looking great! Seems I can’t paste custom emoji to add it šŸ¤”

Replying to Avatar HoloKat

The thing with user-generated content is that it can look ugly. When your app fetches this type of content and you care about the app’s brand aesthetics, you have to think of ways to make user-generated content beautiful. How do you do this? Well, glad you didn’t ask, but I’ll share anyway…

Option 1. Don’t show it. Done. Haha, yeah, seriously. When you have people issuing a ton of badges and your idea is to show them in the profile… don’t. Instead, hide them into a badge tab that doesn’t show all the badges every time you look at someone’s profile. Bonus to that is that you also improve performance of that app view (fewer things to load).

Option 2: Don’t let user add anything they like. Hahah… Yes, seriously. Instead of allowing users to add anything they like, create assets for them. This way you ensure quality of assets. Consider creating sets of assets for diverse looks. I don’t have a social context example right now, but that is one way of handling it.

Option 3: Force users to upload higher quality images. Again, this is not pertaining to the social use case, but you can require users to meet minimum image resolutions / dimensions and even share guidelines as to types of images that work best.

Option 4: Curate. In apps where content is shown to visitors right away, you can manually curate for the best quality and show that first.

Option 5: Stop caring if things look ugly. Let it go! It’s out of your control now. Forget it. Let them do as they please! šŸ˜…

Personally, I try to go for option 1. Don’t show anything that is not necessary to see in a default view that everyone will access immediately. Tuck it into a tab, a modal, something.. anything that doesn’t require constant interaction. Curation is also great where applicable.

In many cases, you can’t do anything about it. Social profiles are one example. You can’t do much to make someone’s custom image or profile look good. You CAN offer themes and color palettes and pre-made profile images and banners. But, once they change it, that’s that.

Did I miss anything?

Some apps integrate with sites like unsplash, giving users some control over images while at the same time ensuring good quality.

The thing with user-generated content is that it can look ugly. When your app fetches this type of content and you care about the app’s brand aesthetics, you have to think of ways to make user-generated content beautiful. How do you do this? Well, glad you didn’t ask, but I’ll share anyway…

Option 1. Don’t show it. Done. Haha, yeah, seriously. When you have people issuing a ton of badges and your idea is to show them in the profile… don’t. Instead, hide them into a badge tab that doesn’t show all the badges every time you look at someone’s profile. Bonus to that is that you also improve performance of that app view (fewer things to load).

Option 2: Don’t let user add anything they like. Hahah… Yes, seriously. Instead of allowing users to add anything they like, create assets for them. This way you ensure quality of assets. Consider creating sets of assets for diverse looks. I don’t have a social context example right now, but that is one way of handling it.

Option 3: Force users to upload higher quality images. Again, this is not pertaining to the social use case, but you can require users to meet minimum image resolutions / dimensions and even share guidelines as to types of images that work best.

Option 4: Curate. In apps where content is shown to visitors right away, you can manually curate for the best quality and show that first.

Option 5: Stop caring if things look ugly. Let it go! It’s out of your control now. Forget it. Let them do as they please! šŸ˜…

Personally, I try to go for option 1. Don’t show anything that is not necessary to see in a default view that everyone will access immediately. Tuck it into a tab, a modal, something.. anything that doesn’t require constant interaction. Curation is also great where applicable.

In many cases, you can’t do anything about it. Social profiles are one example. You can’t do much to make someone’s custom image or profile look good. You CAN offer themes and color palettes and pre-made profile images and banners. But, once they change it, that’s that.

Did I miss anything?

Replying to Avatar Derek Ross

I agree. I made this suggestion to nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z before. I'd like to see the most recent X amount of badges or allow the profile owner to select X amount to display. Then, when viewing the profile, the profile viewer can view all of the badges via an action overflow button.

Hey nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac how would you design this to make it look aesthetically pleasing?

Remove them. I’ve brought this up many times to nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 but I’m not sure if he disagrees or just busy.

Let anyone contribute with a simple to use mixing tool

Any chatgpt model trained on nostr repo yet?

I don’t know what that is