AstroSkipper
Content Type
Profiles
Forums
Events
Everything posted by AstroSkipper
-
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.
-
Please re-download the file uBlock-Origin-Legacy-1.16.4.34-special-mod-by-@AstroSkipper.xpi if you have already downloaded it and have fun! After installing, click the button "Purge all caches" if installing over the previously downloaded version 1.16.4.34! Cheers, AstroSkipper
-
That was totally clear to me and I didn't expect anything else. But the list can still be useful for a while.
-
I have just copied my previously downloaded list from my installation with the version number 3.6.3.2. Therefore, this last version can't disappear.
-
Yep! This user has been blocked. Thanks for pointing to this issue! If this list doesn't appear anymore elsewhere, then I will have to remove this list from my release again, for better or worse.
-
Glad it works. I hadn't any problems when updating this filter list, though. When I am back at my Windows XP computer. I will have a look at this.
-
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.
-
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
-
I do know that CSS styling can also be done inside a JavaScript file. But separating the CSS code in a css file is the usual way when loading files from the chrome folder. Doing so the different CSS styles can be easily enabled or disabled and therefore managed by the userchrome.css file regardless of the script files.
-
You're welcome! This is what I understand by the term autoconfiguration: https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig My package MYPAL_68_CB_requirements.7z contains configuration files as the prerequisite for loading script and css files. Although these files are loaded automatically when starting the browser, the creators of these configuration files do not use the term autoconfiguration at this point. This is merely a question of defining the term.
-
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
-
My Browser Builds (Part 5)
AstroSkipper replied to roytam1's topic in Browsers working on Older NT-Family OSes
As far as I know, Serpent 52 gets more patches from the UXP branch than Serpent 55. The reason for that is not all of these patches can be applied to Serpent 55. Therefore, Serpent 52 is a bit more up-to-date. But @roytam1 and @VistaLover can tell more about that. And if I remember correctly, they already did that in @roytam1's browser threads in the past. -
No, I do not use the property window.status. The script code for creating such a status bar has not grown out of my own hands, though. I simply took over an old script which is still working in Mypal 68. TBH, there are a couple of scripts but most of them are not compatible with Mypal 68. My part was finding working code. And that wasn't so easy due to the age of Firefox 68. Many scripts targeting this Firefox version have been lost or replaced by newer ones. However, I modified the css file for exact placing the status panel onto the status bar by myself. And the css file I am using is much more modified and exactly adapted to my browser, in which I also made changes to the interface font. This file is therefore useless for other users.
-
Update notification! FYI, I have just updated my articles in the first, second and third post of this thread. Cheers, AstroSkipper
-
Not only does it seem that way, but I have definitely implemented a toolbar as a status bar in Mypal 68 with the functionality to display currently loading URLs and hovered links and to place toolbar buttons there as you can see in my previously posted pictures. To achieve this, only two files are required, a JavaScript uc.js file in the chrome profile folder and a corresponding Cascading Style Sheet css file in the chrome/css subfolder. The css file must then of course be integrated into the userchrome.css file. The prerequisite for all this is, of course, the preparations that must be made once in order to be able to load scripts and css files from the chrome folder into Mypal 68 as described by me in the first post of this thread. So, I do not use a startup auto-configuration script. You only need, for example, my package MYPAL_68_CB_requirements.7z from the first post. And to implement an additional toolbar near the navigation bar for placing buttons, you only need one other JavaScript uc.js file. In general, the implemetation of a new toolbar can only be done by a JavaScript uc.js file and any styling of it if necessary or desired by a css file. Such changes of the browser interface cannot be done by webextensions due to their damn restrictions. I actually wanted to write an article about all of this long ago, but refrained from doing so due to a lack of interest. Logically, disinterest and passivity are not particularly motivating. Anyway! When I am back at my desktop computer, I can give you more information if you are still interested in. Cheers, AstroSkipper
-
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.
-
My Browser Builds (Part 5)
AstroSkipper replied to roytam1's topic in Browsers working on Older NT-Family OSes
The obvious always speaks for itself. Things that are such self-explanatory and clear do not need any longer to be explained in detail. Apart from that, a more in-depth consideration would be inadmissible due to our forum rules and of no use in certain cases anyway. -
This extension also no longer works in Serpent 52. Just tested.
-
If you don't want such tons of toolbar buttons (I personally love this extension ), then the extension More About 3.0.0 is a good alternative. You can get it via the Classic Add-ons Archive.
-
@dmiranda The easiest and most convenient way to add such an About Menu button to Serpent 52 is to use the Toolbar Buttons 1.1.1 extension. This extension comes with many toolbar buttons or rather tons of them. Although this extension is old, most of the toolbar buttons still work in @roytam1's browsers. One of them is the button about:about which is still working in Serpent 52. Here are two screenshots. You can download the extension Toolbar Buttons 1.1.1 via the Classic Add-ons Archive. I will write an article about this extension very soon. BTW, I already wrote about Toolbar Buttons 1.1.1 and the about:about button here: https://msfn.org/board/topic/182647-my-browser-builds-part-3/?do=findComment&comment=1225677 Greetings, AstroSkipper
-
Actually, the About: Menu custom button should work in Serpent 52, too. When I am back at my desktop computer, I will have a look at this. In New Moon 28, however, I can definitely confirm that this custom button works as it should. Generally, most custom buttons tested by me should work in both browsers. But, of course, we all know the proof is in the pudding. I have just tested it and have unfortunately to confirm your observation. Although there is the compatibility string of Firefox {ec8030f7-c20a-464f-9b0e-13a3a9e97384} inside the code of the About: Menu custom button, the menu of all about: pages does not open in Serpent 52. The button was created many years ago, though. Therefore, it definitely was developed for much older Firefox versions (< 52). That's presumably why it is still working in New Moon 28. But there are still alternatives in the form of extensions for Serpent 52 which can be tested. I will have a look at that later.
-
In my very old New Moon profile, I have 67 extensions enabled and 5 disabled. But in the more recent profiles, I try to use much less of them.