Difference between revisions of "AI in the Browser"

From MgmtWiki
Jump to: navigation, search
(Created page with "==Full Title== AI is getting added to everything, including the Web Browser, which will have some severe unanticipated downside for the user. ==Context== Google has been tryi...")
 
Line 1: Line 1:
 
==Full Title==
 
==Full Title==
 
AI is getting added to everything, including the Web Browser, which will have some severe unanticipated downside for the user.
 
AI is getting added to everything, including the Web Browser, which will have some severe unanticipated downside for the user.
 +
 +
Author: Tom Jones 2024-09-21
  
 
==Context==
 
==Context==
Google has been trying to make web apps, that are downloaded from web sites, as attractive and useful as native apps, that are downloaded from the app store.
+
Google has been trying to make web apps, that are downloaded from web sites, as attractive and useful as native apps, that are downloaded from the app store. Now that AI is getting added to
 +
 
 +
==Problems==
 +
 
 +
===User Profiling===
 +
 
 +
===Prompt Injection===
 +
 
 +
===Cycle Stealing===
 +
Optimization of web sites has long included pushing more of the web site code into [[JavaScript]] which runs on the browser both to make the site more responsive as well as to reduce the compute load on the server.  For the point of view of the web server, cycles on the browser are free compute resources.
  
 
==References==
 
==References==

Revision as of 07:47, 21 September 2024

Full Title

AI is getting added to everything, including the Web Browser, which will have some severe unanticipated downside for the user.

Author: Tom Jones 2024-09-21

Context

Google has been trying to make web apps, that are downloaded from web sites, as attractive and useful as native apps, that are downloaded from the app store. Now that AI is getting added to

Problems

User Profiling

Prompt Injection

Cycle Stealing

Optimization of web sites has long included pushing more of the web site code into JavaScript which runs on the browser both to make the site more responsive as well as to reduce the compute load on the server. For the point of view of the web server, cycles on the browser are free compute resources.

References