Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


roytam1

My build of New Moon (temp. name) a.k.a. Pale Moon fork targetting XP

Recommended Posts

As usual, my browser installer will now install the latest builds... the new version with firefox45 and UOC patch support IS coming soon, I promise. I've just been a bit busy lately.

Share this post


Link to post
Share on other sites

18 hours ago, Mcinwwl said:

@Sampei.Nihira. Just. Please. When. You. Paste. Some. Link. Give. At least. A brief. Description. What. It. Leads. To. Period.

I'm not the first person on the board to as you for this.

I promise that I will try to do what you suggest.

It is not always possible to do what is right for others.

 

  • Upvote 1

Share this post


Link to post
Share on other sites
1 hour ago, Sampei.Nihira said:

It is not always possible to do what is right for others. 

In this case - writing one-line summary - it was ;) I hope for the better future. peace!

  • Upvote 1

Share this post


Link to post
Share on other sites
Posted (edited)
On 5/31/2019 at 10:13 PM, DanR20 said:

(See 'DanR20' Message above) --> Added as a separate override for google and all seems well so far:
general.useragent.override.google.com

https://legacycollector.org/firefox-addons/59/index.html
Using here the (LEGACY) Add-On (Extension) --> User-Agent-Switcher-0.7.3.1-signed.1-signed.xpi

The following applies to NEW MOON Browser (RT).
In order for the above LEGACY Add-On (Extension) to work, the following change
in 'about:config' needs to be done. Find the ENTRY below:

general.useragent.override.google.com

It has a (string) VALUE that is there, delete ('blank out') that VALUE (UserAgent).
You can leave the ENTRY in place with the 'blank out' VALUE there.
After doing that, THEN using the 'User Agent Switcher' will properly affect GOOGLE,
in terms of the OLD versus NEW FORMAT for GOOGLE (say 5.0 = Old , 60.9 = New).
The DEFAULT will now be the OLD FORMAT for GOOGLE. Hope that seems clear.
So, even if you do NOT install the 'User Agent Switcher' Add-On, to 'blank out'
the VALUE as described, will define OLD FORMAT for GOOGLE as permanent DEFAULT.

https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=findComment&comment=1164249
Add 'coding' for RT BNAV Browser Add-Ons if needed (Extensions, RT BNAV uses LEGACY only)

Edited by TechnoRelic

Share this post


Link to post
Share on other sites
Posted (edited)

@roytam1 -- @VistaLover -- @Mathwiz <--

http://www.palemoon.org/unofficial.shtml

I was looking at the (URL) above 'SHTML' that displays after a NEW MOON upgrade.

The words (graphically) "Pale Moon" is prominently displayed at the 'right' top.
I would replace that with "NEW MOON" instead.

I would also say instead -->
"You have successfully installed or upgraded the NEW MOON web browser."

Also, I would say instead -->
"This NEW MOON version 'Fork' of Pale Moon that you have installed is not an official release.
It is configured differently by RT (The Magnificent) to work with Windows XP OS too.
Those who wish to visit 'The Cult of RT' for support can do so at MSFN.org (clickable URL)."

Hopefully, it is clear that I am intending a bit of amusement with some of the wording above.

Also, at the bottom, there are clickable URLs for MOONCHILD PRODUCTIONS, PALEMOON.ORG,
and I would replace those with maybe some RT (The Magnificent) URLs instead.

So, here, I only care for feedback from RT, VistaLover, and Mathwhiz, on this suggestion.
WHATEVER they might think, decide, and RT does it (including ignore me), is FINE with me.
A certain 'MAT' person came to mind for me, with regard to this suggestion.

Edited by TechnoRelic

Share this post


Link to post
Share on other sites

@TechnoRelic

@roytam1 has absolutely NO CONTROL over the mentioned URI;

http://www.palemoon.org/unofficial.shtml

is hosted on the "www.palemoon.org" domain, which is owned by Moonchild Productions; as you said, a tab with that URI loaded is triggered after an unbranded Pale Moon build (New Moon in this case) has been successfully updated (app version change). 

Actually, what gets displayed in that post-upgrade tab is controlled by the value of pref:

startup.homepage_override_url

For official builds, value is (string): http://www.palemoon.org/firstrun.shtml

and, as stated, for unofficial (unbranded) ones: http://www.palemoon.org/unofficial.shtml

What you suggest implies @roytam1 setting up (and hosting) a dedicated webpage with the changes you proposed; this can be a "minimal effort" solution with just some text and links, more effort required if artwork is involved (background and foreground images, logos etc.); the link to that webpage should be then set as value of mentioned about:config pref...

In any case, you obviously lean towards "proper" rebranding of New Moon; MCP already direct unbranded build users to

Quote

For support for this version we kindly direct you to the person who has published this version; we cannot reasonably provide support for unofficial binaries.

