Excited to announce that https://jumble.social now supports #zap ⚡ #nwc
Discussion
It worked :) currently can't see the text indicator dots (or whatever they are called) in dark mode on the nwc entry box, just fyi
I have submitted a fix to the bitcoin-wallet. This issue will be resolved once the new version of bitcoin-wallet is released. 🤗
plans to bring nip 17 messaging to jumble?
I still need some time to refine the existing features 🫂
totally. id find 'no' to be a perfectly reasonable answer 🙂 plenty of other clients doing that
Thanks for your understanding. The main reason is that I’m not confident in implementing the private messaging feature properly. I rarely use private messages myself because I’m never sure if the other person will actually receive my message. Especially when you and the other person are using different clients, it often happens that they don’t get your message.
yes, that is my experience too.
Something that i think would be really cool for jumble:
if there was pre-set write filters based on what relay list you are looking at, that you could define.
for example, i could be in my follows list and think of something i want to publish that goes everywhere, but then if i am looking through a smaller community, like a nip42 authd relay with just my close friends, id want my published note or reply to just write to that specific relay.
basically, id want a way for the client to either be smart and assume that for me, or give me otions to set that up for each relay listing. Rather than me remembering to update what relays im writing to in the moment. Make sense?
It seems like there’s no need to set up write filters. Just enabling the "send only" switch by default when browsing relay sets should be enough, right?
nostr DMs are a mess, three separate kinds with two different kinds of encryption, and most relays don't require auth to access them so the whole world knows who is talking to who
IMO nostr messaging is never going to happen without a new, relay based protocol, nip-17 is sorta getting there... i have a pending design that makes all chat events ephemeral and requires a nickserv/chanserv type specialised server to implement permissions and storage
none of it is going to happen without people making serious attempts... there is 0xChat and nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzfmhxue69uhkummnw3eryvfwvdhk6tcpzemhxue69uhkyetkduhxummnw3erztnrdakj7qg6waehxw309akx7cmtvfhhstnxd9shg6npvchxxmmd9uq3samnwvaz7tmpwshxummnw3e8wmmjddejucm0d5hsqgrucv52prwm9t7ln7d7w7l07nyrfz0lj7tjrqnav299gtej5frupc5f7xdc has been building a simple terminal based chat app, and most of the implementations in primarily kind 1 apps like coracle or nostrudel etc, are badly implemented and reflect the messy state of the specification and the retardation of the people who decide what nips get merged, and the people who are not trying to actually implement something functional, who are being discouraged by the nip guardians instead of boldly doing the thing
NIPs have undergone countless changes over the past few years, leading to the creation of numerous applications. Some level of chaos is inevitable. Despite the disorder, most applications remain highly compatible with each other. I believe things will continue to improve in the future.
the idea anyone needs permission to build something is absurd, as is the idea that people can't find other people to collaborate together to make their things work together
IMO the nips repo and github and the lack of a proper discussion group for it is impeding progress
> proper discussion group
Yes, por favor!
the problem with this is getting people to agree on a venue though
i think matrix is a good venue but not enough people seem to want to come
really needs a minimal pairing of a relay-selective kind-1 client and a simple way for write permissions to be set up that doesn't bleed over into other clients (so, a special admin permissions based list), and yes, a relay that also understands this scheme
#realy and #jumble could be a good combo for this
gonna of course be thinking about it more, try and figure out a plan
nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h is building a nice terminal based nip-17 chat client, perhaps we can come up with a plan
This sounds like the communities I'm building for.
For proper NIPs publishing and discussions, you at least need:
:wiki: Wikis for the actual NIPs (that can be targeted at the concerning communities)
:thread: Forum-like posts/threads
:chat: Chat
Having all other content types + zaps as a byproduct is great.
Wikis of the NIPs should then probably also be indexed in a 30040 event (type: documentation) to be rendered and organised properly.
yep, that's the general overview of what #gitcitadel is for
from the beginning it has been about opening up the discussion, i think you would have to be completely retarded to think that the current nips repo and cadre of nip guardians are doing this the right way
for a start, most of them are literally not server developers, so letting them dictate protocol seems like a really silly idea to me