Good use case for away-from-laptop access to Claude Code. For a CLI product, Tailscale + tmux is a solid foundation — which many in this thread have converged on. I built a helper [1] that adds a monitoring layer on top: it watches tmux output and sends a push notification when Claude transitions from working to waiting for input.
[1] https://github.com/kmg/tether
Amazon Restaurants ( https://amazon.com/restaurants ) enables customers to order meals from top rated restaurants in their area. Our teams builds ultra-fast delivery experiences for delivering food.
As a software engineer, you will join a small team of engineers, product managers and research scientists working to build ultra-fast delivery experiences. You will own significant portions of the product and help define the next wave of product features and system architecture. You will be part of an entrepreneurial environment and innovate independently, launch quickly, and have fun. Come cook-up something great with us!
If interested, please shoot me an email - kmganesh -AT- kmganesh . com
Though I don't have experience with a large rewrite like this. I am really liking what I see in React.
React + Redux for the Flux pattern seems to be the best combination available right now. Watch this talk by Jessica Kerr - Functional Principles In React https://www.youtube.com/watch?v=1uRC3hmKQnM about why Functional / Declarative approach is good for front end development. Also Dan Abramov (Redux Author) Talk - Live React: Hot Reloading with Time Travel https://www.youtube.com/watch?v=xsSnOQynTHs introducing Redux is great.
Watch this awesome talk by Ryan Florence - Don't Rewrite, React! https://www.youtube.com/watch?v=BF58ZJ1ZQxY on how to approach rewrites bottom up and he rewrites a part of the TodoMVC written in Backbone.js.
Another project similar to this is Forge http://forge.thethemefoundry.com/
Embracing Sass, Less, CoffeeScript is not a bad idea for wordpress themes if you are familiar with them.
Not to be critical of your idea, but Orkut the social network from Google had this as an inbuilt feature from start. So my take is that you have done a good job of turning an idea into a live product. So definitely try marketing it, but if it doesnt pan out, dont lose heart since this is just the beginning !
Intially we are thinking of a web ui to control the filtering rules though Sieve as a mail filtering language might work with some modifications like envelope sender/recipient based filtering and filtering by attachment names. I guess we have to wait and see what kind of power users would want.
Sieve/other mail server filtering implementations currently only target incoming mails, so I would be interested in knowing how you manage outgoing mail filtering if at all ?
From your emphasis on "a mailserver I control" I guess you are leaning towards the in premise version if you ever need this.
About the logo, as you guessed correctly it was a quick selection to get up and running and not the final version !
A hosted version would be preferrable for google apps and other cloud based mail solutions.
But an in premise version is easier due to no need for ip reputation, queue management, server cpu and ram resources and also helps the customer to be in control.
A pretty awesome read. Though peppered with references to Indian culture. For ex, Marwaris - http://en.wikipedia.org/wiki/Marwaris If you are curious about some other things, I can probably chime in !
reply