The next money printing cycle will be massive. Can't wait to see that. #Bitcoin is going to the moon guys. I HAVE NEVER BEEN SO BULLISH ON #BITCOIN. FIAT IS FUCKED. NOTHING CAN STOP THIS TRAIN 🚀🚀🚀

There are way too many people who actually wish for a perfect life. Perfect life never exists but fake social media makes all the people think that perfect life actually exists for real. If you don't believe in a perfect life and you are also a bitcoiner then you can apply the same idea with the whole spamming issue on #bitcoin blockchain. Spammers have been trying their best to sell that narrative that you can't fix spam issue but as I explained before if you want to see perfect #bitcoin, it may not be possible but if you want to see #bitcoin getting better than what it is today then there is absolutely no reason to run the #bitcoin core. Please run Knots to see #bitcoin getting better. Some of the core devs have been compromised by some bad actors and VCs. Knots won't completely fix the spam issue but it will help reduce the spam. Don't fall for "Nirvana Fallacy" in this case and don't also buy into "fake free market principles". If you are a miner then don't forget to point your hash to @OCEAN.

If you understand #bitcoin properly (and not with the fake free market principles) then you can just see here how easy (& cheap) it is to do a DoS attack by spamming the blockchain with junk data. Run knots instead of the #bitcoin core to disincentivize this behavior.

We didn't have any other ways to stop playing this game before 2009 but now there is a way to stop playing this stupid game. Thank God for #bitcoin   

Have been doing some portrait photography while stacking some sats. Disclaimer:- both of these pictures have been edited.

Bitcoiners would have been in a much better place if they spent more time talking about mining pool centralization than future upgrades. Mining pool centralization is a much bigger issue than a scaling issue for #bitcoin. cc @Bob Burnett

The more I see fiat clown world from outside, the more I realize that people consciously and/or subconsciously chose convience and optimization instead of decentralization and self reliance which led us here in dystopian world. Thanks to #bitcoin who has been teaching us how to prioritize decentralization and self reliance over convience and optimization because you can't have a both. Life is filled with bunch of trade-offs and I am very grateful to #bitcoin to teach me that.

The more I think about yesterday's debate the more I think that the whole debate was staged by three letter agencies to get rid of Biden. Would be interesting to see who they choose to become their next puppet. At the same time, I am also hoping that Trump doesn't become a puppet of three letter agencies. Note that he is the one who launched "Operation Warp Speed" so, people should be really careful when they root for Trump After all, as @Jeff Booth said before, you can't fix the system by staying within system so, I believe everything is a clown show but would be nice to see how we will get to hyperbitcoinization world. Last but not least, never ever forget this meme before supporting any candidate from any party because all paths lead to a slaughterhouse in politics.

The more I watch yesterday debate the more I think that we are literally into late stage fiat. Maybe a few more debates like this and some normies might wake up to the fact that we are in deep shit and we need to opt out of this clown world by taking orangepill #bitcoin

Sometimes when I talk about #bitcoin to some people, I can get some weird vibes and I can feel that some of these people really want to see #bitcoin going zero so they can see me getting failed in my life. Not sure if they ever realize that if #bitcoin fails then all of us would be truly and utterly fucked. Anyways if you are someone who has been bitcoin cost averaging for years and come across this kind of people, how would you deal with them? In case, if they change opinion about you in the future (by not wanting to see you getting failed anymore realizing that fact that bitcoin is the only hope), would you change your opinion on those people or you will continue avoiding them for the rest of your life?

One of the major issues with #bitcoin is a lot of plebs rely so much on influencers' opinion before they form their own opinion on something. Is there any way to mitigate this issue?

Very pleased to see a shitcoin magazine mentioned in the scam war. Shitcoin magazine will probably invite Trump to this year's shitcoin conference and tell everyone that they have done more for #bitcoin than anyone else but it seems like these clowns don't know that (YET) "#bitcoin doesn't need Trump, Trump needs #bitcoin." @Giacomo Zucco you have been doing God's work by explaining scam wars to the plebs. 🫡🫡🫡

