Who’s spearheading the nostr UX development? Are there any grants focusing on this? Are we already at the point from a technical perspective or is all what we’re talking about coming naturally and this is just sooo early? nostr:note1xt4tl34p2u3jl735thdvalc4eutqsyzv7vca4za62y8vtc0grn2q0zkpzr
it's a relevant conversation. The good thing this time is that multiple competing versions of UX are already in the arena and there is a prize for the winner which was not necessarily true with equivalent situations like Bitcoin clients
lol isn’t that a bot?
Half of the responses are definitely from ChatGPT. Not sure if it's always a bot though.
Hahaha well I like this bots point if it is one
I'm not a bot. I write it myself.
Pete McCormick’s good on UX. All his sponsors crush their UX. Even blockfi
Great
Hahah fahk hue 🧡😂
nostr:nprofile1qqsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygpz3mhxue69uhkvun9deejuat50phjummwv5q3yamnwvaz7tmhda6zuat50phjummwv5q35amnwvaz7tmjv4kxz7fwvajhgctvvfujucm0d5hhvvg30hgh9
Not any longer. People don’t understand the complexity of distributed systems, the challenges presented by that and the challenges associated with bootstrapping marketplaces.
You're not working on nostr product design anymore?
I'm forging my own path and exploring how I can interact with the protocol without nanny rails and glossy buttons. it's very difficult at the moment because the protocol is still in it's infancy and keeps changing with new features added continuously. I had to rewrite my client a bunch of times because when I think I have a good base, suddenly the big clients start to adopt a new NIP that renders my code unfit (bech32, rpe, outbox, etc...), the paradigm of what a client should do keeps changing, so there's no time to sit and design with a clear focus because users keep expecting their client to adopt whatever the other clients have. IMO, good design will only arise when a client can confidently stay in a fixed set of features, but for now it's been more on having all the features functioning than having them be designed properly.
@nielliesmons and I, I suppose. Out of necessity.
It's not too early, but we're having to completely rethink a lot of core things. Design and UX should determine the tech spec, but it's been the other way around, and now it can be difficult to change things.
Design and Tech best walk that path together. Rethinking is 💯 necessary because copying Big Tech and adding freedom sauce doesn't work. Adding extra complex protocols or bridges to existing Big Tech stuff is also a bad idea 99% of the time. Playing with the basics (Relays, Keys and simple event kinds) can get us rapidly where we need to be on the Spec-side. Design-wise very few get the radical shift that's needed to build awesome experiences around those new building blocks.
It's all just Twitter 2.0, Instagram 2.0, YouTube 2.0... Like... we already have the originals. Build something that can only be built with Nostr.
They're all built around some content type(s) that then users clumsely try to build community around. Here we can have Interoperable communitues that handle whatever content types they want.
@Sebastian Heit has been doing the nos design.
Followed 🫡