Thread
*obfuscates how incredibly centralized your solution is*
primal users: “why aren’t things working!? My relay list is the same as damus!?”
me helping primal users: “oh yeah its not actually reading from your relay list, it reads from their proprietary server, its no different from twitter in that regard”
miljan: FUD!!! you’re cancelling me!!!
Give me a break man. Make it more clear so I don’t have to have this conversation every day.
Replies (23)
How many times did you say publicly that Primal will run out of money? Ballpark? I’d call that FUD.
wasn’t making any specific claims against primal, i was just making the point that any solution that depends on a proprietary server has the risk of just imploding once funding runs out. This has already happened with nostrgram(?) and a couple other clients that eschew configurable read relays.
Are we getting into Mac v/s Windows phase - for #nostr clients :-) .. I love watching this debate !
And i am sitting here waiting for the Linux vs proprietary OSes debate :)
we both are living in the past :-)
Nice. I really enjoyed the thread 🤣
I was waiting for this. Thank you Will.
can you add markdown perchance?
we have markdown in longform? markdown is not spec'd for kind1
How to publish longform in Damus tho?
ah, I want a dedicated client for that, like a focused longform writer. It's a bit awkward to compose posts on your phone, this would be a perfect candidate for a damus notedeck app though.
really though... markdown is hella useful for short stuff too!
allows people to be much more nuanced and creative in an otherwise expressively limited format... no?
feel free to propose it in the nips repo, it has been discussed many times and has been shot down since we want to keep kind 1 simple
that makes sense for sure but couldnt you just allow for longform kind 30023 just for folks who want to make use of it?
or is that problematic in some way I dont see?
yes but its more complicated than just write a new kind. longform supports editing via replaceable events, etc. would be a lot of ux work.
i see now on the git:
""Social" clients that deal primarily with kind:1 notes should not be expected to implement this NIP."
i am supposing what you wrote above is why they stated that...
markdown is allowed for every kind, including kind 0, 1 and -1
primal ユーザーにはxやblueskyがお似合いだよ
Migth be time for all of us to switch to pubky
Maybe later I will have time to read this whole thread. But for now for those who wanna get caught up:
This thread represents a complex discussion about the Nostr ecosystem and its various clients (primarily Primal, Damus, and Amethyst), with several key themes emerging:
1. Architecture & Technical Approaches:
- Primal uses a centralized caching service for better UX, but this creates trade-offs
- Users report inconsistencies between clients (missing reactions, posts not showing up)
- Debate over centralized vs. decentralized approaches
- Discussion about how different clients handle features like reactions, notifications, and GIF support
2. Funding & Business Model Debate:
- Tension between VC funding and community/grant-based funding
- Discussion about OpenSats funding and grant denials
- Concern about centralized architectures being more attractive to VCs but potentially more vulnerable to regulation
3. User Experience Issues:
- Primal praised for good UX but criticized for missing features and slow caching
- Damus criticized for messy reply threading but praised for completeness
- Amethyst noted for showing more complete data but perhaps less polished UX
- Users report missing reactions and interactions in Primal specifically
4. Community Consensus:
- General agreement that each client has its strengths and weaknesses
- Recognition that different approaches serve different needs
- Concern about centralization risks vs. UX benefits
- Agreement that more competition in caching/indexing would be beneficial
5. Current Pain Points:
- Inconsistent experience across clients
- Slow or unreliable caching in some clients
- Difficulty tracking new users and community growth
- Limited reaction support in some clients
The overall sentiment suggests that while the Nostr ecosystem is vibrant and evolving, there's a tension between decentralization principles and user experience, with no clear "winner" but rather different approaches serving different user needs and preferences.
There's also a broader philosophical discussion about how to balance innovation and funding while maintaining the decentralized spirit of the platform, with different clients taking different approaches to this challenge.
jb55
*obfuscates how incredibly centralized your solution is*
primal users: “why aren’t things working!? My relay list is the same as damus!?”
me helping primal users: “oh yeah its not actually reading from your relay list, it reads from their proprietary server, its no different from twitter in that regard”
miljan: FUD!!! you’re cancelling me!!!
Give me a break man. Make it more clear so I don’t have to have this conversation every day.
View quoted note →
jb55
*obfuscates how incredibly centralized your solution is*
primal users: “why aren’t things working!? My relay list is the same as damus!?”
me helping primal users: “oh yeah its not actually reading from your relay list, it reads from their proprietary server, its no different from twitter in that regard”
miljan: FUD!!! you’re cancelling me!!!
Give me a break man. Make it more clear so I don’t have to have this conversation every day.
View quoted note →