so those "clueless" ones are already informed (still, all these who can't be arsed to read any disclaimer of any form will continue to "irritate" Moonchild and company even if a specialised post-upgrade page is set up :angry:).

Even if New Moon becomes fully rebranded to Goldie Locks (haven't decided whether to include the 3 bears or not :D) with completely new artwork and redirections to non-MCP related support sites, I don't think MCP will be totally freed from the random Goldie Locks user landing on their forum/github tracker (and this is what seems to be the only one and poignant issue they have with the rest of us...); just look at what happens with MyPal and (to a lesser degree) Centaury... :whistle:

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/1/2019 at 12:44 PM, VistaLover said:

What you suggest implies @roytam1 setting up (and hosting) a dedicated webpage with the changes you proposed; this can be a "minimal effort" solution with just some text and links, more effort required if artwork is involved (background and foreground images, logos etc.); the link to that webpage should be then set as value of mentioned about:config pref... 

Yes, exactly what you have described it, a new URL to a new hosted 'SHTML' that is altered appropriately.
And, GOOD that you had some 'fun' with your REPLY too. :)

Edited by TechnoRelic

Share this post


Link to post
Share on other sites
6 hours ago, TechnoRelic said:

@roytam1 -- @VistaLover -- @Mathwiz <--

http://www.palemoon.org/unofficial.shtml

I was looking at the (URL) above 'SHTML' that displays after a NEW MOON upgrade.

The words (graphically) "Pale Moon" is prominently displayed at the 'right' top.
I would replace that with "NEW MOON" instead.

I would also say instead -->
"You have successfully installed or upgraded the NEW MOON web browser."

Also, I would say instead -->
"This NEW MOON version 'Fork' of Pale Moon that you have installed is not an official release.
It is configured differently by RT (The Magnificent) to work with Windows XP OS too.
Those who wish to visit 'The Cult of RT' for support can do so at MSFN.org (clickable URL)."

...

So, here, I only care for feedback from RT, VistaLover, and Mathwhiz, on this suggestion.

WHATEVER they might think, decide, and RT does it (including ignore me), is FINE with me.
A certain 'MAT' person came to mind for me, with regard to this suggestion.

Ironically, the problems you noted with the "unofficial.shtml" page are MCP's own doing. They own the www.palemoon.com Web site, and they programmed "unofficial" browser builds (i.e., New Moon) to open that page. They do have a disclaimer about support, but given how sensitive they seem to be about not calling unofficial builds "Pale Moon," it's amusing that their own Web page for unofficial builds commits that very same error.

If Matt or anyone else hassles @roytam1 about "misrepresenting" his browser again, it might be worth pointing out that it's MCP's own "unofficial.shtml" page that's doing a good bit of the "misrepresenting." Since all "unofficial" builds are called New Moon, surely their Web page for those builds should call it New Moon as well, or at least use wording like "unofficial build of Pale Moon" vs. just plain "Pale Moon."

FWIW, I do think @roytam1 should develop his own branding, but that has proven to be more easily said than done; we can't even come up with a browser name that everyone's OK with! ("New Moon" is just MCP's default name for unofficial Pale Moon builds.) Maybe @roytam1 should be a "dictator" on this question and just pick a name he likes. (Or maybe it's been New Moon for so long, he's grown to like the name "New Moon.")

  • Like 1
  • Upvote 1

Share this post


Link to post
Share on other sites
6 hours ago, Seba21 said:

Instagram stories videos now working again on 2019.05.31 (32-bit) version

But blue buttons on player.pl still do not work from February

https://player.pl/programy-online/agent---gwiazdy-odcinki,4305

Thanks for the link, and good to hear Instagram is working for you again.

Do you know the precise version from February that works (with the next version not working)? If so, we can study the change log and see if we can find the change that broke that site. Then we might be able to figure a workaround, or even revert the change. That's how we fixed another Instagram bug a few months ago.

Share this post


Link to post
Share on other sites
35 minutes ago, Mathwiz said:

That's how we fixed another Instagram bug a few months ago.

Cheers :thumbup , you've come pretty close to the resolution of the reported issue; in fact, it's "instagram #2" deja-vu: the type of Javascript code to be sent to the client (browser) by the player.pl video portal is being determined by UA-sniffing; their poorly written site (which, by the way, is infested with third party scripts :angry:) does not like any of the three user-selectable UA strings (testing with New Moon 28.6.0a1) : 

Native: Mozilla/5.0 (Windows NT 6.0; rv:60.9) Goanna/4.2 PaleMoon/28.6.0a1

Gecko compat: Mozilla/5.0 (Windows NT 6.0; rv:60.9) Gecko/20100101 Goanna/4.2 PaleMoon/28.6.0a1

Firefox compat: Mozilla/5.0 (Windows NT 6.1; rv:60.9) Gecko/20100101 Goanna/4.2 Firefox/60.9 PaleMoon/28.6.0a1

The JS code sent with any of the above UA selections renders the SEZON buttons for the Odcinki series inoperable (non-clickable); further troubleshooting reveals that that's because UXP can't handle the Firefox Quantum 60.9-specific code it's being fed :angry:; a pure Firefox ESR 52.9 SSUAO for player.pl will make the SEZON buttons operable again, but when you first load the site you'll get a prompt to upgrade to a more recent (and supported) browser brand/version; you can dismiss that prompt and, hopefully, proceed to view...

However, I've found that to make those buttons work as expected but not get nagged at (for running an older, unsupported, browser), one should use the "Firefox compat" string modified to report a Fx 52.9 version:

general.useragent.override.player.pl;Mozilla/5.0 (Windows NT 6.1; rv:52.9) Gecko/20100101 Goanna/4.2 Firefox/52.9 PaleMoon/28.6.0a1

@Seba21

Please understand that your problem site is specific to Polish speakers and that most of its media content is geo-fenced for non-Polish IPs :angry:; so it's quite difficult for members here that don't understand Polish to navigate that site, troubleshoot it and offer advice/solutions :(

Be that as it may, I believe your issues can be cured by creating (in either New Moon 28 or Serpent 52) a Site-Specific-User-Agent-Override (SSUAO) for player.pl ; that procedure has been explained numerous times in this and other threads:

Load about:config in a tab, promise to be careful :)
Right-click in an empty space and choose to create a new "string" preference - a pop-up will be displayed
As name of the pref, input general.useragent.override.player.pl and click OK - second pop-up will be displayed
As value of the pref, input Mozilla/5.0 (Windows NT 6.1; rv:52.9) Gecko/20100101 Goanna/4.2 Firefox/52.9 PaleMoon/28.6.0a1 and click OK
Close the about:config tab
Reload the player.pl tab

... you should then be able to use your SEZON buttons... ;)

Share this post


Link to post
Share on other sites
Posted (edited)
8 hours ago, VistaLover said:

Even if New Moon becomes fully rebranded to Goldie Locks (haven't decided whether to include the 3 bears or not :D) with completely new artwork and redirections to non-MCP related support sites, I don't think MCP will be totally freed from the random Goldie Locks user landing on their forum/github tracker (and this is what seems to be the only one and poignant issue they have with the rest of us...); just look at what happens with MyPal and (to a lesser degree) Centaury... :whistle:

yes, even MyPal users come here and asked for support, so people will go direct to MCP and asked for support as well, no matter what your browser's name is.

 

2 hours ago, Mathwiz said:

FWIW, I do think @roytam1 should develop his own branding, but that has proven to be more easily said than done; we can't even come up with a browser name that everyone's OK with! ("New Moon" is just MCP's default name for unofficial Pale Moon builds.) Maybe @roytam1 should be a "dictator" on this question and just pick a name he likes. (Or maybe it's been New Moon for so long, he's grown to like the name "New Moon.")

If people can provide names AND artworks(by github Pull Request replacing branding folder), I can change them. (for me, I just want a working binary and naming/artwork are things I'm not good at.)

Edited by roytam1
  • Like 1
  • Upvote 1

Share this post


Link to post
Share on other sites
Posted (edited)
11 hours ago, roytam1 said:

(for me, I just want a working binary

+1 :thumbup; in fact, I am indifferent to the whole "rebranding" hullabaloo :P; personally, I know very well where I first learned about the existence of the Pale Moon fork (yes, that's what it is), i.e. this very forum/thread, I know very well where the compiled builds are hosted and where to download them from, I am well aware of @roytam1's GitHub repositories and blog, so I'd have to be senile to direct myself to one of the upstream sites for official support (especially given the fact how rude/hostile people there are to "intruders" :angry:); OTOH, taking into account how similar the code is between PM and the fork in question, I have every right - if I wish to do so - to visit the official Pale Moon forum as an unregistered user and seek help there by searching already posted content; and, provided I have access to working official binaries, I might post an issue in the official github tracker (given I already have a GitHub account) if a bug I discovered in NM is reproducible in official PM; I won't, of course, make any mention of the fork on a non-supported OS; NB that Moonchild doesn't like people "littering" his tracker before the reported "issue" has been first filtered in his forum, but that's his own problem... To conclude, that is how far I would approach the official support avenues...

... New-name giving and artwork? Fine, if you like to occupy yourself with what is devoid of real substance :angry:; there, I said it...

(DISCLAIMER: No offence meant to members about to - once again - inundate this thread with new candidate browser names ;) )

Edited by VistaLover
  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)
29 minutes ago, VistaLover said:

... New-name giving and artwork? Fine, if you like to occupy yourself with what is devoid of real essence :angry:; there, I said it...

forgot to mention: please be in github Pull Request form.

(to do this, you are required to fork my UXP repo, make changes in branding folder including icons/about dialog background/names, commit it to your cloned-repo, and create pull request)

Edited by roytam1
  • Like 1

Share this post


Link to post
Share on other sites

:no:

Let's not start this whole name changing bit again. There is nothing to be gained from it, and only more work to be created.

There's a relevant point in another thread (that thanks to the lack of a proper BBcode editor in IPB I can't just copy and paste here :realmad:) about how this may affect addons and related applications, requiring them to be modified to recognize the resulting renamed binary.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...