Re:Firefox browser falls to AI. What do we do now?
by Bender on Monday December 29, 2025 @11:58AM
(#46422586)
What do we do now?
- Build some bare-bones simple UI wrappers in front of a.k.a. to drive curl [1]. Give it just enough capability to run uBlock Origin and NoScript. Add a simple menu of checkboxes to enable/disable any protocol and some RFC's like HTTP versions, CSS, ecmascript, etc... (Only features listed in 'man curl') Support a ~/.config/ui_name.conf and global /etc/ui_name.conf to enable and or disable curl features.
- Maintain a IP/CIDR/DNS blocklist of AI endpoints. DNS for those behind a shared CDN. Option to curl download selected blocklists so we do not even gethostbyname their names. Perhaps this might even deprecate the need for uBlock and NoScript if some of those features are in the simple UI front-end.
- Build some bare-bones simple UI wrappers in front of a.k.a. to drive curl [1]. Give it just enough capability to run uBlock Origin and NoScript. Add a simple menu of checkboxes to enable/disable any protocol and some RFC's like HTTP versions, CSS, ecmascript, etc... (Only features listed in 'man curl') Support a ~/.config/ui_name.conf and global /etc/ui_name.conf to enable and or disable curl features.
- Maintain a IP/CIDR/DNS blocklist of AI endpoints. DNS for those behind a shared CDN. Option to curl download selected blocklists so we do not even gethostbyname their names. Perhaps this might even deprecate the need for uBlock and NoScript if some of those features are in the simple UI front-end.
- Let curl handle all the network functions.
[1] - https://curl.se/