uBlockO legacy download method

[Hugo Oberstein]

Hello, can something be done to make it easier to install the uBlockO (for Firefox legacy)? Currently it is hard to figure out, and people will say, "What am I supposed to press to download this"?

On all of your add-ons, there is an "Install" button. Since this is an external site on GitHub, one has to "look around" to find the actual place to download it.

I went to: https://github.com/UCyborg/uBlock-for-f ... y/releases and then clicked the small 1.16.6b1 on the left which took me to, https://github.com/UCyborg/uBlock-for-f ... e/1.16.6b1 and then looked for Distributions or "Dist" and clicked that which took me to, https://github.com/UCyborg/uBlock-for-f ... 6.6b1/dist and then went down the page to the "INSTALL Firefox legacy" and saw the XPI filename there.


Compatible with Firefox 51-56, Pale Moon and SeaMonkey.
Download ublock0.firefox-legacy.xpi (latest release desirable).
Right-click and select "Save Link As..."


Another here with me used a different route by going to, https://github.com/UCyborg/uBlock-for-f ... y/releases then clicking the large center located 1.16.6b1 which took them to, https://github.com/UCyborg/uBlock-for-f ... g/1.16.6b1 and near the bottom under "Assets" is, uBlock0_1.16.6b1.firefox-legacy.xpi.

Can something be done to make it easier for the average computer user to download this fine product? While I and others here do understand how to eventually navigate GitHub, I guarantee the average "Joe" does not.

Another issue with this add-on is the wording after 1.16.6b1 which is "Pre-Release". While many of us in the computer field know that a beta or a pre-release may still be acceptable, it would be nicer if it were an official, "approved" release. Since I have been reading the forums lately I do know it is approved by Moonchild, but maybe it can be bumped-up the release scale?

A thank you to all that support Pale Moon and to the add-on/extension writers that make their programs for Pale Moon.

[Night Wing]

I use the "old" uBlock Origin version 1.16.4.30 for Pale Moon. And it does not matter if you are using windows Pale Moon or linux Pale Moon. I have never had any problems using the old version and I surf all over the internet.

I get it at the link below.

https://github.com/gorhill/uBlock-for-f ... y/releases

Once on the page, scroll on down (if you have to scroll) until you see the word, "Assets". You might have to left click on the word "Assets" to see the "xpi" file since sometimes it hides the "xpi" file.

The file will look like this below.

Code: Select all

uBlock0_1.16.4.30.firefox-legacy.xpi

Then left click on the file and it will start the install.

The reason I do not use the "6b1" version by UCyborg is because I do not like using beta software. "Beta", to me, means the software "may" be buggy. If the software is not buggy and safe, then take it out of beta. This is just one of my odd "quirks" when it comes to (me) using software.

[Moonchild]

We can't do anything about "external" add-ons' ease of installation (or lack thereof). Unless the add-on author chooses to use the add-ons site directly to distribute their add-on, users will have to deal with whatever the external site offers as access to the xpi.

[ron_1]

I save the .xpi file to my computer, so in case I ever have to reinstall it, I do it locally from my computer. I save all the .xpi files of all the extensions I use. It's a big time saver.

[andyprough]

Hello, can something be done to make it easier to install the uBlockO (for Firefox legacy)? Currently it is hard to figure out, and people will say, "What am I supposed to press to download this"?

People might say that once, but after that the first time they'll always know that on a Github Releases page they should look for Assets, and click on the .xpi file. Most of us have probably installed lots of things from Github, so it's nothing new, but I can see that for a first-timer it could be mildly confusing. Maybe some words about what to click could be put as instructions on the Pale Moon add-ons page for uBlock.

Another issue with this add-on is the wording after 1.16.6b1 which is "Pre-Release".

That's what the dev wants it called and he has his reasons. We should all be aware that his version of uBlock is not in its final form and it could be a bit more buggy, although I haven't seen a single person bring up an issue about this version of uBlock and it's performed perfectly for me.

[Hugo Oberstein]

Hello Night Wing, Moonchild and Ron_1. I want to thank you, all three, for posting. Night Wing I have followed your posts in the past and they are always straight and intelligent. Yes I too agree with you on the beta vs stable software reasoning. Also thank you for the older versions download site and your directions (this will help others too). I am currently using the older version like you. Moonchild, again I am honored to hear from you and I do understand your position here. I was hoping a "hint" could be directed to Ucyborg from you. Lastly Ron_1, thank you it is a good idea and I have been keeping my original downloads for decades "just in case" something happens.

All good information from everyone.

Thanks to all that support Pale Moon.

[Hugo Oberstein]

Hello Andyprough and thanks for posting. I missed your post as I was typing my reply.

You said, "People might say that once, but after that the first time they'll always know that on a Github Releases page they should look for Assets...".

I did mention that I (and others here where I am) do know how to navigate GitHub, but is is a "hassle" to do so and not every GitHub site has the ASSETS all setup the same way. In some cases we could click CODE to find what we were looking for.

But yes, once it is done then it is easy to do. My consern was the average user would get lost trying to find download or the download filename.

You also said, "We should all be aware that his version of uBlock is not in its final form and it could be a bit more buggy...".
I agree completely. This is why Night Wing and I elected to go with, and continue to use, the older 1.16.4.30.

Thanks again for posting Andyprough. I have seen your good posts in the past helping others, and appreciate them.

[suzyne]

I save the .xpi file to my computer, so in case I ever have to reinstall it, I do it locally from my computer. I save all the .xpi files of all the extensions I use. It's a big time saver.

