Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vouch

github.com

Post reply on HN
Print view View original

481–490 of 507 posts

Re: Vouch

#481

Post by spruce_tips »

crazygringo wrote: post #320
spruce_tips wrote: post #279

Earlier quoted context omitted.

I built a side project to solve this for myself that’s basically an inbox toll system. It funnels emails from unknown senders into a hidden mailbox and auto replies to the sender with a payment link. After the sender pays, the email gets released to recipient’s main inbox. Recipient can set custom toll amounts, whitelist, etc. Would be happy to share the code, just lmk!

Has anyone ever paid you? The technical side of this seems easy enough. The human side, that seems more complicated. Like, if I were your doctor or contractor or kid's schoolteacher or whoever you hadn't happened to already whitelist, and had sent you something important for you, and got that back as a response... I'm sure as heck not paying when I'm trying to send you something for your benefit.

no one paid me but didnt really have this running for very long on my inbox. was really just a poc. and you're right - the human side is weird. surprisingly hard to solve the "real human, not spam, that's also an email address you see for the first time" scenarios, which there are many of - even with LLMs

Re: Vouch

#482

Post by spruce_tips »

kurtis_reed wrote: post #293
spruce_tips wrote: post #279

Earlier quoted context omitted.

I built a side project to solve this for myself that’s basically an inbox toll system. It funnels emails from unknown senders into a hidden mailbox and auto replies to the sender with a payment link. After the sender pays, the email gets released to recipient’s main inbox. Recipient can set custom toll amounts, whitelist, etc. Would be happy to share the code, just lmk!

Please do share!

https://github.com/JoeBerg8/tollbooth

this was part of a little saas tool i was building (since retired it) so spent some time today having an LLM help me pull it into a headless service. far from perfect but sharing anyway. details in readme!

Re: Vouch

#483

Post by spruce_tips »

Quizzical4230 wrote: post #303
spruce_tips wrote: post #279

Earlier quoted context omitted.

I built a side project to solve this for myself that’s basically an inbox toll system. It funnels emails from unknown senders into a hidden mailbox and auto replies to the sender with a payment link. After the sender pays, the email gets released to recipient’s main inbox. Recipient can set custom toll amounts, whitelist, etc. Would be happy to share the code, just lmk!

Yes please!

https://github.com/JoeBerg8/tollbooth

this was part of a little saas tool i was building (since retired it) so spent some time today having an LLM help me pull it into a headless service. far from perfect but sharing anyway. details in readme!

Re: Vouch

#484

Post by spruce_tips »

chasd00 wrote: post #316
spruce_tips wrote: post #279

Earlier quoted context omitted.

I built a side project to solve this for myself that’s basically an inbox toll system. It funnels emails from unknown senders into a hidden mailbox and auto replies to the sender with a payment link. After the sender pays, the email gets released to recipient’s main inbox. Recipient can set custom toll amounts, whitelist, etc. Would be happy to share the code, just lmk!

I’m interested in seeing this too. Heh an agent will gladly pay a dollar of their human’s money if they can declare success.

https://github.com/JoeBerg8/tollbooth

this was part of a little saas tool i was building (since retired it) so spent some time today having an LLM help me pull it into a headless service. far from perfect but sharing anyway. details in readme!

Re: Vouch

#485

Post by ulbu »

refulgentis wrote: post #150
HumanOstrich wrote: post #27

Earlier quoted context omitted.

If we want to make it extremely complex, wasteful, and unusable for 99% of people, then sure, put it on the blockchain. Then we can write tooling and agents in Rust with sandboxes created via Nix to have LLMs maintain the web of trust by writing Haskell and OCaml.

Zig can fix this, I'm sure.

zig can fix everything

Re: Vouch

#486

Post by awestroke »

Hendrikto wrote: post #416
awestroke wrote: post #407

Earlier quoted context omitted.

I see no advantage with this over real money transfers. At all. Just use some kind of escrow.

You don’t need a third party, or anybodies permission, nobody can censor you or block your transactions, you don’t need a bank account with everything that entails. The barrier of entry is the same as creating an SSH keypair. It works globally, fast, cheap. You do not need to trust anybody, all the code is open and the ledger is cryptographically verifiable by anyone. There are lots of advantages.

In this scenario, the repo owner can just merge the patch but still refuse to pay back the shitcoin. With escrow, the escrow entity would act as an arbiter

Re: Vouch

#487

Post by tristan957 »

verdverm wrote: post #435
tristan957 wrote: post #183

Earlier quoted context omitted.

The barrier in the Ghostty project is to simply open a discussion. It's not really hard.

What about fixing a typo in a comment? Do I have to start a discussion before I can submit a fix for a two char swap? Also, my statement was general, why are you making it about one?

As Mitchell said, the rules of engagement are defined per project. I'm giving you an example.

Re: Vouch

#488

Post by andai »

ramon156 wrote: post #186
andai wrote: post #139

It should just be $1 to submit PR. If PR is good, maintainer refunds you ;) I noticed the same thing in communication. Communication is now so frictionless, that almost all the communication I receive is low quality. If it cost more to communicate, the quality would increase. But the value of low quality communication is not zero: it is actively harmful, because it eats your time.

Sorry, but this seems like a privileged solution. Let's say you're a one-of-a-kind kid that already is making useful contributions, but $1 is a lot of money for you, then suddenly your work becomes useless? It feels weird to pay for providing work anyway. Even if its LLM gunk, you're paying to work (let alone pay for your LLM).

It is simple: we simply add a whitelist for the child prodigies.

Re: Vouch

#489

Post by eps »

k8sToGo wrote: post #148
andai wrote: post #139

It should just be $1 to submit PR. If PR is good, maintainer refunds you ;) I noticed the same thing in communication. Communication is now so frictionless, that almost all the communication I receive is low quality. If it cost more to communicate, the quality would increase. But the value of low quality communication is not zero: it is actively harmful, because it eats your time.

If you want me to read your comment, please pay me $1 first... if I find your comment interesting I might refund.

Who's hit with the transaction fees though?

Re: Vouch

#490

Post by aragilar »

bccdee wrote: post #470
aragilar wrote: post #398

Earlier quoted context omitted.

Would it not be better to report accounts then?

To whom? It's not against Github's ToS to submit a bad PR. Anyway, bad actors can just create new accounts. It makes more sense to circulate whitelists of people who are known not to be bad actors. I also like the flexibility of a system like this. You don't have to completely refuse contributions from people who aren't whitelisted, but since the general admission queue is much longer and full of slop, it makes sense…

Sufficiently bad PRs/comments/etc. are against the GitHub Terms of Service, look under section C (Acceptable Use), which links to https://docs.github.com/en/site-policy/acceptable-use-polici..., which then includes https://docs.github.com/en/site-policy/acceptable-use-polici..., on which you'll find multiple actions would describe posting AI slop (or things ancillary to it).

I wouldn't do this where it's not clear there was an issue, but for something like the really poor OCaml PR that was floating around, reporting the user to me seems like a logical step to reduce the flood.

Post reply on HN