SoylentNews is people
SoylentNews
New AI-powered web browsers such as OpenAI's ChatGPT ATLAS and Perplexity's Comet are trying to unseat Google Chrome as the front door to the internet for billions of users. A key selling point of these products are their web browsing AI agents, which promise to complete tasks on a user's behalf by clicking around on websites and filling out forms.
But consumers may not be aware of the major risks to user privacy that come along with agentic browsing, a problem that the entire tech industry is trying to grapple with.
Cybersecurity experts who spoke to TechCrunch say AI browser agents pose a larger risk to user privacy compared to traditional browsers. They say consumers should consider how much access they give web browsing AI agents, and whether the purported benefits outweigh the risks.
[...] There are a few practical ways users can protect themselves while using AI browsers. Rachel Tobac, CEO of the security awareness training firm SocialProof Security, tells TechCrunch that user credentials for AI browsers are likely to become a new target for attackers. She says users should ensure they're using unique passwords and multi-factor authentication for these accounts to protect them.
Tobac also recommends users to consider limiting what these early versions of ChatGPT Atlas and Comet can access, and siloing them from sensitive accounts related to banking, health, and personal information. Security around these tools will likely improve as they mature, and Tobac recommends waiting before giving them broad control.
Based on these concerns, would you use such browsers ?
(Score: 2) by krishnoid on Monday October 27, @06:25PM (1 child)
That's +1 amazing. You're using Claude for this?
(Score: 5, Informative) by JoeMerchant on Monday October 27, @07:08PM
Yes, claude code for home projects and cursor for work projects - they're remarkably similar - both are using Sonnet 4.5.
Ask me about AI writing code a year ago, I would have told you it's slightly more convenient that Googling the answers yourself.
Whole different world today. The home app is building a music player, lots of fancy automatic next song selection features based on AcousticBrainz... so far the audio playback mechanism is done with all kinds of programmable crossfade at the transitions, a http served developer's UI that shows the queue, decode buffer fill status, parameter editor for 26 kinds of playback variables (buffer refill period, hysterisis thresholds, etc.) resampling to handle input files with varying sample rates, pause with fade-in resume, queue management, skip, remove, etc. and all the hooks needed for the rest of the system. That took less than a week. An auto-tuner module that determines optimal buffer depths for gap free playback with minimal startup lag took about an hour this morning.
🌻🌻🌻 [google.com]