Avatar
Orange Crush
6c0e9016b9c1efe7edef87e505e2a1e03db1fbbcfdc3ed6b4f8aaa4b540ad98f
“When the going gets weird, the weird turn pro” - Hunter S. Thompson #bitcoin #privacy #freedom Paid relay (8000⚡️): wss://relay.orange-crush.com

Also I agree that subscriptions are a bad (easy to implement) model. Pay to post is the way to go. Dynamic markets determine reach baseline is 0.1 sat / kb. Your army of followers can repost at 10sat/kb expand your reach and duration. Signal wins. Nostr incentives are too heavily slanted to the content creators and not the infrastructure.

Nothing is free. The people pay or they become the product. Certainly Will doesn’t need to subsidize a Damus relay for the Damus Client. That’s a shit business model. Nominal pay to post is the future. Folks are zapping around generational wealth for funny shit posts but won’t pay for the rails. Lightning nodes charge for routing. This is an identical use case.

Stop subsidizing the Nostr. Free relays are socialist model at worst or benevolent overlord model at best. We would be doing pay to zap today if kind hearts didn’t like losing money so much.

Free relays will kill this ecosystem. Teach people the true cost of the Nostr or the protocol will starve. The handout days are over. The zap rails are in place. No excuse for losing money in this space. If people don’t want to be the product then pay for the product.

Freedom ain’t free.

You played an enormous part. 0 to banned in China in 60 days 🤣. You write great software (and fast). You are brilliant and generous but you are terrible at incentives. You have disincentivized the birth of relay businesses by giving arguably one of the best relays away for free. This is bad. As your bank account proves, great relays aren’t free!

Turn the Damus relay off IMMEDIATELY (or please stamp an industry leading premium entry fee on it). High volume relays are a huge money sink. If Damus client doesn’t work well without it, then you know what to work on: making Damus client great without subsidizing the traffic.

Who’s in the #bitcoin for beef box business? Planning my 2024 dietary needs.

Related: Any Argentinian beef exporters looking to take advantage of the new guidance around Bitcoin as an acceptable medium for contracts?

nostr:npub1xwwmvty3er863uy9lz03zhc6m9wlzr88f9esywdkq4xjg5en9yyqktl3nz ?

When they lose, and they will lose, they will “federalize” bitcoin holdings in Spot ETFs, Coinbase custody, etc. nostr:note1rv4kf48w6rnsam4yek6k7fv99ffny34wfrvv3gfkhsc07dtr95vs2c3rrd

Imagine the fume from global security agencies as this guy gives up a global honeypot to save his own skin.

20,850 bitcoin until micro strategy owns 1% of all bitcoin ever. nostr:note1u7ejlvuczv4qsu58u0sfrjscsx39qmm8mtj3mv3njs9eq6l66khstn48v6

nostr:npub1jg552aulj07skd6e7y2hu0vl5g8nl5jvfw8jhn6jpjk0vjd0waksvl6n8n nostr:note140gwml0yfa9t0w6trzwjtll3rms0yce52utkq8x50lcjrvs9pexss6u97l

Given that Bitcoin UTXO management will become more and more important over the coming years is there anyway to delegate change to liquid or lightning?

A custodial service that bundles dust UTXOs and consolidates for atomic swaps could be a useful service.

Beat this idea up #bitcoin thinkers

They will see only the UTXOs they received. If, however, the change from the transaction should go to an old change address then you will effectively relate this transaction to any prior transaction using that change address. In general new change addresses should be used but depending on the size of the change you may not want that if it will create dust UTXO (a UTXO whose cost of spending at current txn fees exceeds the value of the UTXO).

Replying to Avatar nostr.build

nostr:npub1e4qg56wvd3ehegd8dm7rlgj8cm998myq0ah8e9t5zeqkg7t7s93q750p76 is working on a new logo for nostr.build, what do you all like best:

A, B or C?

C

Throughput wise it performs well most of the time, though, random server entry|exit can give poor performance. Need to write something for pulling load data from vpn providers over tor, then assembling optimized chains for each application instance.

Also, working on using a disposable template but disposable instances are not really built for connecting to each other. Got to be a workaround, and that would save on template size if I wanted to port something with low specs or put together random/complex/variable length chains on the fly.

Haven’t looked too deep at leakage besides monitoring the traffic from each qube. What do you recommend?

Wouldn’t it be grand if we didn’t live in surveillance states? I have little to hide but even less I want to share