Archive
Discover and discuss technology tools
Explore the Tiscuss archive by category or keyword, then jump into conversations around what matters most.
Google and FBI Alert: Ransomware Group Sends Fake IT Workers
Cybercriminals, part of a gang known as Silent Ransom Group, have sent people pretending to be IT support employees to law firms' offices, where the criminals have stolen data using USB drives or remote access tools.
Gotski: Revolutionizing AI with Workers.dev
Gotski: Revolutionizing AI with Workers.dev Gotski, an innovative player in the realm of AI integration, is leveraging Workers.dev to push the boundaries of art…
AI Tool Raves: Unveiling ravers.workers.dev on Hacker News
AI Tool Raves: Unveiling Raver'sWorkers on Hacker News Raver'sWorkers, a cutting edge AI tool, has sparked excitement among tech enthusiasts on Hacker News. Thi…
Oracle's Remote Worker Severance Controversy: AI Tools
Some found out they didn't qualify for WARN Act protections like two-months notice because the company had classified them as remote workers.
Gate AI: Visual Workspace for Dev Ticket Management
Revolutionizing Dev Ticket Management with Gate AI In the fast paced world of software development, efficient ticket management is crucial for teams to stay org…
AI and Art: Bridging the Divide for a Better Future
Hey,It's A again..The Rambler.. Since you guys were helpful last time,im back here again for more opinions and thoughts. Lately,I've been trying to feel less guilty for using AI. Why? Cause,1.)Im tired of not feeling valid enough anymore for my actual art in writing in a community i greatly care about,2.)People don't believe me when I tell them I out my heart and soul into everything I make,even if i only partially make it by typing writing prompts into a generator and rewriting said things,and 3.)Cause I enjoy it.Things you enjoy shouldn't make you feel bad. I see a lot of people offering pros,cons,and alternatives,but nobody is trying to fix the root of the problem,The fact that fear is the center of it all with the war between pro and anti ai. People are so scared of being replaced cause big companies would rather not pay their workers and have bots do things for them instead,which is leaving people in fear of losing what they love and what is part of their own hearts and soul,and their very being. But This fear mongering over being replaced just leads to people in both fields fighting eachother cause they want to feel valid,But instead of talking about ways to better the other side they'd rather tear eachother down by stopping something that might not be all bad or all good. A lot of things in the past were bad invention wise,or at least started that way before they were made more eco and people friendly. Cars used to run on excess gas,big companies used to pollute before switching ego,Even eating meat could be something you felt guilty for. Why does the better option have to mean sacrificing something just cause you're afraid of it? If we never learn we will never grow,If people stopped inventing we'd all be gone by now.If people don't try to see eachothers point of views were never going to grow and Ai is always going to bad or good,and people are always going to be defensive and that leads to less production in the first place. People that work with Ai feel like theyre not needed cause the other side wants them out for just existing and people in the art community feel like they won't have a place anymore if they let the other side in.Both are problematic,but both arent completely wrong either. Communication is key,and right now,we need communication and looking through eachother's lenses more than anything.I m willing to debate anyone in the comments over this,as my personal belief is Ai helped me through a really hard time writing wise,and I don't want to feel discredited just cause Ai isn't perfect,and needs to bettered. I legit want to make a change,probably starting with a subreddit for making Ai more eco friendly,where people are free to post their creations,as I already run another sub im not going to disclose her cause I don't want to get off topic. But anyway,I wish more people weren't afraid to take a middle approach, We all need to hear eachother out.Dont kill with kindness,heal instead.-A
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?**