Leaderboard

Another reason to avoid QUIC. https://msfn.org/board/topic/186119-youtube-stutter-in-edge-fix-disable-quic-protocol/

When these empty files noop.txt and noop.js are returned, will they be stored locally on the computer? Where are they generated at all? And what exactly means local in this context? Local file on the server, local file on the client/computer? In any case, I couldn't find such files. TBH, this all is a bit confusing.

Hello @Felipefpl! Do once again a clean install! That means you have to manually delete the file ublock0.sqlite inside your profile subfolder extension-data. But don't forget to backup your settings and rules first! BTW, I tested updating from version 1.16.4.33 to version 1.16.4.34 and didn't notice any problems when doing this with the alternative method.

As we already know, QUIC brings nothing but troubles! This wonderful solution to fix video playback worked for me as well, and I want to share. Tried all the standard solutions, reinstall, disabling hardware acceleration, clearing the cache, none of it worked. Then I found the following solution: edge://flags/ and setting Experimental QUIC protocol to disabled. Everything is now working perfect for me now. sourced from Reddit users. https://www.reddit.com/r/edge/comments/12u35dr/youtube_video_streaming_stutter_in_edge_possible/

I was under the impression even posting of non-https links was blocked here.

First of all, I think it's right and good that someone other than myself is also working on the great and very important extension uBlock Origin Legacy and developing it further. Since nothing has happened for years, I see my efforts here in relation to uBlock Origin Legacy as a kind of initial spark to maintain this extension again and bring it up to date. Based on the way a well-known American moron speaks I would say: "Make uBlock Origin Legacy great again!" @UCyborg has started a promising project on GitHub. I already had a look at it. An indirect collaboration has already taken place, as he has used my internal list of all standard filter lists, i.e. the assets.json file, as the basis for his one. But I cannot and will not comment on direct collaboration at this point. In any case, I will continue to maintain my version here for a while. The next version is coming up very soon. This means that the user now has the option of choosing their preferred version. As I have already said between the lines, a wider range of products generally stimulates "business". Cheers, AstroSkipper

Beta Centauri

Should be better than later ones, No conflicts with motherboards. In inf - replace 0FEC with 128B.

As https://wiki.documentfoundation.org/Documentation/System_Requirements stated the last version for WinXP should be 5.4.7.2, but after I installed it, run any application would give a "use CTRL+C to exit" error: The error is like those which do not support WinXP. Is my system have any problem, or the official statement could be wrong?

Technically, they're not really conventional files for main part of the operation, they live as memory resident data structures that can be obtained using a name resembling a file name, basically JavaScript Map containing a bunch of objects, each containing MIME type, encoding and the actual data. Initially they're read from assets/ublock/resources.txt in the XPI file, on subsequent extension startups they'll be read from the ublock0.sqlite database most of the time. These resources are updatable via online repository in these older versions. You'd have to set that setting in the older version as well if you wanted the exact same behavior in that regard. Redirection concept was introduced in version 1.4.0. "uBlock filters – Ads" filter list for instance has more filters using "redirect-rule" rather than "redirect". "redirect-rule" by itself doesn't do anything, it's only effective in combination with another blocking filter, that's the difference between the two.

@UCyborg I know you have implemented the "redirect-rule" directive in your new release. But if one wants to make your version 1.16.6b1 not perform such redirections, the entry ignoreRedirectFilters can be set from false to true in the advanced settings. Then your version 1.16.6b1 will behave like version 1.16.4.30 up to 1.16.4.34 again although this entry has the default value false in these versions which I never had to or intended to change. But when doing so, these strange noop.txt and noop.js entries are no longer in the logger. The network filter @@*$redirect-rule was only introduced in version 1.22 and therefore cannot be used. Although I understand the idea of such redirections, especially to prevent breakage of websites when blocking certain content, these entries in the logger do personally bother me if I am honest.

Off-topic, but here you are! Launcher.zip Remember that it's 16 bit and therefore won't work on a 64 bit system.

When using my updated, fixed release uBlock Origin Legacy 1.16.4.34, then there are no network connection errors anymore. Have a look at my release!