Core devs would talk about all new upgrades and almost every other technical thing being discussed in the #bitcoin community but they will never talk about how blocks are filled almost entirely by spam (sorry scam). In case, if they speak about spam then they will probably try their best to rationalize it in the name of "valid transactions" and "free market". Plebs need to run knots and as @BITCOINALLCAPS 🐦 🐦 🐦 said before "Knots devs need more funding not the compromised #bitcoin core devs". If you are a miner then send your hash to @OCEAN. @Luke Dashjr @Bitcoin Mechanic @Giacomo Zucco

It's becoming more and more clear that reducing the blocksize (with removing witness discount) would be good for #bitcoin   . Maybe we may not get consensus initially but as more and more plebs see more and more spam on #bitcoin , they will realize the importance of not including spam in the #bitcoin    and the cost of running their own node. Just to be clear, even if spammers spam the 80% of blockspace of small blocks, it still makes sense to reduce the blocksize because it will still help with #bitcoin decentralization. It's also becoming more and more clear that there is absolutely no reason to not run knots at this point. If you are miner then point your hash to @OCEAN. Plebs should be ditching the #bitcoin core by now. If they don't do that then either they don't understand #bitcoin    properly yet or they don't understand the real risk of spamming on #bitcoin. cc @Bitcoin Mechanic @Luke Dashjr @Giacomo Zucco

The more time I spend on #bitcoin xitter and nostr, the more it seems like a lot of bitcoiners (including some prominent #bitcoin    influencers) don't run their own nodes. If these bitcoiners were running their own nodes then they wouldn't have easily been gaslighted by scammers in the name of valid transactions and free market. Please learn how to run your own node and also learn how running knots disincentivizes spam on the #bitcoin network.

Hello My Nostr Friends, Does anyone know good alternative of Adobe Lightroom? My preference is open source software. If you can also share a resources about how to use that software, it would be nice. Just want to use as many open source apps as possible.

YOU DON'T NEED 4 MB BLOCK SIZE. 300 KB BLOCK SIZE COULD BE MORE THAN GOOD ENOUGH TO FIT ALL (MONETARY) TRANSACTIONS. #BITCOIN ALWAYS THRIVES MORE WITH CONSERVATISM THAN PROGRESSIVISM. FEW. CC @Luke Dashjr @Bitcoin Mechanic @Giacomo Zucco IView quoted note →

