-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to latest version of NIP-10 (nip-10 other client updates might cause trouble) #2145
Labels
Milestone
Comments
alltheseas
added
technical
Needs recreation
Issues requires concrete steps for recreation
labels
Apr 15, 2024
see #528 |
alltheseas
changed the title
TBC: nip-10 other client updates might cause trouble
Update to latest version of NIP-10 (nip-10 other client updates might cause trouble)
Apr 18, 2024
alltheseas
removed
the
Needs recreation
Issues requires concrete steps for recreation
label
Apr 18, 2024
@tyiu how much work would it be to apply the same nip-10 patch to damus? |
alltheseas
modified the milestones:
2.0,
1.9 post purple testflight, threads, longform, video caching
Apr 25, 2024
alltheseas
added
the
interop
interoperability and compatibility with other nostr apps
label
Apr 25, 2024
Lmk how many candles orders its worth to you @tyiu |
Merged
3 tasks
@jb55 is nip-10 update published to testflight? |
On Tue, Apr 30, 2024 at 07:23:25PM GMT, alltheseas wrote:
@jb55 is nip-10 update published to testflight?
It's still an open PR:
- #2190
1. I still want to add a testcase I hit on the android side:
https://github.com/damus-io/nostrdb-rs/blob/99d8296fcba5957245ed883e2f3b1c0d1cb16397/src/util/nip10.rs#L436
2. Ideally we would support adding nip10 markers when replying to threads which isn't done yet
|
duplicate #528 |
Closing because dup of: Trying to get our issue numbers down a bit 😅 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Team is anticipating trouble, as discussed between @danieldaquino and @jb55 on @tyiu changes to Primal
The text was updated successfully, but these errors were encountered: