No, it means what is top will be determined based on sats and nothing else

Then you'll love this! :)

Good question. We'll probably keep the log transformation but it'll apply something like as follows: log(0.3*(zap_sats+boost_sats) - downzap_sats).

The log transform won't be applied per zapper, but for the entire item.

overheard in my brain: boring in bed but a freak in the threads

At least from the outside, it appears IBM's business model is to acquire something nice, sell it to all their customers in multi-year contracts knowing a dependency will form, then let it slowly rot.

I'm probably super wrong. Their customers might be relatively invisible to someone like me. But that's what if feels like.

A major motivation behind new payments engine was to make incentives relatively trivial to change.

I had my first experience using it that way by making 100% of downzaps go to the rewards pool. It took modifying 3 lines of code: https://github.com/stackernews/stacker.news/commit/4b74d2673f5dd6bab2ef810dec9b22a9222dc105

I was wrong. I was unintentionally recreating the original bug with my manual probe by not specifying a preimage.

Too rich for my cud, but I hope they release a cheap version at some point.

What's your bitcoin origin story? Like, how did you come to bitcoin?

What's something you believe about bitcoin that no bitcoiners agree with you on?

What's the most surprising thing you learned about bitcoin writing the book that you didn't know before writing the book?

I'm no writer, but it might help to not think about writing a book. I imagine it constrains the work in an unhelpful way. I'd think about describing/communicating something with words. The book is just one potential artifact should the description be a certain size and warrant sharing.

Like, if I were an actor, I wouldn't think of my task as starring in movies. Where would I start in that case? Every small step I made toward the goal would feel worthless, pointless. Instead, I'd think of my task as pretending well. It overwhelms the task to constrain yourself to a particular outcome.

We plan to move the CC limits to an easier to access settings page. It's the last screen when attaching/modifying a wallet.

You should be receiving sats for zaps again.

I removed probing. In the meantime we're using LND's route prediction stuff instead which doesn't suffer from this problem.

After implementing a custom probe, it would appear that the probe causes the route to be marked as invalid temporarily. Merely attempting the probe, by itself, causes the payment to not succeed.

Yikes. I guess we'll just stop doing probes in the meantime and rely on mission control's guesses.

lol

In the case of there being no route from SN's node to the receiver's, rather than a probe failing, the sender's payment will fail.

The probe is helping us predict the weather. Absent a weather report, we risk the sender stepping out into the rain.

I think it's clout. Perhaps more importantly self-clout. It feels like an accomplishment because it looks like one from a distance.

In this case, I think it's also a subconscious DoS attack.

sigh ... the tides of new ... s