标签：#ia

Good system. One addition that moved the needle for me: ​ I track "capacity conversion" -- when AI saves me 3 hours on a task what do those 3 hours actually become? ​ Most people save time with AI and then fill it with more busywork. The ROI only materializes when you deliberately redirect saved time toward higher-value activities. ​ I keep a simple log: "AI saved X hours on [task]. Redirected to [activity]. Value of redirected time: [$amount]." ​ After 6 months, my actual ROI was 4x higher than the "time saved" metric suggested because of where the saved time went. ​ submitted by /u/JaredSanborn [link] [留言]

When a platform started with total developer autonomy, teams felt overwhelmed and ended up solving the same problems in completely different ways. The company shifted to enablement over support, working together with teams intensively, and helping teams feel confident and capable, turning the right way into being the easiest way. By Ben Linders

Bluesky is launching a communities feature this year, according to its head of product.

Google DeepMind is funding research into the potential dangers of situations where millions of different AI agents interact with each other online. According to Rohin Shah, who directs the company’s AGI safety and alignment research, the mass-market arrival of agents that can carry out tasks without human oversight and follow instructions given to them by other…

A lot of discussion about Fable 5 has focused on the visible restrictions: cybersecurity, biology, certain chemistry. You hit a wall, you get a notification, you get redirected to Opus 4.8. That's frustrating, but at least it's honest. At least you know the model stepped back. Here's the part that's really disturbing, buried in a 319-page system card: There's a second category of restriction. For AI development and research work, Fable 5 doesn't redirect you. It doesn't notify you. It responds. It just delivers a deliberately weakened answer, and the system card describes this explicitly as "not visible to the user." Anthropic walked this back within 24 hours after fierce backlash. They apologized. "We made the wrong tradeoff." Good. But sit with what actually happened here, because the reversal is being treated as the end of the story when it's the beginning of a much harder problem. We now know three things we cannot unknow: Anthropic built this. They shipped it. And they only reversed it when the backlash was loud enough. The question isn't whether this specific invisible downgrade still exists. The question is what else might they be doing, in categories that don't generate the same backlash, that isn't disclosed in a document most people will never read anyway. This is a new kind of problem. And to understand why, you have to take a step back for a second. The pattern In January 2026, OpenAI announced that they would retire GPT-4o. Hundreds of thousands of daily users had built working relationships with that model over months: preferences it learned, corrections they made, communication styles that developed through hundreds of sessions. Gone. In February 2026, Gemini users found their chat histories had quietly vanished. No warning. No export. In April, Anthropic cut off Claude Pro and Max subscribers from using their subscriptions with third-party tools. Workflows that people depended on broke overnight. Each of these was framed differently. Model retirement

Every layer of AI solved the problem the last one left behind. The unsolved one: a shared, measurable standard for how to RUN intelligence — yours and the AI's, together. I spent 10+ years writing it down and it's falsifiable (pre-registered tests, failure lines locked before data). Asking for your strongest critiques Essay: https://joshmason573557.substack.com/p/colive-the-missing-standard-for-the submitted by /u/Useful-Ad-7895 [link] [留言]

I think it is but I'd just like to get some second opinions, especially from music creators. This is their spotify page https://open.spotify.com/artist/4dSJvPjnA1RU6KcngvaZ96 The artwork is definitely AI and there's no real composer name so some red flags there already. submitted by /u/WelderRound2925 [link] [留言]

submitted by /u/Tiny-Independent273 [link] [留言]

I'm really interested in trying to learn about this new concept of having a one central AI-powered database acting as a digital brain for your business, pulling in all of the various data sources and having one single source of truth. People like Nate B Jones talk about it and I really want to try to build something - but concious how wrong they can go. Are there any credible ones already build I can base off? Has anyone done this? submitted by /u/zascar [link] [留言]

