Hacker Newsnew | past | comments | ask | show | jobs | submit | mteigers's commentslogin

I've been a personal paying customer going on 2 years now. The biggest benefit I get from fig is their "build a script / cli" functionality. With it you can define UI elements like "list all branches" and you have a nice UI sector and then you can string together code snippets using the outputs of the UI elements. So I have some fig scripts that prompt me for half a dozen inputs and then execute bash and python based on the outputs.

Fig has been a godsend for acting as glue for one-off bash scripts that are added to repos.


I've been using Run [0] for this purposes.

[0]: https://github.com/TekWizely/run


Anyone have any thoughts as to ballpark costs to run this? My napkin math on the cosmo-db requirements is failing me (largely because I do not know Azure at all).

I'm wondering as a hobbyist / tinkerer if a solution like this is "affordable" (I know it's all relative)


I have no direct affiliation with this service (nor am I a user of it) but I recently learned about "Pool Together" which is a "lossless" lottery system. It's a daily lottery that happens automatically, you do not need to collect as it happens automatically, and you can withdraw all of your capital at any time.

I thought that was a decently novel use case.


First off, wanted to say thanks very much for posting this, primarily because I think it is an example that is straightforward and easy to understand. That said, I'm also thinking "if this is one of the best, straightforward examples people are talking about when referring to 'the value of smart contracts', then smart contracts are just nowhere near the important tech its boosters believe." (To be clear mteigers, not directing this at you, just saying this because what you've posted is probably the best example of a real-world use case I've seen).

In summary, what PoolTogether (https://pooltogether.com/) does is basically act like a normal savings account, except instead of you getting 4% interest a year or whatever, that interest is all pooled and then given out in big chunks at random - most people get nothing, but "winners" will get what is essentially everyone else's interest. Some notes:

1. I'm not clear what activity they're engaging in that actually generates interest (e.g. who they're lending to in order to generate a spread), but in fairness I didn't spend much going into the details. That said, if they really are generating income by lending, then I'm very curious how they can't suffer from some of the same negative edge-cases inherent in fractional reserve banking, like a run on the bank. If they are not generating real income from lending, I'm very suspect about how they can really be generating interest. Again, I didn't look much into this, so totally admit I could just not be understanding the details here.

2. I see absolutely no real benefit that comes from doing this as a smart contract vs. just doing this as any other kind of normal software (e.g. what core banking software provides), despite what their blurbs on the website say.

So still just dumbfounded by the lack of real utility in any of these smart contract examples I've seen.


PoolTogether routes deposited funds to a liquidity pool on aave. Those funds can be lended out via over-collateralized loans. That’s how the interest is earned. They could of course use other types of pools and gain funds on swap fees etc.


So they’re “premium bonds”? Indeed they have been around far longer than crypto


Oooh, yeah, sounds exactly like that, which according to Google has existed in the UK since 1956. AFAIK we don't have anything like that in the US.


Sounds really unnecessary. What is there not to trust in an actual lottery? Are the people that go on TV to show the results not worth the job they have?

Why does the website have a starting sentence that includes:

"a passion project I hold dear to my heart."

What is it about lotteries or smart contracts that have people that saying "dear to my heart". The only thing "dear to my heart" is probably my wife and family. I don't know how something related to money could be. And I have a hard time trusting a person that has a passion project dear to their heart related to lossless lottery systems.


That sounds amusing ... albeit the lottery aspect makes me suspect shenanigans. Is anyone reading the contract to understand if it really is what it says it is?

One of those issues is of course that people will need to find someone who can read the contract for them, and hope they get it right.

Still, good example that is easy to get, seems like easy to code and work.


Such a "lottery" is effectively a trillion dollar rug pull in waiting....


I'm curious if you have any pointers for whole Mac config with nix-darwin. This is something I've just started looking at and at the moment don't have much more than a nix-shell with some nice-to-haves. Any tips / tricks / guides are greatly appreciated.


not sure how approachable it might be, but i like to think the documentation isn't too bad for my personal stuff.

definitely nothing so well thought out as a tutorial, but i try to describe the structure & implementation of my approach + cross-link to relevant tools that i incorporate.

lmk if you find it useful at all: https://github.com/jkachmar/termina


Life’s short. Don’t waste it configuring nix-darwin.


As someone who has nix-darwin on their daily driver machine I can confidently say that I spent very little time configuring it and my config is almost in full shared between both NixOS and nix-darwin


Upfront payment figuring out Nix is amortized, and is less than a lifetime of payments of dealing with flakey machines, assuming you have a decent amount of lifespan left.


I do something similar but with HAProxy and a micro GCE VM which acts as my edge which hits a Tailscale subnet router and routes to my MetalLB install. Works _really_ well.


Ditto, my managed service at Google threw close to 3k 500s / second when I was still there. Anything from cosmic rays, faulty hardware bit flipping, hard drive failures.

We did, however, aggregate and group similar 500s and those did get looked at, but no way could we have looked at all errors.

The other thing, is that with resilient infrastructure, who cares about an occasional 500. Back off and retry. No harm done.


User experience might indeed not be influenced by these errors, but errors of a less stochastic nature will impact it. The former obscure visibility of the latter, and that's probably the point of TA.


It's likely some fraction of those errors would have had some tangible impact on user experience.


3k? What percentage of requests is that?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: