Avatar
rkfg
bc1f8b83991f46f6f2f2b4569314d50b229e9f2761716ca56d4572a190801a44
Nostr testr
Replying to Avatar Jon Matcho

Sorry, but today the sun is not out for Bitcoin.

A few Core Devs gaslit and steamrolled their way into merging a pull request that was vehemently opposed and not even well-supported by "Core Devs" at large.

Rather than showing the clear opposition (the "nays" / NACKs) as was usual for prior PRs the summary was changed to only show the "ayes" (ACKs). This disingenuous move made it look like the PR was entirely supported. Amazingly, after approving, the PR now shows the ACKs AND NACKs.

Reading through the details in the PR shows a very different story.

https://github.com/bitcoin/bitcoin/pull/32406

Is this the day Bitcoin begins to die? I surely hope not (although "hope" was a word used repeatedly as reasoning for why this PR would actually benefit Bitcoin, as in "we hope this will work").

FWIW, 3% of Core Devs wrote an open letter expressing their opinion (obviously having permission to the Core website), with little-to-no proper debate that includes the majority in dissent.

It's time to take a serious look at the Bitcoin Core process before it becomes a worldwide virtual government organization. Who is paying Gloria Zhao (Chaincode)? Who is paying Peter Todd as he defends Citrea as the primary use case for the change, citing concerns for "millions of dollars of [VC] funding" (his words), and appeasing large mining companies?

How are we not seriously concerned about this? "GM" has now replaced "how 'bout that game last night".

Facts.

And yet starlink is not globally available even though there's coverage everywhere. Ironic.

Personal human time is scarce though. Money can only measure human life time, and with 100% automation that doesn't require any maintenance by human money will cease to exist. Same with humanity achieving immortality.

I added nostr zaps to go-host-lnaddr, everyone's welcome to review and comment: https://github.com/hieblmi/go-host-lnaddr/pull/27

I couldn't find any other such solutions except the reference implementation which is in JS. go-host-lnaddr allows hosting your own Lightning address/LNURL pay/Nostr name, and now it also lets you receive zaps to your own LND node. I haven't tested it much, just followed the spec and used the mainstream libraries. It's effectively a small addition to the existing functionality that parses zap request and posts zap receipt + puts the request to the invoice description. Still, there could be quirks I missed. I currently run this patch myself.

High time preference ftw!

Best of all, nobody got shot or killed 😂 These censored, cucked, non-local models ain't worth shit. You will not be allowed to do anything serious with them or train on any material. It's an expensive toy you can only rent.

Central Bank of Russia and Ministry of Finance just submitted a bill that will impose a fine of 100 000 RUB (≈$1200) for buying things with "cryptocurrencies". No idea how they're gonna enforce it, probably by monitoring the merchants. But it's something to consider if one wants to just buy things. Imagine living in a country where your biggest concern is tax obligations after a payment and not a fine that's 2-3 months of your salary. Damn.

Same about relays btw, I added relays on coracle and didn't see them in other clients like they didn't save in my profile meta info at all. Then one client (presumably) removed or reset my relays and I only had like 3? Imagine installing a buggy client that does that and suddenly everything is affected and your posts no longer have the same reachability for this reason that's quite hard to notice.

I had issues with snort and coracle regarding post loading. Infinite loading and all that. I'm starting to doubt that "simplicity at the center and complexity at the edges" is that good of a paradigm... all clients lack something very fundamental like showing and making posts reliably, following people and such, but they're very eager to implement non-essential features such as zapping or badges. Looks like debugging the core features is quite hard if they're in such a poor state.

The biggest problem in nostr is... following people apparently. I've seen too many clients where this basic feature is either missing or unavailable because of adblock hiding it for some reason or it's buried so deep I can't find it. On primal it's the former I think:

Non-working zap button, a menu...

Add user feed? Is that following? Nope, it's something else completely. Ah, there it is:

Very convenient, just open any post and you can find the follow button if you're lucky. No wonder engagement is so bad on nostr if you can't even follow people in one click.

Great DoS potential! Since pushing an event doesn't mean you're able to sign, just pick whatever events of other people and push them to this relay, get a bunch of such messages that *those* people receive, not you, lmao!

I suppose Ark only makes sense if literally hundreds of millions users send txs all the time. Then it justifies spamming UTXO updates in *every* block. Otherwise this on-chain footprint is ridiculous. LN defeats it easily while being faster and less chain-polluting. Also, I don't think Ark would be more effective in case of mass exodus (same as multiple LN channels dying at the same time).

The difference, if I understand it right, is that ASP can simply rob the user if they don't refresh their VTXO without additional on-chain txs and in LN the other peer has to publish a tx (or wait). It's also said in another explanation ( https://github.com/fiksn/awesome-ark/blob/master/explained.md#tradeoff ) that there would be no more than 256 ASPs in total due to on-chain limitations and their capitalization requirements are also pretty high ( https://gist.github.com/RubenSomsen/a394beb1dea9e47e981216768e007454#payment-pool-comparison ), I wonder if those requirements might exceed the total 21M limit. Because the total liquidity is the volume speed (BTC/second) multiplied by the lock time (1 month), so if all BTC are locked in one ASP it'd be limited by ≈8 BTC/sec throughput. Which is already unrealistic if you count the lost coins and those in cold storage.

And who's gonna pay the on-chain fees? How to calculate them? What happens if ASP's UTXO is evicted from mempool or significantly delayed? Or reorganized? Overall, I'm absolutely not sold on this idea, it's kinda fresh and interesting but I don't see how it's practical today. And if it only works for many more users then it doesn't scale well with the capital required.

Or maybe I just don't understand it well enough.

Using an opensource LLaMA-based model that runs fully locally in browser, on JS

What's funny is that their fake market cap is falling. I remember reading about 1 billion mc, now it's more than 2x down from that.

Nostr is now "the other bird" app lmao! Giver enough time and work Twitter will get that title instead, hopefully.

Well yes, any relay can do that for any reason. But there might be game-oriented relays that don't care, or maybe they filter normal events and only let the custom gaming events through.

🤙 in the USSR was a gesture used to invite someone to a drink, probably a code during the prohibition period.