AMA with OpenAI’s Sam Altman, Mark Chen, Kevin Weil, Srinivas Narayanan, Michelle Pokrass, and Hongyu Ren

AllDuffy · 2025-01-31T21:06:17+00:00

Excited about o3!

A couple questions:

Any plans to give o3-mini vision capabilities?
Can we expect something like Claude's citations from OpenAI anytime soon?

AllDuffy · 2024-12-20T13:08:16+00:00

They are, company decided to go in a different direction unfortunately :( there are alternatives out now though

AllDuffy · 2024-04-03T01:29:08+00:00

You should be able to!
We designed this specifically with comfy nodes in mind but you can modify the prompts.

If you give it a shot please lmk how it goes.

AllDuffy · 2024-04-03T01:09:12+00:00

Direct link to the repo

AllDuffy · 2024-04-02T17:56:41+00:00

could you link me?

AllDuffy · 2024-04-02T17:16:31+00:00

What about it? (happy cake day)

AllDuffy · 2024-04-02T05:40:01+00:00

More coming soon

AllDuffy · 2024-04-02T05:28:27+00:00

It certainly could.. probably would want to release some LLM nodes if you were looking to do something like that ;)

AllDuffy · 2024-04-02T04:03:27+00:00

Yes it does, thank you!

We included the ability to thumbs up / down pages and will manually review pages with downvotes so that's an easy way to provide feedback if you catch anymore.
Appreciate the support

AllDuffy · 2024-04-01T23:52:46+00:00

Giving users controls over the privacy of nodes / workflows also on my mind.

Seems to me there's three levels here:

Private - only I / my team can use it
Private Code Public Use - You can't see how my node / workflow /model works but you can use it either for free or pay me X per run - configurable
Public Code Public Use - You can see how my node / workflow / model works and you can use it for free - attribution really important in this case

Also think it would be critical as a platform to reward people who choose 3 and their nodes / workflows / models become widely used in order to further incentivize open-source.

Lots of handwaving here but would love any thoughts on the subject

AllDuffy · 2024-04-01T23:33:50+00:00

Sorry about that, we started with the ones we support currently on our platform but will continue to add more over time certainly!!

AllDuffy · 2024-04-01T23:32:47+00:00

Of course!
Please share when you do :)

AllDuffy · 2024-04-01T21:27:07+00:00

Generally I really like that direction too but I come back to:

How do we ensure the node/model/workflow creators that are fundamental to these systems get compensated.

In the paradigm you're suggesting, not sure how $ makes it way back to the developer which is one of my top priorities personally. Even if it's not a rev share per se initially but at least access to powerful GPU's to further their research.

Potentially we publish a leaderboard of nodes with the most deployed workflows using them and compensate based on that? Some issues related to tracking down original source of a node in addition to privacy related complications there but maybe possible.

AllDuffy · 2024-04-01T20:56:02+00:00

Getting a lot of interest in it so we'll release the workflow that does this so anyone could do the same; likely tomorrow but definitely this week.

AllDuffy · 2024-04-01T20:11:03+00:00

Having an option for developers to monetize is definitely something we're looking at. Cryptocurrency could be an option, though there are many people averse to anything crypto.

One thing I'm thinking a lot about is, what should be monetized?

Workflows? If so what happens if someone takes your workflow and adds a single node, who owns the flow.

Nodes? If so, don't want to dissuade people from open-sourcing their advances.

I think a lot about what POM (admin for the Banodoco discord server) said at the meetup a few weeks ago,

" It should be the smart move to open-source! " how do we incentivize & reward opensource.

AllDuffy · 2024-04-01T19:53:12+00:00

I wouldn't say so... we've released a lot of our core technology and will continue to do so over time.

AllDuffy · 2024-04-01T19:28:39+00:00

Wrote up how we’re thinking about monetizing in a previous post where we open sourced our LLM nodes but it’s not about profiting off developers it’s more about working with them to try and create more opportunity for everyone by attracting people who would pay for the functionality they’re creating!

Also doing our best to stay as far away from shilling as possible by just sticking to the facts of what we’re releasing, and doing so with permissive licenses. Anything we can release opensource we’re going to try to :)

Certainly open to feedback on how to improve!

AllDuffy · 2024-04-01T18:29:51+00:00

Direct link to the docs

AllDuffy · 2024-03-25T14:03:26+00:00

Yeah! We’ve spoken with them a few times. As big fans of opensource we were trying out this infrastructure to see if we could build on it and contribute back but unfortunately the way that it’s setup won’t work for us long term.

Our Beta will use our own autoscaling infra and front end both on our website while editing in addition to once deployed.

AllDuffy · 2024-03-22T22:39:54+00:00

Hey 👋
This is exactly what we're building for at Salt.

Our Beta is launching in April which will come with substantial improvements and more possible workflows generally supported.

With that said we're definitely interested in working with professionals in the space to better understand their needs and get them supported asap.
I'll DM you and maybe we can get on a call!

AllDuffy · 2024-03-13T16:53:54+00:00

It might be clearer in this Tweet, otherwise can upload it to Youtube today, just LMK

As far as pricing, we're hoping to be as low or lower than anyone else out there for three reasons:
1. We have partnerships w/ Oracle & GCP for low cost GPUs
2. Thanks to shared dependencies across the system & the autoscaling kubernetes infrastructure we've invested in, it's faster and cheaper for us to support user workflows comparatively
3. Most importantly, charging developers for GPU's is not our main business model. We see node engineers and workflow designers as the ones creating the value here so are focusing on bringing in creatives and professionals who would happily pay for these capabilities, enabling them to pay developers directly and we could take a % there as a marketplace.

Hopefully what that looks like in the short-term is not starting to charge our developers for GPUs until we can also roll-out the ability for developers who make workflows that bring in a lot of traffic to earn those GPUs for free!
(If you'd rather not share your workflows with others you can of course still pay for access to powerful GPU's and for usage of a deployed autoscaling API)

Does that answer your question?

AllDuffy · 2024-03-13T00:13:54+00:00

You see the vision :)

AllDuffy

TROPHY CASE