I have also found WebInstall Ninja 1.0.2 mentioned here viewtopic.php?t=25190 to be useful for making sure I have a copy of the XPI file of the add-ons that I install.

[back2themoon]

Aren't all installed extensions already stored in the profile/extensions folder? Some of them will have cryptic file names (which is annoying), but those can be revealed with Help/Troubleshooting Information.

[FranklinDM]

Can something be done to make it easier for the average computer user to download this fine product? While I and others here do understand how to eventually navigate GitHub, I guarantee the average "Joe" does not.

It's also available on Project Fresco: https://projectfresco.github.io/addons/ ... ock-origin

[andyprough]

Off-topic:

It's also available on Project Fresco: https://projectfresco.github.io/addons/ ... ock-origin

Could you possibly link to the priv8 extension (for managing container tabs) in Fresco, @FranklinDM? It's in the Classic Add-ons Archive, but you are already linking to everything else I would need from Classic Archive in Fresco. Linking to priv8 would make Fresco my one-stop shop for all external extensions. I know there's at least two of us using priv8, maybe more, it's been a relatively popular topic when it's brought up in the forum.

[ron_1]

I have also found WebInstall Ninja 1.0.2 mentioned here viewtopic.php?t=25190 to be useful for making sure I have a copy of the XPI file of the add-ons that I install.

What does this extension exactly do? I just simply right click the link and select "Save Link As..." to save a copy of the .xpi file.

[suzyne]

What does this extension exactly do?

It adds a Save button when installing the extension which is helpful for users like me who didn't know that the Save Link As command was already an easy way to save the XPI file. But now I know, and so don't need WebInstall Ninja anymore!

[Goodydino]

Can something be done to make it easier for the average computer user to download this fine product? While I and others here do understand how to eventually navigate GitHub, I guarantee the average "Joe" does not.

It's also available on Project Fresco: https://projectfresco.github.io/addons/ ... ock-origin

That is a blank page. I looked at the source code and there is not much in there.

[moonbat]

That is a blank page.

It's not. Try reloading it, maybe a network hiccup at your end.

[gepus]

@Goodydino

Enable cookies and the site will show up.

[Night Wing]

It's also available on Project Fresco: https://projectfresco.github.io/addons/ ... ock-origin

That is a blank page. I looked at the source code and there is not much in there.

The page renders correctly for me as well.

At this time I am using 64 bit linux Pale Moon 33.4.1 (GTK2) running in linux Mint 22 (Wilma) Xfce.

[Kruppt]

Aren't all installed extensions already stored in the profile/extensions folder? Some of them will have cryptic file names (which is annoying), but those can be revealed with Help/Troubleshooting Information.

Yes that is true, but there is a Extension by RealityRipple called ExtExp that allows you to export/save a particular extension or all.
It places an Export Button on each extension and theme in your Add-ons Manager or all from the drop down menu at the top right
in both Extension window or Themes window.

Link to ExtExp:
https://realityripple.com/Software/XUL/ExtExp/

[back2themoon]

I know. All I'm saying is that the extensions are already present in one's profile. Just copy the folder, or specific extension(s) somewhere else. Or not. No need to "export/save", there is no "format conversion" or anything.

However, the cryptic filenames can be an issue, so ExtExp certainly helps. It will convert/rename the cryptic filename to a proper one.

Well, they are not actually cryptic. It's the extension's ID, but having a bunch of random characters as a filename is not a pleasant experience.

[Goodydino]

@Goodydino

Enable cookies and the site will show up.

That did not make any difference. I also tried giving a fake user-agent and that did not help either. This is the entire source code for the page:

Code: Select all

<!DOCTYPE html>
<html lang="en">
    <head>
        <meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
        <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
        <title>Fresco</title>
        <link rel="shortcut icon" href="assets/images/favicon.png"/>
        <link href="assets/common.css" rel="stylesheet"/>
        <link href="assets/themes/default/theme.css" rel="stylesheet" title="Default"/>
        <link href="assets/themes/cavendish/theme.css" rel="alternate stylesheet" title="Cavendish"/>
        <link href="assets/themes/blue/theme.css" rel="alternate stylesheet" title="Blue"/>
        <script src="https://cdnjs.cloudflare.com/ajax/libs/systemjs/6.14.1/system.min.js" integrity="sha512-5QtTSqKLlp9G1SmuQYBgk5t+rZ0/6yaqL/KGzq1Js66iUdLSgBBhIeOWGQa0GAe4fbo+gcw2dGzBdq2FdHGp9w==" crossorigin="anonymous" referrerpolicy="no-referrer"></script>
        <script src="assets/main.js"></script>
        <script>
            var pageInfo = { id: 1 };
        </script>
    </head>
    <body data-loaded="false">
        <noscript>
            This site requires JavaScript.
        </noscript>
        <div class="giscus talk-box"></div>
        <script src="https://giscus.app/client.js"
            data-repo="projectfresco/projectfresco.github.io"
            data-repo-id="R_kgDOHFN5gw"
            data-category="Q&A"
            data-category-id="DIC_kwDOHFN5g84CYqrx"
            data-mapping="url"
            data-strict="1"
            data-reactions-enabled="1"
            data-emit-metadata="0"
            data-input-position="bottom"
            data-theme="preferred_color_scheme"
            data-lang="en"
            data-loading="lazy"
            crossorigin="anonymous"
            async>
        </script>
    </body>
</html>

You can see that there is no content; only a few scripts and stylesheets.