AI's doing a lot of work on miner centralization, as will the halvings. Big mining pools are something I think we're seeing follow a bell curve trajectory. People come into mining thinking they're gonna pick up free money on the ground, and they come out, hopefully not totally insolvent, realizing that they were in a knife fight over every penny.

We could use more work on StratumV2 (and yes, DATUM), but the sky is staying right where it belongs on this matter.

If anything OP_RETURN reduces blocksizes, given that it doesn't have the segwit discount.

He literally went off down a "think of the children" psychotic break suddenly concerned that CSAM was going to be on the nodes (and that this would make them illegal to run).

I'm not sure why you'd want to incentivize spending. Humans want things. Humans need things. Those natural incentives exist -- people are going to spend.

Capped money to stand as a counter balance to those incentives is what allows any of it to maintain its shape.

Now, is growing the money supply slower than the rate of real production in the economy going to ruin it and turn it worse than fiat? Of course not. If you're looking for a compromise that's probably quite liveable, yea, tail emissions are probably it (and beat constant balance sheet expansion in the private sector for credit booms and busts).

My bigger concern, if I have one, with Bitcoin, is the divisibility only out to the satoshi. I don't worry about it in my lifetime, or likely this century or two. But IF the supply does manage to dwindle, or enough coins end up relatively stagnant in large hoards, then I'm not sure things go all that well for such a large minimum denomination. I don't expect it to become worth much more than a 10-20 cents or so in present day purchasing power in the next few decades (and that's 100-200x from where we're at) so I'm really not so worried. But with stepped up production and futuristic manufacturing potentially coupled with reduced monetary flow, yea, it could be something a future generation wants to really take seriously.

Given that assertion, I'd say y'all made a far more sensible approach than the Blake2B crowd.

I don't share that assertion, fwiw. But if it's one that is held XMR makes a heck of a lot more sense than Blake2B.

I don't really see either of them being nearly as decentralized, but Blake2B doesn't even seem to be trying.

In the event that miners actually decide to go against the incentives that the network has laid out, then you fork off.

The balance of incentives for diverse parties, not "the nodes," is what has always kept Bitcoin afloat.

Eh, the Fed controls the supply of bank reserves. That's not at all the same as controlling broad money supply. Especially when most dollars in the world exist outside of the United States entirely, where they can't even access bank reserves.

The Fed WISHES they controlled inflation the way that some of us pretend they do.

And they do have a role. It's just not quite so cut and dry. When the Treasury debt level is lower they can do a number on reining it in by hiking interest rates, making banks and shadowbanks suddenly a lot less interested in borrowing from each other. The problem is, at the level of outstanding treasury debt we have, every rate hike they make is just an additional payday to anyone buying treasury bonds/notes/bills, and more issuance of even more debt by the treasury (which in turn is the collateral used in the repo market that fuels private formation of deposits -- what most people call "money" despite it having no direct connection with the Fed at all).

In Fiscal dominance, the Fed mostly is just along for the ride, unless they can figure out a way to pull a Judo move that puts the market on course to reverse and go back into Monetary dominance.

And no, this doesn't mean Bessent is in charge (frankly, unfortunately). It means that Congress's ability to manage money is what determines our levels of inflation.

So yea, hope you're stacking...

People just do stupid things like buy their fats in refined form. You can buy some pretty large amounts of suet pretty cheaply if you go looking for it in the frozen section where they stuff the liver and pigs feet. Chop that shit up, throw it in a slow cooker for 6 hours or so, strain it into a jar, and you've got what they're selling for $30 that you just paid $3 to.

If you worry nostr's dead, you probably should jump on a concord chat.

Though I think nothing excites me more than fips right now given that it killed a 20+ year nuisance of updating dyndns redirects on a monthly basis for my home server.

I was looking more at a Slackbuild script for it so people can build their own packages and install them. The reality is, I haven't seen ANYONE else here using Slackware -- it's definitely more of a niche system these days, especially when we're still rocking glibc 2.33 and all the new and interesting stuff complains about it.

I mostly set out to build it for myself but figured if I get something reliable enough and up for the format that slackbuilds.org uses I may just throw it there.Slackware users are very familiar with the fact that you either go through slackbuilds or you're just building freely from source -- NOBODY carries packages for us otherwise.

It honestly took me years of using linux before I even really realized package managers for installing software was a thing -- tar -xvf && ./configure && ./make && sudo make install was life.

That said, thanks for the invite. My goal is to be able to have something that's abstract enough that it can ignore a lot of the dynamism of a very early stage program and just spit out a .txz slackware package after the script is run in a directory with the latest tarball, with a modification to the VERSION variable being the only user modification. And that's mostly what I've got at this point. It's just a little rough around the edges.

Good to know. I ran the dig and nc commands to test and it looked okay which is why I went so nuts on everything else. I've since just put a few more peers in so as to have a bit of redundancy.

The fact that I've got a less than standard installation is what really left me wondering. Happy to say though that getting it together as a slackpack has been pretty smooth.

Not quite standard enough to publish on slackbuilds.org but fairly close. Still working out some of the script for not blowing away config files and making it more manual (my clanker put downloading the code in the slackbuild script itself trying to be helpful, and it was -- just not standard).

Turns out Test-US01 was down.