yeah. a male loli.
saged and reported
Reviving Fiber
William Cruz
Lincoln James
>the milquetoast (((Holla Forums)))tard fears the anime
Aaron Rivera
It's called uzbl
sage for browser thread, stop bumping these
Christian Sullivan
Hi, Idea Guy™, I'm Logo Guy™.
I'll get started on the logo ;^)
James James
> en.wikipedia.org
Well so much for that one. Next!
Colton Gray
Browser threads are a Holla Forums tradition at this point,
Wyatt Gray
I see. You're one of (((those))).
That does sound pretty good, but it would be pretty hard to make it work. How would you prevent conflicts, and plugins that affect the behavior of other plugins would probably have to be dependent on the plugin that it's compatible with unless there was a clear and enforced standard to ensure modularity. Also, you know that if it caught on the kikes would try to test what plugins you have installed, and they would make proprietary plugins required to use their sites and it would be shit all over again. At least it would solve the problem of different browsers having cool shit but also having cancer, and being unable to just have one godly browser just for you.
Benjamin Edwards
Look at the shills go on this thread.
Yes, absolutely, we need a browser where you can choose what parts actually run, more granular than being able to just toggle JS on and off. Something which could be used to prevent (((tricks))) but still provide a usable experience even on pages like Youtube.
In my mind it could use youtube-dl and other such tools to get at media normally hidden under megabytes of coin-mining JS, and possibly present itself (to the server) as some normalfag browser but only running / displaying the text, images, and videos directly.
Let's break web 2.0.
Owen Richardson
Is this a good imagining of how a basic browser built in such a way would work?
Obviously its just a simplification, but it has the general idea. You could take an example from how windows and X11 work, in that they have either "events" or "messages", and then a program will have a blocking function like this:
while(get_message(&msg)){ switch(msg.msg){ case HTMLR_NEW_HTML: render_html(); break; default: break; }}
Basically, the whole idea is that everything you do is in response to some kind of message passed to you by another component.
Brandon Mitchell
The trick is to use the components, libraries, etc. which are already available and just glue 'em together. I don't even know if we want an HTML renderer, we could do the whole thing in Emacs (for example only), stripping out the useful text and images from the HTML and rendering them in some sandbox where no actual downloaded code is running would be ideal.
I don't want to be overly critical, there's no reason why this thing can't be modular as heck and have different 'front ends' from a full blown CIA nigger Firefox Quantum front end to just a plain ass text window.