Pwans updated. Adding eCash/Cashu/NutZap, how I wanted it, was a big headache testing things out and solve all the edge cases x3 But ya, it's in, and... don't forget this whole thing vibe coded and is a pwa so be careful x3

PWANS

(auto update wasn't robust enough, so if you don't see the thing to refresh the app, then you have to first backup your seeds and/or keys, then basically delete the cache of Pwans from the browser you installed it on)

I wanted to push an updated to Pwans with the thing that got announced for DEGA yesterday, but nutzaping has a lot of edge cases that needs work. Not sure if I'll be able to finish it today even but fingers crossed

This wasn't planned, but it happened. First look at DEGA (heavily stripped down, this is basically a static page). Social post: https://xcancel.com/DEGAStoreX/status/1998802728328606026 Page:

DEGA

Once the site actually goes live (still far away since i'm still designing), and the link will change because of nostr addresses, I'll do a redirect (so the devs won't have broken links on their hands)

I think we need a new "we" Theres the normal we as I've just used it. Theres the royal we. How a freedom lovers we? We, the collective of freedom lovers, have spoken x3

Something neat will be announced tomorrow. (and, on a different note, maybe an update to Pwans. Still tinkering)

I just realized I can try to implement the "perfect" eCash/CashU UX, that's geared towards nostr, in my head, at least one flow of it, in PWANS. Dunno when tho.

There's catbox.moe for uploading files with direct download links (click a link, it downloads right away), with an upper limit of 200mb. There's pomf.lain.la (discovered this today) with an upper limit of 1gb. Anyone know another such service? (direct link + upper limit of 1gb + that version is free like the above).

PWANS changelog Main points: - Offline signing with fun animated qr codes = Super cool x3 - Manual reconnect = a quick "have you tried turning it off and on again?" - Post whatever kind of nostr event directly (this is more for technical nostr users) - You can find this changelog in tapping the logo on the top left then scroll down What I couldn't do: - Push notifications (would've been cool, but ya it's ass to add =/) What I didn't do yet: - Remote offline signing for bitcoin transactions - DNN name/ID implementation Also, here's the repo:

Gitea

PWANS

Progressive Web App Nostr Signer

This is a test post, signed offline via Pwans, using an offline mobile device, and broadcasted via a different device, that's connected to the internet, via Pwans. What does this mean? A PWA nostr book/wallet manager and remote signer that works on most devices/OS with offline/cold signing capability. Air-gap any device after installing Pwans as a PWA and use it to publish on nostr 🤘 I'll post more in the replies.

PWANS Progressive Web App Nostr Signer with native Bitcoin wallet functionality (Bitcoin address derived from your nostr address, not from seed)

PWANS

Vibe-coded. Play around with it at your own risk. Play with it, on pc, android, and ios (don't have an ios so dunno if it works there).

Agh! I spent 8+ hours trying to solve an issue only to realize at the end it was a user-caused issue (that user being me). (aaa xD) Well, happy that it's over and there's no issue. Not all was wasted, things in general were improved and now i know about this 'issue' so i can better diagnose future related issues and/or help others if they experience this issue. This'll make sense once post what I've been working on (hoping today/soon if all's well).

This is a test post through something interesting that I'm hoping I can share tomorrow (if there aren't anymore nonsensical bugs to fix...)

Miku Miku beam? Miku Miku whip yo ass

I found the right words to use in regards to ads and how I'd introduce ads 2.0, and the words were right there in front of my this whole time but now it clicked: Ad blocking is a service problem. It shall be fixed =3

Dug deeper into ZKP (Zero Knowledge Proof). My initial understanding of it a while back (when I made a post about it) of it is correct, and I'm pretty sure most people who talk about it don't properly understand it correctly in sense of verifying information about someone. What I didn't 'dig' back then was if there was an actual working solution in doing so. Can we verify that someone is 'above 18' without providing any information about who we're targeting? After digging into it now, it seems like the tech has been there for a while (CL) and now an improved version of it (BSS+), but there's barely adoption for it from the looks of it. (obviously I can verify the validity of the tech since I'm no coder or cryptographer, so for those who do, dig into that x3). Basically: ZKP (BBS+) is: Private + Secure / Verifiable Info, but can't be traced to a person (meaning 'hey can i use your zkp? i want to access this site' to an underage person.) KYC is: Secure / Verifiable Info + traced to a person, but not private at all (consequence: doxxing, blackmail) Obviously ZKP is better if we're weighing things, however, you have your answer why ZKP isn't being deployed by countries even though it matches their 'protect the children': It was never about protecting the children; it was about having power/control over you. I've reached an understanding on this, nearly, where I can explain the full process in a simple way (it took me a bit to understand it, since it's different then the knowledge of normal private key signing and proof of signature / who signed what). Will continue going down the rabbit hole in this (right now, learning more about BBS+).