Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
neilxm
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
How to Build a NextJS Blog Using Obsidian as the CMS
(neilmathew.co)
2 points
by
neilxm
3y ago
|
0 comments
2.
▲
by
neilxm
3y ago
Yes! That's where our heads are at as well. The reality with a lot of multimodal / image proc style code is that it's never truly serverless - image manipulation in node.js is tragically bad so you always end up needing pytho
3.
▲
by
neilxm
3y ago
Thanks! We'll ponder over this one :)
4.
▲
by
neilxm
3y ago
YEP! If you've used blender you'll notice the parallels with shader nodes :)
5.
▲
by
neilxm
3y ago
It's a combination of things. The idea is that you can build workflows that chain functionality from ai models, as well as lower level image processing tasks. For lower level tasks we use the usual suspects - PIL, ImageMagik, OpenCV
6.
▲
by
neilxm
3y ago
We're working on shareable graphs and premade recipes! I actually started sharing a few on our blog - here's an example: https://blog.mlblocks.com/p/auto-generate-banner-images-for-... haha, the tilt animatio
7.
▲
by
neilxm
3y ago
Thats true. We started off with a base set of blocks but i think the real utility will come in the easy orchestration and api end point building. We're pushing in the direction of apis and shareable workflows so hopefully some of these
8.
▲
by
neilxm
3y ago
We started this to solve bulk processing issues we had when building a previous eCommerce tool so I 100% know what you mean. We're adding API support soon and we'll add some examples of how to connect this to Shopify or something
9.
▲
by
neilxm
3y ago
Thank you!!
10.
▲
by
neilxm
3y ago
Thanks you beat me to it :) That being said, you're not wrong. It's definitely inspired by ComfyUI. But, with much simpler abstractions, much broader utility and extensions like building a user front end coming up shortly
11.
▲
by
neilxm
3y ago
To add to pj's comment - We are adding more blocks constantly. We're also considering allowing the community to push their own blocks using an open api schema.
12.
▲
by
neilxm
3y ago
Oh yea I know what you mean. There are several parallels here with shader nodes for sure. We've been thinking about a voyager/agent-style approach where an agent can start to learn "skills" where skills are individual bl
13.
▲
by
neilxm
3y ago
Nice! Sharing workflows is coming up in approximately 2 sprints. We're working on 2 flavors of sharing. The first is sharing the workflow directly and letting someone copy it for the dev community. The more interesting option though is
14.
▲
Show HN: ML Blocks – Deploy multimodal AI workflows without code
(mlblocks.com)
112 points
by
neilxm
3y ago
|
32 comments
15.
▲
Show HN: Zapier-Like Automations for AI Image Processing
(mlblocks.com)
2 points
by
neilxm
3y ago
|
1 comments
16.
▲
by
neilxm
3y ago
Good ideas! Thanks! I'm definitely going to implement the style picking next
17.
▲
by
neilxm
3y ago
Currently there's no way to steer it, but I'm thinking about ways I can allow steering the image gen. Maybe just showing the prompt open ai spits out so you can edit it, but I wonder if there are better ways to allow control
18.
▲
by
neilxm
3y ago
BannerGPT is an AI agent that can auto-generate banner images for any blog post. The premise is pretty simple. You paste your article into BannerGPT, it analyzes the text and generates a banner image that can complement your article. Under
19.
▲
Show HN: Instant Banner Images for Any Blog Post Using GPT3.5 and SDXL
(bannergpt.dabble.so)
3 points
by
neilxm
3y ago
|
3 comments
20.
▲
Show HN: An AI agent that Auto-generates Illustrations for any Blog Post
(bannergpt.dabble.so)
3 points
by
neilxm
3y ago
|
3 comments
21.
▲
by
neilxm
3y ago
BannerGPT is an AI agent that can auto-generate banner images for any blog post. The premise is pretty simple. You paste your article into BannerGPT, it analyzes the text and generates a banner image that can complement your article. Under
22.
▲
by
neilxm
3y ago
yea true. some trade offs. i'm going to look into consolidating everything into just the nextjs piece.
23.
▲
by
neilxm
3y ago
awesome ideas! the configurability and flexibility of 3D models is a huge advantage over a pure 2D approach these scenarios.
24.
▲
by
neilxm
3y ago
yea for sure. i guess i'd like this to be something usable on mobile as well. but directionally you're right. there's a lot to be gained from optimizing for local compute in many applications. something to look into.
25.
▲
by
neilxm
3y ago
Yea! Shadows on the item or shadows propogated back onto the scene
26.
▲
by
neilxm
3y ago
That’s the idea for next steps. Basically if you generate a backdrop and then estimate light direction you can inverse render that onto the 3d model given all the depth information you get for free from the model
27.
▲
by
neilxm
3y ago
So the api used for inpainting is very easily swappable to a local instance. But when you say consumer hardware, I think you might be overestimating how capable most people’s computing setups are.
28.
▲
by
neilxm
3y ago
Yes and no. So I did it because I honestly get annoyed with pixel operations in node js. The same thing in Python with the pillow library achieves the same things in quarter the lines of code as you would need in something like sharp in nod
29.
▲
by
neilxm
3y ago
Hah. Yep!
30.
▲
by
neilxm
3y ago
bingo
More ›