As most of the bitcoiners know that scammers have been spamming the bitcoin for more than year now. I have seen some good arguments in support of filtering the spam to disincentive the behavior. Time for the post on strawman and steelman arguments on spam. Strawman: - What is your definition for scam? While I agree 99% of the trading is done because of speculation and will cause many to lose money. The scams are only projects lying to their customers to run out with their money, which there are many, but much less than speculate traders. Steelman: - Just because you want to have sex doesn't mean you're justified in raping people who don't consent. Strawman: - But aren’t they within the consensus rules and therefor it’s not rape? They found an exploit! Ok. Filter. Won’t they find another exploit? Wouldn’t it be better to focus on the monetary use cases? And people will choose to use it as SOV? Steelman: - What if I find a way to steal anybody’s bitcoin within the consensus rules. Will you fix the bug? I will let him steal my Bitcoin as long as it is in consensus rules. Strawman: - Ya I probably would want that fixed. But 1) how would someone steal bitcoin and still be within consensus? And 2) how are cat jpegs on blockchain the same as stealing someone’s bitcoin? That’s a clear issue needing addressed. Steelman: - 1) people thought that the supply limit was 21m until someone found out how to violate it within the code's consensus engine. There's no know way to steal today, but the question is about how you would react if such a hypothetical vulnerability was discovered in the future - the exact mechanics of the exploit don't matter for the hypothetical. 2) cat jpegs on chain and steal someone's Bitcoin are the same issue because there isn't consensus for either one of them. Strawman: - Is the 'exploit' that the code was written just fine, operates just as expected, and is being used in a different but anticipated way, but at an unanticipated rate? Or is there more? Steelman: - Bitcoin script was not intended for unlimited arbitrary data storage, therefore it is not operating as expected. Strawman: - Seems like Casey expected OP_FALSE, _IF, _PUSH, _ENDIF to operate that way. Do you mean he just guessed? Storage is still bound by block size(not unlimited) and the 'scammers ran out of fiat for their attack', ie fees operated exactly as we all expected them to do. Steelman: - You're describing every single exploit/hack/crack in computer software history. The people who designed OpenSSL intended it to be a library for HTTPS security. The people who designed the Heartbleed hack expected to break OpenSSL so, you think Heartbleed wasn't an exploit and OpenSSL was just fine? This is clown-world logic. Steelman: - In information security terminology, a "bug" is a problem found in the software. Some bugs are also "vulnerabilities", meaning that you can leverage them to cause unintended or unexpected behavior by the software. Leveraging them is the "exploit" of the vulnerability. Strawman: - I can convince myself it's an exploit (semantically) but I still struggle to see the bug. Everything is operating as expected, but some users are using those operations (in an obvious way) to do something others for whatever reason didn't expect. Steelman: - The bug is the datacarriersize is not properly counting data carried inside op_false op_if Strawman: - ty! (although begs the q what is meant by 'properly') Was there a reason it was ignored? Was this deliberate decision? A non-concern? My (crude) understanding was some initially used this for commenting, as it doesn't execute anything. Steelman: - When datacarriersize was first introduced in 0.9 it was done so simultaneously with op_return. Prior to 0.9 people had started to use ridiculously inefficient methods to embed small amounts of arbitrary data in transactions, so a consensus emerged to create a strictly limited, but TOLERATED way to add arbitrary data to transactions - that's what op_return was. To limit the amount of arbitrary data per transaction, datacarriersize was added. For the next 10 years, all was happy. Then in early 2023 someone discovered a way to add arbitrary data to a transaction outside of op_return, and bypass the datacarriercheck matching heuristic. This bug was critical for inscriptions to work because it meant that they could bypass the existing spam filters to add any amount of arbitrary data up to the block weight limit. In mid-2023, the bitcoin core managers closed the issue about the bug, claiming that discussing the github topic was "too controversial" In August 2023, a Bitcoin core maintainer changed the documentation/comments in the source code which defined arbitrary data. Since then the core team has been unwilling to acknowledge that this is a bug. Strawman: - Also remember that a property of OP_RETURN is that it creates a provably unspendable utxo, which can be safely pruned if you don't want to store the arbitrary data on your node. Steelman: - This isn't an argument against spam, though. Pruning just adds to the work of a full node, it doesn't eliminate it. And Inscriptions are all equally prunable. Steelman: - OP_RETURN is a top symbol of altcoining mindset, such mindset classic 'solution' is a BAND-AID to pretend the problem does not exist and life goes on. As hash-anchoring to TXs is possible, the question needs to be: how to make it VERY cumbersome. NOT apply a band-aid on top. As you can see clearly from some of these arguments that legitimate bug is being exploited by some bad actors in the #bitcoin community. I would strongly suggest running @BitcoinKnots to disincentivize this behaviour and if you are miner then send your hash to @ocean_mining . If this bug doesn't get fixed then I wouldn't be surprised if we have to reconsider the blocksize limit since spam (sorry scam) has been bloating bitcoin blockchain and UTXO set like never before. It will drive up the cost to run your own node hence we may need to think about reducing the blocksize limit as you can see most of the mempool is filled with garbage (to scam the people) Maybe 300kb-400kb limit would be optimal blocksize limit. It will at least keep the cost of running your own node low for a very long time. If you want to see bitcoin getting succeed, you don't want to see NGU in only #bitcoin price but NGU in node runners as well and current spamming condition will severely affect the NGU in node runners (in the long run for sure). cc @Bitcoin Mechanic @Luke Dashjr @npub16s0g...8ky6 @Giacomo Zucco