Last Notes
Nice. Why does it need the network permission?
How does marmot solve spam?
When will this update land in Zapstore?
I'm assuming that at scale some fragmentation will occur due to undiscovered 10044. But technically you are correct: In a perfect network there would only ever be one encryption-only key pair. With all the issues Marmot has been having with key package discovery and reconciliation on NOSTR, I think 10044 will suffer a similar fate.
Also, the kind 4454>4455 bootstrapping process assumes that at least one other client storing the genesis secret encryption key is accessible. That may not always be the case. If my phone is smashed, I may lose all clients at once in an irrecoverable fashion. In the past, I only needed to back-up a single secret: my identity nsec. Now I also have to track & backup multiple secret encryption keys across multiple clients. That's bad UX.
I like the idea of decoupling, but I think this proposal will be unreliable at scale. If the original kind 10044 event isn't found by each and every new client on setup (some narrow window of time), we end up with fragmentation through competing 10044s. Missing content & broken interop. IMO, it will get ugly fast.
Where can I read up on NIP-4e? Can you drop a link?
Just saw you added this in v0.9.2! ty
@nprofile…jejf would be nice if Wisp could handle "nostr:" web links like Amethyst. See the Default App link on npub.world as an example.
What's wrong with NIP-17? In my experience it works well. Use it daily across multiple clients. Nospeak is my go-to lately. Marmot, on the other hand is just too early. For all the hype, even the reference implementation (White Noise) is still horribly unreliable at the most basic functions & feature incomplete. At Marmot's current pace, I think it will be at least another year before they catch up to the reliability & features of NIP-17 clients.
Best of luck! I've not had good success with Surface devices & Linux.
Just FYI, I left everything as-is to see if the issue would repeat. It does. Absolutely wrecking my battery. 43% consumption and I never even open WN
can try to share logs if it happens again
@nprofile…xqkm check out this battery drain on v2026.3.5 on GOS...
https://blossom.primal.net/eee95387af88e9acb7767cae96d3869088290e853bd54b562f7a56e9eec62724.jpg
Haven't touched Obtanium since @nprofile…tdq0 v1.0. I'd recommend you get all your nostr stuff from their. MUCH smoother experience.
hash tag follow lists + "combined" feeds - similar to Amethyst
Hmm... that hasn't been my experience. Are you running the latest version of Amber & wisp?
Tap on the profile you want to log in with (if you have already set up Amber); otherwise, load your nsec into Amber first.
Handle is now visible, but the link is dead.
A single npub was pasted and sent. This is the result. If you attempt to copy the message, you'll discover an invisible @ handle https://blossom.primal.net/4bb8b8468e56f4322528ea0008cef2b7b82a80458840cc6432ba0ebb368c7b93.jpg
@nprofile…jejf sending an npub via nip-17 dm in #wisp renders as an invisible user handle. Might be a font color issue.
General impressions: Awesome app, but we desperately need better video compression options. 13+ Mb for 6 seconds is far too big for smooth playback on many connections.
No, I don't see that list anywhere in wisp v0.1.1
testing image upload on #wisp
https://cdn.azzamo.media/8d793bd072b20c9029282a1dc54e75d2e0e90480be532b872b63a299dc9dc774.webp
I like it because I think it forces the WOT folks to re-evaluate the signal value of a follow. It doesn't necessarily imply trust. I just use follows to create a feed.
yes, Amethyst names it "private follows" by default and merges automatically with public follows when viewing the "All Follows" feed
inter-op with Amethyst private follows
https://gearlever.mijorus.it/
If you genuinely think there's a problem with my relays, hit me up in a DM and I'll investigate. FWIW, I test lots of different NIP-17 clients with my current kind 10050 list. If a client has issues, I always swap relays to make sure the relay is not the cause before raising issues with the dev.
How does Divine handle low bandwidth connections? TikTok and Reels are buttery smooth, but Divine is practically unusable on the same connection.
Still patiently waiting for your apps to land in @nprofile…xpvj
Nice, I like this approach
@nprofile…radp what does this symbol mean? I've been doing testing, and its behaviour seems erratic. Succesful send? Receive? https://cdn.nostrcheck.me/77761fd19886ec53ca70ba93e008ca822e2ea23540e902cbe2ab6a59adf098f4.webp
Well, after a device reboot, it magically started working! 🎉 Still has issues, though. My friend's Samsung phone never receives notifications when screen is off, and messages are sometimes delivered out of send order.
Just updated. Amber seems to work, but message reliability has not improved. If anything, it's worse. Tap to send and messages just disappear. No errors, no feedback. Recipient never receives.
Web version is now doing the same. Chats are not loading. UI is basically non-responsive even after full cache clear and reload. Console showing uncaught errors from svelte
No chat lists, no messages, not even relay connections. Appears to be animating a page load, but nothing happens. No rush to fix. I rolled back to the previous version.
I should specify: Android app via Zapstore
Update broke for me. Chats no longer load.
My existing pfp doesn't load on the My Profile page but does on the Edit Profile page -- no edits made, just tapping Edit
Does #Amethyst not support portrait orientation video posts?
I think visibility is good. Users need to see which relays are not honoring delete and hold them accountable.
The latest Amethyst implements full Outbox (and works exceptionally well), but you need to specify relays for it to work.
You have no public inbox relays.
Great job! Responsiveness has noticeably improved. Definitely seeing more notes as well.
@nprofile…sd6r search field text is hard to see in dark mode https://image.nostr.build/4fa70be8b09f5fa61beaf3f95146a0b7c9d9068cb7f1477522801ee084cc967c.jpg