The filter list of version 3.6.3.2 still works on www.nytimes.com. Just tested. The last version Paywall Pass 0.0.3.1 does not work (anymore? I can't judge it ) on www.nytimes.com, unfortunately. Just tested. And TBH, this extension has not been updated since 2015. Any kind of such technology is subject to a game of cat and mouse. The one who is more up-to-date is ahead for a short time. But thanks for pointing to this extension anyway!

Thanks for clarification! And indeed the entries generated by the logger of your version were strange and led to a slight confusion for me.

Thanks for that! Such files are worth to backup and prevent them from disappearing.

Hello @UCyborg! I have just tested your new release uBlock Origin 1.16.6b1 by using the ad block testing site https://test.adminforge.de/adblock.html. While my release uBlock Origin Legacy 1.16.4.34 blocked all ads with a score of 100%, your version wasn't able to do this and got a score of only 84%. The comparison was done using the same filter lists and same own filters in both versions. I was checking the performance of both releases with the uBO logger to see what's going on and noticed entries about noop.txt and noop.js in the log generated by your release which I didn't get when using my release. As far as I know, noop stands for no operation. One consequence of this is that some of my own filter rules under the tab "My rules" are simply ignored when using your release. Any ideas what your release is doing on this ad block testing site? Here is a screenshot testing uBlock Origin Legacy 1.16.4.34 in New Moon 28: And here is a screenshot testing uBlock Origin 1.16.6b in New Moon 28: Cheers, AstroSkipper

Update notification! - uBlock Origin Legacy 1.16.4.34 - Special mod by @AstroSkipper I have again updated my special mod uBlock Origin Legacy from version 1.16.4.33 to version 1.16.4.34. Starting with this version, installing over an existing installation of uBlock Origin Legacy (1.16.4.34 and higher) is completely working again. The immediate loading of the updated, internal list of all preselected filter lists (assets.json) can be triggered by the function "Purge all caches" or "Update now". From now on, the user will get the internal list of all preselected filter lists (assets.json) automatically. And I added new filter lists to different groups. More details can be found in the changelog in my main article, and of course the download link. The update to version 1.16.4.34 should be done as already described, but this time for the very last time. The easiest way is the alternative method: Backup all your settings using the "Back up to file" button on the page "Settings". Install the new version of uBlock Origin Legacy over the existing one. Reset your installation using the "Reset to default settings" button on the page "Settings". Restore all settings from your backup file. Cheers, AstroSkipper

Cosmic Energy https://www.yogapedia.com/definition/5811/cosmic-energy

The Shih Tzu (UK: /ˌʃiːˈtsuː/, US: /ˈʃiːtsuː/;[1] Chinese It's a toy dog or pet breed originating from Tibet https://en.m.wikipedia.org/wiki/Shih_Tzu

I wouldn't risk my computer with the officially proven to be compromised browser. In the comments they wrote many other nasty things it does, in addition to what already been found, but of course, everyone decides for himself. The Reddit community advises to delete it. Are the just stupid? I don't think so.

Alpha Female

Compulsive Behaviour

Another nice variant, fully working in Serpent 52, is the extension What about:.. 4.15 which can be also downloaded from the Classic Add-ons Archive.

Dark.

Mark.

"I block it...it's proxy avoidance." https://www.reddit.com/r/cybersecurity/comments/wiquz1/with_quic_what_is_going_to_happen_to_firewalls/

"I just block it, source browser detects that quic isnt working and reverts to ssl instead. Easy" "Just block it where you need full visibility. Probably in the future vendors and sec-experts will come up with something to work with QUIC." This article on Reddit.

What about the fan? Or it's a passive card? If it's passive, try to put a vent near it. Passive cards reaching 90C are common. Max allowed for Kepler is 95 (shut down temp).

GTX 750 is a rare, odd beast. It belongs to a different (newer) gen., despite being among the old Kepler 700 series, it explains the lower temps and better seeking perfectly fine. https://www.techpowerup.com/gpu-specs/geforce-gtx-750.c1986

Sacred 2 (2008) - but of course it can be disabled. Yet the bundle still needs to be installed. Rolling corpses and magic projectiles rely on Physx. Much better than Diablo III.

It's because the driver branch is higher than 344. (R343) This one is branch R346. Abd don't worry about Physx, it will work. 347.26 - Branch [r346_00-270] https://forums.guru3d.com/threads/geforce-icafe-347-26-whql-driver.396457/

These temps are related to the B1 revision of your card. I had two GTX780 with A1 and B1 revisions. A1 was cool and silent. B1 was hotter and noisier. Also, it had a tendency to crash with newer drivers after 347.26. That's why I know the problem, You can try to replace your cooling solution or apply MX4.

It's a very well known issue with all nVidia drivers after 347.xx and old motherboards. https://forums.guru3d.com/threads/gtx-560-point-of-view-games-crash-with-drivers-newer-than-347-88.441449/