Either way I'm glad I read it and waiting for the other parts of the series. Really curious how to get access to this airline booking data so I can write my own bot to book my flights and deal with all the permutations and combinations to find the best deal.

>> is almost mythological. In 1953, C.R. Smith, president of American Airlines, was seated next to R. Blair Smith, an IBM salesman, on a cross-country flight. By the time they landed, the outline of a solution had been sketched. IBM and American Airlines entered a formal development partnership in 1959.

edit: oh and then the actual system didn't actually go live another 5 years later - in 1964. Over a decade after the two of them sat next to each other.

Reminder to myself when my potential customers don't sign the deal 5 minutes after my pitch!

I even made it into an open source runtime - https://agent-air.ai.

Maybe I'm just a backend engineer so Rust appeals to me. What am I missing?

I want to give kudos to two things:

1. It took you 10 months to build this. This is focused product development and craftsmanship which is very different from Vibe coding something. So let this be a reminder to all the "I can vibe code this or that in a weekend". Good products / experiences take time.

2. You've pursued building something in a space that anyone would normally dismiss right away: "Why would anyone use this? Google Docs/ Word etc already does this" or "MSFT / GOOG will destroy you". Good on you for picking something that is hard and building it well. I actually had this idea and almost built it but dismissed it myself for the same reasons as above. So reminder again for the builders in the back: Doesn't matter if there is a 800lb gorilla building this, if you can execute it better go for it.

Kudos!

This should be solved by the vaults (hashi corp / AWS Secrets Manager).

The one thing that I did build was based on a service that AWS provides (AWS STS) which handles temporary time bound creds out of the box.

https://timebound-iam.com

What if we did build a clean room as a service but the proceeds from that didn't go to the "Malus.sh" corporation, but to the owners / maintainers of the OSS being implemented. Maybe all OSS repos should switch to AGPL or some viral license with link to pay-me-to-implement.com. Companies that want to use that package go get their own custom implementation that is under a license strictly for that company and the OSS maintainer gets paid.

I wonder what the MVP for such a thing would look like.

Maybe once enough posts have been flagged like that then that corpus could be used to train an AI to automatically detect content generated by AI.

That would be cool.

Maybe the HN site wouldn't add this feature but if someone wrote a client then maybe it could be added there.

Then the recipients can reply to the email thread with "Thursday works".

Not affiliated with vela - just what I understand from their site and the comments on this page.

Now the issue of which properties can "ask to verify your age" and "apple now knows what you're looking at" is still an unsolved problem, but maybe that solution can be delivered by something like a one time offline token etc.

But again, this is a very hard problem to solve and I would personally like to not have companies verify age etc.

Unless your thing has strong network effects or a large capex requirement (ex: GPU infra) its easily replicated and I think that's really what makes things hard.

Then when I raised from a16z and had some money in the bank it didn't get any easier. The money didn't help (maybe it wasn't enough). Ad spend or content marketing or paid channels were all hard regardless of the free vs paid.

Maybe I just wasn't good at it.

That was before AI and you had to manually pound the bits into place.

Now with AI yes there are a lot of people shipping a lot of things but humans can tell when someone's put effort into something vs not and the time to traction is still as high as it always was.

Someone should do some analysis on number of things that go "viral" or gain adoption quickly today vs 5 / 10 years ago.

Getting traction has always been hard. Thats just business.

If you can't get atleast 20 stars then its probably not ready for the wider world to see it.

I'm sure there's problems with that approach but the current situation doesn't seem to be working.

Disclaimer: I tried to do a Show HN today and it didn't make it (and to be fair I wouldn't have made it past the filter I proposed above so I guess its working).

I've been using Claude Code for managing my AWS infra and I have multiple accounts (probably should have just one but here we are), and everytime I needed to work with my Cloudfront or S3 or Dynamo or anything else I was constantly updating AWS IAM Policies and had to remember to remove the policy permissions after I was done so my account didn't just have access to everything for my user.

So I built a simple MCP server that talks to AWS STS and allows claude code to request temporary credentials with a standard AWS IAM policy scoped to the specific service and permissions for a limited amount of time.

Now claude asks me to approve the permissions and the MCP takes over and vends the credentials. The nice thing is that there is no backend to maintain or durations to manage since AWS STS handles all those including expiration of the credentials.

Check it out, give me your feedback and feature requests are welcome.

Free & Open Source: https://github.com/builder-magic/timebound-iam

Comments URL: https://news.ycombinator.com/item?id=47047851

Points: 2

# Comments: 0

It took me a few hours to do and as Joel says in the article, it was not a fun thing to do (jumping right into code was more fun) but I stuck with it and did the whole thing.

Then I followed that list of tasks and kept track of when tasks started and ended and I was pleasantly surprised when after a few weeks the project was done right on schedule as predicted by the excel sheet. So my experience (data point of 1) was that it works if you do it exactly how he says to do it in the blog post.

I did it only that one time so take that for what it is.

The only two downsides:

1. A few people have reported my emails from fastmail (calendar invites mostly) going to their spam folder. Not enough reports so I'm not worried.

2. Google won't let me sign in and create / edit /comment in google docs with my custom email hosted at fastmail so I have to have a random@gmail.com account just to use free google docs to collaborate with people who only send me google docs.

Overall I think AI features are going to be great but give me the ability to pick and choose which I enable / disable and we should be good. If not then I agree with OP - Bye Bye Gmail.

oh, and don't read my emails and protect my privacy google! - no? Ok bye bye!