The world ends not with a bang, but with a “you’re right, I shouldn’t have done that. It’s right there in my agents.md file.”
replyAI Session Hijacking is such a dead end and I think this will be the thing that kills it. Just register these things in the IDP and let them sign into their own accounts.
replyMaybe if we give these things their own identity people will stop letting their AIs post as them in linkedin
> Just register these things in the IDP and let them sign into their own accounts.
replyAnd when you get blocked by whatever anti-bot tech the site is running?
Not sure I understand the point your are making. how is this unique for bots with their own identity? Bots hijacking a user session can also be blocked
replyBots skinwalking their users inherit the behavioral scoring of that user. As a rule, they'll take a lot longer to get blocked than new bot accounts would.
replyBut then whoever added them to the IDP becomes accountable for what the bots do.
replyBy hijacking a real person's credentials, that person becomes the accountability sink. Very neat. Very deliberate.
I assume they store your session state/token for whatever SaaS it needs to work with but not the creds.
replyMany people assumed they didnt upload your whole home dir when you launched their IDE
replyYeah, assuming that X is doing the honest and well-behaved thing is a mistake given their past actions.
replyit's crazy that we have multi-user computers and all this permission stuff on linux and none of it is used
replyWell, it's the "Everything App" after all!
reply/s
[flagged]
replyWhat? How? Just the x.com creds or other ones too?
reply