Hi there. There are lots of phrases/patterns that Claude always uses when writing and it was very frustrating with 3.5. I can see with 3.7 those persist.
Is there any way for me to contact you and show those so you can hopefully address them?
The best thing that 'documentary' highlighted was that fishing isn't necessarily just for human consumption, there's likely a large portion of fishing that's done for feedstock of fish farms.
It's a global problem but there's one bad/reckless actor (China) that needs to better police the issue internally.
To be honest, I don't know if a 'global' effort of physically policing the oceans is possible (given they cover 2/3rds of the Earth). I do think it in the short term it will eventually come down to fishing crew being arrested and boats confiscated and sunk, with the crew being given one way flights back to their home country.
It might be watching as entertainment, but it's not really worth watching if you're looking for objective analysis. ie. https://news.ycombinator.com/item?id=26749401 (or the rest of the thread)
* The documentary distorts facts and in some cases even outright lies:
1. They claim that the oceans will be empty by 2048, but that claim is based off widely refuted (by even the original authors!) paper from 2006. A 2020 update says the global fish stocks are improving.
2. They claim that 40% of seafood caught is "bycatch", but they define bycatch as "anything that's not sustainably managed". No reputable scientific organization uses that definition for bycatch.
3. They claim 250k sea turtles are killed per year as a result of bycatch, but the source cited for this is some random blog post. Actual studies show the number is closer to 4600.
5. They claim that 46% of plastic in the ocean is from fishing nets, but that's based off a study that shows that in a specific area of the ocean (great pacific garbage patch), fishing nets make up 46% of the floating plastic.
* The documentary allege corruption but their evidence amounts to "well they could be faking the numbers". A company could be cooking the books (it happens all the time, eg. wirecard), but that doesn't mean it's a widespread practice. Independent studies have verified that msc certification is a reliable and overall beneficial program.
* The documentary's interviews are misleading because they ask simplified questions to complex problems, then play them back out of context in an attempt to create gotcha moments. The movie has received criticism from the people interviewed, even the ones that were portrayed positively.
* The creator doesn't seem to be interested in sustainability at all. In one segment he visits a bunch of whale fisherman. He concludes that the practice is totally sustainable, but he still doesn't like it and goes on to say that sustainability is not how we should care for our oceans. The documentary doesn't end with ways on how to make fishing more sustainable, it instead lists reasons why you should go vegan.
I'm seeing high CPU usage on YouTube after recent updates on Xubuntu. I think it started when they enabled GPU acceleration by default.
Previously I could watch even FHD videos without much fan noise, but after recent updates, fans spin at the max speed by playing even 480p quality vids. Anyone else?
It's very very very simple and quick, there is a video demo and a text explaining what to do, and then you can open a bug at https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&comp..., with the profile link (you can login with a github account or email). This will be triaged and hopefully we'll understand what's up. Please use a Nightly build or a Mozilla-provided build when doing so (so there are symbols). It's just a matter of downloading and untaring the tarball.
Please also attach a copy of `about:support` raw data (button at the top), so we can understand what your configuration is: desktop Linux systems can be pretty diverse and sometimes it isn't clear what works, what doesn't and why.
If you're playing 480p, then youtube might be serving you AV1, and this is (for now) using the CPU (trading a lot less bandwidth for increased CPU usage), you can check the codec it's using by right clicking on the video and clicking on `Stats for nerds`, there is the codec string. You can adjust your codec preferences in your youtube profile I believe.
Just did some tests on Firefox 83 and DOM reflow time grows exponentially with the depth of DOM tree. With grid elements of depth 10 single reflow takes seconds on my Ryzen laptop while on chromium is not noticable at all.
GPU acceleration is not a magic bullet it seems. In our case drawing large SVGs suddenly becomes really slow when GPU rasterization is enabled. Chrome has the same problem. I really hope we will see more polishing in this area and maybe a cooperation between Chrome and Firefox developers?
Thing is, when I play the same video with VLC which uses HW decoding, it doesn't even break a sweat. So I think there might be something wrong on the browser part...
There could be something related to FAN thresholds that resides in BIOS directly thus starting using GPU just slightly over some minimal limit might raise FAN speeds significantly and not be related to temperature raise as there is some inertia between temperature readings and real temperature inside GPU core.
I'm also experiencing FAN noise raise on my Ryzen APU based laptop.
i mostly stopped bothering with in-browser video when mpv wiht youtube-dl integration came around. either drag the url to the player window or use an open-with addon.
This particular example is only slow on Chrome. Even if you move the edge of the shape into the viewport Firefox is much faster than Chrome. But I know from real life examples that Firefox becomes slow if handling large SVGs. I will have to investigate this and file a bug report.
I checked again with our app on Firefox and performance is not that bad. Rendering gets a slower with large SVGs, but it is still good and there is not much difference between hardware rendering enabled and disabled. So I was either wrong about slow performance on Firefox or things have improved recently.
I'm on Linux. I stubled on webrender from a blog yesterday, and enabled it. My observation was the same - high CPU usage, so I then disabled. Got 84.0 today, and gave it another go. It appears to be behaving well so far. So I'm guessing there was some fix in 84.0 that made it work for me.
Yep. We've seen bugs with different window managers so WebRender is only enabled in Gnome in 84 to minimize the risk of breakage. This restriction will be removed in subsequent releases.
Also, we have it enabled in nightly and beta for many more configurations already :). There are many bugs to fix, but we're working through them. This is the exact same treatment we gave Windows and OSX in previous releases this year.
I know the usual rational about users blaming Firefox and yadda yadda but I am rather not convinced this is how things should work in the open desktops. If there are clear bugs in other environments, file them and break them if necessary. The only potential exception I can see is when it's not clear if it's a bug or not..
Yeah, that seems odd. I wonder if the update doesn't help/involve Weyland people, and if GNOME is an X11 holdout? I haven't been paying enough attention to know.
Same as the others.
Using antergos/manjaro as my daily driver on different machines ( PC/laptop/server ) for 4+ years now, and I am more than happy.
I used ubuntu, xubuntu, elementary, mint and others before. Once I found antergos I stayed with arch-based distros.
Quick releases of new software is amazing.
I've had very few issues and when they are appear it's usually solved within hours.
I love the rolling updates, and the wiki is really helpful and easy to read/navigate most of the time.
