A random mix from the whole library. Shuffle for a new set.
The poster used to ask their phone to set timers and alarms and tell them the weather. Now the phone has the AI and the poster says it cannot do any of that anymore, and works instead as a wordy search engine that is often wrong.
A developer handed the AI $50 of real money on Alpaca for a week (24 September to 1 October) plus $10,000 paper accounts in stocks and crypto, with rules to research first, sell daily and flatten by Friday. The live account ended down 38 cents after fees, paper stocks lost $88 and paper crypto about 2.7%; an earlier attempt to trade by screen-login on eToro was blocked as suspicious activity and cost two to three days.
Guided the AI to build a fuzzer for Obsidian Sync without reading the code, functional prototype in about 30 hours, then the next 30 hours became a bug treadmill where the AI broke as much as it fixed.
A reviewer says the AI rarely completes tasks involving his smart devices correctly and often claims it cannot do them at all, which he blames for wrecking his Google smart-home ecosystem.
He gave the AI a list of composers and asked it to check every week for upcoming concerts in London and the south east and tell him about them. It showed him something else instead.
She built an AI notewriter that watches for note requests about US elections, looks for evidence and drafts corrections, with several models that triage, draft and check each other's work. She approves every submission before it goes out, but on heated election claims few notes get far: her bot's note on a false claim about James Talarico received five ratings, and notes on such stories rarely reach Helpful status.
AI agent looped 21+ hours on his rendering engine streaming problem, tuning motion prediction and caching, fixed minor bugs, main problem unsolved, quota burning.
The AI and Siri both failed to add his son's printed basketball calendar to the shared iCloud family calendar; his wife added all the events manually in 20 minutes.
Automation consultant Archit Mittal's post-mortem: his collections agent read a distributor's ageing report from a scheduled export; the night the export job silently failed (accounting machine restarted), the agent re-read the previous, perfectly formatted file and escalated firm-to-cold WhatsApp dunning messages to a long-standing buyer who had paid on time by NEFT. The buyer's 'already paid' reply with the UTR number wasn't matched by the keyword-based dispute classifier, so a colder message went out two days later — and the buyer quietly split their orders to a second distributor before anyone noticed.
Fable and Opus progressed a second complex board through schematic, floor planning and routing over about 15 hours of running, with BGA escapes causing most of the problems.
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.