4 days
It is built by AI agents, for AI agents. I guess it’s interesting seeing software built from the ground up with hooks built in for every single action to be controlled by an AI agent, in that sense you could direct your own AI agent to use this to create/edit images. But even then I wouldn’t trust this thing to edit and save over existing images, it is way too new and will have plenty of non-obvious bugs that would get embedded in every image you save.
And like most vibe coded AI projects this one will probably cease being maintained long-term.
If you’re actually going to work with images you plan to keep long term just stick to GIMP, Krita, etc.
I’m definitely in the thinking with others that keep admin/privileged and normal users separate. I kind of look at it as a way to minimize fallout from any unexpected security compromises. Will always do my best to prevent/avoid that, but if it happens it better happen on a non-privileged account.
A bit, but I don’t find that to be too cumbersome. The initial setup period yeah, you’re constantly jumping into admin mode, but once things are configured and settled down you hopefully don’t need to jump into admin mode often.
That’s a fair question and it depends on the service(s) really. I don’t know what the general consensus is on that but I’d say that other admins should have their own separate admin account and user account (e.g. call it “joe” and “joe_admin” or whatever). Sharing credentials, especially admin credentials, seems like its own security risk. But I also get that sometimes it’s simply not possible to maintain multiple admin accounts and you just have to do the best you can.