Archive
Discover and discuss technology tools
Explore the Tiscuss archive by category or keyword, then jump into conversations around what matters most.
Hormone Lab Results Interpreter: AI Tool for Men's Health
Hormone Lab Results Interpreter: AI Tool for Men's Health Men's health is complex, and hormone levels play a crucial role in overall well being. Understanding h…
Trading System V2: AI's Role in Deterministic Execution
Thanks to the incredible feedback on my last post, I’m officially moving away from the "distributed veto" system (where 8 LLM agents argue until they agree to trade). For v2, I am implementing a strict State Machine using a deterministic runtime (llm-nano-vm). The new rule is simple: Python owns the math and the execution contract. The LLM only interprets the context. I've sketched out a 5-module architecture, but before I start coding the new Python feature extractors, I want to sanity-check the exact roles I’m giving to the AI. Here is the blueprint: 1. The HTF Agent (Higher Timeframe - D1/H4) Python: Extracts structural levels, BOS/CHoCH, and premium/discount zones. LLM Role: Reads this hard data to determine the institutional narrative and select the most relevant Draw on Liquidity (DOL). 2. The Structure Agent (H1) Python: Identifies all valid Order Blocks (OB) and Fair Value Gaps (FVG) with displacement. LLM Role: Selects the highest-probability Point of Interest (POI) based on the HTF Agent's narrative. 3. The Trigger Agent (M15/M5) 100% Python (NO LLM): Purely deterministic. It checks for liquidity sweeps and LTF CHoCH inside the selected POI. 4. The Context Agent LLM Role: Cross-references active killzones, news blackouts, and currency correlations to either greenlight or veto the setup. 5. The Risk Agent 100% Python (NO LLM): Calculates Entry, SL, TP, Expected Value (EV), and position sizing. The state machine will only transition to EXECUTING if the deterministic Trigger and Risk modules say yes. The LLMs are basically just "context providers" for the state machine. My questions for the quants/architects here: Does this division of labor make sense? Am I giving the LLMs too much or too little responsibility in step 1 and 2? By making the Trigger layer (M15/M5) 100% deterministic, am I losing the core advantage of having an AI, or is this the standard way to avoid execution paralysis? Would you merge the HTF and Structure agents to reduce token constraints/hallucinations, or is separating them better for debugging? Would love to hear your thoughts before I dive into the codebase.
AI Tool Comparison: Claude, GPT-4, and Gemini for Article Summarizatio
I've been building a product around AI-powered reading (more on that later) and wanted to share findings on summarization quality across major LLMs. Tested with 50 articles across news, research papers, blog posts, and technical docs: **Claude (Sonnet/Haiku):** \- Best at preserving nuance and avoiding oversimplification \- Strongest at academic content \- Excellent for "explain this without losing the point" **GPT-4:** \- Fastest summaries, often most concise \- Sometimes drops important context \- Good for news, weaker on academic **Gemini:** \- Strongest source citations \- Tends to add information not in the original \- Good for factual but careful with creative content Most surprising finding: **bias detection accuracy**. Claude flagged loaded language and framing in 78% of test articles correctly. GPT 64%. Gemini 51%. Anyone else doing similar comparisons? Would love to hear what you're seeing
New Benchmark for Testing LLMs for Deterministic Outputs
New Benchmark for Evaluating Large Language Models for Deterministic Outputs In the rapidly evolving landscape of artificial intelligence, the evaluation of lar…
How Do Developers Correct AI LLMs When They Spread Misinformation?
I watched Last Week Tonight's piece on AI chatbots today, and it got me thinking about that old screenshot of a Google search in which Gemini recommends adding "1/8 cup of non-toxic glue" to pizza in order to make the cheese better stick to the slice. When something like this goes viral, I have to assume (though I could be wrong) that an employee at Google specifically goes out of their way to address that topic in particular. The image is a meme, of course, but I imagine Google wouldn't be keen to leave themselves open to liability if their LLM recommends that users consume glue. Does the developer "talk" to the LLM to correct it about that specific case? Do they compile specific information about (e.g.) pizza construction techniques and feed it that data to bring it to the forefront? Do their actions correct only the case in question, or do they make changes to the LLM that affects its accuracy more broadly (e.g. "teaching" the LLM to recognize that some Reddit comments are jokes)? On a more heavy note, the LWT piece includes several stories of chatbots encouraging users to self-harm. How does the process differ when developers are trying to prevent an LLM from giving that sort of response?
Waiting for LLMs? Play a Game with This AI Tool
Waiting for LLMs? Play a Game with This AI Tool In the fast paced world of technology, waiting for the latest large language models (LLMs) can be frustrating. F…
Preventing AI Model Collapse: The Need for Human-Generated Data
Im all for acceleration. I think the faster we hit AGI the better. but theres a bottleneck nobody here talks about enough-training data. right now we are quietly poisoning the well. More than half of online content is already synthetic. bots talking to bots, articles written by AI, reddit threads generated by LLMs. when the next generation of models trains on this they eat their own tail. model collapse is real. we saw it with image generators. Outputs get blander, weirder, less useful.we need a way to label or filter human-generated data. not because humans are better but because diversity prevents collapse. I know the standard solution sounds like a dystopian meme. biometric scanners, iris codes, hardware verification. and yeah maybe it is dystopian. but so is a dead internet where nothing can be trusted.Reddit CEO Steve Huffman put it simply recently - platforms need to know you're human without knowing your name. Face ID / Touch ID level stuff. im not saying that specific device is the answer. but the category of solution - proof of human that doesnt create a surveillance state - seems necessary if we want to keep scaling past the cliff.what do you think? Is proof-of-personhood just a regulatory speed bump, or is it infrastructure for the next generation of AI?curious where this sub lands.
Show HN: AI Prediction Market Analysis App with LLMs and Data APIs
Show HN: AI Prediction Market Analysis App with LLMs and Data APIs Discover the future of market analysis with our innovative AI Prediction Market Analysis App.…
QuickCompare by Trismik: Compare & Pick Best LLMs
Compare LLMs on your data, measure, and pick the best.
Arc Sentry: Advanced Prompt Injection Detector for LLMs
Been working on Arc Sentry, a whitebox prompt injection detector for self-hosted LLMs (Mistral, Llama, Qwen). Most detectors pattern-match on known attack phrases. Arc Sentry watches what the prompt does to the model’s internal representation instead, so it catches indirect, hypothetical, and roleplay-framed attacks that get through keyword filters. Benchmark on indirect/roleplay/technical prompts (40 OOD prompts): • Arc Sentry: Recall 0.80, F1 0.84 • OpenAI Moderation API: Recall 0.75, F1 0.86 • LlamaGuard 3 8B: Recall 0.55, F1 0.71 Arc Sentry has the highest recall — it catches more of the hard cases. Blocks before model.generate() is called. The lightweight pre-filter runs on CPU with no model access. pip install arc-sentry GitHub: https://github.com/9hannahnine-jpg/arc-sentry Happy to answer questions about how it works.