PostgreSQL Partitioning for Multi-Tenant Audit Logs: Querying 100M Events Without Table Scans I'll be direct: if you're running a SaaS with compliance requirements and your audit_logs table is approaching 50M rows, you're three months away from pain. I've watched audit queries go from 200ms to 8 seconds in production at 2am because someone ran a "give me all logs for tenant X" report. Partitioning isn't optimization theater—it's table-stakes infrastructure. At CitizenApp, we store 9 months of audit logs across 50+ tenants. Without partitioning, a single compliance query would full-table scan 100M+ rows. With it, we hit the same data in <100ms. This post is exactly how we do it. Why Partitioning Matters (The Reality Check) Most developers treat audit_logs like any other table. You add an index on tenant_id and created_at , call it done, and move on. Then your compliance officer runs a query like: SELECT * FROM audit_logs WHERE tenant_id = 'acme-corp' AND created_at >= '2024-01-01' ORDER BY created_at DESC ; At 50M rows, even with a composite index, PostgreSQL has to: Index scan → finds millions of matching rows Random I/O all over the table Spill to disk if sorting is large Hope the OS cache is warm Partitioning solves this by eliminating the data you don't need from day one . Instead of scanning a 100GB table and filtering it down, PostgreSQL can skip entire partitions. A query against January 2024 data simply ignores partitions for February–December. I prefer partitioning because it's native PostgreSQL—no external caching layer, no read replicas, no Redis gymnastics. It's boring infrastructure that works. The Partitioning Strategy: Composite Partitioning (Range + List) I use a two-level partitioning scheme: Range partition by month ( created_at ) — keeps each partition to ~5–10GB List subpartition by tenant — ensures compliance queries are single-partition scans This is deliberately opinionated. You could do range-only, but then a multi-tenant query still scans the

I didn't set out to build a content API. I set out to stop copy-pasting. Every week, the same ritual: open a doc, stare at a blank page, write a headline, delete it, write it again. Multiply that by every client, every product page, every email drip campaign. I wasn't doing creative work — I was doing assembly-line work while pretending it was creative. PostAll started as a script I wrote to stop doing that. The API is what that script became after other developers asked if they could use it too. This guide walks you through integrating PostAll's API into your own workflow — authentication, the endpoints you'll actually use, real working code in both Python and Node.js, and the specific places things will break before they work. By the end, you'll have a functioning pipeline that generates formatted, CMS-ready content programmatically. What you'll build A script that takes a list of content briefs (keywords, tone, target length) and returns publish-ready content — with proper formatting, metadata, and error handling for the rate limits you'll hit in production. Here's the shape of what you're building: [ CSV of briefs ] → [ PostAll API ] → [ formatted content objects ] → [ your CMS / database ] The full working code for both languages is at the end of each section. I'll explain the interesting parts inline. Prerequisites A PostAll account with API access enabled (free tier works for this guide — rate limits noted below) Node.js 18+ or Python 3.10+ Basic familiarity with async/await in either language An HTTP client: axios or native fetch for Node, httpx for Python Step 1: Authentication PostAll uses API key authentication. Every request needs your key in the Authorization header. Get your key: Dashboard → Settings → API Keys → Generate New Key Store it as an environment variable. Never hardcode it. export PostAll_API_KEY = "postall_live_xxxxxxxxxxxxxxxxxxxx" Your key has two prefixes: postall_live_ for production, postall_test_ for the sandbox. The sandbox returns r

anthropic just released fable 5 two days ago and i haven’t had a chance to properly dig in yet for context it’s basically a public version of mythos, the model they’d been keeping locked behind project glasswing for select partners only. now it’s out for everyone on pro/max/team plans until june 22 for free, after that it’ll need usage credits from what i’ve read it’s supposed to be insane at long agentic tasks… like multi-hour sessions where it spins up sub-models, gathers data, writes and tests its own code. someone gave it one prompt to build a travel-time map and it went off on its own for hours and just… built it the one catch is it has hard safety blocks in areas like cybersecurity, bio, chem. falls back to opus 4.8 when it hits those but i want to hear from people actually using it right now. what’s the best thing you’ve noticed? and what feels overhyped or still rough? drop your experiments in the comments, genuinely curious submitted by /u/NewMuffin3926 [link] [留言]

Hi, I want to use AI to check my grade with the mark scheme and see what grade it would give me. Now, after doing this, would the assignment be flagged by an AI detector? submitted by /u/No-Witness1045 [link] [留言]

submitted by /u/ThereWas [link] [留言]

submitted by /u/Fcking_Chuck [link] [留言]

I mean human still operates but basically gets one joystick 🕹️ because machine will think for itself how to put its leg better. So some sort of spinal cord intuitive walking. With the library of objects one shouldn’t step on, no way. submitted by /u/Ubud_bamboo_ninja [link] [留言]

