Eh, I'm willing to take a few downvotes if it means raising awareness. I tag pretty much every Firefox post with some sort of report on battery life. I've added bug reports... doesn't ever seem to get taken seriously. Like I said I'm OK with taking a few downvotes on the off chance someone on the Firefox team may actually see this and be able to prioritize work to address the issue. Firefox is my primary browser, but…
Isn't it less work to do the bug report in the proper place than post about everytime in half-related threads? You could even send it as its own post to HN to do the raise awareness part.
I hear this, but also it works fine in Safari... and even less bad in Chrome on a MBP. Not an expert, but that makes me think there's something the Firefox folks can do to improve this issue. If they wanted to. It's not like 2x, it's like 40x more power used. This makes the MBP super heat. Thing was never cool to start, but I suspect it's getting hot enough to shorten the battery life. It's really hot. Happens on eve…
Well, it's much easier for Apple to get the optimizations on their hardware, drivers, OS, and web browser to all line up. There are some benefits of the cathedral. However, I agree with others that there may be an actual bug going on. There are definitely listings in Bugzilla for WebRTC bugs[0], the oldest of which is 7 years old. I'm curious if you're just seeing high battery usage, or is there high CPU as well? [0]…
CPU goes up some, but not a ton. Like it's weird. It really just super heats my computer, fans go to max RPM, and burns battery like there's no tomorrow... but I don't see CPU usage off the charts -- it's using CPU more than Safari or Chrome would, but doesn't seem like CPU is maxed. It's like it just gives the instructions, "Heat up!" I don't know, like just grab a MBP and try a call. Happens on all of them I've tried it on. 2019 MBP 16" is my daily computer, and the one I have the most issues with. I had a 2017 (Maybe 2016? First model with butterfly switches) and it happened there too. Happens on the 13" MBP I got form work. Happens on my girlfriends MBP 13" with the M1 chip, but it's not nearly as much of an issue as the Intel Macs.
Exactly - why do I as a user want this? I already need an extension to fake the Referer...
How can you be sure you actually need to send a Referer header. Whats the (user) benefit of sending one. I never send Referer and I have never had any problems as result. I remove unwanted headers from requests generated by user agents I cannot adequately control, e.g., graphical web browsers, using a loopback-bound forward proxy. Perhaps this will be another one to remove.
Some websites (IIRC twitter does) open link differently based on the referrer header, so automatically sending a twitter referref for all twitter links improves your experience.
How is this different from the origin header? Does the origin header not tell the webbserver if the requested originated from the same website? Is the origin header flawed in some way?
> Is the origin header flawed in some way? tl;dr yes. It's not always sent.
This is true. Could we not disregard requests without an origin header?
According to [0] we can force CORS behaviour be using a non-simple request in our webapp. By setting the mime type to JSON for example.
For me, recent firefox releases have been MISERABLE. I guess it could just be my computers but the browser constantly locks, no performance whatsoever, and just no help on troubleshooting anywhere.
I went with the long term support releases and have had a better experience. Course, still no sound lol but I use Chrome when I want sound. I still like Firefox, just can't use recent releases.
Well, it's much easier for Apple to get the optimizations on their hardware, drivers, OS, and web browser to all line up. There are some benefits of the cathedral. However, I agree with others that there may be an actual bug going on. There are definitely listings in Bugzilla for WebRTC bugs[0], the oldest of which is 7 years old. I'm curious if you're just seeing high battery usage, or is there high CPU as well? [0]…
CPU goes up some, but not a ton. Like it's weird. It really just super heats my computer, fans go to max RPM, and burns battery like there's no tomorrow... but I don't see CPU usage off the charts -- it's using CPU more than Safari or Chrome would, but doesn't seem like CPU is maxed. It's like it just gives the instructions, "Heat up!" I don't know, like just grab a MBP and try a call. Happens on all of them I've tri…
Well, if the fans are spinning, it heats up, power is drained, and the CPU usage is fine... it's gotta be the GPU. There's only so many things in the system that can use power and generate heat, after all.
I don't know enough about MBPs of that age, but I'd guess they have discrete GPUs and it's those are running. I wonder if you'd be better off disabling GPU optimizations, or if there's a codec issue of some kind.
How can you be sure you actually need to send a Referer header. Whats the (user) benefit of sending one. I never send Referer and I have never had any problems as result. I remove unwanted headers from requests generated by user agents I cannot adequately control, e.g., graphical web browsers, using a loopback-bound forward proxy. Perhaps this will be another one to remove.
Some websites (IIRC twitter does) open link differently based on the referrer header, so automatically sending a twitter referref for all twitter links improves your experience. There might be more critical uses
Twitter does not require a Referer header to return user-generated content ("tweets").
Sending a Referer header does not improve [your] experience. It is the opposite for me. I cannot tolerate Twitter's Javascript, I do not use a graphical browser. I find it annoying when people submit Twitter status messages to HN.
I have a script that reformats the JSON into a simple HTML page with no Javascript. This improves the experience for me:
Does that mean that the quest of finding a working direct link to the image/video will soon become impossible?
If site producers want to it's already pretty much impossible today. At least without some "tricks", and nothing prevents your video-downloader from just adding a header which pretend it's origin is a website. (Or more funny you inject the downloading JS code into the website in question extending it with a download functionality ;=) ).