Tomorrow me #[0]โ #[1]โ #[2]โ and #[3]โ will be recording bitcoin.review about Nostr. The state of things, ideas, problems, etcโฆ
Let us know what you want to hear discussed.
Discussion
When key management on nostr
This
no
Haitian mobsters ainโt nothing to trifle with setting cartelios on fire.
Go figure.
If by this you mean plus plus, no not yet.
Going on about plus plus being a matter of hate or not has become the new hmm.
But lets not forget the apple treatment when accused of the fraudulent sale which the head apple is guilty of, but not allowed to make right.
Has the head apple read the dragons letter yet?
https://www.youtube.com/watch?v=cAnOt74e9_Q&list=RDcAnOt74e9_Q&start_radio=1
The Avengers. I would love to hear what your individual visions for #Nostr are in the short and long term
Wow, this is perfect
Can nostr relays replace APIs
How to improve DM privacy so people can't see which npubs I'm messaging
Why are blobs bad for relays
Torrent implementation for decentralized media storage/streaming.
Do people actually torrent from their phones? I mean sure it'd be cool for a nostr client to respond to magnet links/torrent files, but don't users want a separate app to manage the torrent session in that case? Personally I use a thin client to manage my torrents on a machine dedicated for that use and organize accordingly.
Automatically seeding torrents while opening a bunch of websocket connections to relays just seems...... wrong. Not looking to seed some stranger's cat pictures scrolling through my nostr feed
Or am I just too old to understand what people use? ๐ฅน
My reasoning (that might be wrong/outdated in many ways) was:
Why "we" use centralized media silos in nostr? Isn't there a years tested protocol that could help?
It wouldn't be reasonable from mobile users to seed. But the "silo operators" could be the big seeders, while others could help to seed some parts. And some would probably just run archives of old and important stuff.
It would be easy for any new entity to permissionlessly "mirror" the content and add to the data resilience.
The nostr client could just download/stream and display/play the file(s) the magnet link points at as if it was any other image/sound/video. Seeding would be optional, the nostr client would "ask" some big seeder/pool to seed it for you.
It might need some new bits to be added to torrent or between torrent and nostr. No idea, I'm not a coder unfortunatelly. So I was interested to hear some feedback from people who are.
Also it's all well and working nicely as it is now. So there is no pressure. Until nostr becomes "public enemy" and the media silos disappear over night.
Not a problem for most cat memes and AI generated bitcoin logos, but not great for important content. Esp. when you can't edit the notes to point at a different address, breaking a lot of content permanently.
Not that torrent is perfect as seeders can disappear overnight as well. There would need to be many big ones.
Valuable content in old notes will get reposted just like old torrents ๐ no worries
Notes don't need to last forever
I'm sure most of it will.
I'm also aware that not everyone cares about the old notes. Only the "tip of the spear" is important to them. I'm not in that camp, there is a lot of knowledge tossed around that you might like to find later on. There are events that will help to fight some future fights for freedom if you can point to them as an evidence.
Yeah I like that
Wow. Canโt wait! ๐๐ซ๐
- Hardware based key management or delegation in a way.
- Nostr marketplace for Lightning transactions.
- Relay implementation optimizations and monitoring.
- Relay administration and management tools/web UI tools.
- Backing up our Nostr events - Self-hosted solutions
I am going to call in to ask Will when he is going to implement NIP94. ๐
Why ask me ? Why not ask the 20 other clients that would need to implement it as well?
You are more fun..
You realize there are people (dozens!) who use older versions of amethyst for all sorts of reasons, forcing them to upgrade does kinda suck.
It's great that you implemented this NIP so quickly and it works great, but we can't all keep up with every NIP 24/7 ๐ค 2 months of discussion may seem like a long time to you, that's just two billing cycles for others.
I agree
I think we had our fun but now it's time to figure out how to make Nostr scale with a multitude of interoperable apps which follow the NIP specifications AND do not break each other.
I was going to ask, what is NIP94?
Feed filtering, multiple feeds with different sets of filters, easy filter set sharing to see specific parts of nostr in one click... and ideas like that.
Footstr game theory
Discuss how NIPs get finalized/approved and implemented. Obviously a timely topic.
How do we make sure update in Client A on OS A, does not break notes in Client B on OS B.
Why not add #[6]โ who develops a browser first client in #[7]โ ? iOS, Android, browser are all unique, thus carry their own learnings, and are complementary.
Need to nvite vitor for maximum ๐ฟ
That should be a good listen. Btw I cloned my Coldcard Mk3 to a Mk4 yesterday, sooo easy! ๐
๐ช
I have a thought that I'd like to hear their opinions on.
Communication between two people involves two actions.. One person "pushes" a message (data) out while the other person "pulls" that data in.
Legacy social media and the fiat-brains have always sought to control by moderating the "push". Ex. Twitter bans you if you say the wrong thing out loud. Msm deplatforms those who swim against the tide.
But the key, imo, is to create systems that always allow for a user to have absolute freedom to push whatever data they wish but also giving users the agency to curate the data they "pull" in.
I believe these user-freedom principles must always be kept in mind and protected.
Nostr clients do a great job of this which is why it's such a breath of fresh air. Anyone can post whatever foul racist or contriversial note they like but users can block whomever as well. Your freedom to shout into the void is not restricted, nor is your right to curate your feed (aka your nostr world) exactly as you wish.
#NostrBrainTrust needs to include #[7]โ The value of competition in the market is vitally important to the protocol. Move slow and make things resilient
What could be done to improve the nip system? Like what happened with NIP-94, is it a bad thing? Or a good thing? Yes debate is good, clash of ideas too, but do we really want NIPs post-merge to degenerate like that?
Would love to hear peoples current thinking around key rotation/revocation. I havent followed that discussion for a few months.
When fix for fake zaps?
1. How do client devs and tool devs plan to work together to built more use-cases for users?
2. How do they plan to attract users from those market segments ?
There are ~30 social networking clients on Nostr but we've not seen many clients for other use-cases. Do you think we'll see that picking up going forward? And which use-cases do you wish we have on Nostr? (aka, what else are you building #[3]?)
Is there something in the pipeline to improve discoverability of notes/people on Nostr?
One for odell:
Since we have now since metadata alone be sufficient to count as evidence in a court of law, what are the current contenders to protect people from incriminating themselves? Specifically : because nostr blasts metadata out to everyone forever, what are some of the proposed schemes to address this?
How to ensure the interoperability and longevity of the protocol that supports the whole ecosystem? How we avoid the pitfalls of the previous attempts to build something open and non-centralised?
Support for NIP-23 in mobile clients to attract content creators from Substack and Medium.
https://damus.io/note1vr2zef2q2w0z6432dd356whq0fy9wuvemcl3rtzkx6wsk4fyajqsx6recc
Maybe some discussion on this thread and the thinking behind OnlyZaps?
nonkyc trade exchanges via lightning using a "universal" orderbook within nostr or without? Anything out there that allows either shorting or leveraging long or take a "usd-like" cash position? lol
Now, as a new comer to the nostr community, how does one get a job working with you guys?
Might be able to solve certain needs beyond swift implementation too.
A way to share a relative time time in Nostr content would be cool. What is your tomorrow in my time? 8 hours? 16 hours?
Trying to compare timezones or count GMT hours is legacy.
Great idea for a nostr time app, we're gonna need it w/stupid daylight savings time
Even just a way to embed a Unix time into an event content (like an image or mention) or tags if needed (better for search perhaps? Not perfect), that can be rendered or calculated against the readers Timezone.
Multiple accounts on Damus ๐
this is gonna be awesome, looking forward to this! #nostr is clearly going through some growing pains but the opportunities for things like CivKit and n3xB are exciting and super important. move fast and break things is fun and dandy but there's value in moving slow and carefully too
Marketplaces: LNbits demo'd an extension for quickly setting up a retail post/store on mostr recently (@benarc did this at the WBD live event) - would be good to get all your thoughts on this as well as other options.
Iโd like to hear about how relays will scale as more users come onto the platform, without them needing to become more commercialized/centralized.
ไปๆฅๅ้ฒใใใชใใ่ญฐ่ซใใฆใปใใใใจใๆใใฆใใ ใใใ
โBitcoinโ.review
I tried to #zap this note from Damus but for some reasons my Wallet of Satoshi shows โFAILEDโ. This is the first time that I have this issue. What could be causing this? Will this payment go through at some point or should I make a new one? Thanks
#[2]โ #[7]โ
> "Man, opening a wallet to send a zap is so annoying" (46:56)
Ser, I wrote Shadowy LN Tips to solve exactly that.
To send, someone simply has to Like a post.
I just sent you one by clicking Like on your post, from a client that has no LN or zap support whatsoever.
This Like caused my Umbrel to trigger a LN payment in the background, to the LN Address in your Nostr profile.
To support this, Nostr Clients don't need to change anything. Recipients don't need anything special (LNURL and plain LN Address works out-of-the box).
The sender simply needs to run a bot (listener) that's connected to their LN node, and pair it with their Nostr profile.
Spec: https://oak-node.net/doc/trunk/doc/ons/ons-3.md
Reference implementation: Oak Node app on Umbrel app store