this was posted from 0xChat, very impressed with how instagram-y ( this is a compliment) it felt to upload many photos from my device. although, nostr:npub10td4yrp6cl9kmjp9x5yd7r8pm96a5j07lk5mtj2kw39qf8frpt8qm9x2wl it would be nice to be able to caption individual photos..right now its just one caption for the uploaded set of photos. Better than ive experienced in other mobile clients 🤙
#nostr
nostr:note1wmv83jteyvjmxxv9clq0xaquqyzcdmz39mm6u0weh3cy8u359desattvqx
Makes sense, I will consider adding this in future updates.
cc nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug nostr:nprofile1qqs84k6jpsav0jmdeqjn2zxlpnsajaw6f8l0m2d4e9t8gjsyn53s4nspzemhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6qg5waehxw309aex2mrp0yhxgctdw4eju6t0qyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueq9vuy3v you may find this useful.
Thanks, 10050 will be supported in our next update, along with DM bug fixes.
NIP-87 has not been merged yet, but you can check it out here: https://github.com/nostr-protocol/nips/pull/875
imo, which NIP to adopt depends on what the client wants to achieve. My goal is to replace Telegram for large group chats, meaning supporting tens of thousands or even hundreds of thousands of members. Currently, NIP-29 seems to be the only one capable of achieving this. NIP-87, based on a shared key scheme, can protect privacy, but I think it limits group size to around a thousand members. Correct me if there are any misunderstandings nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn
After next update, we are compatible with Coracle's NIP-17 group. However, we are not compatible with closed groups. I plan to implement using NIP-29, whereas Coracle uses NIP-87.
kindof a bummer that Coracle and 0xChat private groups arent interoperable. maybe yallz can change that? 🙂
nostr:npub10td4yrp6cl9kmjp9x5yd7r8pm96a5j07lk5mtj2kw39qf8frpt8qm9x2wl
@npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn
We are using different NIPs. In 0xchat next update, the private group will be updated to NIP17 group, and NIP29 support for large group chats will be added.
Hello guys. I have some changes to NIP55, but some of them might be breaking changes. Can we discuss them?
1. Change some fields ```pubKey``` to ```pubkey```, just other nips does.
2. When transmitting information, other nips use pubkey, but here npub is used, and npub is changed to pubkey.
3. Add a function ```get_relays``` just like other nostr signer [NIP-07](https://github.com/nostr-protocol/nips/blob/master/07.md) and [NIP-46](https://github.com/nostr-protocol/nips/blob/master/46.md)
You can see the detail from this https://github.com/haorendashu/nips/blob/nip55-fix/55.md
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 nostr:npub10td4yrp6cl9kmjp9x5yd7r8pm96a5j07lk5mtj2kw39qf8frpt8qm9x2wl
This is great tbh; we can ensure backward compatibility.
thank you, so sometimes you can’t load the reply message?
Hey nostr:npub10td4yrp6cl9kmjp9x5yd7r8pm96a5j07lk5mtj2kw39qf8frpt8qm9x2wl, would this speed up the zapping experience in nostr:npub1tm99pgz2lth724jeld6gzz6zv48zy6xp4n9xu5uqrwvx9km54qaqkkxn72? Love it btw. 🤙
It's definitely going to be huge. Once finish the NIP, I think I will implement it right away.
Oh sorry for the inconvenience. Have you tried the latest version, Derek? I fixed some performance issues.
It seems that having a self-setup push server along with a push app is a good choice
Pushstr? 🤔
I am considering moving Amethyst's Push Notification features to a separate app. If that "decentralization" becomes a thing on Nostr, multiple Nostr clients can use just one Push Notification App that keeps downloading of all events citing the user and forwarding to each local client, including the local relay.
When a notification arrives, the Push App pings your preferred Signer app to decrypt it and shows it on the system tray. If you click on the notification, it opens the Nostr event in your preferred Nostr Client for that event.
The good part is that multiple "Push" apps can exist with different ways to address the need for push notifications (using Google Services, NFTY, etc)
Then we would have broken down into Amber (Signer), Citrine (Local Relay), Amethyst (and other clients) and the Push App.
What do you think? nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9usjfpck
No need for a push server? If there is only a push notification app to download all events, does it need to be kept running in the background all the time?
GM Nostr!
I’m excited to share more about what I’m building and why. My project is Seer, a consumer-friendly, NIP-29 enabled application that's native to Apple platforms. Why Apple first? That's where my expertise lies. I believe the Nostr ecosystem needs more apps that are intuitive for newcomers while delivering exceptional performance and leveraging the latest platform features.
Seer will concentrate on NIP-29 relay-based group communications. I'm staying focused on making group interactions seamless and efficient, without trying to encompass all of Nostr's capabilities. This approach echoes what nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m pointed out a while back about the value of "micro apps" — tools that do one thing exceptionally well.
Additionally, Seer will be powered by my Swift Nostr libraries, Nostr and NostrClient. While there are some excellent options out there, I plan to develop and adapt these libraries specifically to fit Seer’s needs. This doesn't mean they can’t be used for other Nostr projects, but my primary goal is to ensure they serve Seer’s requirements optimally and conveniently.
I'm looking forward to bringing Seer into your hands and making Nostr even more accessible to everyone. Stay tuned!
Oh wow, I am also working on the Nip-29 group for 0xChat, and I’d love to work with you, especially regarding group compatibility between our two clients.
Based on the NUTS protocol's P2PK and DLEQ, we don't even need 9735 to verify a legitimate token. And of course, this token needs to be on a mint trusted by the recipient.
I guess some will not implement because waiting for the nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc proposal to happen
This is a trade-off: implementing Double Ratchet on Nostr will be very challenging. While NIP17 doesn't offer the same level of forward secrecy as Double Ratchet, it allows DMs to be recovered on other devices and Nostr clients, which is essential for Nostr users.
Nostr clients should all support NIP17, lol.
lmk if you have any questions