pull down to refresh
@k00b
19,224,864 sats stacked
stacking since: #1longest cowboy streak: 837 verified stacker.news contributornpub1qkfnm...c3hq09ertphuumn
0 sats \ 0 replies \ @k00b 5h \ parent \ on: btc++ scaling edition day 1 livestream from Istanbul bitdevs
hrm I'll make a github issue
There's a steep benefit curve to
graphql
. It's awesome when your API is evolving rapidly or you are caching on the client a lot. For something like git
I'm not sure you need either of those much.I looked into
git-bug
when I was hacking on https://gitern.com. I probably would've forked or rewritten it from scratch but that's how I imagined implementing github-like issues while maintaining portability.if you're dumb you don't know people don't like you so you can at least enjoy the company of other people
smart+untrusting+low empathy seems like such a curse. you're smart enough to detect people don't like you, but can't tell why on your own and don't trust anyone else to tell you why. and the result of learning people don't like you, usually, is not liking them.
I suspect what really biased the top ten horses were that they were well-known horses and when people came to visit them in their stables, before and after the race, they did tricks for them. The sheikh may have made a mistake of letting these visits to the stables influence the race, because the sheikh's normal races are not about winning but camaraderie.
Definitely don't trust a sheikh, and especially don't trust that they're infallible, but I wouldn't assume they're malicious and meddling when the results could be just as well explained by a flaw in the race design.
We discuss it a bit here: #1200292
It won't feel real to me until the 30 day sma is at 1 ZH/s.
that's cool we rank high for sybil fee. it's not a special word or anything. it's just a literal description. i guess it's just not something that's very common yet.
Continuing to my refactor of our payments "engine." Most of what's left are:
- sanity asserts and constraints of various kinds
- overlaying our existing subtree exclusion privacy pattern for the api
- polish
- testing (might vibe some automated tests) and verifying behavior of edge cases
- migrating the old data