You would help a lot of people
Having multilingual conversations on #nostr as someone who only speaks one language is freaking awesome
Pourquoi nostr:npub1g3ykp6yge2nsz5r3c60yt625enfndnluatls08v9vw7p5ck0vacsmge9wz besoin de plus d'arguments concrets
In the conclusion: “Ultimately, it depends on what your goals are as a developer. If you’re aiming to reach a wide user base, Bluesky or Mastodon are your best bets. But maybe, like Rabble, you’d rather have complete control over your app’s destiny.”
The fact that bluesky and mastodon have more users right now seems temporary. I was more wondering about fundamental differences between BlueSky and Nostr at the protocol level. The article mentions BlueSky is more narrowly targeted for Twitter-like experiences and that the company behind it has big influence on the protocol (or just the data coming out of the current BlueSky client?).
I was hoping to find something like BlueSky protocol doesn’t have feature X that Nostr has, and you can’t just add feature X to the protocol because of Y.
Bluesky vs Nostr - Which should developers care about more?
https://thenewstack.io/bluesky-vs-nostr-which-should-developers-care-about-more/
Deep dive in to the two communities and protocols.
Is the main drawback with bluesky development that you can’t trust the company with future decisions about the protocol, data, etc?
Article was great btw!
#nostr what’s a good audiobook you’ve listened to recently, I have some audible credits I need to spend
#plebchain
Is this a reference to the recent 25.0 bitcoin core update?
Yes! Thank you!
Forgot to add that he thinks I like ethereum just because I like bitcoin and I want to lay out why Eth is bad.
What’s your favorite resource to explain Ethereum’s problems? Gonna be meeting up with a friend later who is mostly new to bitcoin and ethereum and want to do a good job hitting the highlights.
Major points I have so far:
- is a security
- had a premine
- proof of stake is centralizing
- not easy to run your own node
What would you add or elaborate on here?
#bitcoin #plebchain
This critique of SoftWar is incredible #[0]
I had some unresolved questions about Lowrys points and you highlighted them clearly. Anyone interested in Lowry or in SoftWar should read your critique.
I wanted to write something like this against the book SuperIntelligence by Nick Bostrom but never got around to it.
I’s time intensive and I know you put a lot of time into your critique. I’m personally saving it as a model if I want to write one in the future.
Thank you for your time and energy to put that together!
https://blog.lopp.net/critique-softwar-concepts/
nostr:note15m4j6nqhe9hzp4mun5yh4q4k93sgx23m2p7slasrzscevv2dl9pqs5lvcr
Neat! I wanna be friends :)
I’m wondering about general design philosophy for these kinds of apps. The prototypical example would be a stacker.news app but posts and comments are nostr events.
Is it fair to think of apps like these as a nostr client but for only a small subset of notes?
What is the best way to keep track that a note is a “stacker.news” note? Would hashtags be fine? We don’t want a special stacker.news “kind” number do we? And I assume we don’t want a special stacker.news nip either. Is this what a “tag” is for?
Must we run our own relay to be practical? I see you’re planning one for outer.space , curious if you think it’s always necessary for these kinds of apps.
Tagging #[4] #[5] #[6] in case they want to chime in.
If these questions have all been answered somewhere, please share - I’m still a noob on the nostr protocol side of things and want to build in a helpful way to the whole ecosystem.
What’s a good term for making mistakes on #nostr like linking the wrong note, typos, zapping yourself, …
#nostrclumsy ?
I linked the wrong note sorry - I meant this as a hypothetical example:
nostr:note1lp6h54rx2e69dy7j57nxlh56em4zjuqhy6sctazczmhatsqw8fsqzrydyh
#[0] #[1] are there reasons one shouldn’t do something like this? Would it be bad for #nostr ecosystem in anyway?
nostr:note17ewwfeqs97uwc5lwnyud98w3clgmgjye97w0uelz9xgqv0sx6tss3mlv8v
Imagine if stacker.news used nostr to login and every post and comment was a nostr event, then those comments and posts could be individually zapped, shared, etc
(That’s not what I’m building btw, just an example of a non-nostr site using nostr)
I’m working on an app that I’ve wanted for a while now, and I’m going to build it on #nostr even though it doesn’t have to be on #nostr - and apps like these could drive more and more people to the #nostr ecosystem

