This approach makes a lot of sense. Advertising is a marketplace and this is a great way to bootstrap advertising inventory. Its inevitable they will allow advertisers to manage ad spend directly through OpenAI but right now the product is too new to capture meaningful ad budget. This way they can begin testing delivery and develop proof points around ROI and build towards larger ad spend directly.
> Being able to tag chats with keywords would be nice. Being able to pull chats into docs easily would be nice. Being able to pull chats into more than one doc -- not just move, but tag/reference/copy. Global tags (with ACLs) as well as team and personal tags (also with ACLs) would be fantastic. Don't forget read and access ACLs, not just write ACLs.
Tagging is another organizational feature that is on our roadmap and has always made sense to me. Right now our organizational model is primarily hierarchical which has obvious limitations.
RE: email integration - We have a pretty robust email integration right now. Neville was always insistent that we shouldn't force people into the app to have a conversation, especially for one-off collaborators who get looped into a chat. They can stay blissfully ignorant of the fact that the conversation is actually happening on emdash if it suits them.
Thanks for the advice. One challenge for us will be how to price-in token based costs, e.g. downstream GPT services. There was an interesting post earlier today on HN related to this https://news.ycombinator.com/item?id=43186032 which recommended progressive pricing, which I thought was really interesting. On the other hand, the marginal cost of these services is being aggressively driven down by the big players so it may ultimately be safe to provide a fixed cost subscription model.
This is in the works. We have a prototype integration with Github that supports the deep search use case you mentioned. My favorite anecdote from this was a few weeks ago I was revisiting some work on transactional support in our controller framework and asked assistant "A few months ago I was working on transaction support and had to revert my change. Can you remind me what happened?" and it spit back my original PR, the reversion, and a deep link into the standup video meeting where we discussed the issue. For me, that was the magic moment where I knew this could be something much more than just a chat client.
This is good feedback, thanks. We packed a lot into the product so far and could have spent more time focusing the media assets to distill things better.
Early adopters range in size from 2 people to ~20. As you said, the Catch-22 for larger teams usually have established tool stacks so the (operational) switching cost is prohibitive.
FWIW we are a team of 5 and already find the feature set useful (we're biased, of course). I expect that ~5 is the threshold the organizational and search features become invaluable.
Thanks! One of the benefits of dogfooding our product everyday is that we invest a lot in working out the everyday kinks in addition to the marquee features.
I should introduce the rest of the crew. We're a team of builders who have worked together for the better part of the last decade. Neville and I were early engineers on Facebook Ads. Neville later founded Rimeto, which was acquired by Slack. Fred has held various roles driving growth and was an early employee at Facebook, Doordash, and Rimeto. Nick jumped into startups right out of college, joining Rimeto and now diving back in with us at emdash.
In particular, I appreciate that you assign value to the consequences and not the decision itself. Anytime junior engineers on my team would complain about "shitty code" I'd assure them that someone would be complaining about their code in a few years.
Having the context or, better yet, responsibility for the past decisions is great for developing a pragmatic approach to software design AND empathy for other software engineers.
emdash | Bay Area | Hybrid | Full-time | Senior Frontend & Infra Engineer | https://emdash.io
We’re looking for engineers to join our small but mighty team at emdash to build the next generation collaboration stack, starting with chat & video.
This is a very early-stage opportunity, meaning you’ll have a foundational role in shaping our product, technology, and company culture. We already have daily active customers (including ourselves) but we are just starting to scratch the surface of what emdash can be.
Founders have a long history working together and solid engineering & management experience from FB, Square, Slack, and their previous startup Rimeto (acquired by Slack).
Check out what we’ve built so far at http://emdash.io and help us figure out the future.
if you work in palo alto then its roughly 40 miles from the city, 80miles roundtrip. assuming 30mpg, 2 2/3 gallons * $4/gallon > $10 in gas. + saving time. if the shuttle ran regularly enough and was comparable in time, then i think $10-$15 roundtrip is reasonable.
That phrasing is a bit loaded. I'm an engineer on Facebook ads (I actually work with Paul, he's sitting right behind me. hi paul) and as much as people want to demonize ads, they do create real value for the businesses that use them and the users that click on them. We never think in terms of "get users to click". If we wanted to do that, we could make the ads bigger, flashier. But we don't because a good user experience is our prime directive, even for ads. And yes, there is a lot of room for improvement. zuck reminds of this regularly.
As I see it I'm building a tool that lets people promote their cause, their business, their band. The fact that they are paying for it is only because there is contention for that space.
First things first, you need to chill the f*ck out. You're 20 years old. You've only accomplished a small fraction of your life's mistakes, you have plenty more to look forward to.
Next, get a job. It sounds like your life needs some structure and distraction from your own thoughts. I'm not suggesting this job should be your life's purpose, just enough to give you something to focus on besides yourself.