After debugging 20+ broken RAG systems, I've identified the 6 decisions that determine whether yours works. Here's how to get each one right. The RAG Developer's Trap Every RAG developer falls into the same trap: you build the basic pipeline, it sort of works, and then you spend weeks tweaking prompt templates — while the real problem sits untouched in your indexing pipeline. The 80/20 rule: 80% of RAG problems come from indexing, not generation. But 80% of debugging effort goes into generation. Let's fix that. Decision 1: Embedding Model — The Single Biggest Lever The mistake: Using all-MiniLM-L6-v2 for Chinese documents because it's the default in every tutorial. Why it's wrong: It's English-trained. Drop it on Chinese text and it loses 30-50% of semantic fidelity. Language Use This Chinese BAAI/bge-large-zh-v1.5 (1024-dim) Chinese + English BAAI/bge-m3 (multilingual + sparse) English text-embedding-3-large Code jina-embeddings-v3 or voyage-code-3 Non-negotiable: Indexing model and query model must be byte-for-byte identical. Switch models = rebuild entire index. Impact: +15-40% Recall@10 for Chinese RAG. Decision 2: Chunk Size — Not a Magic Number Physics: Too small (< 100 tokens) = semantic fragmentation. Too large (> 1000 tokens) = noise injection. Document Type Sweet Spot Overlap FAQ / Short-form 128-256 20 Technical docs 512 50 Long-form articles 768-1024 100 Code Function boundaries 0 The method matters more than the size. Use recursive splitting, not fixed-length: from langchain.text_splitter import RecursiveCharacterTextSplitter splitter = RecursiveCharacterTextSplitter ( chunk_size = 512 , chunk_overlap = 50 , separators = [ " \n\n " , " \n " , " . " , " " , "" ] ) Impact: +5-15% Recall@10. Decision 3: Index Type — HNSW vs IVF Scale Use Why < 1M vectors HNSW Recall > 0.95 1-5M, RAM tight IVF + PQ 75% memory savings > 5M IVF + PQ + Sharding Horizontal scale Key nuance: HNSW has high insertion cost. Streaming docs → IVF may be better even at small scale. Im

Once you start noticing them, they're everywhere. And the algorithm makes it worse, the more you engage, the more it feeds you... Perfect lighting in every single photo. That glow on the face in every other pic or video it doesn't matter what the background or lighting is. Follows 3 people but has 40k followers. Generic bio that could apply to literally anyone. Comments that are just emojis or "love this!" The creepy part is how consistent the patterns are across platforms. Same pose angles. Same aesthetic. Same engagement ratio that makes no sense for a real person. I built a small community tool where people can flag and vote on suspicious profiles. Not trying to be the judge, just crowdsourcing the pattern recognition. I feel humans are really good at spotting these when you give them the right frame and observation. Anyone else been noticing more of these lately? Curious what other people pick up on this. submitted by /u/Brilliant-Nerve-8972 [link] [留言]

TLDR TypeScript has 7 primitive types: string , number , boolean , null , undefined , bigint , and symbol . You use them to tell TypeScript what kind of value a variable holds. You write them in lowercase. TypeScript can often figure out the type for you. But knowing how each one works is key to writing safe and clear code. What Are Primitive Types? Primitive types are the simplest building blocks in TypeScript. Every piece of data in your program starts with one. They hold a single value. They are not objects. You cannot add methods or properties to them directly. TypeScript has 7 primitive types in total: Type What It Holds string Text like names, messages, or IDs number Any number: integers, decimals, negatives boolean Only true or false null An intentional empty value undefined A value that was never assigned bigint Very large whole numbers symbol A unique identifier value This article covers all 7. You will use string , number , and boolean the most in everyday TypeScript code. How to Use the string Type A string holds text. Use it for names, messages, emails, URLs, and any other text data. Basic string annotation let firstName : string = " Alice " ; let greeting : string = " Hello, world! " ; let empty : string = "" ; Three ways to write strings TypeScript supports the same three string styles as JavaScript: let single : string = ' Single quotes work fine ' ; let double : string = " Double quotes work too " ; let template : string = `Template literals with ${ firstName } ` ; Template literals (backticks) let you insert values inside a string with ${} . TypeScript checks the types of those inserted values too. let age : number = 30 ; let message : string = `I am ${ age } years old` ; // TypeScript checks that 'age' is compatible here What TypeScript catches with strings let name : string = " Alice " ; name = 42 ; // Error: Type 'number' is not assignable to type 'string'. name = true ; // Error: Type 'boolean' is not assignable to type 'string'. Once a variable

Curious about the ones that didn’t stick. everyone talks about what they use but nobody talks about what they tried and dropped and why. submitted by /u/aiprotivity_ [link] [留言]