HN user

ajstiles

54 karma

[ my public key: https://keybase.io/ajstiles; my proof: https://keybase.io/ajstiles/sigs/07HM5A0ki-KR-eR1RBdigU7_6nOLMQ892EGCLHsv_BM ]

Posts5
Comments23
View on HN

On deck is “Failing Up” by Leslie Odom Jr. and “Risk: User’s Guide” by Stanley McChrystal.

Fav listen on the last few months was Dave Grohl’s “The Storyteller”.

On Browser Tabs 6 years ago

I built the "first tabbed browser", NetCaptor, back in 1997. https://www.buzzfeednews.com/article/josephbernstein/meet-th...

My take - some of us leave tabs open way too long because we fear not being able to get back to those sites again… it’s loss aversion. Tabs aren’t the core problem per se, it’s recall. We need to solve the “I want to get back here again” problem.

I primarily use Brave and effectively start fresh every day. I might get up to 20 open tabs at any given time, and I sometimes use tabs as a sort of Inbox that needs to be cleared. But sometimes, it’s best to declare tab bankruptcy and start over.

Fun to see NetCaptor mentioned here... I wrote it. The first version was released in 1998. I put the tabs on the bottom because HomeSite, the HTML editor that inspired NetCaptor, had tabs on the bottom.

The solution I've been envisioning would require you to pick a domain or sub-domain and allow the service to handle all incoming mail for it. You'd change your DNS settings for that domain/sub-domain to point to something we'd provide.

Then, when new emails come in, they'd be captured and we could do one of a couple of things with it: - post just the headers to a webhook - do something in response to the webhook response - delete the message - post full message to another webhook - put the message in an S3 bucket - put a pointer to the S3 message object in an SQS queue ...etc...

I've worked on other solutions that monitor specific accounts via IMAP, or have monitored Maildir queues, and they can be kind of a pain... that's why I'm looking at the service solution.

What do you think?

Sorta. SendGrid lets you point an MX record at them and they will process incoming emails by posting them a webhook. Google App Engine does something similar... but neither option is particularly flexible or can handle emails with large attachments.

Personally, I'd pay for a service that let me point my MX records somewhere, then be able to specify if I wanted a webhook called, or to get the emails pushed to S3, or a message queue... or some combination thereof. I'd still be developing, just not worrying about the mail server interaction itself.

There are lots of "simple services" that make developers jobs easier. Why write my own file storage system when I can use Amazon or Cloud Files?

We're hiring a bunch (interns and full-timers in search engineering, search tools, query intelligence) at AT&T Interactive (YellowPages.com) in Glendale CA. Email me for more info: astiles@attinteractive.com.