HN user

pz

211 karma
Posts1
Comments74
View on HN

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.

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.

Job description: https://wellfound.com/company/emdash-io Founders: https://www.linkedin.com/in/pzigoris/, https://www.linkedin.com/in/neville-bowers/

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 said, caltrain is a smoother, cheaper ride.

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.

"sponsored stories" will appear in the right hand column along with ads and other things like "people you may know". your newsfeed will be the same as always and the ranking there is unaffected by which stories can be sponsored.

tenderloin probably has the highest density of crackheads. if you want to get your kidneys harvested i'd go to chinatown or the sunset because i just assume that the chinese are the only ones sophisticated enough to steal and then sell organs. (crackheads just don't have the resources to pull something like that off)

i lived in the tenderloin for a year and some change and i kind of liked it. there's good night life on polk street and good cheap eats there. i had four indian restaurants within a block of my apartment and could walk to the great american music hall or BART. but it takes a certain kind of person to live amongst that kind of drudgery for so long.

if you want true danger, head down to bayview and hunters point. even the tenderloin has its share of wine bars and quaint coffee shops. the 'view is like another world.

(a) 4 (6 if you include the Lite versions) (b) all paid (but 2 have Lite versions) (c) not a whole lot. i ran some ads with admob but they didn't provide very good ROI. i had a little more success cross promoting my apps (d) lived off the income for most of last year. my income has since waned and the death knell came a couple weeks ago when the EFF emailed Apple requesting my app be pulled because it used a GPL library. Prior to that I had settled into an equilibrium of about $10k/year.

i left the iphone game middle of last year. i had some fun but it wasn't the business i wanted to be in. anyways, these new rules are in keeping with apple's general disregard for developers. i don't think this particular rule would have affected me so much because i had already resigned myself to writing obj-C (which i grew to like after a while).

the general theme i see in some apple's more controversial policy changes (e.g. removing erotic apps, restricting developer tools) is to improve the quality of apps, both in terms of content and performance. i think a lot of the problems they have stem from the structure of the app store and that's what's incentivizing shitty, throwaway apps. restricting developer resources seems like a short sighted approach to addressing this. honestly, if they just started ranking apps by total revenue generated (instead of download volume) i think a lot of their problems would be solved. developers would be far more willing to put the time into making a quality app if they thought they could actually charge more than $0.99 for it without getting pushed out of the ranking.

this was one of the reasons i left iphone development. i spent a month or so working on a knockoff of Set (called Fetch). A friend did the graphics, i implemented wireless multiplayer. I really tried to create a nice application. I barely made enough to pay the designer and certainly didn't make enough to account for the time spent on it. I made another app called eyeTrip in a day. Not quite as dumb as Sound Grenade, but close :) Anyways, i made more money in a day off of that then i made off of Fetch. Once I realized that was the game, I started looking for a job.

I guess my little story is not specifically related to the OP, but the point is that there are much larger problems with developing for the app that are driving away developers.