pull down to refresh

0 sats \ 1 reply \ @k00b 28 Jan \ on: πŸ“βœοΈ Weekly Design Catchup: what have you designed this week? Design
I don't have much to show for it yet, but I've been thinking a lot about:
  1. how to manage settings for attach wallets that are global and not specific to a particular wallet
  2. improving the readability of posts/comments
  3. territory UX, specifically crossposting and filtering
  4. what a discovery page might look like and how to unify it with search/top
write
preview
0 sats \ 0 replies \ @supratic 29 Jan freebie
Nice, I was probably waiting for this! Have few ideas for any of the points you mentioned:
  1. The goal I believe is to make SN a non-custodial service: if this is the case people need to run a node or alternatively or be able to spin up one easily. How? this are the options I suggest:
  • 0: Nostr Wallet Connect: a native nostr wallet connection
  • 1: LND via LNC to connect to a LND node with Lightning Node Connect
  • 2: LNDHub for a generic LNDHub wallet (BTCPayServer / Alby / LNBits)
  • 3: Alby integtration
  • 4: Spinup a LDK node locally (something like BlueWallet does)
If you could enable all of these options, you'll be in a great position. It's like enabling social login/signup in 2000
  1. This is my dessert! Accessibility! Exciting! Dear Steve innovated PCs in the 80 adding fonts into OS before caring about the Ui itself. Now SN has various options to "improve readability"
  • 0: step zero I believe is to provide options for fonts: a simple dropdown menu in the settings page could enable the user to choose between some universal web fonts like (π‘ π‘’π‘Ÿπ‘–π‘“, sans-serif, π’Έπ“Šπ“‡π“ˆπ’Ύπ“‹β„―, π”£π”žπ”«π”±π”žπ”°π”Ά and πš–πš˜πš—πš˜πšœπš™πšŠπšŒπšŽ). If you keep the css settings at a base level as mentioned, the OS will load the first default font for each one, you maybe doing this already but only for sans-serif.
  • 1: Next evolution could be to define some web-safe fonts (that can adapt to any browser on any device) for each of the options in the above-mentioned dropdown menu; instead of keeping it "generic", you define really basic fonts options.
  • 2:if you find a really cool font you really want to use, there's @font-face. This will give the site a really defined identity. That font (or fonts) are usually a result of a branding exercise or a deep communication and identity research.
  • 3: Enable user to load local fonts. Some freaks like me design and spend a lot of dirty fiat buying fonts that --under license-- are usable only on specific devices or websites. So if you could allow the connection with the local-user-font-library-folder it would be super cool!
Lastly: there are some css sets that enhance readability for any font used on the website: letter-spacing and line-height are fundamental + plus consider the today's standard font-size: 16px
p, textarea {
-moz-osx-font-smoothing: grayscale;
    -webkit-font-smoothing: antialiased !important;
    -moz-font-smoothing: antialiased !important;
    text-rendering: optimizelegibility !important;
    letter-spacing: .01em;
    line-height: 1.3;
    font-size: 16px;
}
  1. Man, I need more time to sketch out this but I'll be happy to submit a proposal
  1. Ah! have you seen this? in particular, the second image attached. It's just a prototype but the aim was just to increase content discoverability, welcoming the users with a menu of all the options available for your brain to digest today in SN: there's much more that could be done... do you guys use figma or penpot?