HN user
tm11zz
Very nice results! I recently created this SVG CLI agent with a similar idea: https://github.com/svgnew/Saul
We run a fuzzing fleet of 1,000 dedicated CPU cores 24/7.
that a lot
Nice job!
I've been working on a similar project @ https://vectorart.ai
There are lots of interesting problems to solve and I feel SVGs have been somewhat underrepresented in the AI boom. But that's beginning to change...
Re Edit: great job on hyvector! are you open for some sort of collaboration? any way I can contact you to discuss?
Great feedback, thanks!
Working on an AI to generate SVG vector images.
SVGs are awesome and currently unrepresented in the diffusion-based model landscape. We have something that produces pretty great results and we're working on the next version which should be even better.
I'm working on a service that generates SVG vector graphics using generative AI.
This is something current models struggle with but I've always wanted high quality vector graphics for my projects.
This is a really useful mindset as a programmer, but backfires in real-life as it makes you an anxious person.
Clearly this is another example of Sora in action
hey, what's down for you?
updated, what do you think?
ouch
Thanks everyone for your feedback and support. I've been adding GPUs as fast as I can to meet demand and some of the earlier performance issues should be much improved.
Obligatory mention of "Consider the lobster" by David Foster Wallace
https://web.archive.org/web/20230325034108/https://www.colum...
Thanks for surfacing this. I'll work to improve this to reflect reality - your prompts and images are private and owned by you.
Should be fixed now!
Fixed, thanks for reporting.
That's the dream, unfortunately with the costs attached it isn't currently possible.
Probably timed this announcement with a new book coming out on the topic
curl is the ffmpeg of url fetching
Inside the image for those interested: https://contains.dev/hectormolinero/qemu-win2000
Great pointer, thanks for that. Now I'm trying to piece together what happened to that project :)
The plan is to integrate with the different registries to support private images and in parallel to expand what contains.dev can do for individual images.
Amazing! that's great to hear.
Generally we process the Docker images and extract useful information and organize the data in a consumable way.
Some information is obtained from the Docker Hub API, but most of the data comes from the registries and images themselves.
Thank you! Signing up allows you to view your own private images.
Thanks! that's a great idea.
We're initially focusing on private images available on one of the major registries (AWS, GCP, Azure, Docker Hub, etc.). But on-premise is definitely one of the options we want to offer in the future.
We created contains.dev to allow quick exploring of Docker images, their contents, layers, etc.
To get any sort of info about an image we found ourselves pulling them locally and spending lots of time with CLI tools and manual layer exploration.
Much like GitHub is a great way to explore different repositories quickly, we're hoping contains.dev is a step in that direction.