This is an interesting idea, and I'd love to see whether people come up with interesting stories/imaginations with this, but I feel very strongly pushed to engage before I've even properly explored the platform to see the potential. Like, all the stories seem to have their images locked, I assume until I make an account. Then there's also this mention of a pro subscription and some deal for the. firlst N subscribers. I'm not even sure yet if this a platform that's worth enough for me to make an account, let alone pay money for. I understand that image generation isn't cheap so you need to think about monetization early, but I suspect you'll need more ways for people to see the value of it without the commitment of even creating an account to have this become successful.
I can certainly believe that this is really an agent doing this, but I can't help that part of my brain is going "some guy i his parents' basement somewhere is trolling the hell out of us all right now."
This looks very neat indeed! Are there any plans to adding network limits? Like, you might want to avoid an agent running code that just requests a resource in a loop, or downloads massive amounts of data.
It came up for me and accepted a photo, but it has just been stuck in the "Don't go anywhere, it's almost ready" state for 10+ minutes.
No idea how long it is supposed to take. They can pull a 3D world out of thin air but they apparently can't vibe-code a progress bar...
Edit: Now it's saying "We'll notify you when it's ready, and you'll have 30 seconds to enter your world. You are 37th in the queue." Go to restroom, come back 1 minute later: "The time to enter your world ran out." Lame-o.
Bunny CDN (https://bunny.net) is great, HQ located in Ljubljana, Slovenia and also have great support which seems most faster and gives better responses than most others out there, but might just been my luck, YMMV.
>but was you or anyone you know affected by a DDoS?
Yes, all the damned time.
Some people must have experienced a completely different internet from the one I've had to run servers on over the years. I've had tiny, local sites for customers randomly get gigabytes of traffic per second for days. No rhyme or reason why. Try to run anything with a forum on it where people have strongly held beliefs, yea eventually you'll get a DDOS. Have a site where some global competitor can influence your sales by slowing traffic on important holidays... you can see where this is going. Heck, I've even worked at ISPs where we had to take particular IPs out of the DHCP pool and null route them because for some reason they were getting traffic blasted for weeks at a time.
While they do sale fear, it's not really an irrational one for those that have worked in the industry.
A lot of people here don't just run trivial hobby sites. They work for companies that actually have a real need for DDOS and WAF protection. Maybe you have no experience with that, but it is extremely common and even required for sites that require compliance certifications like SOC2.
Sorry I pressed downvote and cannot revert my press...
I had to set up CF for a small local business in a very small country that has ecommerce presence targeted mainly at local population. It just gets non-stop ongoing traffic a hosting provider cannot handle.
i'd personalloy love a quick video demo on the home screen, with someone walking through the experience of using the app; other than that, looks interesting;
I think more important than worrying about people treating an opaque value as structured data, is wondering _why_ they're doing so. In the case of this blog post, all they wanted to do was construct a URL, which required the integer database ID. Just make sure you expose what people need, so they don't need to go digging.
Other than that, I agree with what others are saying. If people rely on some undocumented aspect of your IDs, it's on them if that breaks.
Exposing what people need doesn’t guarantee that they won’t go digging. It is surprisingly common to discover that someone has come up with a hack that depends on implementation details to do something which you exposed directly and they just didn’t know about it.
The entire post is one big ad hominem. The entire premise is "these people's arguments don't matter because of who they are", which is a fallacy.
I don't care if you think that a broken clock is right twice a day, that competent, intelligent people aren't wrong all the time, or that people are sometimes able to look past their biases and call out the truth, but dismissing arguments for or against AI just because of who someone gets a paycheck from is wrong.
> If you ask for an endpoint to a CRUD API, it'll make one. If you ask for 5, it'll repeat the same code 5 times and modify it for the use case.
>
>A dev wouldn't do this, they would try to figure out the common parts of code, pull them out into helpers, and try to make as little duplicated code as possible.
>
>I feel like the AI has a strong bias towards adding things, and not removing them.
I suspect this is because an LLM doesn't build a mental model of the code base like a dev does. It can decide to look at certain files, and maybe you can improve this by putting a broad architecture overview of a system in an agents.md file, I don't have much experience with that.
But for now, I'm finding it most useful still think in terms of code architecture, and give it small steps that are part of that architecture, and then iterate based on your own review of AI generated code. I don't have the confidence in it to just let some agent plan, and then run for tens of minutes or even hours building out a feature. I want to be in the loop earlier to set the direction.
reply