@makomichi the wolf of weeb street got reference material for your wolp productions =3. Mange: Hitoner

Username and password v2

Realized there would be a complication with DNN when there'd be a desire to lower the min fee rate from 5 vByte to something lower, and doing so will cause headaches to fix. Simple solution: Min fee rate rule should be change from 5 to 1 sat vByte and shouldn't be changed. Result: No need to change this rule anymore, lower cost to entry (but also lower cost spam but still relatively costly). No more headaches. Win-win. (Also I've begun working on that username password v2 =3)

How easy is it to get a DNN ID/TLD? As easy as this: send money to yourself, then claim. Side note: I do want to wrap/package this signer as an android app and utilize keystore (so it'll supposedly be as secure as any other mobile signer). At this point, should it still be called PWANS? Maybe PWANS Native? PWANNS? I think i'll keep the original name and have a bs thought of the N in it is both Nostr and Native x3

Ending and starting the year by giving you a smile x3

BUGS & HASH BUGS & HASH BUGS & HASH

I WAS going to have fun with making 'username password v2' today, but i noticed/realized a snag in DNN, where sometimes the input UTXO might be older than the bitcoin block DNN's genesis block is anchored to, and a DNN node wouldn't have that data, and realizing transactions could come from bitcoin block 0/genesis, i was contemplating and figuring out a possible solution: -almost no node indexes transactions for querying, so that's a bust -i didn't want dnn to rely on electrum servers, small decentralization element + trust factor, so that's a bust (last resort) -i could grab a minimum of block data, and while that's a lot smaller than downloading the full node, it's still kind of big and getting bigger with time, so that's also a bust -i did figured out a super-nice trick, but because of market dynamics, this would put a weird limit and create ux confusion So, after all that thinking and testing, what's the end solution? No headaches, hard limit: Self-transfers with an input utxo found before the bitcoin block that dnn's genesis block is anchored to will not be accepted. For most (99% and growing to 99.9%) won't be an issue, and if it does become an issue, the cost is just another self-transfer and they'd be all good. Either way, after this, i'll see if i can have a detection mechanism for users to be aware of if they're doing a self-transfer for the purposes of acquiring an ID in DNN, to just have that nice UX warning so they don't hit that small road bump.

AI love. A comforting falsehood. Reminds me of Beyond the Aquila Rift episode from Love, Death & Robots, though without the care of the monster but a mathematical conclusion so it's even colder than that. (This is assuming we're not dulluding ourselves of being something other than a structural logical outputs and conclusions like AI)

Worked today on figuring out methods to prevent a spam attack vector on DNN node relays, and on the way improving one part's UX. 80% done, 20% tomorrow (it's almost 4 am =P) A bit more testing after that, then I want to work on 'username and password version 2' and have fun with that (it's been on my mind for a long while and i really want to do it x3), basically a fun but productive break before i move back to the boring stuff. Side note: While thinking of that username and password v2 thing, I realized there's a security and privacy issue with with that process in general for everyone (extension or remote signer or other), a trust factor between you and the nostr client you're using, where even if you go 'one approval per any action' and have no auto-approvals, so they can't sign something on your behalf maliciously, they could potentially read what you decrypt. Yes open source and people would know etc but there's a delay, and that delay can cause damages. I already thought of a quarter-baked solution to this (something about having a user-generated/controled layer between the user and the client where only it renders the results and handles more approval sequences), but my plate of things to do is already overflowing so i won't be doing it x3 Maybe in the future / hopefuly i remember this issue.

I think the interesting thing about DNN is the supposed 'con' about it, there being no ability to transfer IDs, and that's actually a 'pro' thing. DNS and all other attempts to be an alt to DNS has: Unique (scarce) names + human readability + human memorability + human meaningful This combo results in the need for transferabilty (adds complexity) and figuring out solutions ot the squating problem. DNN removes the uniqueness (scarceness) and human meaningfulness out of the equation, removing the need for transferability (simple operations) because there's no need to keep track of transfers, and not needing to worry about squating because the ID you get are readable and memorable but not meaningful. This shift in perspective solves scarcity and complexity of such naming systems. In the eyes of DNN, unique names (not IDs) and transferability is basically a 'con', which is kinda interesting and maybe a bit funny x3

I just realized a did a massive oversight with the DNN spec =...D It started with "so what's this error and why is it happening?.... OH SHIT!" xD (Joe meme gif was basically me x3) This affected a lot of places in the code. Fixing and testing. Happy I caught it now though / with DNN not being 'public' yet x3

I think the moment I start and finish developing then demo the "username and password version 2" part, and the presentation is done right (with 30-40 seconds or less for the demo video length), i think that'll be the "oh shit" moment other devs on nostr will get decently curious and want to add DNN support on their clients and signers.

I just discovered this piece of new. Garbage. Hilarious xD View quoted note →

@makomichi the wolf of weeb street i'm hoping one day you'll adapt this to a wolp version x3

if someone takes my hardware wallet somehow:

Step 1: Make hardware financially inaccessible to most people Step 2: They now have to cloud game with a subscription Step 3: Control the customers, how they play, what they play, and how long, as you milk every penny out of them

The parent company of TheGamer will launch a new game mods site. I'm veeery confident what future actions and decisions they'll take, it's like i have a crystal ball x3