Dave runs in the cloud and charges per query rather than running client side?

The supply can't be priced in because there's a liquidity issue. The people buying are limited by cashflow. No one assumed it would inflate by 2% a year forever and suddenly started buying after the halving.

Bitcoin is bought by a lot of people who put all their savings into it and is sold by a lot of miners who need to pay bills now. That's why price goes up after halving.

You are doing a Linux install but keep in mind that masjid audience is less technical, but more importantly, the average non technical user doesn't do anything but browse web on their laptop. I'd say shout out system76 for new laptops, and do your whole presentation on a laptop, not a desktop. Just make it look so convenient that it's easier than the normie way. Maybe even have a brother set up a fresh windows laptop on a smaller side screen and do things faster than him, while still explaining your full steps. This will take practice to do smoothly but I think the side by side will help your case a lot.

Why should note hosting be commoditized? Can it even be commoditized? Compare it to renting servers. There isn't a single market price to host a web app. Every host has its own features, pricing structure, free tier etc.

Same with relays. Why standardize income source? The default might be to pay to have your notes hosted, but you could just as easily have a format where a relay invests in scouring and indexing all kinds of posts, and users pay to have a curated feed of the best posts of the day, or maybe even a personalized feed. You could see relays that charge for notes on demand you can't find elsewhere where you give the note ID and pay them to get the note back. I even imagine there will be relays that hold on to notes that people request to delete and will charge to see them like a paid wayback machine.

Even in the most common case where relays charge to host your notes, they will differentiate on many factors such as $/storage, $/bandwidth, uptime, speed, hosting location, redundancy, censorship resistance etc. Hosting is not something that can be commoditized.

One thing for certain though, and it's biggest difference between your concept is the ad funded relays. I don't believe this can ever gonna be a significant part of Nostr and the best thing about it. It will be a thing when there is a company that builds out a full stack with a client that works with their own relays but even then it's not necessary for any standard protocol to pay for it.

The client side decides what the users see. It always has last say in that field. Therefore, any attempt to fund a relay with ads will be fought off by client side filters if it ever gains significant market share.

You can just use a downloader app on your device much easier. Why the hell would you broadcast a DM to a bot to get an MP3 as a note?

If we were trading in gold we would have invested much more in industry instead of weapons and would be competitive industrially on the global market without needs for tariffs.

A trade deficit is a self destructive phenomenon. It's physically impossible for it to exist continuously forever. (In terms of total net trade in and out of a country). If you count up the total goods entering/exiting America (or any other country), it will always be net neutral.

The only reason its seemingly not the case with America is a purely monetary phenomenon and wouldn't exist without dollar hegemony. And this isn't hurting America (at least any more than its hurting the rest of the world at Americas expense).

Why would nostr support be needed at an engine level rather than as a plugin on an existing engine?

I've been saying this for a while. AI training on your public posts is good and it's both dumb and futile to oppose it.

Clearly we need to start mass reporting everything until they all get banned by ai

Boston? They absolutely have them there

I don't think any of them are shy enough about it to call it a confession. They would say that quote outright no problem.

All AI tech so far is good at being very average. Until theres a breakthrough that makes AI smarter than the data it's trained on, only below average people will be made obsolete, and they already work in service jobs which require arguably much bigger leaps in robotics to be made obsolete.

But since you have both, you will have both forms of surveillance. They don't spy on you less when income tax is 10% less. As far as privacy is concerned, it's better to have full income tax and no tariffs than 10% less income tax with the rest in tariffs. And as opposed to income tax, the surveillance and imposition from tariffs scale with the amount. The more tariffs you have from more locations and product categories, the more nosy border patrol and customs will be, questioning your personal belongings and anything you bring with you.

This is not to mention that they are economically terrible for everything they propose to fix. Even if you believe the purported goals they are taxing everyone to save a few thousand jobs in some swing states. It's a terrible deal all round.

The value of all imports in 2023 was 3.3 trillion.

The revenue from income tax was 2.2 trillion.

The more tariffs you impose, the less return you get on it, since if they work at all, it will result in less importing. The potential revenue from tariffs is a fraction of the income tax. One is not an alternative for the other.

The more important point is that trade deficits as a whole are a myth that is self contradictory if you stop to think for a second. Also protectionism does not work in any way, and tariff heavy countries are genuinely a terrible dystopian place to live, as someone who has lived in a tariff heavy country. There is no good whatsoever that comes from tariffs. Even if the counterparty is imposing them on you, you still lose more by imposing them back.

> OP_CHECKLOCKTIMEVERIFY (CLTV): This opcode allows you to create a transaction output that cannot be spent until a certain time in the future. It is more reliable than nLockTime for future spending conditions.

Every Bitcoin transaction is a script that redefines the permissions required to affect a specific quantity of Bitcoin. When you send the normal Bitcoin transaction, you are not sending Bitcoin to an address, you are telling the network that the signature must match that pubkey for a transaction involving that coin to be valid. You can set other restrictions on valid transactions through other opcodes and scripts.

The reason there's a 65k block limit with CLTV is because this opcode accepts a 16 bit integer value.

Basically the locking is done by requiring a certain block depth as well as a signature from the address your sending to. This means that any transaction that tries to spend that coin prematurely is invalid because it violates the condition you wrote when sending it.

The second one works by writing a transaction that itself is invalid until a certain block height.

The difference between the 2 is that the former will go on the chain now, meaning the coins are spent now but locked in place until that future date. The latter does not go on chain. It can't be mined until that future date. This means that you can still spend the bitcoins before it goes into effect. Essentially, the on chain one is actually sent while the second is still fully in the sender's possession until the time comes and its resubmitted to the network by some party.

Agreed. I'd say tho that the gap between LN and card in person is much much smaller than the opposite gap online.

Scanning a QR code and paying genuinely isn't much harder than pulling your card out. It's only a couple more buttons than using apple pay. I say this as a business owner with a square POS. The interface is dead simple to the customer and my boomer customers will still spend 5+ seconds staring in confusion trying to find how to use their card. It would genuinely be easier for some of them to pull out a wallet app and scan a QR code.

I do think you have somewhat of a skewed perspective as a Dev. You are probably constantly trying edge cases and reading github issues of every lightning payment that failed. I have never had a lightning payment fail and as far as I've used, everything just works. Same way I'm oversampling boomers who struggle to use a credit card. I'm well aware of the limitations of lightning and that it's far from perfect but it is still extremely usable in its current form.

In person or online? Because for online, lightning is an order of magnitude easier than anything with a card. Even on chain is much easier than a card.

And of all languages mine has to be js