I've learned over time that Bitcoin (unfortunately) doesn't exist in a bubble. A few external things affect it (that I wish didn't).
-politics
-macro
-crypto
Politics affect the network most where it interacts with meatspace. This includes the mining infrastructure, exchanges that still accept useless fiat for bitcoin, and bitcoinERS, themselves.
Macroeconomics impacts mostly the strength of NGU technology. Certain macro landscapes cause people to liquidate their liquid volatile assets. This causes institutions and retail 'non-believers' to sell.
Fucking Crypto. The paper (by that, I mean non-existent) Bitcoin sold during this cycle, in my opinion, caused us not to hit 100k. The collapse of much of the Shitcoin industry caused us to dip below our previous high of 20k. This limits NGU technology.
NGU technology drives adoption, keeps the network secure, and even is frequently re-invested back into the industry. Although there are a few well needed Bitcoin-only VC funds, much of that comes with the aid of NGU technology.
There are ways to insulate ourselves against and limit the impact of these factors on Bitcoin. But to do that, we can both simultaneously be aware of their power AND choose to disregard it.
How?
Last month,
Montana and Mississippi passed
"Right to Mine" Bill's.
We can
BOTH
fight for similar bills
AND
ignore the law if they outlaw it.
peace & pv.
To everyone who was blackpilled until they found Bitcoin...
...remember that?
That was the worst! I definitely didn't want to produce any children. And I think that's a reasonable reaction to seeing a future without hope. So when you see some nihilistic 'party' (well, escapist) drones, they aren't 'bad' people, they are just missing a VERY important part of the puzzle.
An event that has a one in a million chance of happening to a person each day happens 7,800 times a day. (At world population of 7.8 billion people)
Ohhh so it's going in the protocol? Wow. What's happening to my dumb protocol?! Honestly I think adding a POW feature instead of adding a sats feature... but hey, I'm a bitcoiner.
Yeah, could do a whitelisting of people "in network" (friends and friends of friends) but some people are just super busy. Like... 'Bitcoin celebrities' (lol) might just opt to require 5,000 sats to see a message. And that's just the first message, after that, you could whitelist them rather than charge them EACH message.
I don't know how you would implement that without the receiver and sender both having a client with this capability.
The one I was thinking of only requires the receiver to have a client with this feature, and could work with the sender using any client as the invoice occurs via DMs
Yeah, I mean you can set it at 20 sats, which is about 1/10 of a penny. Doesn't take much to stop the bots. And many you could do a thing where you add them to a whitelist after their first message if they aren't a spammer.
Yeah, this is just be a nostr dm spam filter.
If DM spam becomes a problem, How about a client feature where someone can charge a fee to get a DM
I think it can be done at the client level in a way that doesn't matter what client the other person is using.
-Person sends a message to me
-My client autoreplies with an invoice at an amount I set
-that person pays it
-my client then allows me to see message.
Since on his end the payment is entirely through DM, it should work no matter what client he uses.
I have no skills to do this, but what do you guys think?
But if they weren't using the same client, how would the invoice pop up?
Ok. You send your dm.
My client auto replies with an invoice.
You pay
Then I get the message.
Since it happens through DMs, it should work no matter what client you have
Well, if you were creating a system from 0, you could do that, make it so all npubs could only send so much. But nostr already exists, I can't alter THEIR clients but perhaps I can alter mine to require such. It would probably be on the client level and not need any protocol change, just when you attempt to send something a invoice would pop up at an amount you set
It would be great for newsletters to come either to my feed and @ me, so I don't miss it. Orrrrrr, just nostr DM me. At the moment nostr DMs aren't dead and useless yet. Like emails are.
But, I guess that will happen.... right? Is there anything we can do? Can we do things with putting a Bitcoin "hashcash" fee on sending messages to Nostr DMs?
Will there be blacklisted relays the way there are blacklisted... whatever 'zones' in IP addresses are called. Let's make it so we don't recreate the same system. (that story about that guy that ran his own email server for 40 years and had to stop because he was ALWAYS filtered out as spam.)
When adding Snowden to this picture, I couldn't find a picture of Edward standing, because he's usually just sitting, streaming from Russia, so I used a picture of a Asian man, and his skin is pretty brown, especially compared to Snowden's.
I know Nostr is 'separate from Bitcoin' and everything, but they are quite entangled. Zap functionality, yes, but paid relay monetization will prove to be pretty big. Credit Cards would be a real hassle, although accepting them through the appstore would be the route that makes sense. That is making the big assumption app stores won't ban clients/have specifications on a restricted Nostr experience that is deemed 'acceptable' for the masses. Maybe apps will have two versions as there might not be too much difference in code between the versions. Upcoming Bolt 12 may enable recurring payment functionality on Bitcoin, for monthly plans of unrestricted Nostr use. The future is orange and bright, as Bitcoin now has a way to communicate online, whether that means replacing Twitter, Facebook Marketplace/Craigslist, Github, even coordinating coinjoins. The future is indeed orange and bright.
Then I must softfork Nostr to stop this "lying and tricking".
You should try to put your YouTube window in here next time. I know that when will #[2] livestreams on Twitch, the window shows up embedded in the feed, on Snort at least. It's cool watching and zapping in the same window.