@brentsimmons This would be an awesome web. I will toss my penny into that wishing well!
Hmm. Ads rendered on the server would be harder to block, too. We might need to be careful about these wishes.
@brentsimmons Iām fairly certain it was possible to do the cookies part in Camino; one of our team members liked to browse that way. (It was not user-friendly; there was no real UI, you had to jump through hoops to allow sites, and IIRC we had to egregiously abuse the not-designed-for-actual-humans Gecko cookie API to do so, butā¦.) The JS part maybe could have been done with CAPS, but that component was an even worse mess and got deprecated.
Itās clear that a lot of the fundamental behavior assumptions of browsers need to be rethought in light of todayās abusive behavior by surveillance capitalistsābut the problem always comes in making the changes in a user-friendly/understandable way and without breaking all sorts of websites :-(
Many sites already have āserver-sideā ad code in a noscript
tag for JS-less situations; you can usually block those easily enough with CSS or a content-blocker for the image domain. // @fgtech
@jasonekratz You can whitelist the baby! Otherwise, yes, Iām pretty happy with taking the web back to theā90s.
@brentsimmons makes sense to me however building my main stuff these day in Vue I feel conflicted šš¤Ŗ
@adamprocter Kind of a cars vs. trucks situation. I think Brent is spot-on with the functionality; but that it should be something a power-user can turn on for themselves, e.g. "Enable Fast and Private Web Mode?" I don't do any virtual DOM (yet) but I'm sure it's in my future if I want to keep making a living building websites.
@brentsimmons I agree. I have been using the NoScript plugin for Firefox which gives you this control.