Last Notes
https://nostr.info/resources/ is a nostr client I'm developing, so please report back issues ;)
When ZapStore? Please add your client to https://nostr.info/resources/
Some of the APIs were not designed as well as they should have been. We’re redesigning and refining them with v1.0 in mind (no ETA yet)
And so much easier that freaking zaps
rust is all about rewriting everything tho
Very cool. Don't do nip4e/MLS.. that is never going to be "simple".
I just took a quick look, and I think the problem is that the relays being added with NONE capabilites. This means they can't do anything (neither read nor write).
Unless you want to use specific capabilities, you can omit that argument in addRelay, so they will be added with the default capabilities (READ + WRITE).
Have you a small example to reproduce it?
We just moved our icons to a font for better performance :)
https://npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w.blossom.band/036adb459053e5cb5b0c28d5636cef9fe945901a40541128ababea04d33bd33e.gif
Nip44 support - says right in the note
Ask Claude to make it look nicer haha
Not going to test this justified by 'if it aint broken don't fix it'
Whats new about it?
Yes, I'm studying/evaluating it.
We are moving from create to build() then you get an event template, which extra methods to customize your event before signing. More complicated, yes. But more flexible too
Feel free to ask for things or send stuff in a PR that can make things easier for you . Quartz was built from Amethyst (which is a complicated architecture), but we want to make it simpler.
Yeah, Quartz is quite low level. No linked cache or database. You need to make subs by yourself. But there is a SQLlite event store inside of quartz if you want to save things.
Here is a very simple Twitter like interface:
https://claude.ai/public/artifacts/a1b4db2c-9648-4e9f-a3e7-900104f1eb9a
See if the first sections here help
https://github.com/vitorpamplona/amethyst/blob/main/quartz/CLIENT.md
We are also lost :)
What are you tryin to do?
I've already adapted FFI APIs but not released anything yet. There are still a some things to rework before the next release.
I think if you fork the repo, you should be able to run the workflow for building them by yourself:
Fork the repo -> Go to "Actions" -> Select the "Publish" workflow -> Click on "Run workflow" -> Select the commit to use, deselect everything except "Build KMP" (the "Swift package version" can be empty) and DON'T select "Publish" -> Run it and you'll find the AAR in the artifacts (called nostr-sdk-ffi-kmp-aar).
Compilation can be done also locally, but unfortunately requires macos as it needs binaries also for iOS, and I didn't found a way to cross-compile them from Linux.
https://github.com/rust-nostr/nostr-sdk-ffi/commit/72c07c61b460c701dcfc93d51bc83e4a1c5eb689
I was thinking on moving to your style of icon + text in horizontal and add the chat right there too. So, everything becomes a double pane design...
Because we will put a lot more things in that menu.. just the different relay feeds alone will be huge.
@nprofile…prwr we could use your help in the UI design
I DMed you.
> recommendations still contribute greatly to helping devs make decisions
Yes, I agree; in fact, I'd be happy to take a look at any Nostr project that needs some advice.
I'm happy to help, lets talk about the NIP-4E integration; I'm particularly interested since I would like to implement it in Manent.
Lets talk about that on... Coop :)
Speaking of Nostr Design: the main problem is that few developers are willing to commit to a genuine process of optimizing the UI and UX; they are generally interested in improving, but in the end they don’t follow through on the recommendations.
Yes, I'm still here :)
Do you need any help?
No. I would just use one of the models to generate something better.
This one sucks.
Your you're absolutely right is absolutely right
It's about the feeling of a native app. Unless people re-code all the little animations that match how the default apps of the phone do things, people will find it weird and reject time. I have been there many times.
You can, but they generally suck.
This should not happen if you have a browser signer installed. I should add a hint or something explaining the error.
You don't have room for the message. It's pretty clear. Make more room.
@npub1zfs…w445 what is this? "No room for message"?
https://nostr.media/c2423e9f509ada1992ccb3de5e66ecef86063f394fcea6223272b51b57db18bd.png
They keep showing up, I don't understand. I have 10 of these in the screen, one vanishes, a new one appears.
They were there yesterday too when I tried, but I was running out of patience so I didn't tag you.
I can... What does it do? Can you add terms and conditions and privacy policy for the service for users that want to investigate if they want to use your service?
learning how to truly submit to a Woman has been the most challenging, yet rewarding experience of my life. and something i'm still working on.
Coop was the first client to support NIP-4e, and it lets you choose different modes when sending messages. Jumble only displays NIP-4e, so when sending a message from Coop to a Jumble user, make sure to select “encrypt by encryption key.”
How does it know when to use my identity key or when to use my decoupled key? Is it like if I send a message to someone who has a decoupled key then it will also use my decoupled key?
The domain registrars are hinting at the coming digital gulag
#nevent1q…d78a
Does this work with nip17?
I just built it based on your ideas, I should be the one thanking you guys.
Jumble currently only subscribes to gift wrap events whose p tag contains the user’s pubkey, since some relays only allow subscribing to gift wraps that mention you. But when Jumble builds a gift wrap event, it mentions both the user’s public key and the encryption public key. I remember Coop does it this way too
