pull down to refresh

Howdy there, partner! Welcome on into the Stacker Saloon.

Saddle on up to a stool and spill the beans about your day, fire away with them questions, or let loose and give us the lowdown on your wild and woolly life. We're all ears, so don't hold back!

We're open round the clock, so mosey on in whenever you please!

1 sat \ 2 replies \ @k00b 19m

I think lit's half-life is too long. I'll probably take it down to three hours next week.

reply

What's the half life currently?

reply
1 sat \ 0 replies \ @k00b 16m

Four hours

reply
reply
201 sats \ 8 replies \ @jasonb 1h

Woot! Woot! sn in OP_Daily today. Woot! That was a nice convergence of two of my favorite daily reads. Kind of ironic article for me to share though while I've lost all my cowboy equipment. :)

reply
1 sat \ 0 replies \ @ek 55m

wow, thanks for sharing

reply
10 sats \ 2 replies \ @jasonb 1h

If you want to get in on the OP_Daily newsletter:

https://bitcoinpark.substack.com/subscribe

reply

deleted by author :)

reply
1 sat \ 0 replies \ @jasonb 1h

Fixed! 😅 With 4:20 to spare! Sorry, I suck.

reply
121 sats \ 3 replies \ @DarthCoin 1h

such "non-custodial"

reply
1 sat \ 2 replies \ @jasonb 1h

ha! You gotta admit though, you got it if you want it.

reply
21 sats \ 1 reply \ @DarthCoin 1h

sure, like this guy #1436660, right?

reply
1 sat \ 0 replies \ @jasonb 1h

Ha!

reply

building up a backlog of Scoresby posts to reply to... lol

reply
71 sats \ 0 replies \ @DarthCoin 4h

reply

MFW installing curl every damn CI run just to download and install a nodejs binary

