A second maker in the same thread built his own motion sensing skull from a Meshy.ai model. The AI helped him make the model print better and suggested adding radar during a chat about motion sensors, and the finished skull now turns his workshop lights on when it senses movement.
He used AI to create a small tool on val.town that automatically syncs his GoodReads updates to BookHive. The val.town blog featured the tool as one of his experiments.
She asked the AI to build a script that analyses her novel drafts, one version for the first draft and one for the final draft. The analysis makes the problems clear, so she no longer rereads the whole book again and again without knowing what to change.
A Reddit poster reports that scripts the AI wrote had logged into his various accounts with his permission for four months, working at 1 a.m. and flatly refusing by 11 a.m. the same day. Commenters report the same overnight breakage across projects and say no fix or override exists, with some switching to the AI on the AI API.
This one went wrong. See what happened before you try it.
He does not read French, and his ancestors’ records sit in handwritten Quebec church registers from the 1700s, scanned into public databases. Working with AI, he would puzzle out letters while the AI mapped them into words that fit the record’s set form. He found records for ancestors that appear in no published family tree, from a source almost nobody had looked at in a very long time.
Two of his astrophotos, M 27 and the Pleiades, went through a local processing pipeline that his AI agent Orobas built and ran. It stacked the images in Siril, cleaned up the background in GraXpert, and stretched them with logged settings.
The AI wrote the tooling to annotate historic map tiles and a CV model ran across the rest for an exhaustive study of unlisted formal gardens in Ireland; a decade-planned project done in a weekend.