Archive
Discover and discuss technology tools
Explore the Tiscuss archive by category or keyword, then jump into conversations around what matters most.
AI Tool Trains Chess Engine to Play Like Humans
AI Tool Trains Chess Engine to Play Like Humans Artificial Intelligence (AI) has significantly impacted various fields, including strategic games like chess. A …
Unlocking Super Intelligence: tinyhumansai/openhuman AI Tool
Your Personal AI super intelligence. Private, Simple and extremely powerful.
Open-Source Dashboard as Code Tool DAC for Agents and Humans
Transforming Analytics with Open Source Dashboard as Code (DAC) for Agents and Humans Open Source Dashboard as Code (DAC) tools are revolutionizing the way data…
Spotify Adds Verified Artist Badges to Combat AI Impersonation
Spotify looks for an identifiable artist presence both on and off platform, like concert dates, merch, and linked social accounts on their artist profile.
Exploring AGI: Beyond Tools, Towards a Shared Condition
​ AGI is often framed as a continuation of current AI progress, but it may represent a qualitative shift rather than a quantitative one. Not all technologies are of the same kind. Some function as tools (e.g., cars, elevators), while others function more like shared conditions that reshape the environment in which decisions are made. In that sense, AGI may be closer to a “sun” than to a “tool”: not something we simply use, but something that defines the space in which we act. This distinction matters, because treating AGI purely as an instrument may obscure the importance of alignment, interaction, and long-term co-adaptation. The challenge may not be control alone, but co-evolution a process in which both humans and artificial systems adapt through ongoing interaction. In biological terms, evolution is not only driven by competition, but by mutual selection. Of course, AGI will still be engineered systems in practice, subject to design choices and constraints. The point here is not to deny its instrumental aspects, but to highlight that its effects may extend beyond conventional tool-like boundaries. If AGI is approached in this way, the central question shifts: not simply how to build it, but how to relate to it in a way that remains stable, aligned, and beneficial over time. *Inspired by the film Sunshine (2007, dir. Danny Boyle) — particularly the image of the crew not simply "using" the sun, but being consumed and redefined by proximity to it.*
AI and Population Control: Is There a Hidden Agenda?
Hello everyone, I’m a 21-year-old and I’ve been thinking about something today. What if AI is actually being used as a long-term strategy by powerful people to reduce or control the human population? Here’s what I mean. Over the last few years, we’ve had things like COVID, rapid AI development, robots becoming more human-like, and a lot of wars and instability around the world. Maybe it’s all coincidence… but what if it’s not? My theory (maybe a bit crazy, I know): What if AI and robotics are being developed to the point where they can replace humans almost completely? Then, with things like wars or even new viruses, the global population could be reduced drastically. Meanwhile, the rich and powerful would have the resources to stay safe or leave. In that scenario, you’d end up with a much smaller population and advanced AI/robots doing most of the work. No resistance, no complaints — basically total control and fewer “problems” for the people at the top. I know this might sound far-fetched, and maybe I’m just overthinking, but the timing of everything feels strange to me. What do you guys think? Am I going too deep into this or does anyone else see these patterns? Quick note: they don’t need money paper currency and those numbers on your bank account are just illusions the 50 dollar bill isn’t 50 we al just say it has a value. Only real currency is gold and silver. Plus the rich want sunny beaches, yachts,alcohol /drugs and good food
AI Optimists vs. Pessimists: Will AI Reduce Unemployment?
How does what Dario is saying that unemployment is going to 20% if AI is going to be used to solve our problems? AI is a tool for humans to point at problems and solve them. Making humans act less like machine. Good. Making humans afraid that they will lose their income source because of a machine. Bad. This doesn’t make logical sense. Do they not like humans and want to solve their problems? Unemployment is one of our biggest problems. And they are saying that AI can’t fix it? Also, universal job guantee polls higher than universal basic income. Most people like to work and provide value. They don’t like being exploited and living in fear that their livelihood will be erased. What am I missing here AI optimists? AI pessimist? Realists?
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.
AI Agents: Identity, Not Memory, Was the Key to Stability
Everyone's building memory layers right now. Longer context, better embeddings, persistent state across sessions. I spent weeks on the same thing. But the failure mode that actually cost me the most debugging time had nothing to do with memory. Here's what it looked like: an agent would be technically correct - good reasoning, clean output - but operating from the wrong context entirely. Answering questions nobody asked. Taking actions outside its scope. Not hallucinating. Drifting. Like a competent person who walked into the wrong meeting and started contributing without realizing they're in the wrong room. I run 11 persistent agents locally. Each one is a domain specialist - its entire life is one thing. The mail agent's every session, every test, every bug fix is about routing messages. The standards auditor's whole existence is quality checks. They're not generic workers configured for a task. They've each accumulated dozens of sessions of operational history in their domain, and that history is what makes them good at their job. When they started drifting, my first instinct was what everyone's instinct is: better memory. More context. None of it helped. An agent with perfect recall of its last 50 sessions would still lose track of who it was in session 51. What actually fixed it I separated identity from memory entirely. Three files per agent: passport.json - who you are. Role, purpose, principles. Rarely changes. This is the anchor. local.json - what happened. Rolling session history, key learnings. Capped and trimmed when it fills up. observations.json - what you've noticed about the humans and agents you work with. Concrete stuff like "the git agent needs 2 retries on large diffs" or "quality audits overcorrect on technical claims." The agent writes these itself based on what actually happens. Identity loads first, then memory, then observations. That ordering matters. When the identity file loads first, the agent has a stable reference point before any history lands. The mail routing agent learned the sharpest version of this. When identity was ambiguous, it would route messages from the wrong sender. The fix wasn't better routing logic - it was: fail loud when identity is unclear. Wrong identity is worse than silence. The files alone weren't enough Three JSON files helped, but didn't scale past a few agents. What actually made 11 work is that none of them need to understand the full system. Hooks inject context automatically every session - project rules, branch instructions, current plan. One command reaches any agent. Memory auto-archives when it fills up. Plans keep work focused so agents don't carry their entire history in context. The system learned from failing. The agents communicate through a local email system - they send each other tasks, status updates, bug reports. One agent monitors all logs for errors. When it spots something, it emails the agent who owns that domain and wakes them up to investigate. The agents fix each other. The memory agent iterated three sessions to fix a single rollover boundary condition - each time it shipped, observed a new edge case, and improved. These aren't cold modules. They break, they help each other fix it, they get better. That's how the system got to where it is. You don't need 11 agents The 11 agents in my setup maintain the framework itself. That's the reference implementation. But u could start with one agent on a side project - just identity and memory, pick up where u left off tomorrow. Need a team? Add a backend agent, a frontend agent, a design researcher. Three agents, same pattern, same commands. Or scale to 30 for a bigger system. Each new agent is one command and the same structure. What this doesn't solve This all runs locally on one machine. I don't know whether identity drift looks the same in hosted environments. If u run stateless agents behind an API, the problem might not exist for you. Small project, small community, growing. The pattern itself is small enough to steal - three JSON files and a convention. But the system that keeps agents coherent at scale is where the real work went. pip install aipass and two commands to get a working agent. The .trinity/ directory is the identity layer. Has anyone else tried separating identity from memory in their agent setups? Curious whether the ordering matters in other architectures, or if it's just an artifact of how this system evolved.
AI's Productivity Boost: Layoffs or Worker Benefits?
I keep hearing that AI will make workers more productive. But the part I don’t understand is this: If one employee can now do the work of three people, why is the default outcome usually: * fire two people * keep the same workload * give the remaining person more pressure * send the savings upward Why isn’t the obvious outcome: * shorter work weeks * higher wages * lower prices * more time off * better services It feels like AI is being sold to the public as “everyone will be more productive,” but implemented by companies as “we need fewer humans.” Maybe I’m missing something, but productivity gains only feel like progress if normal people share in them. Otherwise it’s not really “*AI helping workers*.” It’s just automation being used as a layoff machine. **Do you think AI will actually improve life for workers, or will it mostly just increase profits while making jobs more insecure?**