Trying to make a Signal account. Signal: Signal couldn't send an SMS code because of issues with the SMS provider. Guess I'm not joining Signal unfortunately.

Realized that DNN doesn't need op_return, so considering i see that as mostly spam and doesn't full for any DNN need, i'll add a new rule to the policy to reject self-transfers with op_return data. This will make DNN even more lightweight =3

Some one replies to me "no that's not possible" me replying back "sure it is, we've already done it" them replying back aggressively "no it's not, you don't seem to know what you're talking about" was about to reply back with more clarity, but paused... looked at their profile, their replies, "ah, they're a troll wannabe trying to be popular through conflict". Ok, didn't reply and muted the account. Peace restored x3

One bug fix led to another bug fix led to another bug fix, led to a structural design flow that had me brainstorm a fix that I'm now implementing in DNN. 1. There'll now be no rule, on DNN, that requires a minimum fee per transaction 2. Transactions must be conducted using Native SegWit (P2WPKH) One rule removed, one rule added. Reasoning: I wanted to keep DNN nodes lightweight, and considering taproot doesn't contain information about the input part of a new transaction, only its hash id, meaning the node would have to store all transactions of a bitcoin block, resulting in running a full bitcoin node basically, but from a different starting point, that didn't feel right to me. Native SegWit has send/input information in its witness data from what i looked into, meaning there's no need to store old and barely related utxos, so that's why only Native SegWit. Regarding no minimum fee per transaction, well, because that information isn't found in witness data or anywhere else aside from looking at the old utxos, so considering that, and the min fee rate was 1 sat/vByte, i'd remove that rule. It's still a deterent to spam attacks of 0 sat fee rate, as most blocks are filled and that'll be more so the case as time moves on. I'd now need to also update PWANS to derive Native SegWit address types from an nPub instead of Taproot. With all of this, i think we're about to reach gold / no more fundementally breaking bugs or structural design flaws. All that's left is testing, and once things are nice, i'd imagine a code cleanup is in order, and then code audit+refactor where needed, more testing, and DNN node would be golden =3

The issue isn't a store not hard-filtering (not allowing them to be published) low quality games, you'd piss off the devs and the players that way (as we've seen in the past), but rather it's not providing the tools and systems necessary for the market to handle that curation effectively.

I'm curious what people think about this idea (because I think it's fair but also depressing x3): A game developer sets the price of their game based on the median cost of a global basket of essential goods across multiple countries, resulting in a single global price (no regional pricing). Meaning: The developer thinks of the game’s value in real-world terms (for example, “this game is worth about two X meals”), which at launch corresponds to $40. Every quarter, the price is updated based on changes in the global cost-of-living index. Over time, the price might move from $40 to $45, then $50, later drop to $35, and so on. This would be handled automatically by a game store. Under this model, the question shifts from “what is the price of the game?” to “what is the value of the game?”

I love 'demo day', each time, and on seperate machines and networks, as it reveals "well... shit's broken, let's see what's wrong and fix it" x3 Discovered three issues with DNN that needs fixin, and I think that's about it.

Here's that forked jumble that has support for username/password v2 nip + DNN:

Jumble

A user-friendly Nostr client for exploring relay feeds

If you're curious about it, you can now test a 'traditional' login method with username and password but on nostr. Here's the updated pwans apk as well: https://files.catbox.moe/qv8coc.apk (remove accessibility, added silent audio player always playing (forgot what the default is) that you can turn off in the settings, but keep it on, along with giving it no restriction on the battery, if you want the signer to always be on) If you don't feel like installing the apk, here's the pwa updated:

PWANS

Here's a quick demo showcasing upv2 with an npub and with a dnn id:

This is a demo post test

Damn, I didn't know I had, *checks balance, 100,000 BTC I should start hiring 100 devs to finish my projects, should be done with 10 project by the end of the year xD Low-IQ decision = Implementing BIP-177 High-IQ decision = Not implementing BIP-177 Sexy High-IQ decision = BIP-188 (because apparently a bip needs to be written to not make bad decisions =P)

BIP-188: The Sat Symbol

View quoted note →

The UX for setting up/using multisig bitcoin wallet is horrible on most wallet apps, wolpus-christ.

I just realized a very useful thing I can ask AI to do: "Tell me the red flags of this ToS" Finally, some users can overpower their "I'm not reading all that shit" x3

Right, the changelog (it's not just making an android build): View quoted note →" target="_blank" rel="noopener">https://image.nostr.build/94d92db393a03daca163ddfe7ad4ff0e597ae9399d2ed5a9b8eefbf38d3874b1.jpgNOSTR_0

I noticed Primal used 'have the app play music on loop forever so the app doesn't get killed by the OS' trick. It's funny because i learned about that 2 days ago and opted not to do it x3 It's a shame though that only things approved by google, and the average user can't do anything about it, can only allow apps to always run and not get killed by the OS after a time. Anway, update on PWANS: After a lot of back and forth (and complications because this thing is basically web+native. Honestly I want to do native only later, but it is what it is for now), I'm comfy sharing the apk for pwans now for anyone to test. https://files.catbox.moe/p7ddu4.apk (use fresh keys / don't import your personal nsec/seed of course (unless you're feelin risky ;3), since i didn't update the repo with the android code yet, well, and it's been a while since i updated it =P, so you can't verify the code is clean/safe/etc, verify don't trust yadayada, will do it later)

1. lmao x3 2. What DNN brings to the table: No expirary for the Certificate, and no need for the co-signature of the Certificate Authority =3

I wonder when they'll kidnap the most evil of our current time. Ah, wait, a slave can't kidnap their master/s. Oh well. (or masters can't kidnap themselves, however you want to look at it / whichever is which). Of course i'm talking about a plot of an anime. of course.

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