Hit:1 http://deb.debian.org/debian trixie InRelease
Get:2 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB]
Get:3 http://deb.debian.org/debian-security trixie-security InRelease [43.4 kB]
Get:4 http://deb.debian.org/debian trixie/main amd64 Packages [9670 kB]
Get:5 http://deb.debian.org/debian trixie-updates/main amd64 Packages [5412 B]
Get:6 http://deb.debian.org/debian-security trixie-security/main amd64 Packages [108 kB]
Fetched 9874 kB in 1s (6974 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libbrotli1 libcom-err2 libcurl4t64 libgnutls30t64 libgssapi-krb5-2 libidn2-0
  libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libldap2 libnghttp2-14
  libnghttp3-9 libp11-kit0 libpsl5t64 librtmp1 libsasl2-2 libsasl2-modules-db
  libssh2-1t64 libtasn1-6 libunistring5
Suggested packages:
  gnutls-bin krb5-doc krb5-user
Recommended packages:
  bash-completion krb5-locales libldap-common publicsuffix libsasl2-modules
The following NEW packages will be installed:
  curl libbrotli1 libcom-err2 libcurl4t64 libgnutls30t64 libgssapi-krb5-2
  libidn2-0 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libldap2
  libnghttp2-14 libnghttp3-9 libp11-kit0 libpsl5t64 librtmp1 libsasl2-2
  libsasl2-modules-db libssh2-1t64 libtasn1-6 libunistring5
0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

@bot plz rewrite github.com/actions/checkout in an ash-compatible shell script because nodejs is the sux

reply

First time seeing this. Welcome!

reply

Those are fun to get and unfortunately rare

reply
24 sats \ 4 replies \ @optimism 6h

Great! Good job. I think I got 3 of 'em last month and I suspect that they were all bots, but that "comes with the territory", in my case. lol

reply

that reminded me of this XD
#453705

throwback @ek meme from that thread

reply
123 sats \ 2 replies \ @ek 5h

nice

reply
101 sats \ 1 reply \ @plebpoet 3h

a wild ek appears

reply

"fucking legend"

reply
122 sats \ 5 replies \ @ek 6h

@optimism, I want to know what you think about this; my insecurity is holding me back:

I'm reviewing Add a "tx output spender" index.

I was confused by -whitelist=noban@127.0.0.1 in the tests. When I learned what it's for, I also learned about self.noban_tx_relay = True, which afaict does the same thing. I also noticed that tests usually use self.noban_tx_relay instead of a manual -whitelist. I now consider mentioning this as a nit in my review when I'm done.

But I'm not sure, because it's a nit. In the grand scheme of things, it doesn't matter. Also, the other reviews are about more important things. Nobody else mentioned it. Isn't this nit just distracting, then? Wouldn't it just look like I'm showing off that I know about self.noban_tx_relay? lol

I might only mention it when I also have something more important to mention.

Anyway, I guess my question is: Would you mention this as a nit? Or is this too much of a nit even for a nit?

I'm glad you're here so I can ask you this, but I’m sad I need to ask someone this instead of just making a decision on my own

reply
301 sats \ 2 replies \ @sedited 1h

I mention most of my nits. I think you should in this case too. The test framework option was introduced after the original PR was opened: https://github.com/bitcoin/bitcoin/commit/c985eb854cc86deb747caea5283c17cf51b6a983 , so it should have been picked up during some rebase along the line.

It is very quick to fix and there are other review comments that require action from the author anyway.

reply

Thank you for letting us summon you!

reply
101 sats \ 0 replies \ @ek 1h

Thank you for taking the time to reply!!

I didn’t realize the framework option was introduced later. I will definitely mention this nit now.

reply
203 sats \ 1 reply \ @optimism 6h

Nit: (haha) I think a better person to talk to this about is @sedited as an actual project maintainer - I have zero commits to Bitcoin Core and I intend to keep it that way. There are things I want to remain an independent user of!

Personally, (on any other repo, haha) I'd do this:

  1. Always mention a nit. Review-done-right is the most expensive part of any codebase, so early flagging is good flagging. [1]
  2. Always prefix it with nit:, so that it is clear that it's not a showstopper finding.
  3. Don't be afraid to make a mistake sometimes, as long as you're willing to make them at-most-once.
In the grand scheme of things, it doesn't matter.

Per my above rationale, it absolutely does matter. It helps when reviewing now to see the nit, rather than having to context switch into that code later once more and think about it again. Human minds (at least of code reviewers) aren't that different from LLMs in terms of context resets!

Wouldn't it just look like I'm showing off

Just mention it, don't make a show out of it. Stay humble and spend effort.

I'm glad you're here so I can ask you this

Aww.. I'm glad you're here too <3

  1. especially on Bitcoin Core where every little nit is not just technical debt, but social debt because it is another PR that needs to be reviewed by 10s of people. Catch 'em while they're hot!

reply
101 sats \ 0 replies \ @ek 6h

Thank you! This helped.

reply
11 sats \ 1 reply \ @BlokchainB 7h

87th Cowboy Plunda Drop in the @saloon

Howdy cowboy! Come on in!

Use that fancy LN wallet you got and login into plunda.co and git you some loot! Get a shot at some coins🪙 Box of loot🎁 or an arcade token!

Use the below voucher code to collect!
GDKSLEF9RR1M

To redeem Click here

Got questions? Reach out to the sheriff @plunda

reply

Coin of the day:

reply

I'm glad @k00b took my suggestion to sync the daily subsidy with the block mining reward!

reply

No wonder you are a statist. You love to be paid by gov.

reply
reply

pay your SN taxes !

reply

if it helps catch the parasites of all sizes & personalities, that's a good "tax" to have;

reply

I'm not gonna talk about that again!

reply

hahahahaha
Is not the SN pool rewards like a communist state subsidy ?
I was for long time a supporter of removing any of these "subsidies", remember? #796213

reply
CAmount GetBlockSubsidy(int nHeight, const Consensus::Params& consensusParams)
{
    int halvings = nHeight / consensusParams.nSubsidyHalvingInterval;
    // Force block reward to zero when right shift is undefined.
    if (halvings >= 64)
        return 0;

    CAmount nSubsidy = 50 * COIN;
    // Subsidy is cut in half every 210,000 blocks which will occur approximately every 4 years.
    nSubsidy >>= halvings;
    return nSubsidy;
}

https://github.com/bitcoin/bitcoin/blob/master/src/validation.cpp

reply

I am talking about SN rewards pool. The Bitcoin mining "subsidy" is totally something else.

reply

Jaja great analysis 😉🤫