Last Notes
I would prefer the additional obscurity of silent payments but I also like the fact that you can now pay almost anyone without permission.
I am still trying to figure out how to get only good outbox relays out of nip66 records that will accept posts from the user or good inbox relays, etc.
Tldr centralized one and tow are gonzo. Try centralized three and four? Until morale improves and nip66 takes hold..
Lightning has great sender side privacy though. Not even the same ballgame as tracking payments onchain.
Lots to improve yet. Let me know if you want anything better.
https://media.tenor.com/Ojl7Cdv6yB0AAAAC/rainbow-spongebob.gif
Also FYI you are using nostr.band as inbox and outbox and that relay went bust a few months ago.
Maybe add nos.lol and nostr.mom to your public outbox and public inbox.
Since you are there, also reset your index and search relays to the defaults (just press the button)
Can you check if the Tor relays are connecting? We did a few changes on it and might have affected it.
add a onlyfans section on Amethyst, but for gay dudes
Back to reality
Ops there goes gravity
Curious, not sure how accurate this is. Though most, as in, over 50%, yea, probably.
I definitely spend at Square from the same wallets I zap with, and replenish through things like ZBD and Satsman (and you know, purchases).
ahh OK got me there... yeah that'd be nice to be able to search by geohash
that feature doesn't work for me because I'm not looking for events in my city or around. I'm going to Toronto next week and it's not possible to search for Toronto. So how can I find events in Toronto if I'm hundred or miles away.
This is so cool.
I'm envisioning a data dump thing where we just take public events directly from Eventbrite or whatever, geotag and hashtag it, and have some npub spit it out.
I think the issue is that most of the calendars are not geohash indexed :(
You just click the calendar tab, and then the drop-down select "Around me" and it'll filter based on geohash... I think
It's back to the basics season
I implemented 3 versions by now. I don't think it adds much to our use case.
can you add countries and cities. There is no way to find any calendar events in my city.
Calendars are up!
#nevent1q…mhp6
#Amethyst v1.11.0: Calendars
Highlights:
1. NIP-52 Calendars — feed, day/week/month views, event/collection editors, RSVP, ICS export, "starting soon" notifications, share-as-nostr-link, gallery picker.
2. On-Chain zaps — splits with dust gating, shows in the reaction gallery, display transaction history, privacy guidance
3. Payment-targets redesign (QR + copy + pay), public-address chip + confirmation
4. Inline nowhere-link cards in rich text.
PRs:
- Restore Lightning Address + LNURL fields in Edit Profile
- Raise the default maximum hashtag limit from 5 to 8
- Include on-chain zaps in notification summary stats
- Add electrum.nmc.ethicnology.com to default ElectrumX server set
- Translate call-permission and git-repo strings (cs, pt-BR, sv, de) + New Crowdin translations
- Subscribe and observe PaymentTargetsEvent for other users
- Only bridge to local cache when URL is BUD-01 layout; dedupe public-channel rows; normalize video/x-m4v to video/mp4
- Enable Send when typed name resolves via NIP-05; on-chain Bit recipient
- Inline Namecoin resolution indicator + result row on on-chain zaps
- Inline Namecoin resolution indicator in global search bar
- Long-press to copy Nostr Address, Website, LN Address, identities, payment targets
- macOS VLC bundled discovery and video rendering
- Make RelayAuthenticator authStatus thread-safe
- Pad GitRepositoryOverview content to clear top/bottom bars
- Use LargeCache for RelayAuthenticator authStatus
- MIME-type normalization for MediaStore
- Split delivery vs display, add Categories section in notifications
- Accept floating-point dimensions in imeta so image space is reserved pre-load
- Explain hashtag-limit hide reason in HiddenNote
- Route media-upload signing through launchSigner
- Render nowhere links inline as branded cards
- Release MediaController after 30s in background; skip timer for PiP
- Clickable on-chain card opens transaction history; tappable on-chain rows + txid index in LocalCache
- Disable ProGuard optimization entirely on desktop (fixes kmp-tor crash); .deb launch CI smoke test
- Show on-chain zappers in expanded reactions gallery
- Convert hashtag-limit message to <plurals> and add cs/pt-BR/sv/de translations
- Restore long-press on root note + anchor popup to the card
- Keep filter chips visible on empty on-chain transactions list
- Make playback notification tap open the note on warm-pool resume
- Validate zap receipts against LNURL provider's nostrPubkey (NIP-57 Appendix F)
- Stable sort in ShortsFeedFilter to avoid TimSort contract crash
- Align push notifications with Notifications feed filter; resolve addressable events to their replaceable note; WakeUp bypass + lookup hoist
- Update on-chain-zap + headers-explorer plans for NIP-BC inline SPV tags
- Start zoomable dialog close animation from zoomed bounds
- Scaffold I2P as a parallel privacy transport to Tor; route-aware HTTP stack; BlockedRouteException
- Reorder feed filter popup sections (DVMs before Communities, interest sets next to hashtags)
- Stop spinning Around Me when Geocoder is unavailable
- NIP-52 calendars — feed, day/week/month views, RSVP, ICS export, reminders, edit, share-as-nostr-link, participant picker, multi-day bars
- Audit follow-ups on MLS reply paths; route reply button on MLS messages to the encrypted group
- Use LaunchedEffect instead of remember for VM reset
- Switch to Dispatchers.IO around the whole executeAsync call in relay-info
- Drop crossfade around the card feed in notifications
- Observe locale in CalendarDateTimePickerButton
- Modernize zap amount choice popup to match reactions popup style
- Catch ForegroundServiceStartNotAllowedException in PlaybackService
- Include crashing thread name in crash report
- Convert remaining .gradle files to Kotlin DSL
- Redesign payment targets modal with QR, copy and pay buttons
- Add Public chip to on-chain wallet card; clarify privacy guidance on on-chain wallet popup
- Require running material-symbols-subset.sh when adding new icons; add new information icon
- Re-add Nostrcheck.me Blossom server to defaults
- Surface on-chain zaps from the reactions zap button
- On-chain zap splits — drop sender from splits, merge duplicates, gate Send on dust
- On-chain option on the Zap the Devs button
- On-chain handoff from the custom-zap dialog
- Keep listening on default index+search relays for users with no kind 10002
- Skip offline relays when fetching user metadata
- Include indexer and proxy relays in the trusted relay list to avoid Tor
- Confirm on-chain copy with public-address warning
- Swallow LegacyCursorAnchorInfo IllegalArgumentException
- Render ContactListEvent in NoteCompose with tap-through user list; add preview for DisplayContactList
## Contributors
- @nprofile…vhl6
- @nprofile…m3sx
- @nprofile…wpzp
- @nprofile…xcpk
- @nprofile…n65v
- @nprofile…mjk6
## Translations
- Czech, German, Swedish, and Portuguese by @nprofile…m3sx
- Hungarian by @nprofile…ns2l
- French by @nprofile…d26f
- Dutch by @nprofile…ge6h
- Polish by @nprofile…ajyt
- Hindi by @nprofile…3hlx
- Slovenian by @nprofile…406e
- Bengali by @nprofile…3aw2
- Spanish by @nprofile…yhdq
- Chinese by hypnotichemionus4 and @nprofile…r68m
- Russian by Anton Zhao
In an alternate universe, people are complaining that Amethyst has added zaps via Lightning.
See? This is a reaction I would want to react to. The gold star deserves a snicker.
Good guy @nprofile…pt5w. 🫂
@nprofile…vhl6 totally wants to add threading to reactions, I know it.
Yes. But maybe you are not in the right universe, though.
I wouldn’t be surprised. Amethyst is brilliant.
@nprofile…0md0 says it's coming pre-installed to all Graphene OS users...
But then someone would have to download Amerhyst. 😏
https://mutable.top/muggable/npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
Pretty cool, but I can see my transactions on Amethyst so mine is better :)
which NIP-29 impelmentation should I use as base for mine? The spec is too ambiguous.. I need to give claude something more specific
The cold wallet cabal worked so well that they scared everyone from developing and using a hot wallets that can be trully used.
Fear turns any rational decision into an emotional one. And that trully sells.
yea i thought of having some sort of tiny hint in op_return, but then the sender would need to use a wallet that does this which brings it closer to what Bitcoin SP does kind of in terms of needing to use a wallet that supports Bitcoin SP flow. Also I don't think I can add stuff in other chains nessarily?
I guess where I'm going with this is:
Discover valid sends > save them in your own nip78 > empty them out > clean up
The sender, assuming a nostr user utilizing a client/signer that supports this, would also have his own nip78 of what he sent (same cleanup of empied balances) as another just-in-case sort of thing where he can rebroadcast or republish if the event got lost.
Is there a risk? yup, but hey draft 1 or something x3
I'll probably add a warning on this NSP page in this signer mention the loss risk.
So, that is what people do when they take a break from Nostr... interesting... :)
You could just giftwrap an unsigned kind 8333, no?
You still need scanning if you don't want to lose funds, since Nostr events have the tendency of disappearing.
We have a Coinjoin @nprofile…ye3s
No. I won't use on-chain zaps at all.
The most useful UX testing is looking over the shoulder of a new user trying to use it. Observe their difficulties. Their expectations and understandings and what they are thinking and trying to do. Where do they get stuck? What are their expectations and what in the app is not making sense to them? Stuff like that.