Merry Christmas to /jp/ from /g/!
>>14525466
Ｍｅｒｒｙ Ｃｈｒｉｓｔｍａｓ ｆａｍ
>>14525466
fuck off faghag
thanks senpai
>>14525466
makifag?
>>14525466
Hey, /g/ why does FF suck monkey balls now? They should bring back that fagphobic guy. At least he knew what he was doing.
The "browser situation" in general is just depressing... Firefox has been hot garbage for at least a few years now, at least since the big Australis update. Its gotten so bad that IE is viewed as a superior alternative to it or chrome...
>>14525511
Try Qupzilla
Merry christmas free software man.
>>14525511
http://zacbrowser.com/
Thank you /g/.
Just ignore all the rude /jp/ shitposters on this thread.
>>14525511
What are you, a Microsoft shill spreading misinformation?
>>14525466
arigatou gentoo-kun
kuso thread
>>14525776
Maki smells
>>14525808
kuso post
>>14525466
Thanks
>>14525893
...good!
>>14525511
>>14525491
I still like firefox
>>14525974
i switched over to chrome when firefox's bloat and instability finally made me mad enough. it won't let me set my new tab page to an html file but otherwise i have no complaints.
>>14525976
I don't experience any of the problems you describe to be honest
>>14525982
yeah i've noticed that about half of the people i've talked to experience the issues i got, and the other half don't. i wonder why.
>>14525988
I'm still of the opinion that such issues can be solved through programmers volunteering their time to creating a better open-source browser.
>>14525995
>programmers
>volunteering
holy shit, no. as long as I can make the equivalent of $200/hr for bugfixing phone apps, I know where my free time is going.
>>14525488
No, just a secret admirer...
>>14525976
I can't trust Chrome (or derivatives) at all. Look at this bullshit:
http://rpw.sh/blog/2013/06/11/postpwnium_writeup/
https://code.google.com/p/chromium/issues/detail?id=64229
TL;DR sometimes (due to a race condition) the framework can't accurately determine the domain it's on when checking for plugin authorization, getting NULL instead of "foo.google.com" or such. So instead of fixing the issue, they said “Let's just always default to TRUST when we get a NULL hostname.”.
That's just one bug (which is probably fixed by now, since it got attention), but any developer team that is comfortable with that thought process is not a team that I want writing my browser.
When I saw that, I started looking at webkit-based microbrowsers instead, but the Webkit codebase is a 2G+ ratsnest of codecs and libraries and "features" you can't turn off (last I tried, disabling geolocation/webgl just made the build fail). How do I know their sandbox is good enough? How do I know they don't accidentally include an exploitable codec?
The whole situation is completely pathetic: there are no major web browsers whose code I can trust, and vettable browsers don't implement enough javascript to handle things like posting on 4chan.
>>14526015
plugin authorization/signing is a shitty ``service'' anyway, but yeah that's a silly workaround.
>>14526009
Whatever happened to the values behind "free as in freedom"? Are we all willing to lie down and accept the tyranny of proprietary software when it pays us to do so?
>$200/hr for bugfixing phone apps
Haha, yeah sure. You have an invoice to prove that?
>>14526034
Oh, right, you reminded me of Mozilla's latest attempt to shoot themselves in the foot. As it is, I've had to skip the last two or three upgrades because they can't be bothered to fix https://bugzilla.mozilla.org/show_bug.cgi?id=1174997 .
It used to be better than this.
>>14525647
>ZAC Browser (Zone for Autistic Children) is a web browser designed specifically for children and teenagers with autism and autism spectrum disorders
>>14526072
So...I should probably have auto-update turned off?
B-but Chrome-kun is a steaming hot mess of a wreck as well, plus "muh botnet." What to do? Maybe I should sign up for a service that mails me print-outs of the best shitposts on /jp/ via surface mail every day. Completely safe, plus no more fucking CAPTCHAs. Ping time would be god-awful though
>>14526090
There are no good answers these days. Update regularly and be subject to whatever feature removal and bullshit UX the dev team decides. Freeze updates and be subject to security flaws.
>>14526112
Freezing updates and disabling JavaScript/plugins should keep you safe from most security flaws.
>>14526129
>disabling JavaScript/plugins
This also breaks a lot of websites, including some that I have to use for work.
>>14526174
The NoScript addon let's you whitelist sites.
>>14526177
It doesn't really help when so many sites outsource all their JS to some cdn. It's not very helpful when a site doesn't work and you check NoScript and your options are dw11hjcex0uqb.cloudfront.net and ec2-some-ip-address.compute-1.amazonaws.com. We're almost back at square one with the options “Don't use the site” or “Use the site”.
Also, the thing that I'm worried about is bugs in the browser. I don't trust the "disable plugins" button. I don't trust the sandbox. I don't trust the webm player. I don't trust the whitelist (see the above Chrome bug).
>>14526224
>It doesn't really help when so many sites outsource all their JS to some cdn
You can use it in conjunction with requestpolicy to whitelist which sites can load scripts from that cdn.
>>14526237
That's not my concern. Suppose I examine a site and see three cloudfront scripts. Which one is required for the site to operate, and which two are useless scripts that I shouldn't trust?
Also, the thing that I'm worried about is bugs in the browser. No amount of javascript/plugin protection would protect you from CVE-2015-2710 or CVE-2014-1576 (as I understand them).
>>14525466
https://www.youtube.com/watch?v=u9HWcFl41Xw
>>14526277
Use uMatrix and run Firefox within Sandboxie or a VM that you restore regularly.
>>14527083
When this is the only acceptable solution to the question “How do I browse the world wide web?”, I think I'm safe in saying that “The whole situation is completely pathetic”.
Bump! Merry christmas minna!
>>14526015
Complain about popular thing number 1
Complain about how small niche things sucks
This is how you post when you want replies on /g/, take a note lads.
