To clarify, publish_stream is a superset permission that includes publish_actions. That's why you're not seeing it.
While I agree with you that it removes a step in the funnel, we still need read_stream to provide our advertised service, that is pulling videos that your friends post on Facebook. read_stream is also an extended permission so we can't get around that additional screen anyway.
However, I've read that less permissions means a higher conversion rate so we may experiment with removing publish_stream and only asking for read_stream + publish_actions and we'll see what happens.
I'm one of the developers at mixy.tv -- we are indeed asking for publish_actions and using open graph to publish video watches and likes. However, we use publish_stream for adding a video because we found that it shows up more often in the news feed as opposed to being shown in the ticker on the right of the FB home page.
I think you have a good point though about publish_stream being in the extended permission screen, however. I know you mentioned working for a competitor, so you don't have to answer this if you don't want to, but -- have you guys seen better conversion rates for signups or better share rates by using Open Graph actions explicitly as opposed to a combination of publish_stream and publish_actions?
Be honest about your skills. Don't try to over-inflate your skillset, the interviewer will be able to tell.
Try to make mention of the fact that you are loving every moment of the learning process that you started a few months ago. Generally, people who consider hiring novice programmers are looking to help grow that person into a lean, mean coding machine, so if you appeal to that fact and tell them you're in it to learn, they'll love it and you should have a higher chance of getting the job.
Otherwise if the company is looking for someone with the know-how from the get-go, your only chance would be to nail the technical aspects of the interview, so study your ass off!
Launched http://mixy.tv to the public last week. It's a video aggregation site that pulls video content from different sources, including your Facebook and Twitter accounts.
While I agree with you that it removes a step in the funnel, we still need read_stream to provide our advertised service, that is pulling videos that your friends post on Facebook. read_stream is also an extended permission so we can't get around that additional screen anyway.
However, I've read that less permissions means a higher conversion rate so we may experiment with removing publish_stream and only asking for read_stream + publish_actions and we'll see what happens.
Thanks for all your input!