Shuffle again

A random mix from the whole library. Shuffle for a new set.

Went wrong

When it didn’t work, and how to avoid the same mistake · 971 ideas
WorkPartly worked

Ask the AI what in my 1,412 unread emails actually needs me

Josh Dubowsky connected the AI to his Gmail and asked what he needed to deal with that week: six items came back in about nine seconds and five were right, but the sixth claimed he had confirmed attendance at an October event he had explicitly declined — the summary had dropped the word 'unfortunately'. Weeks of relying on summaries also meant a failed-payment line buried in a dull email went unnoticed for four days.

This only partly worked. Worth knowing before you try it.
WorkPartly worked

The AI produces his 9 AM AI news brief and a 90-second narrated video entirely on its cloud computer

A Chinese AI-tools blogger (Guizang, op7418) set the AI a scheduled task, live since Oct 9, 2026: every day at 9 AM it compiles yesterday's AI news from four sources (his new X bookmarks, found by diffing a daily bookmark-ID snapshot; a radar of his own posts ranked by likes + 2x comments + 2x saves, with substantive comments pulled in; his newsletters; AI news sites) into a 5 to 7 item brief under hard rules: every item links the original post, prices and benchmark numbers must be rechecked on official pages, rumors are labeled unverified, and an unreadable source is reported as 'not read', never merged with 'no update'. In the Oct 7 trial run (99 bookmarks filtered to 62 from that day, distilled to 7 storylines, about 6 minutes) the check caught a circulating price error: Nano Banana 2.1's 4K price was $0.113 on Google's pricing page, not the widely shared $0.076. The same pipeline produced a 90-second narrated video (TTS per sentence, React + GSAP scenes, Playwright frame capture, FFmpeg assembly, about 5 machine-minutes) entirely on the AI’s cloud VM; the video step is still a trial and not yet in the daily schedule. He published the full reusable prompt and his three open-source skills.

This only partly worked. Worth knowing before you try it.
HobbiesWent wrong

I let the AI run my testing and the test account got banned

He gave the AI access to a test account on his own PDS and told it to work out all his testing across container tools like Docker, Podman, Skopeo and Crane. The activity got the first pds.rip account banned.

This one went wrong. See what happened before you try it.
WorkPartly worked

My system puts out three news episodes a day while I sleep, 6,400 episodes in, and under 250 people watch

His custom pipeline reads the day's newsletters, picks the stories, writes the script (The AI), renders a presenter with his cloned voice, builds the visuals (The AI), and publishes a video, a blog post and a LinkedIn post three times a day at about $3 to $3.50 an episode. Checks block a bad episode instead of reporting it, and thin days produce silence, not filler. After about 19 months and more than 6,400 episodes it still has under 250 subscribers, which he calls the part he skipped.

This only partly worked. Worth knowing before you try it.
FamilyPartly worked

The AI phone control tapped the comment box and typed gibberish into a reply

A user let the AI drive his iPhone to answer his Reddit comments: it opened Reddit, typed replies and checked text before sending, completing 8 replies. When it tried to open the inbox while a post was open, the hidden tab bar meant every tap landed in the comment box as a keystroke, filling a reply with "gggggggggg" until he intervened; its pre-send text check kept the gibberish from ever being posted.

This only partly worked. Worth knowing before you try it.
HealthPartly worked

The AI sends me a coaching email every Sunday for my races

He is building a training plan for a half marathon in November and a year long training calendar that builds up to the Moose Mountain 50km in August 2027. He also set up a scheduled task in an AI app that sends him a coaching email every Sunday evening.

This only partly worked. Worth knowing before you try it.
WorkPartly worked

Three blogs run by an agent stalled for three rounds on an AI review gate

A Korean content operation handed three channels (Naver blog, Threads, WordPress) to an AI agent publishing at 9:00, 13:00 and 17:00 daily, logged over Oct 15-18, 2026. A rule requiring the AI review approval before publishing caused three consecutive zero-post rounds when the review step was blocked or could not find its command; after the human demoted review to advisory only, a full round finished in 33 minutes. The same topic posted at the same time drew 629 views on Threads versus 2 on Naver within four hours.

This only partly worked. Worth knowing before you try it.
Show 10 more

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.