i dunno man maybe i just can’t imagine getting this worked up over a mempool relay setting.
why u so mad. you can literally run any version of the code you want
are you going to make a technical argument or just an alex jones-like tirade?
ok I use maintainers and contributors interchangeably, my bad
we'll you're hearing my side. I am a bitcoin core contributor. there aren't many of us. we are outnumbered millions to a couple dozen at most ?
you will naturally mostly hear the crowd when we are this outnumbered.
I think there is a valid counter argument: I have yet to see anyone point out why the setting matters when you can get around it via witness data (like how inscriptions abused the network)
unrestricted OP_RETURN is strictly better since those are provably unspendable, meaning you don't need to permanently bloat the utxo set. if people are going to do it anyway and you can't stop it without a hardfork, then removing the restriction so people don't do dumber things that hurt the network even more is better is it not?
what's the difference? he's is just a guy who ships code. unless you're talking about people who only merge code, I don't think sipa was ever a maintainer in that sense.
I like luke for his contrarian nature but the idea of him in charge of the future of bitcoin is bit much. He is the defacto leader of knots and noone could really appose him.
wat?
git author-stats --no-merges v26.0..v29.0 | tac | head | cat -n
bro implemented libsecp256k1, segwit, taproot, miniscript, and is working on cluster mempool algorithms as we speak?
yup! these render in most microblogging clients as well
since there are ways around it, and OP_RETURNs don't add any utxo bloat, and the person making the transaction has to pay a fee... i think that storing data this way is unsustainable, so its really a non-issue. in reality this whole debate is node operators thinking they have control of something that economics will sort out by itself. the setting has basically no effect, as most node running use default settings... so whats the point again? deluding yourself and making yourself feel good that you are doing your part to save bitcoin from people putting stupid shit in transactions when in reality you have no real control over this? great. yawn.
its probably best discussed via back-and-forth longform articles
we'll still try and see what happens
maybe it has to be more like this?
nostr:note1tnmuwvu2a4ycktpvgd0ag7npvkpc8akuewln63pj6mztkan4gc8qztfqqy
maybe its the fact its cryptocurrency is the issue? its all so vague.
hmm who knows, maybe they lied to me
I wonder the same. guy is shilling for a company that actively collects private searches from your account, and their devs who laughs at the users who point this out. What a 🤡
simply not true, how did inscriptions work then? how did they get around the limits and put jpgs in?
bitcoin is defined by its implementation, if anyone could change it and convinced everyone to run it, it would change bitcoin. then that would be the new definition of the currency. if we want to maintain its current properties, then it is by definition a meritocracy that maintains that.
if it is never updated ever again then sure, but its still the product of this meritocracy.
how is he wrong? bitcoin is a meritocracy. if you have not contributed to bitcoin in any way why should anyone listen to you?
This appears to be some sort of metrics functionality. Don’t think there is any bad faith.
I’d recommend nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg fix this.
The public key seems to be used for certain personalization, so it makes sense they might store that for debugging, but still a privacy risk.
They could rework their debugging system to integrate tracing and logging to identify specific issues, without storing search queries or pubkeys. And limit retention to a few days, and only when necessary (query error or high latency).
nostr:note1g6lpr8p6jjmw8q7gj4336prk49efqk8htuwh00s43hsffy2kf2vsj390w5
So this is a lie ?
What is the purpose of nostr wallet connect on Damus if I can’t zap?
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s
you can still zap profiles and/or enable note zaps with https://zap.army
Only you control the key, noone else can publish under that key
Yes, cashu.me has it as an experimental feature. It's been implemented in backends mostly. The upcoming BTCPayServer plugin by nostr:nprofile1qqsdmcml9nhl7q59zxm0t4xjx9zsryp3kxkqn7dvkazlszqg9psd5xgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgjwaehxw309ac82unsd3jhqct89ejhxqgnwaehxw309aex2mrp09skymr99ehhyec7nx7m9 supports it.
yeah without that it forces me to attempt to melt to accept it, if I knew every token was from a mint I trust then I could accept payment even if the mint is down, since I trust it to come up again.
is it safe to do that with those proofs somehow?
yeah the swap thing was an aha moment for me, if I can assert that cashu wallets have to use my preferred mint in a static payment request and the wallet does the swap, then thats fine for me.
do wallets implement the swap thing?
can the payment request be static or is it always interactive?
I don’t see how it’s good for scalability and privacy where there are glaring payment finality issues when actually using this in practice for commerce.
Imagine you give your waiter a tip or gift someone else some sats via cashu as a present. If you see then after xyz time that they still have not redeedem your gift you can just take them back instead they getting lost/unused. Obviously as soons as they are accepted/reedem you can't get them back.
So I guess what nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk was saying is e.g. I could send you know now 100k sats in cashu via DM and say please build xyz into damus. And if you don't want or ignore my request I could always get my sats back without having to ask for a refund.
so its explicitly designed to be doublespend + rugpull tech. makes sense. I guess that is technically a feature for the sender
This seems to be the main benefit, offline payments.
So we’re re-adding visa-like chargeback liabilities to payments. Why would anyone want this
Why? To accept it you need to instantly convert it to lightning anyway to make sure it’s “real”. At that point why not use lightning to begin with?
you seen nostr:npub1m0str0d7z2ww8rdh20t2n9lx520xjwhaq24p68umqp06wwrwtsnqen40un ? it's supposed to be that or so i understand...
is there a UI for it? it easy to use? I don't see any info on their website on how to run it. it looks like you need to run an LND node? this is way too complicated. it needs to be easy so anyone can do it.
or maybe I should do 300 for amethyst users xD nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z
there are plenty of paid relays that will do this for you