Nostr Web Client

nostr:nprofile1qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4spz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uea5z4g why does knots have a configurable option that allows the relay of CSAM? this seems like an insane thing to encourage based on how your views have changed about this config option over the past two weeks

Replying to

Bitcoin Mechanic

Of course it _can_ but the only examples offered wouldn't mess with cloud stuff run at the hypervisor level on behalf of the *provider* - rather disk scanning stuff purchased by the customer.

stutxo 3mo ago

please elaborate

Replying to

Bitcoin Mechanic

Already aware, as I said on twitter 4KB is less than 100KB.

stutxo 3mo ago 💬 1

so a 4kb file can’t trigger anti malware?

Replying to

Bitcoin Mechanic

Old methods of storing evil stuff required obfuscation: they would need to break it up into multiple chunks and reassembly would require specific software and knowledge of what the data is and how to reconstruct and interpret it exactly.

The old formats looked like this:

"Hi, I'm a Bitcoin transaction, here's my first output of 45 outputs - , here's my second output , here's my third output" along with a tonne of other stuff that has to get parsed out when processing the highly obfuscated material. This is thankfully also true of inscriptions.

OP_RETURN however is just a dump for raw, serialized data. It's not the same.

It says the equivalent of "Hi I'm a Bitcoin transaction, here's an unspendable output: end".

This wasn't a problem for tiny OP_RETURNs i.e their current limit of 80 bytes.

If they're permitted to be 100kb, that's where the abuse begins.

And that's the end of plausible deniability.

When the stuff gets processed - which it has to be for your node to verify that they are valid transactions - then you just have a raw, unadulterated file that will trigger primitive antivirus/forensics software to alert the user: "Hi, you have CP on your computer."

You now need a licence to run a Bitcoin node, everyone thinks you're disgusting if you do, and they're not even wrong.

https://youtu.be/JLtmSzeLXOU

stutxo 3mo ago 💬 1

hey mechanic, just fyi you can already store 4kb files in control block sibling hashes in plain text without having to reconstruct them. plenty of malware is under 4kb in size, so you will have to stop relaying taproot transactions if you believe this is a real threat glhf

stutxo 4mo ago

wen bitchat classic

stutxo 4mo ago

can someone on here pls explain to me why jack added nostr to a bluetooth mesh network chat app?

Replying to

dolu

Just built Passkey39: a library that generates the same crypto private key every time you use your Face ID or Touch ID. No more seed phrases to lose, your biometric authentication becomes your deterministic wallet key through WebAuthn magic.

What do you think? I'm curious if it's a good or bad idea 🤔

👉 https://github.com/dolu89/passkey39

🎯 Live demo: https://passkey39.dolu.dev

(Not published to npm until it's safe to use)

stutxo 6mo ago 💬 1

very cool, i was building something similar but now i can just use this, how do you handle recovery if the domain name you are using for the passkey goes away? can i just spoof it locally? i’m not sure how that works

Replying to

DagzTagz

X joining forces with polymarket is kinda wild!

stutxo 6mo ago 💬 1

i didn’t predict that

stutxo 7mo ago

this x experience makes me nostalgic for 2023 nostr

stutxo 7mo ago

x - the everything is broken app

stutxo 7mo ago

twitter is fucked

Replying to

stutxo

the filter boiis are running fake libre relay nodes to try and drop non standard transactions, but this meant they leaked their ip address to everyone as they are very easy to identity

stutxo 7mo ago

and also actual libre relay node runners are easy to identify by design

Replying to

DagzTagz

What does this mean?

nevent1qqs0kc4sgeuxr6jkq2hecnzfc4qrz39ecqvmy0pzp7wwvh5lpz3lp3sn6rsra

stutxo 7mo ago 💬 3

the filter boiis are running fake libre relay nodes to try and drop non standard transactions, but this meant they leaked their ip address to everyone as they are very easy to identity

stutxo 9mo ago

grok pulled the plug

stutxo 9mo ago 💬 1

nostrs killer use case is posting about twitter being down

stutxo 10mo ago

whats the best way to verify messages are in the correct order? does anyone use nip03 anywhere?

Replying to

mfostr

🥪 You’ve got 99 problems but zero fee's ain't one 🥪 Does this only work on signet?

stutxo 11mo ago

you can do p2a on mainnet, just not CTV…YET 🥪

stutxo 1y ago 💬 3

zero fee ctv transaction using pay to anchor outputs!

🥪 +⚓ = 😋

nostr:note19ymflskw06dyt9yuvedpuzhd5qp3t3eqaez253vj2d2qjkx2ys5s7kthmn

Replying to

stutxo

i’ve been testing out p2a with ctv, it seems to work pretty well, what is the mining centralisation you referred to and is it related to this in anyway? thanks https://x.com/stutxo/status/1868213353480667393?s=46

stutxo 1y ago

https://mempool.space/signet/tx/32f4f4e6165e7f8df9b9a762e11a6ca7f16087713e0e3e42352021e6bf3800e3

https://github.com/stutxo/simple_ctv

Replying to

Rusty Russell

I'm slowly coming around to the following roadmap:

1. Simplified CTV for whole-tx commitments (ie you *will* spend this output using a tx which exactly like X.

2. Optimised sponsors for solving the "but how do I add fees" problem in a way that doesn't drive miner centralisation.

3. Script restoration so we can don't have arbitrary limits on things like amount arithmetic and examination sizes.

4. Introspection opcode(s) so we can examine txs flexibly.

5. Script enhancements for things like merkle proofs (e.g Taproot trees) and tweaks, checksig.

You could argue that #1 is simply an optimisation of #3/#4, and that's true, but it's also an obvious case (once you have #2) that we will still want even when we have all the rest.

stutxo 1y ago 💬 1

i’ve been testing out p2a with ctv, it seems to work pretty well, what is the mining centralisation you referred to and is it related to this in anyway? thanks https://x.com/stutxo/status/1868213353480667393?s=46