home.social

Search

1000 results for “My_plants_dance”

  1. It's not a new thing to be asked but aren't eco-systems so cool!? The way waste, nutrients and resources are passed around to benefits everyone is so fascinating!
    This is my oldest aquascape! A mossy terrain with blade grass growing in between the rocks. It's established, meaning I don't have to baby it. It has a large population of tiny little shrimp. It filters most of it's own waste, keeps the water clean and everyone is fed.
    #aquascape #ecosystem #plants #aquatic

  2. This night I have found these two little ( snails)..
    They have been eating the leaves of our plants and today I have decided to trace them when I found them goin near the plant .. that's When I realised the culprit.
    Then my question goes to the #naturelovers should I spray pesticides to them or what can I do kill or fix that In other means .
    #garden @[email protected] @[email protected] #mastodon #environment #food #biodiversity #biology #vegans

  3. V is for Vegetables 💚
    I have terrible internet connection rn. I've been failing to upload this picture all day! Good thing it posted in my Ko-fi:
    ko-fi.com/post/V-is-for-Vegeta

    Join us for #ArtABCs, the most laid-back art challenge ever
    Share your art of anything starting with V!
    No AI, Yes alt text, CW as needed

    #MastoArt #ArtABCs #Watercolor #Watercolour #Painting #Nature #Plants

  4. CBR-II update (V3): smoother gait + trying to stand on one leg reddit.com/r/robotics/comments all, here's a small update on CBR-II, my DIY biped. This is the third iteration. Clip 1 (V3): It walks a lot more confidently now, with much less jitter. The only harsh moment left is when a "stop" comes right after "forward". It plants its front foot and slams it into the floor pretty loudly. Clip 2 (V1): The original version, for

  5. 'To make matters worse, several high transmission lines were also running below capacity due to maintenance, meaning huge amounts of mostly renewable energy and storage capacity could not be delivered to Sydney just when it needed it most.

    '"And some people with home batteries who are seeing that price are saying, 'Oh, it's a great opportunity, I can discharge my battery for five minutes'.

    '"In total, approximately 2,400 [megawatts] of coal-fired generation capacity was unavailable across NSW," the spokesman said.

    'Spring has traditionally been when coal plants do scheduled maintenance after winter and before ramping up again for summer demand, but analyst Tristan Edis said that window appeared to be narrower because of global warming.

    'Grid-scale battery capacity has more than doubled in the past year to more than nine gigawatts and in the third quarter of 2026, Westerman said, batteries set the wholesale electricity price almost 50 per cent of the time, up from 18 per cent in the same quarter last year.

    'Dave Smith said the ability of household batteries to move the market was growing every day as installation numbers rose, but AEMO remained largely blind to their presence and intentions'.

    abc.net.au/news/2026-10-17/hom

  6. The Greenland Diaries: Day 77

    Last night, I’m not sure what happened, or why there were people moving through the area in the darkness, but around midnight the shadows were flashing with popping gunfire and small explosions. I followed the sounds of the bullets, and they bounced off of everything in hollow glances and pings. A few even hit the shed. I covered Snowy with my backpack and put her around my chest.

    I was so worried that a shot would pierce the shed and split one of us open.

    I hugged up so tightly to her, she would lick my face through the backpack as the thunder of distant mortars and rockets threw tree branches everywhere. They sounded hollow and rocky, like skeletons were trying to swallow up the shed and pull it away. A few times I shifted to the other wall and buried us beneath the boxes of supplies and gallons of water.

    I heard machines rolling through the streets, hundreds of them. The pavement cracked and moaned against their heavy treads. The grinding was so intense, I thought the earth was going to fall apart and my house, shed, and everything would be swallowed up. It’d be nice to go out that fast. It’d be nice to avoid the shadows and wild claws.

    The Drum still beat behind the whirlwind of gunpowder. I stayed still the entire night as the shooting raged. Seldom did I hear a gun or cannon stop firing to reload. It was like they were spending every inch of ammunition on this battle. I know the Unnamed aren’t overt and present when you fight them. I’ve been lucky enough to fight them in close quarters. At a distance, they’re nearly impossible to see, especially in the dark. How could these people fighting them possibly know where they were hiding?

    Around four in the morning, they finally stopped their fighting, and the world returned to the Drum and the silence between each beat. There were no illusions or Unnamed sulking around the empty spots of crumbled houses or caved-in walls. I stayed up all night watching them, but there was nothing. Only the bugs brewed about in aimless clouds.

    In the morning, I scouted the area for traces of the battle. I looked for bits of fresh rubble, empty bullet casings glittering in the sun, and bits of torn clothes with inky blood beneath their layers. There was nothing though, not a single crater in the ground or pulverized wall from any of the nearby houses. In previous battles, I’d find this debris so fresh, it’d be shedding dust in the sun like wayward dandruff.

    There is nothing though, no sign of the previous night’s battle.

    I walked around the block three times with Snowy, looking for the smallest, most minuscule remnants of the battle. Nothing moved. Only the trees and sheets of thick grass shook against the breeze. The plants always look like they’re ready to bubble and burst.

    I stopped searching in the late afternoon. It had been an illusion. It was all part of some massive trick by the Unnamed and their unseen allies. When I wandered back home with a worried Snowy, I saw the kid from before. He had been following me the entire time, dodging behind the houses like I used to do when I played with Nerf guns when I was his age. 

    I bet he regrets any imaginary nightmare he played war with now, the apocalypse was too real

    “Don’t get tricked by the battle, they’re illusions too,” I yelled, as he ran away from me. I hope he listens. I don’t know why he always runs.

    I’m not going to hurt anybody.

    #apocalyptic #books #fiction #horror #journals #monsters #novels #reading #writing
  7. No Clean Singing 🤘 SHADES OF BLACK: GLORIOR BELLI: (written by Islander) Life events external to NCS have forced me to again truncate my plans for this usual Sunday column devoted to variants of black metal. All is well, but I need to leave home and computer fairly soon, too soon for me to do more than write about one album that came out [...]

    The post SHADES OF BLACK: GLORIOR BELLI appeared first on NO CLEAN… dlvr.it/TW3Qj6 👀 Bio Link 4 More 🤘

  8. Planned to go to a zine fest for queer people of the global majority and I had been planning to go since earlier this year, made a zine to share that I have not shared before but got dragged out to see my brother who is moving abroad because I am a bad guy if I don't suddenly change my plans to go. He spent most of the time cussing me out for being chronically ill, cussed me out for needing to be on a treatment that makes me ill, cussed me out for having to be on a treatment for the rest of my life that increases the probability of cancer and cussed me out because I'm dealing with discrimination at work because I'm chronically ill. I mean he did ask, am I meant to just say that I am magically cured when there is no cure?

    I guess I'll just go and die then.

    That zine fest is over so I have to wait to see if they bring it back next year.
    I'm off to take myself to an art shop to get lost there. I can make some more zones that I won't get to share. That'll surely cheer me up. 🫠

    #zine #disability

  9. #Today 24

    Good day!

    The forecast for yesterday was for a trace of moisture. Instead, we had a light to moderate rain all day. It made for a lovely walk and day, and we certainly needed it.

    My plans? The book read-thru and answering questions for Talk to Me Day.

    Be everwell.

    #WritingLife #AmWriting #WritingCommunity #Aging #HealthyLiving #HealthyLifestyle #GetOutside #Hiking #Trails #HikingAdventures #Nature #NaturePhotography #NatureLover #Photography #LandscapePhotography

  10. I’m making my third trip home to Virginia this year. Trying to help my aging parents navigate different stages of memory loss and mental decline. I’ve never felt this much stress in my life before. If your parents are not there yet, talk to them about it now. Make some plans now.

  11. “The rebellious children are as good as dead,” says the Lord,“those who make plans without consulting me, who form alliances without consulting my Spirit, and thereby compound their sin. Isaiah 30.1 NETB.

    #Bible #Prophets

  12. Eternal Energy of existence itself, you soften my heart from the inside out. May my softened heart have the strength to be someone else’s refuge of comfort when it is most needed, so that the seeds of love you plant in each of us find the shelter and care they need to grow and blossom. Amen.

  13. “The Evil” (1978) – Review

    Hello again, my lovely Gorehounds and Horrorfiends,

    3FMC is here with you with more fun and laughs as we review horror films from yesterday, today, and tomorrow. Today, we decided to wait until the nice day was over, then it was pizza time, and some Horror to scare the mozzarella out of us. As we are drawing closer to the 31st, and All Hallow’s Eve, we have cranked up our Horror viewing by a factor of 5. If we had cranked it up to 10, we would not be going to work, and that would be a big problem. Anyways, we spun our Wheel of Death to see what it landed on…BTW, we made a cute little wheel that works like the Wheel of Fortune, that we spin to pick Horror films when we cant decide. It has the subclasses of:

    • Monster Movie (includes Vampires, Werewolves, Alien Creatures, Zombies, etc)
    • Haunted House
    • Slashers
    • Ghosts
    • Witches
    • Sci-Fi Horror

    It landed on “Haunted House” so we pulled one from the drawer that we haven’t reviewed on here yet. That would 1978’s The Evil, starring Richard Crenna, Joanna Pettet, and the late great, Victor Buono.

    Premise: A psychiatrist, Dr. Arnold (Crenna) purchases an abandoned mansion that he plans to turn into a drug rehab. He then has some friends come in and help him clean up the place to get it in order. Apparently, the house was previously owned by a Civil War General, who had the home built of some sort of hot springs. Then, when working in the basement, Dr. Arnold finds a trapdoor that he opens and unwittingly releases a nasty spirit which traps all of them in the house. Dr. Arnold later realizes that the trapdoor is actually a doorway to Hell (at least it wasn’t a well in the basement like another house located in Amityville).

    Discussion: Once the spirits are released from the basement, the body count starts to soar, and people are killed in some gruesome ways. All in all, this was a very effective, and in a lot of ways, underrated haunted house horror film. Strong performances from Crenna and Buono, set this one apart from many of the other Haunted House films of the genre. Buono’s portrayal of The Devil was particularly good, and frightening. We definitely think that this one is in the Top 5 best Haunted House films of the 1970s and 1980s. Not Poltergeist-level special effects, but definitely more psychological in nature, and an effective one at that. Give it a try.

    ” I feed on 3FMC Reviews, Mr. Arnold.”

    Rating: 4 doors to Hell out of 5.
    – 3FMC

     

     

    #80s #cinema #Devil #fear #ghost #hauntedHouse #Horror #horrorMovies #movie #scary
  14. Tokens Over Hires

    In the middle of September I ran ccusage against every Claude Code session on my laptop since May. It walks the local logs, counts the tokens, and prices them at what the API would have charged. I expected a big number. What came back was about twenty billion tokens and just under fourteen thousand dollars, across every project I’d touched in four months, with most of it going to Pepper, which is now open for signups, so go check it out. Nineteen billion of those tokens were cached reads.

    I sat with that for a minute. Fourteen thousand dollars is real money. At my current pace it works out to roughly thirty thousand a year. I could triple it and spend a hundred thousand dollars a year on tokens, and that still isn’t one engineer. In exchange, Chris and I have shipped more code than I’ve shipped in any stretch of my career. I wrote in September that the two of us merged 657 pull requests in our first thirty days with a budget instead of a platform team. When I put the ccusage number in those terms on a panel, it came to about a dollar fifty a pull request.

    That number is what my laptop would have cost at API prices, and it isn’t what we actually pay. Here’s the whole bill for both of us. Two Codex subscriptions, one each, are $200 a month. Anthropic is $550 a month: a Max plan for me and Chris, plus two Vycari team seats, one for Chris and one that runs our automation. I have an Ollama subscription at $200 a year. Greptile is about $1,500 a month. All in, that’s a little under $2,300 a month, or about $28,000 a year, for both founders and every pipeline we run. It still isn’t one engineer.

    The obvious conclusion is the one a friend reached when he heard the figure: if code is that cheap, just get more tokens. I thought so too, for about a day. Then I looked at what was actually slowing us down, and the token budget wasn’t on the list.

    The Constraint Is Attention

    Every agent I run needs things from me that tokens can’t buy. It needs a plan approved before it starts. It needs its pull request read when it finishes. When it hits something it can’t decide, it escalates, and somebody has to be there to answer. None of those steps is expensive on its own. The problem is what happens when I run enough agents that the steps overlap.

    When I run too many agents, the cost goes up a little and the risk goes up a lot. The biggest thing that’s slipped past us so far was how we managed database connections. It got out of hand, a little at a time, while my attention was on other pull requests, and eventually it caused an outage. Chris had to roll forward while I was out of town, and I spent the following week building a proper database abstraction layer. He put it more bluntly than I would have: the thing that kills us is splitting our attention. That’s when stuff slips through.

    When people ask how we decide what to spend, I give them the order. Optimize for human time, because that’s the scarcest thing we have. Then money, because that’s the second scarcest. Then everything around agent time. “I can waste agent time all day. I don’t care.”

    So the number that limits us is how many agents one person can supervise well at the same time. I don’t have a precise figure for that ceiling. I know I’ve been over it, because I can feel the difference between a day when every pull request got a real read and a day when I was skimming to keep up.

    Another friend told me recently about engineers at his company running up bills in the thousands to build simple internal copies of SaaS tools. His reluctant guess was that they just aren’t as good at using agents yet, and that it’s a skill people have to develop. I don’t know what they’re doing differently. It doesn’t sound like token maxxing, which I’ve never really understood either. I’d love to sit with engineers who run up giant bills and just watch. My guess is they’re using the agents inefficiently, and that what’s missing is supervision, which a bigger budget won’t fix.

    Building for More Agents per Person

    Almost everything I’ve built since the summer has been an attempt to raise that ceiling, and almost none of it has been about spending less.

    The pipeline I described in The Agent That Never Merges is the first piece. Agents open pull requests continuously and never merge them, which means the supervision cost per pull request is bounded at one careful read. The pipeline absorbs the rest: triage, planning, the first round of review comments, the retries. I only see the work once it’s in a state worth my attention.

    The second piece is where the work lives. I wrote about pulling Pepper apart into small, bounded repositories to keep CI fast and give agents less to load. It mattered just as much for my attention. An agent working in a repository with one job produces a pull request I can evaluate in one sitting.

    We’re up to fourteen repositories now. Last week I moved our iOS app out of the monorepo into its own. That was 150,000 lines of code, and nobody noticed except Chris, who had to wait a day to land his next batch of iOS changes. Agents make refactors that size easy. Having the CLI and the iOS client in their own repositories also forces us to keep good API definitions between the server and its clients.

    The third piece is delegation inside the agent layer itself. I run two Claude Opus 5.5 orchestrators on medium effort. One is the UTL, for uber tech lead, and its job is to spawn subagents that build features. The other is what I call the focused worker, and its job is working with me. It catches the manual tasks that come out of the UTL’s pull requests and keeps them in a ledger. Then we work through them together: systems changes, bringing up new platforms, migrating data, anything that needs my level of access and oversight. Everything else goes to a subagent under the UTL, Opus for design docs and code reviews, Sonnet for implementing a feature from a design doc. Every one of these agents can consult a model a tier above it as an advisor, and they all share a wiki for notes.

    Anthropic is now advertising much the same pattern with Claude Projects, and I’m happy to see others arriving at the same answer. Chris has been building a loop that babysits open pull requests through review until they score well enough to be worth a human’s time. Each layer like that turns a job I used to do by hand into something I check. The ceiling goes up one delegated task at a time.

    The Token Budget Was the Easy Problem

    There was a week in September when the meter really was the constraint. We ran through our free credits and paid about $120 in overage. Then AutoDev ate the whole Vycari quota, and I did server cleanup by hand because I couldn’t do anything else.

    Most of that was self-inflicted. I’d started with Fable as the orchestrator, with no cap on context, and burned a week’s quota in three days. The setup above fixed it. The orchestrators run on medium effort, and the cheaper model does the implementing. Opus answers the reviews because Sonnet is too literal about them, and a literal reading turns two review cycles into twelve. Every agent auto-compacts at 200K tokens, because Anthropic charges more for context past that point. With that setup, and the work spread across parallel sessions, I find it hard to spend all of my quota. My goal now is to hit 99% of it every week just before it resets. I keep a list of research projects, and if I have quota left 24 hours before the reset, I spin one up. That isn’t the same as maxing out tokens. I’m not trying to use as many as possible. I’m trying to use all the ones I’ve already paid for.

    There’s also a second account on the same machine. Claude Code reads a CLAUDE_CONFIG_DIR environment variable, so two shells with two config directories give you two accounts side by side. The second one runs the AutoDev and code review pipelines, and those use up its quota every week, so it isn’t a fallback for my own sessions. When I do run short, I supplement with other labs’ plans. Every one of those fixes took an afternoon or less. None of the supervision problems above has had an afternoon fix.

    Where the Money Actually Goes

    While I had the numbers in front of me, I looked at where development spend actually lands, because it isn’t where I expected either.

    Development tokens currently run about ten times what the product itself consumes, even with real people using it. Building the thing costs more than running it. That won’t last. The feedback from our private beta has been really good, and we now open Pepper to a limited number of new signups every day, so product usage is rising quickly.

    Most of what we actually pay goes to code review. Subscriptions are the cheap way to buy tokens if you’re willing to hit limits, so they’re the smaller line. Greptile reviews every pull request we open, and at about $1,500 a month it’s our biggest single expense. We both think it’s worth it, because it’s the layer that lets the never-merge pipeline run without me reading every first draft.

    In October I tested that. I spent a few days building a cheaper reviewer to replace it. I came out the other side saying, “I think we should just pay for it because I can’t do it cheaper.” What I could change was how often we call it. The agents kept asking for a re-review before they’d fixed anything. Because every repository shares a common dev environment, the fix went in once: our pull-request skill now has agents run /simplify and then /code-review before they’re allowed to open a pull request. On many of our repositories, our own reviewer also does the first round and only then calls Greptile. My goal is a pipeline where Greptile’s reviews come back with nothing to say. We’re not there yet, but we get a little better every week.

    I’d rather pay for review than have a second person do it, and the reason isn’t salary. The person would need supervising too, because review is a job I’d have to check, not one I can hand off.

    What a Hire Is For Now

    Five years ago, if I’d been getting a product like this ready for market, I’d have been hiring twenty to fifty engineers. The work would have needed that many hands, and most of what they’d have done was write code. Today the code is the cheap part. If I bring someone in to write code, I’ve added a person who needs plans approved and pull requests read, which is the exact resource I’m short on. A hire whose job is output adds coordination faster than it adds capacity.

    I said on a podcast that came out last week that the code I’ve written would have cost about fifteen thousand dollars at API prices, and that I couldn’t hire engineers for that money. That’s true. The engineers I’d still want are a different kind from the ones I hired at Google. We need a few more people who can herd agents, not fifty.

    The engineering hire that adds capacity is a different shape. It’s someone who can own a bounded service whole. Here’s the interface, here’s everything it needs to do, let me know when it’s done. That person brings their own supervision. They run their own agents, read their own pull requests, and answer their own escalations, and the only thing that crosses the boundary between us is the contract. Supervision divides along the interface instead of piling up on one person. That’s a tech lead’s job, and it’s the only kind of engineering hire I can see that raises the ceiling instead of lengthening the queue.

    That raises a fair question about how anyone grows into that job now, which I tried to answer in The Questions Are the Job. The other advice I give is to work on open source. I’ve met people who showed they could work really efficiently with agents through open source projects, Gemini CLI in particular, and some of them ended up being hired onto my teams. Open source has its own problems right now. But if you show up as a thoughtful engineer with features or bug fixes that are well reviewed, well tested, and bring value to the project, I think you’ll be welcome. That’s one of the reasons I decided to open source the Pepper CLI.

    The first hire probably isn’t an engineer at all. I’ve said this a few times now, including on stage at a panel in September. Neither Chris nor I are go-to-market people, and I may hire one before I hire another engineer. I can create piles and piles of code, even relatively good code. What I can’t do is agentically acquire customers. (Did I mention that Pepper is open for signups now?) Someone in marketing came up after the panel and told me I’d validated her existence.

    The Third Trend

    I’ve watched this happen twice before. Open source developer tooling made it so a small team didn’t need to buy or build its own compilers, databases, and frameworks. Cloud infrastructure made it so that team didn’t need to own hardware or a data center. Each time, the number of people you needed to start something real dropped, and the skills that mattered shifted toward the people who understood systems well enough to compose what was suddenly free.

    Agentic tools are the third one. Anyone with a good idea can now get from concept to production on a budget that would have been a rounding error in a Google planning cycle. But the constraint didn’t vanish. It moved, the same way it did the last two times, toward the people who understand systems design well enough to drive the agents and notice when something has slipped through. I wrote a year ago that management skills were going to carry over to working with agents. I didn’t expect to be proving it with a two-person org chart and fourteen thousand dollars of tokens.

    This isn’t only a small-company problem. At Google it was hard to get more than a few changes in a day, because each one waited on code review. I’ve talked to engineers there who now do all their work in experimental directories that don’t require review, then port it back to their team’s repository at a pace the review process can keep up with. That’s what happens when you don’t manage for human attention. Productive people spend their cycles waiting on the process.

    When other companies ask me what to change, my answer has become: drive until human attention is the scarce resource, then build for that. If you’re reading your own ccusage number and wondering whether the answer is more tokens, look at where your attention went first. For us the answer has been more interfaces. Those are the places where one person’s supervision ends and another’s begins, or where an agent takes over a job one of us used to do by hand.

    #Agents #AI #Developer #Startups
  15. Good morning Mastodonians! Back from vacation, back at the office! Fun stuff. Boss is telecommuting so at least I can take it somewhat easy, but I have so much to get caught up on. My holiday was pleasant...lots of rambling on Delmarva, visiting old churches and roaming in forests, and paying a call on some friends who just retired to Delaware. (I have no plans on moving there.)

    How're all my friends & followers this morning?

  16. Good morning everyone 🌻 Windy old night and the storm is still blowing, but the power has stayed on so far 🤞 An extra hour in bed this morning due to the clocks going back was helpful as I was awake off an on all night and wanted to be able to get up early to help Grant with the parrots in case there was no power. Luckily that wasn't required so I managed to slip back to sleep for a while.

    I'm sitting with them now and they are clearly unsettled, but all cosy at least. Toby is covered over the front of his cage since he has been screaming at me constantly since I came in and I find that just blocking him off from seeing me while leaving the rest open calms him right down 🤷🏻‍♀️ I can hear him happily munching away. I'll uncover him again when I leave the room, but I would like some coffee in my own warm living room first 😂

    We didn't end up playing BG3 yesterday as Grant said he just wanted to watch stuff instead. I played some Fields of Mistria on my Steam Deck for a few hours instead. I'm really enjoying it. It's like Stardew Valley meets Zelda or something 😊

    Plans for today are more crochet work and watching things if the power stays on.

    Have a very lovely day, whatever you get up to 🤗

  17. CW: satire of terfism, defacation
    Gyns tell me I'm not crazy here. No one I've told about this so far has sympathized with me, but I know radblr is more reasonable than the outside world.
    I'm really afraid of moids going into the sewer and eating my shit and drinking my urine. Everyone makes fun of me for this and tells me why I should care when it's bodily waste anyways, but it's my bodily waste and I don't want moids putting it in their mouth.
    We can all agree that's perfectly reasonable right? Right? We all know how moids can be about women and we all know that they actually do this. So what is the problem if I do it first? 
    I've been reading articles about it and unless you have parasites it's actually not that bad for you and can actually help you absorb nutrients you may have missed before. The only problem is if you ONLY eat and drink your own piss and shit and you get nutrient defeciencies.
    Everyone I've told about this seems completely disgusted by it and I'm at my wits end. I just want my FEMALE piss and shit to stay pure of moid saliva. Why are women treated like this for protecting ourselves?
    Why is it so wrong when I do it but not when MEN do it?
    
    
    Sisters, I need your counsel.
    I haven't flushed in four days and I need advice.
    I know this sounds extreme but I have my reasons. There's been documentation—studies, personal accounts, patterns—that moids and TRA activists have established colonies in the sewer systems. They subsist on what we discard. Every time you flush, you're feeding them. You're giving them sustenance, allowing them to maintain their presence in the infrastructure that connects us all.
    My toilet is reaching a critical point. I can smell it. I know I need to do something but I can't bring myself to push that lever. It feels like... surrender. Like contamination.
    _____________________________________________________________________________________________
    can i be a political lesbian if im super straight? i have never experienced any attraction to women and i find the thought of the female body disgusting. in fact i hate my own body and wish i could be a man. but then id be gay. i have dated men for like 15+ years and after spending so long dating men and being mistreated i feel like i want to claim political lesbianism. maybe i could be a man and force myself to be straight and claim political lesbianism. could this maybe work for me? what kinds of activism should i get involved in to become a political lesbian?
    
    heres a thing that happened to some friends of mine. was walking down the street talking about the bears game and a bus pulled up and a bunch of white women with short hair and bad plastic surgery came out with baseball bats. they all had shirts that sayed 'down with trans'. i(22 afab wombynly wombyn) was able to hold them off while my friend(19 amab mynly myn) ran away. bareley escaped
    
    aita for accidentally harrassing an afab?
    was at the grocery store and had to used the restroom. damn urinary leash amirite? i was
    so terrified of seeing an transexual but had no choice becuz i(35 wombynly afab) had to pee.as i was washing
    mine hands a person came in. i could tell by their jawline and cheekbones that they were
    obviously an amab. so i stood in the door and made them pull down their pandts. and they
    said no so they started walking away but i kept following them demanding to see what was
    in his pants. by the time we reached the checkout it was really statring to cause quite a
    scene which was very triggering to my sex based oppression. i followed him out to his car
    and he turned and looked at me and said "dude im a butch stop being wierd" in a perfect
    femininely wombynly afab voice. aita?
    
    hi yall. i was amab and transitioned 5 years ago. just a normal straight girl, right? couple of months ago i figured i would try reclaiming my masculinity. puicked up some boxers and cargo shorts. instand raging boaner. now i cant ger off without thinking of hot bear for bear frotting. am i still trurrans?
    
    How do you feel about male exclusive radical misandrists? yeah i was born a man and i hate it this cock tortures me evry minute of my existence if i even think about being a man i break down. And due to my unfortunate attraction to men, i experience sex based oppression due to being a bottom. i sometimes wish i could transision and be a political lesbian but then i would just be a male invading women's spaces. so i coined a term to describe me: male exclusive radical misandrist. because if i am going to be oppressed for being a male i want to be the one opressing me. its basic bodily autonomy. only we can oppress ourselves. #moids dni #foids dni #kill all men #kill all women #oppress yourself responsibly #liberate the noone #righttooppress
    
    harrassing random trans women will not brign the downfall of gender. indiviual action will never bring any revolution. what we need is collective action. so stop trying to do anything about gender until the vanguard party has established a positon for the overthrow of gender. if you disagree your just a lifestylist reactionary.
    __________________________________________________________________________________________
    and to my immune system: if you want to drown yourself in snot and mucuous that's your right but would you kindly do me a favor and LEAVE ME THE FUCK OUT OF IT. 
    
    and to my subconscious mind: need i remind you that your job responsibilities cover automated systems like breathing and circulation, not fucking keeping me awake all fucking night? kindly focus on attending to your job description instead of insane extracuriculars? I need you to remember that we are a team here and your actions affect everyone.
    
    dear James in engineering,
    I cant believe you still haven't solved the problems with the power couplings. I know this may be hard to understand but you need to turn the set screws to the OFF position to turn OFF the flow restrictors and you need to turn the set screws to the ON position to ENABLE the flow restrictors. Kindly, learn to do your damn job.
    
    dear administration,
    I appreciate all of your hard work in finding staff in these difficult times but I need clarification on one thing: where do you find all of these morons? You have sent us five new employees in the last two weeks and only one of them knew what a philips head was. We cannot be spending what little time we are given to train new employees in basic skills. Might i recommend hiring people who demonstrate technical proficiency instead of your fuckup nephew?
    
    heres something i actually sent my local news station:
    Hello Andrea,
       I apologize if this is not your department but I cannot find a contact for the meteorology department. My complaint is quite simple: I ask that weather forecasters please refrain from inserting their personal judgements and opinions into the broadcasting. I get that some people might appreciate warmer weather but this opinion is not universal and many of us find it quite shocking to see 80 degree highs in late october described as "nice", "mild", or "fair". If you would like to hear my opinion on the matter, personally I find this heat oppressive as I am someone who spends a good deal of time outside engaged in hard physical activity. In fact, I would go so far as to say that if you enjoy this weather you might consider relocating to an environment with a more suitable climate, such as the fucking sahara desert. And frankly, the Sahara might be an improvement: at least I could manage the heat in a dry climate.
    Thank you for listening to my rant and have a blessed day,
    Foob
    P.S. Anything you could do to keep the temperatures in the mid 50s would be greatly appreciated on my end.
    
    dear Administration,
       While I appreciate that finding competent staff is difficult sometimes and that you have been able to find teaching staff with high levels of technical proficiency, several of your staff have been lacking in professionalism and pedagogy. I have actually had teachers cancel class with 5 minutes notice, on multiple occassions, so much so that it in fact became a recurring pattern with them. As if that wasnt bad enough, these are often the same teachers who's prefered teaching style seems to be blindly reading off their powerpoint without so much as looking at the class, much less checking for understanding. I ask that in the future you please hire teachers who actually show up to class and actually know how to teach.
    Best regards,
    A concerned student
    ps. and dont even get me started with your online offerings. in a live classroom setting, a student can at least raise their hand and steer an incompetent teacher. but your online classes are just underpaid staff reading off thier lecture notes with no furter explanation beyond basic concepts. I might as well watch a youtube video, that would be a better value. For $1000 dollars a class, this is a total ripoff and perhaps even a full on scam. fuck you.
    
    Whoever is in charge of hiring at this place is a real piece of work. I get that there are others who may have better qualifications but to interview a candidate and not even send a rejection email, much less useful feedback, demostrates a level of profesionalism that would embarrass a tavern wench. These institutions, and society as a whole, would benefit greatly from giving people a fighting fucking chance.
    
    Dear hiring manager,
       I have an important formal inquiry(injury): on your website you have multiple listings for so called entry level positions with a minimum qualification of 5 years of experience. This leaves me wondering how one is supposed to get 5 years of experience if all of the so called entry level positions require 5 years of experience. This is so prevasive accross your job listings that I suspect I might have a decent case with the Equal Opportunity Employment Commission, considering that these requirements absolutely have a discriminatory impact against people who are new to the job market. So I guess my question is this: do you actually hire human beings or only bots?
    Also, what the fuck are you smoking? This is a job which entails mostly filing sales reports, which is not exactly a rare or difficult skill. Stop acting like corporate bureaucracy is a skilled trade: it isn't.
    
    Dear hr,
       It has come to my attention that the tone of my recent emails is "problematic and unprofessional". While I can appreciate that others may have trouble with the self awareness necessary to address issues raised in good faith, I must suggest that my coworkers stop being such a bunch of little bitches.
    Thank you for your attention to this matter.
    
    hello hr representative,
       I am writing to inform you of several concerns i have with this companies hr department. While I do appreciate the structure whereby advancement depends on undying loyalty to the establishment and whereby power is exercised both for its own sake and to keep underlings in check, I must say that you lack the ability to be gangsta unless you have the full backing of the entire institution. Kindly, if you have a beef with me, settle it like grown men instead of hiding behind your lackeys. Also, you claim to have meaningful power over me but we both know that you would be nothing without the backing of your institution. Once again, lets drop the bullshit and settle this.
    Best regards,
    Mr. Dick Head
    __________________________________________________________________________________________
    
    
    ____________________________________________________________________________________________
     Have
    
    you owned a month-end close and an annual audit relationship for a fund
    
    or investment vehicle, without a supervisor above you?
    
    I ride a bicycle everywhere and if i cant get there on a bike i simply ride there anyway. i ride in the middle of the road, often dodging traffic in the oncoming lane. Its like dancing its all about your footwork, timing and spacing. I know this sounds dangerous but you need to know something about me: dick does not fuck up. If there is a collision it is your fucking fault for being in my fucking way. Dont you know pedestrians have the right of way?
    
    
    Do
    
    you have five or more years of accounting experience, including fund or
    
    investment-vehicle accounting (private credit, debt fund, or real
    
    estate fund)?
    
    Yeah ive been riding my bike for like 8 years now at this point and let me tell you i have put a lot of work into it. every goddamned time i go out to ride it something needs adjusting, be it the brake cables, shifter cable, tire pressure, or seat position. and thats just the tip of the iceberg. i have replaced the drivetrain 5 seperate times including completely reengineering it at least twice. and if theres even a bit of rain in the forecast i have to be prepared to replace everything cuz nothing is designed to handle a bit of moisture much less the kind of loamy mud i subject it to.
    
    
    This is an independent contractor (1099) engagement on a fixed monthly retainer, roughly 30 hours in a typical month. Does that structure work for you?
    
    the only structure that works for me is completely egalitarian horizontal structures. anything else concentrates power that will eventually be abused. and the structure of most corporations, including yours, more closely resembles monarchal fuedalism than any form of democracy, much less free association. and to be frank monarchal fuedalism would be a fucking improvement., at least under monarchal feudalism i have the dignity of providing for my own and my community's survival by contributing to the grain store instead of relying on opaque and inhuman institutions for the "privilege" of keeping a roof over my head. fuck you.
    
    
    What monthly retainer would you propose for the scope described in the posting?
    
    i aint paying you no goddamn monthly fee for the "privilege" of selling you my labor. fuck you. 
    

    #copypasta #satire #moids #foids #kill #kill #oppress #liberate #righttooppress #moids #foids #kill #kill #oppress #liberate #righttooppress
  18. After a short restless sleepless night of pain the old man drags his breathless lifeless corpse out of a sunken bed of jagged shards of glassy thorny rocks and steel, unable to yet see or function as the classical music plays he drags his rigamortis laden corpse across the floor to prepare his coffee, as his hands shake and tremble he pours in the water and counts the scoops of grind, then after fumbling he manages to plug in the percolator and as the coffee begins to perc, he shuffles off to the toilet where in a hungerous ragging fit his bowels bellow out, in the mirror as he blankly stares into the abyss his reflection shows his greasy disheveled hair and beard, to tired to care he stumbles back to his bed, he struggles to pull on his pants then he slips on his slippers and pours a cup of coffee, he gently packs scraps of tobacco into his pipe and pulls on his coat, he steps out the door, the morning is dark cool and damp, as the world begins to wake not a single soul takes notice nor care for the horrish existence the old man is forced to endure yet another day;

    You can encourage my continued useless #poetry, creativity and expression of self, #commentary, random thoughts, #philosophy and ideas, and by doing so your helping to feed, house and clothe a #disabled man living in #poverty, $5-10-15 It All Helps, via #cashapp at $woctxphotog or via #paypal at paypal.com/donate?campaign_id=…

  19. I wish people could actually watch listen and read this, and with actual comprehension and compassion realize the desperate need to have people actively provide meaningful lasting support;

    The Physical Reality of My Existence

    Existence is stealing my vision, as constant pain and exhausting reign in this disabled, poverty-stricken corpse. My sight, along with the rest of me, is suffering. Some days things are clear and vibrant for a little while, but more often than not, it's all a dark fuzzy blur that often feels like a shrinking tunnel. The brighter the light the harder it is, and darker light makes fine observations impossible to see. When you couple that with my joints that are actively revolting against me, it makes the mundane an extraordinary feat.


    If I sit too long my ankles, knees, and hips lock up; if I stand too long my leg muscles all burn and become stiff. Vertigo keeps me dizzy, and sometimes between bad knees and that, I have issues walking, stooping, or bending down. My hands randomly drop things along with aching all day long, and my blood pressure is on a continuous rollercoaster. Due to poverty, I have a very poor and often absent nutritional uptake, so my body simply ages ten times faster than the average person. I tell people I am 48 but more like an 80-year-old man, and they simply cannot wrap their heads around it. It takes me an hour or two in the morning before my legs work, and often three to four before my eyes focus and my brain is fully functioning.


    The Cycle of Sleeplessness and Decline

    If I lay down in my torture device of a bed—a mattress that is 20 years old and completely useless for support, with no room for a couch or recliner to alternate to—everything goes haywire. My wrists and hands go numb as my shoulders and back ache, and trying to upright myself seems to take days. The more I do, the less I sleep. When I am past tired, I won't actually sleep at all; I will simply get aggravated by the circumstances.


    Every movement, every breath, seems to become a battle that simply lasts too long. My overall mental executive cognitive functions are declining at a noticeable rate, and my thoughts are fading and fraying more each day. It is very much tiring to be me.


    The Isolation and Misunderstanding

    I really don't feel well, I am exhausted, I am in pain, and my anxiety is bothering me. I am plum wore out from it all, and sadly, people simply do not understand, nor do they even attempt to feign empathy or compassion if they cannot express it naturally. It gets really old explaining over and over that I am disabled and I am aging, which means my disabilities just get worse.


    They see me helping and doing what I can when I can, and assume it is all easy for me and no big deal, yet have no clue of the physical pain and constant exhaustion. It is infuriating when people think you can just do A, B, C, etc., despite you making it clear you cannot. I have no family to call on and no friends to rely on.


    The Crushing Weight of Poverty

    I exist in poverty because I am disabled, and every facet of my life hangs on a precarious precipice. My tiny cave is a mess; I really need to organize and clean, but between physical energy not being there and financially not able to obtain what I need to do so, everything is chaos.


    My bowels constantly complain there is no food in here. I fight with what I can eat today versus can I afford to take a shower and will I have clean clothes to put on. From the constant need for food I can never afford, to underwear, socks, shoes, pants, shirts, and personal hygiene, there is so much I truly need and no real way to obtain any of it. My near non-existent disability income cannot cover even a quarter of life today, and I have no safety at all. For if I was an actual corpse this decay would seem okay, but as I am somehow still alive, simply existing is becoming more than I can bear.


    My Plea for Dignity and Support

    This disabled man existing in poverty is really, truthfully struggling. I am exhausted mentally, spiritually, and physically. It is imperative that I raise the money I need to buy property to build my own forever home, so that I have security and stability. I need a massive infusion of cash to get myself caught up, and then I need a monthly support amount to stay somewhat stable.


    I have never expected one person to bear the brunt of my burdens; rather, I hope that all will help how they can, with the compassion, empathy, and understanding that if it was them in need, would they not pray for the same? If only humanity was not a failure, maybe I could actually raise the money I need to live beyond barely existing. And if I am lucky, I will be able to help others through the rest of my life by having my own place to offer them the help they may need.

    I have had a very hard life. How much longer must I be forced to fight and endure an existence void of compassion, empathy, support, respect, dignity, and safety? I am begging for help to live, I am begging for compassion and dignity. Please, I am not in a good place. Please help me climb out of this hell of desperation today.


    This Disabled Man Existing In Poverty, Is $8,505 Away From Being Able To Afford To Take Care Of Myself And The Things I Still Need To Take Care Of Right Now. Your support today could mean the difference between nourishment and starvation and some kind of stability.

    This is not a request for luxury. This is a cry for dignity.

    Urgent need: $27,305, Monthly survival: $1,500, Long-term liberation: $25,000 to climb out. $5 million to build a forever home and sanctuary for others like me.
    If you’ve ever wondered what despair looks like, this is it. If you’ve ever wanted to make a real difference, this is your chance $5-10-15 It All Helps,

    🔗 Donate here: paypal.com/donate?campaign_id=… 💸 CashApp: $woctxphotog

    #MutualAid, #Disabled, #Poverty, #Help, #Survival, #Compassion, #Pain, #MentalHealth, #Food, #Groceries, #Hygiene, #Anxiety, #PTSD, #Bipolar, #Dignity, #Disablity, #Life, #Housing, #Support, #Aging, #Love, #Empathy, #Health, #Rent, #Cronicillness, #dentalhealth, #healthcare, #dental, #Emergency, #oralhealth,

  20. Reading List – 2026-10-23

    The agent stories show several ways to constrain or inspect access, from keeping credentials out of an agent’s hands to narrowing network calls and previewing tool requests. They leave a harder boundary open: what can the agent do once access is granted? I keep coming back to that gap. Elsewhere, Jev’s schema-valid output makes a separate point: valid structure isn’t evidence of a sound decision.

    1Password wants AI agents to handle logins without ever taking a peek at your passwords

    1Password’s agent model keeps the credential out of the agent’s hands: after you approve a request, 1Password fills it directly into the sign-in form. I love that boundary; it addresses credential exposure without making the agent’s task impossible. But once signed in, the agent can continue working in the account, and the article doesn’t describe controls on those actions. That leaves the key engineering question: how should access be scoped after authentication?

    Nvidia OpenShell

    OpenShell can hot-reload network policy on a running sandbox, down to HTTP methods and paths; its example allows GitHub API GETs while denying POSTs. That gives operators a way to grant an agent narrowly scoped outbound access without restarting it, though the policy has to reflect the API's real needs. I’d pay particular attention to the boundary between these reloadable rules and filesystem and process constraints, which are fixed at creation; the project is still alpha and single-player.

    Median product "lifespan" has fallen from ~4y down to ~1.5y

    The post cites a drop in SaaSHub’s median product lifespan from roughly four years to 1.5, and links it to cheap, vibe-coded launches. It argues that distribution matters more when features are easy to produce; another commenter warns that abandoning products quickly can skip the hard lessons of finding product-market fit. What catches my attention is that faster failure only helps if teams capture those lessons, so each launch needs to produce evidence before the team moves on.

    Grok Bot can now add events, set reminders, and even turn off your lights for you

    Grok can read and send messages, use location, manage calendar events and reminders, handle contacts, and control Home, with a separate Allow button for each app. That lets someone enable reminders without granting message access, a useful boundary when an assistant can both inspect information and take actions. What catches my attention is the unanswered scope of each permission: the article doesn’t say whether sending a message or locking a door requires any further confirmation.

    The Rise and Fall of Jev

    The article’s strongest engineering point is that Jev’s schema-valid output isn’t evidence of a correct decision. It says conventional language models can get the same constraint through a type checker or JSON-schema parser, while Jev does it faster and without reasoning. I like the distinction: there may be something useful under the hype, especially where local execution or speed matters, but those advantages don’t establish quality for your task. I’d evaluate it against real inputs and error costs, not its claim that it can’t hallucinate.

    Feng Shui for Robots: The Fly MCP Server

    Keeping the agent’s sandbox and production target on Linux avoids a runtime rewrite: Sprites retain files across restarts and run services. The Fly MCP server can create a Machine, volume, and secrets, while the agent brings knowledge of what it configured. Fly says there’s no universal promotion flow because each Sprite can contain a different project. I like that honest boundary; the remaining question is whether the agent can account for production requirements beyond its setup.

    Physicists Trap a Single Antimatter Particle For a Month

    Keeping a positron for a month depends on a container with no walls: electric fields confine it vertically, magnetic fields at the sides, in an ultracold vacuum. I can see why that setup sounds remarkable; it makes a particle that risks annihilation during handling available for measurement over time. The team plans to compare its magnetic moment with the electron’s, testing a precise Standard Model prediction. The trap enables that comparison, but the article reports the positron measurement as future work.

    Is this the new cyber normal?

    The hard part here is less whether LLMs change vulnerability research than whether maintainers, vendors, and operators can coordinate before a patch is usable. The PHP disclosure timeline shows how leaks and premature fixes can compress response into hours; AWS also reported seeing probing before those leaks, so better disclosure alone won't close the window. I’m probably in the author’s naive camp: coordinated security work is hard, but treating rapid exploitation as normal leaves no acceptable alternative. Teams need plans that assume exposure without giving up on improving coordination.

    Rivian buys world model startup to accelerate self-driving ambitions

    Proposal: Rivian's bet is to combine Third Dimension's AI-generated 3D worlds with real driving data, so its simulator can cover complex conditions before rare edge cases occur. The company says its customer fleet uploads more than 400,000 driving sequences daily. What catches my attention is whether generated scenes preserve the details needed for reliable validation; as more companies pursue autonomy, this is a world-model approach worth watching.

    Introducing the Gemini API CLI

    For shell-capable agents, gemini-api makes the interface inspectable before a request runs: –help, machine-readable –usage, –schema, and offline –dry-run expose commands and validate calls. Media commands write files to disk and emit only paths, while JSON, toon, and –jq keep results parseable, avoiding throwaway SDK scripts and base64-heavy context. I like that it treats output shape and offline validation as part of the agent interface, not an afterthought. Because the preview's command surface is still changing, I'd test those contracts before building a durable workflow around them.

    #Agents #AI #Developer #Infrastructure
  21. Stop sharing your credentials with agents — per-agent identity is here, and here's the order to fix things in.

    Disclosure: some links in the original are affiliate links, and we may earn a commission if you buy through them — at no extra cost to you. It doesn't change our analysis, and the security advice below is the same advice we'd give with no links at all.

    You gave an agent a job. To do it, the agent needed to log in somewhere — a dashboard, a cloud console, a bank, a SaaS tool. So you did what almost every developer has done this year: you handed it your password, or a key that works just like one. It is probably still sitting in a prompt, a script, or a .env file you meant to clean up later. That is the quiet security debt of the agent era. Your agents are logging in as you, everywhere — and the institutions on the other end have started to notice.

    How we put this together


    We based this piece on vendor launch materials from 1Password and IDENTOS, reporting by Axios on bank responses to agentic activity, and 1Password's Developer Pulse survey of developers. Where a claim comes from a vendor — launch features, plan inclusion, partner lists, survey results — we label it as a vendor claim or cite the source by name. We have not hands-on tested 1Password for Agents or IDENTOS PolicyArc; this is researched analysis, not a product review.

    Verdict


    Stop sharing your own credentials with agents, starting now. Give each agent its own identity, scoped to one task, for a limited time, with a log you can read and a revoke button that works. Per-agent identity is becoming the default — 1Password for Agents and IDENTOS PolicyArc, both launched this week, are early, concrete versions of it. Fix in this order: inventory what your agents can reach, kill shared passwords, then add scoping, expiry, and audit.

    Why banks are suddenly interested in your agents


    Start with the bank's point of view, because it explains everything else.

    According to Axios reporting, US banks are detecting unverified agentic activity on customer accounts. Chase has warned customers not to share their credentials with third-party agents. Read that warning carefully. The bank is not making a philosophical point about AI. It is telling you that when an automated agent signs in with your username and password, the bank cannot verify who — or what — is actually on the other end.

    Mechanically, the bank is right. A legitimate agent using your password and a criminal using your stolen password produce nearly identical signals: correct credentials, an unfamiliar device or location, odd hours, rapid navigation, no human typing pattern. Fraud systems were built to flag exactly that shape of activity. Your agent does not look like innovation to a risk engine. It looks like account takeover that happens to be polite about it.

    That distinction matters for you even if you never automate a bank login. The same pattern is now playing out across cloud consoles, payment dashboards, ad accounts, and production SaaS tools. When something goes wrong — a bad transaction, a deleted resource, a leaked export — the audit log will say you did it. Because as far as the system is concerned, you did. You gave the agent your identity, so every action it takes inherits your name, your permissions, and your liability.

    And developers are doing this at scale, under real pressure to keep doing it. In 1Password's Developer Pulse survey, 65% of developers said they are expected or encouraged to use AI agents. Only 33% said they have a secure way to let agents sign in. That gap — between "you must use agents" and "here is a safe way to give them access" — is where passwords end up in prompts. It is not carelessness, mostly. It is a missing piece of infrastructure. This week, two companies shipped attempts to fill it.

    The five ways agents sign in today, compared


    There are really only five patterns in use right now. They are not equally good, and we are not going to pretend they are. Here they are, worst to best, with the two launches from this week placed where they belong.

    1. Your shared password — the worst option, and still the most common


    How it works: You give the agent your actual username and password. It stores them in a prompt, a script, a config file, or its own memory, and signs in exactly as you would.

    Strength: It works with everything, immediately, with zero setup. That is the entire list of strengths.

    Weakness: Everything else. The credential has your full permissions — no scoping, no expiry, no way to tell agent actions from your actions in a log. If the prompt leaks, the password leaks. If the agent is compromised, you are compromised. Rotating the password breaks every agent using it, so nobody rotates it. If you are doing this today, you are not alone — but you should treat it as an incident waiting for a date, not a workflow.

    2. Long-lived API keys — better than a password, worse than you think


    How it works: Instead of your password, the agent carries an API key — often created under your account, often with broad permissions, often valid until someone remembers to delete it.

    Strength: At least it is separate from your human login, and most platforms let you revoke a key without changing your password. For machine-to-machine calls to a single API, this is a reasonable baseline.

    Weakness: "Long-lived" is the problem. Keys get copied into repos, CI logs, screenshots, and chat transcripts. They rarely expire, rarely get scoped tightly, and rarely have a human in the loop when they are used. A leaked long-lived key with broad scope is a password with better branding.

    3. Scoped, short-lived tokens — the right shape


    How it works: The agent gets an OAuth-style token limited to specific permissions, for a specific service, for a short window — minutes or hours, not months. When the window closes, the token dies and a new one must be issued.

    Strength: This is the pattern security teams actually want. Least privilege by default, automatic expiry, and a much smaller blast radius if a token leaks. A stolen token that expires in an hour and can only read one project is a bad day. A stolen password is a bad quarter.

    Weakness: Support is uneven. Plenty of tools your agents need still do not offer fine-grained, short-lived tokens, and wiring up issuance and refresh for every agent and every service is real engineering work. The pattern is right; the ecosystem is still catching up.

    4. Per-agent keys with human approval — 1Password for Agents


    How it works: Each agent gets its own identity instead of borrowing yours. 1Password for Agents, launched October 22, 2026, is the clearest consumer-and-developer example so far. As 1Password describes it — a vendor claim, based on its launch materials — each AI agent signs in with its own unique digital key, you approve every sign-in attempt on your own device, and the actual password never reaches the agent. 1Password lists the feature as included in its Individual and Family plans via 1Password.com.

    1Password names its launch partners as rolling out, including Meta's Muse and Grok Bot, with Claude Duet, ChatGPT Work/dots, and Townie listed as coming soon. It also says integrations are being built by Browserbase, Browser Use, Perplexity, and Ramp. Treat that partner list as a vendor roadmap claim until each integration is live and documented — but note the shape of it: browser agents and finance tooling are exactly where credential-sharing risk is highest.

    Strength: The password never reaches the agent, every sign-in needs your approval on your device, and each agent is distinguishable from you and from every other agent. Revoking one agent does not mean changing your password everywhere.

    Weakness: Human approval does not scale forever. Approving every sign-in works for high-value logins; it will chafe for agents that authenticate constantly in the background. And you are trusting one vendor's vault and approval flow with the keys to a lot of doors — convenient, and a concentration risk you should choose with your eyes open.

    5. Policy and audit engines — IDENTOS PolicyArc


    How it works: Instead of managing credentials agent by agent, you define policy in one place: who and what can access which resources, for which tasks, for how long — and you get an audit trail across all of it. IDENTOS PolicyArc, which reached general availability on October 23, 2026, is positioned exactly there. As IDENTOS describes it — a vendor claim from its launch materials — PolicyArc is one place to define, enforce, and audit access policy for people and agents, with task-specific, time-limited access grants.

    Strength: This is the enterprise-grade answer to the real question, which is not "how does this one agent log in?" but "what is every agent in this organization allowed to reach, and can we prove it later?" Central policy, time limits, and audit in one system is what compliance and security teams will ask for.

    Weakness: Weight. A policy engine is infrastructure to evaluate, buy, integrate, and operate. For a solo developer or a three-person team, it can be more machine than the problem needs today. It also only governs the systems you connect to it — an agent with your password typed into a prompt is outside the policy no matter how good the engine is.

    Our ranking, plainly: shared passwords are last, and it is not close. Long-lived keys are a distant fourth. Scoped, short-lived tokens are the baseline every developer should aim for today. Per-agent keys with human approval rank first for individual developers and small teams right now, because they fix the worst failure — password exposure — without a platform rebuild. Policy and audit engines rank first for organizations managing many agents across many people, where the audit trail is the point. Pick based on your scale, but do not pick option one.

    What to do this week


    You do not need to buy anything to start. You need an inventory and the willingness to delete some credentials. Work through this in order — and if you want a structured pass, run our Agent Access Readiness checklist on Pick a Tools alongside it, then read the broader background in our AI Agent Identity hub.

    • Inventory every agent and what it can reach. List every agent, assistant, script, and automation that signs in to anything on your behalf. For each one: what service, what credential, what permissions, who else has that credential. You cannot fix what you have not listed. Most developers find at least one agent they forgot was still running.
    • Kill shared credentials first. Anywhere an agent uses your personal password, stop — this week, not this quarter. Rotate that password, and do not hand the new one to the agent. If the agent breaks, that breakage is information: it tells you the workflow had no safe sign-in path, which is the thing to fix.
    • Scope to least privilege. For every remaining key or token, cut permissions to what the task actually needs. Read-only where read-only works. One project, not the whole account. If a platform only offers an all-or-nothing key, note it as a risk and shorten its life.
    • Make grants time-limited. Prefer short-lived tokens where they exist. Where they do not, put a calendar date on every long-lived key and rotate on schedule. Task-specific, time-limited grants — the model PolicyArc describes — are the target even if you implement them manually for now.
    • Keep audit logs you actually read. A log nobody opens is decoration. Once a week, scan sign-ins and agent actions for the services that matter: anything you do not recognize gets investigated the same day. Separate agent identities make this possible; shared passwords make it pointless.
    • Make revocation one click, and test it. For each agent, know exactly how you would cut its access in under five minutes — and actually test the revoke path once, before you need it during an incident. If revoking one agent means changing your own password and logging yourself out of everything, you still have a shared-credential problem.

    When the inventory is done, score yourself honestly with the Agent Access Readiness tool and fix the lowest-scoring area first. The goal for this week is not perfection. It is making sure no agent anywhere is signing in with your personal password.

    The honest limits


    Some restraint is warranted, because this category is three days old in its current shape and the marketing is running ahead of the standards.

    The standards are unsettled. There is no single, widely adopted protocol for agent identity yet. What 1Password ships, what IDENTOS ships, and what the browser-agent platforms build may converge — or may leave you migrating between incompatible approaches in a year. Early adoption buys you safety now at the price of some rework later. For the password-sharing problem, that trade is still worth it. For a full platform commitment, go in knowing it.

    Platform lock-in is a real risk. If one vault holds every agent key and one vendor's approval flow gates every sign-in, leaving that vendor becomes a project, not a settings change. That may be an acceptable trade — password managers already hold that position in most of our lives — but count it as a cost, not a footnote.

    Small teams may not need an enterprise policy engine yet. If you are two developers with four agents, a written inventory, scoped tokens, and a calendar reminder to rotate keys will carry you further than a policy platform you have not finished integrating. Buy the layer that matches the number of agents and people you actually have. PolicyArc-class tooling earns its keep when "who approved this agent's access, and when does it expire?" becomes a question you cannot answer from memory.

    And this is a developer story first, a consumer story later. The Developer Pulse numbers describe developers because developers are the ones wiring agents into real systems today. Consumers handing agents their banking passwords are the next wave of the same problem — which is precisely why the Chase warning matters. The tooling will follow the developers down-market. Your job is to not still be sharing passwords when it arrives.

    The bottom line has not changed since the first paragraph. Agents are useful, agents are not going away, and agents need to sign in to things. All of that can be true while "sign in as me, with my password, forever" is a bad answer. This week gave developers the first mainstream alternatives. Use them — starting with the unglamorous work of listing what your agents can reach, and taking your own password back.

    FAQ


    How do AI agents log in today?
    Most agents today log in with credentials borrowed from a person: a shared password, a long-lived API key pasted into a prompt or .env file, or a broad OAuth token. Newer approaches give each agent its own scoped, short-lived credential, or a per-agent key that requires human approval for every sign-in.

    What is 1Password for Agents?
    1Password for Agents, launched October 22, 2026, is a feature where each AI agent signs in with its own unique digital key instead of your password. You approve every sign-in attempt on your own device, and the actual password never reaches the agent. 1Password lists it as included in its Individual and Family plans.

    Why are banks flagging agent activity?
    According to Axios reporting, US banks are detecting unverified agentic activity on accounts. An agent signing in with your password from an unfamiliar location or automation pattern is mechanically indistinguishable from account takeover fraud, which is why Chase has warned customers not to share credentials with third-party agents.

    What is an agent identity?
    An agent identity is a distinct, revocable identity for a single AI agent — separate from any human user — with its own credential, limited permissions, and an audit trail. It lets you grant task-specific, time-limited access and revoke that one agent without changing your own password or breaking other tools.

    What should a developer do first?
    Inventory every agent you run and what it can reach, then kill shared credentials first. Move agents to scoped, short-lived, or per-agent credentials, add time limits and audit logs, and make sure you can revoke any single agent in one click.

    What is IDENTOS PolicyArc?
    IDENTOS PolicyArc, which reached general availability on October 23, 2026, is described by IDENTOS as a single place to define, enforce, and audit access policy for people and agents, including task-specific, time-limited access grants.

    Originally published on Pick a Tools.#security #ai #programming #devops #software #coding #development #engineering #inclusive #community
    Your AI Agents Are Logging In With Your Password. Banks Have Noticed.

  22. My love/hate relationship with Eero, and how Ubiquiti saved me $600: lexontech.org/my-love-hate-rel

  23. My lunch today was epic: the last of yesterday’s baguette toasted and served with chicken paste, mayo, crunchy chilli oil and cornichons. Absolutely delicious.

  24. My local farmer has been using a vehicle to make crop circles that are perfectly round.

    I think he has a protractor.

  25. My inner five-year-old smiled at the existence of a business called “Doudou Fragrance Cocoa Estate.”
    taipeitimes.com/News/taiwan/ar

  26. CW: NSFW

    My boyfriend loves to stretch my delicious hole out
    Video Link: playmogo.com/e/rbwa85ble4tp

    MORE VIDEO LINKS:

    gaystash.com?ref=BENO77
    and
    MyVidster:
    myvidster.com/profile/slobeno

    NO POP-UPS AND ADS:
    Use the BRAVE browser // brave.com/

  27. My controversial-not-actually-controversial take is that the Meta fine is still too small by a factor of 10, in principle the judge shouldn’t have discounted it (but I realize in practice he’s just trying to get some scrap of it to survive appeal), and if liability were actually an •existential• threat to megacorp instead of a cost line then that would mitigate a whole bunch of societal problems at once.

  28. My voice is hoarse and intermittently dysphonic at first, especially around the passaggio where it takes great vigilance at the beginning to avoid a splintering of the sound. After about twenty minutes' warmup, this is largely resolved, but it's part of a longer-term trend in which it takes longer to get a smooth flow from bottom to top of my range. Today I get up to a high Bb...

    5/

Share on Mastodon

Enter the server where you have an account.