Jump to content

My Browser Builds (Part 1)


Recommended Posts

9 hours ago, LoneCrusader said:

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.

There are already bugs with existing addons (at least with Basilisk). Options dialog in GreaseMonkey doesn't work. Also this particular fork's default configuration breaks ColorfulTabs (it expects Firefox version number in the user agent string).

Link to comment
Share on other sites


1 hour ago, UCyborg said:

Options dialog in GreaseMonkey doesn't work.

Have you, by any chance, tried GreaseMonkey for Pale Moon

https://github.com/janekptacijarabaci/greasemonkey/releases/latest

(file greasemonkey-3.31.4-pm_forkBranch.xpi) ?

Personally, in Serpent 52.9.0 I'm using latest ViolentMonkey (2.10.5) as userscript manager (of the WE type, still supported in St52 - but not official Basilisk/UXP). ;)

Link to comment
Share on other sites

18 minutes ago, VistaLover said:

Have you, by any chance, tried GreaseMonkey for Pale Moon

https://github.com/janekptacijarabaci/greasemonkey/releases/latest

(file greasemonkey-3.31.4-pm_forkBranch.xpi) ?

Thanks, this one works. Still find it odd; GreaseMonkey 3.11 doesn't have compatibility issues with Firefox 51. Waterfox on the other hand runs them all.

Link to comment
Share on other sites

21 hours ago, LoneCrusader said:

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.

I too once suggested changing the names of the .exe files, but it turns out that requires too many other changes; so I think now we're only talking about changing the names of the .7z files on @roytam1's page, some default prefs (so various links would point to Web pages controlled by @roytam1 vs. MCP), the displayed names, and the logos. The .exe file names would remain the same, and the other changes shouldn't affect add-on compatibility.

12 hours ago, TechnoRelic said:

And, in my view, the best three to 'work this out' (RT, VistaLover, Mathwiz) are now somewhat 'engaged' in that dialog.... And even VistaLover noted that the changes that I originally suggested are NOT very difficult to implement (Name the Browser, change the install SHTML message).

It is a lot of work in total, though - as @Sampei.Nihira noted, there are several Help menu links to fix as well - and the work is probably best suited to a Web designer, which I am not. I've already suggested names (Titan; Apophis) and could probably even create logos, but not all the necessary Web pages based around them - at least not if you want them to look decent!

22 hours ago, LoneCrusader said:

Let's not start this whole name changing bit again. There is nothing to be gained from it....

The benefit to be gained depends on how likely Matt or MCP is to take drastic action (such as making PM/Basilisk closed-source, thus cutting us off from all future enhancements) next time they think @roytam1 is to blame for unwelcome New Moon/Serpent support requests. Rebranding won't end those unwelcome requests, but it would give @roytam1 a good defense against their likely future complaints.

Link to comment
Share on other sites

13 hours ago, VistaLover said:

It's controlled by pref app.support.baseURL

default value is http://www.palemoon.org/support/

When you choose "Help", the browser tries to load
http://www.palemoon.org/support/firefox-help
which then auto-redirects to 

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

I think @VistaLover has a point, here. Changing both app.support.* strings to default straight here to this thread on MSFN is easy to do and might be a good 1st step. This @roytam1 might implement already in his next installment of the compiled versions of all browsers he's providing modded versions for XP. It's much simpler than rebranding, uncontroversial and breaks nothing, while being an incontrovertible proof something is actually being done to proactively prevent people from going to PM forums for support. :yes:

Link to comment
Share on other sites

uB0-legacy has just been updated to version 1.16.4.11; those without uB0 updater installed, should download and install manually:

https://github.com/gorhill/uBlock/releases/tag/firefox-legacy-1.16.4.11

Also, latest NM28-compatible language-packs have been (recently) updated to v28.6.0_RC2 :

https://github.com/JustOff/pale-moon-localization/releases/tag/28.6.0_RC2

:P

Link to comment
Share on other sites

In my St 52 copy (dated 2019.04.19), app.support.baseURL still points to Mozilla! So it seems the default was only changed in PM/NM.

We can still change it (in both versions), along with browser.feedback.URL in NM (app.feedback.baseURL in St), which is opened when the user clicks Help / Submit feedback and currently points to the PM forums in both browsers. And as suggested long ago, app.releaseNotesURL should point to http://rtfreesoft.blogspot.com/search/label/browser vs. the Palemoon.org release notes.

That's only three prefs per browser, but would clean up the Help menu and reduce the number of unwelcome support requests going to the PM forums.

I believe all these defaults are buried somewhere in <install dir>\browser\omni.ja. It might take a bit of searching to find & fix them all; an easier approach might be to override them by putting a new .js file in <install dir>\defaults\pref.

Oops: Discovered a minor wrinkle with changing app.support.BaseURL: Help / Keyboard Shortcuts no longer works :( So it might be best to just revert to Mozilla for that pref.

So the final prefs I ended up with are:

app.feedback.baseURL;https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=getNewComment
app.releaseNotesURL;http://rtfreesoft.blogspot.com/search/label/browser
app.support.baseURL;https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/

(change app.feedback.baseURL to browser.feedback.URL for NM)

Edited by Mathwiz
Link to comment
Share on other sites

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

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

Okay, I was 'over thinking' this (my view) for NEW MOON Browser.
What about to just 'blank out' (remove) this above listed URL ???
So, do NOT open ANY URL at all. Just have a 'blank' Browser Screen open.
That way, the reference to PALE MOON disappears.
And Users SHOULD then think to use the (Menu) HELP choices.
So, you make the HELP choices be URLs that aim at RT websites.

Which, there is a clearly misleading ERROR on the HELP = TROUBLSHOOTING INFORMATION
It references "New Moon" there, like this -->
" ... common questions about New Moon, check out our *support website* ... "
And the clickable URL for *support website* = http://www.palemoon.org/support/
Which, that clickable URL needs to instead be aimed at say the MSFN.org RT Forum Area (here).

As others suggested, the other (Menu) HELP URLs should aim at appropriate RT websites.
Finally, even the BOOKMARKS that come with the NEW MOON Installation, should be CHANGED
to aim at instead appropriate RT websites (or be removed), as opposed to PALE MOON websites.
Eventually, it will become clear to Users that NEW MOON is a FORK of PALE MOON anyway.

Hoping all three of you will agree that this is a good 'quick and dirty' fix for this overall issue.

Added later: @Mathwiz has posted just below, and seems to agree with views here.
And (thanks!) 'Mathwiz' has taken on the task of doing the 'Github Pull Requests' needed.
'Mathwiz' and 'VistaLover' now seem to share a common cooperative viewpoint.   
It appears that RT is 'engaged' too. I anticipate significant improvement soon.

Edited by TechnoRelic
Link to comment
Share on other sites

I agree; I never liked those "you've successfully upgraded" pages anyhow. I think simply blanking out the pref would prevent any such page from opening in the first place - not even a blank page. (Setting the pref to "about:blank" would presumably open a blank page, but that would be confusing.)

I looked over the UXP source tree and think I found where that pref is stored, as well as a couple of others mentioned above. So I cloned the tree, made the changes, and created a "pull request" as @roytam1 requested; but please keep in mind I'm a total noob at Github, so even though this was just a few simple changes, I'm not sure I did it right :blushing:

Link to comment
Share on other sites

38 minutes ago, Mathwiz said:

I agree; I never liked those "you've successfully upgraded" pages anyhow. I think simply blanking out the pref would prevent any such page from opening in the first place - not even a blank page. (Setting the pref to "about:blank" would presumably open a blank page, but that would be confusing.)

I looked over the UXP source tree and think I found where that pref is stored, as well as a couple of others mentioned above. So I cloned the tree, made the changes, and created a "pull request" as @roytam1 requested; but please keep in mind I'm a total noob at Github, so even though this was just a few simple changes, I'm not sure I did it right :blushing:

Thanks for your effort. Please comment if you finished modifying for this pull request so I can merge them to my custom branch.

Link to comment
Share on other sites

Yes, the mods are complete. Let me know if it causes any problems and you have to revert any of the changes.

I did not modify the app.support.baseURL pref because I couldn't find that one. Serpent doesn't need that one changed anyway; only New Moon. If / when I find it, I'll create another pull request to fix that pref.

Link to comment
Share on other sites

On 5/29/2019 at 4:29 AM, VistaLover said:

I was recently given a link to a specific facebook video (two orphaned bear cubs being given milk):

https://www.facebook.com/arcturosgr/videos/2355323964725837/UzpfSTU2MzI1NjMwNjoxMDE1NTgyNzQ4OTUzNjMwNw/

[...] as soon as I pressed the play button, I would only get sound but no video (player turns to black :realmad:).

I decided to investigate [...]

It's really nice that with LAV Filters and FFmpeg it's still possible to watch videos in New Moon, but I assumed most New Moon users here have a really old cpu which makes it nearly impossible to get a smooth video playback to begin with.
I stopped investigating years ago, as with my AMD Athlon XP 3200+ it's simply not possible to watch videos in-browser. Whenever I can I try to get my hands on the direct video-url and open it with MPC-HC instead so my gpu can do the decoding (dxva)!

Youtube-dl works for this url and so you could simply do:

FOR /F "delims=" %A IN ('youtube-dl.exe -gf dash_hd_src "https://www.facebook.com/arcturosgr/videos/2355323964725837/UzpfSTU2MzI1NjMwNjoxMDE1NTgyNzQ4OTUzNjMwNw/"') DO @mpc-hc.exe %A

I also wanted to see if I could extract the video-urls myself with my favorite scraper, and it appears I can :):

xidel.exe -s --user-agent="Mozilla/5.0 Firefox/67.0" "https://www.facebook.com/arcturosgr/videos/2355323964725837/UzpfSTU2MzI1NjMwNjoxMDE1NTgyNzQ4OTUzNjMwNw/" --xquery "let $a:=json(replace((//script/extract(.,'\((\{bootloadable.+?)\);',1)[.])[1],'\\\x','\\\u00'))/(.//videoData)() return {'name'://span[@class='_6w6o'],'date':extract($raw,'data-utime=\"(.+?)\"',1) * duration('PT1S') + date('1970-01-01'),'duration':format-time(duration($a/parse-xml(dash_manifest)//@mediaPresentationDuration),'[H01]:[m01]:[s01].[f001]'),'formats':[{'format':'pg-sd','container':'mp4[h264+aac]','url':$a/sd_src},{'format':'pg-hd','container':'mp4[h264+aac]','url':$a/hd_src},for $x at $i in $a/parse-xml(dash_manifest)//Representation order by $x/boolean(@width),$x/@bandwidth count $i return {'format':'dash-'||$i,'container':concat(substring-after($x/../@mimeType,'/'),'[',extract($x/@codecs,'(^[\w]+)',1) ! (if (.='mp4a') then 'aac' else if (.='avc1') then 'h264' else .),']'),'resolution':$x/@width ! concat(.,'x',$x/@height),'samplerate':$x/@audioSamplingRate ! concat(. div 1000,'kHz'),'bitrate':round($x/@bandwidth div 1000)||'kbps','url':$x/BaseUrl}]}"
{
  "name": "Ο Μπράντλεϊ και ο Κούπερ πίνουν το πρωινό τους γάλα σε χρόνο ρεκόρ!",
  "date": "2019-05-28",
  "duration": "00:00:21.430",
  "formats": [
    {
      "format": "pg-sd",
      "container": "mp4[h264+aac]",
      "url": "https://video.fams1-1.fna.fbcdn.net/v/t42.9040-2/61843568_373590383500381_78334383798353920_n.mp4?_nc_cat=110&efg=eyJybHIiOjMyNCwicmxhIjo1MTIsInZlbmNvZGVfdGFnIjoic3ZlX3NkIn0%3D&rl=324&vabr=180&_nc_ht=video.fams1-1.fna&oh=2db0888690b363f77cd2347d0a1b2ddc&oe=5CF72C9D"
    },
    {
      "format": "pg-hd",
      "container": "mp4[h264+aac]",
      "url": "https://scontent.fams1-1.fna.fbcdn.net/v/t39.24130-6/61896969_1057774241083394_2143298778333200645_n.mp4?_nc_cat=107&efg=eyJ2ZW5jb2RlX3RhZyI6Im9lcF9oZCJ9&_nc_ht=scontent.fams1-1.fna&oh=af11dc0bdaa1e1c3677ec995c683ef63&oe=5D8CE345"
    },
    {
      "format": "dash-1",
      "container": "[aac]",
      "resolution": null,
      "samplerate": "44.1kHz",
      "bitrate": "49kbps",
      "url": "https://video.fams1-2.fna.fbcdn.net/v/t42.1790-2/61730896_653046878453207_4586614327225614336_n.mp4?_nc_cat=100&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfdjRhdWRpb2ZvcnNvdXJjZXBpcGVsaW5lXzEyOF9jcmZfMjNfbWFpbl8zLjBfZnJhZ18yX2F1ZGlvIn0%3D&_nc_ht=video.fams1-2.fna&oh=5432806f4c33af32edc22bf2c4795329&oe=5CF723DB"
    },
    {
      "format": "dash-2",
      "container": "[h264]",
      "resolution": "144x256",
      "samplerate": null,
      "bitrate": "94kbps",
      "url": "https://scontent.fams1-1.fna.fbcdn.net/v/t39.25447-6/61730728_299189114366438_1302159605964110084_n.mp4?_nc_cat=107&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfb2VwX2xxMl9mcmFnXzJfdmlkZW8ifQ%3D%3D&_nc_ht=scontent.fams1-1.fna&oh=2565a3b437594c6fd2a7e7e651aa4ea7&oe=5D9CD5BA"
    },
    {
      "format": "dash-3",
      "container": "[h264]",
      "resolution": "240x426",
      "samplerate": null,
      "bitrate": "226kbps",
      "url": "https://scontent.fams1-2.fna.fbcdn.net/v/t39.25447-6/61739980_450267335732795_2637262664050798254_n.mp4?_nc_cat=102&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfb2VwX2xxMV9mcmFnXzJfdmlkZW8ifQ%3D%3D&_nc_ht=scontent.fams1-2.fna&oh=fa642dce8efabd37bb0f0301b3b31bea&oe=5D517AB3"
    },
    {
      "format": "dash-4",
      "container": "[h264]",
      "resolution": "360x640",
      "samplerate": null,
      "bitrate": "457kbps",
      "url": "https://scontent.fams1-1.fna.fbcdn.net/v/t39.25447-6/61957295_2167711626615482_3010584285180055097_n.mp4?_nc_cat=110&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfb2VwX2hxMV9mcmFnXzJfdmlkZW8ifQ%3D%3D&_nc_ht=scontent.fams1-1.fna&oh=db5624b4ce1ad59185330b7829bfe667&oe=5D897F64"
    },
    {
      "format": "dash-5",
      "container": "[h264]",
      "resolution": "480x852",
      "samplerate": null,
      "bitrate": "736kbps",
      "url": "https://scontent.fams1-2.fna.fbcdn.net/v/t39.25447-6/61777483_2414353792131319_5709933467491253734_n.mp4?_nc_cat=102&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfb2VwX2hxNF9mcmFnXzJfdmlkZW8ifQ%3D%3D&_nc_ht=scontent.fams1-2.fna&oh=0137dbb04f320370fe13bfa645073c3c&oe=5D8B7C5B"
    },
    {
      "format": "dash-6",
      "container": "[h264]",
      "resolution": "720x1280",
      "samplerate": null,
      "bitrate": "1484kbps",
      "url": "https://scontent.fams1-1.fna.fbcdn.net/v/t39.25447-6/61788732_1213415742166317_6377004606775886417_n.mp4?_nc_cat=107&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfb2VwX2hxMl9mcmFnXzJfdmlkZW8ifQ%3D%3D&_nc_ht=scontent.fams1-1.fna&oh=9f8619407dea9ca6caf04b96ffa1d3e3&oe=5D95591A"
    },
    {
      "format": "dash-7",
      "container": "[h264]",
      "resolution": "1080x1920",
      "samplerate": null,
      "bitrate": "3146kbps",
      "url": "https://scontent.fams1-1.fna.fbcdn.net/v/t39.25447-6/61801829_107103767207074_4181022582485783456_n.mp4?_nc_cat=107&efg=eyJ2ZW5jb2RlX3RhZyI6ImRhc2hfb2VwX2hxNV9mcmFnXzJfdmlkZW8ifQ%3D%3D&_nc_ht=scontent.fams1-1.fna&oh=d0c7ea5b7a870149b55a1bb0f674872d&oe=5D9E1271"
    }
  ]
}

 

Link to comment
Share on other sites

On 6/2/2019 at 4:17 AM, VistaLover said:

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... ;)

Many thanks. I do not use Pale Moon, only Serpent

For me working user agent for player.pl is:

general.useragent.override.player.pl;Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.9) Gecko/20100101 Firefox/52.9

Due to the ads,scripts I do not watch through the browser. I only need to change seasons/episodes and download videos an external program. Now thanks to you I can do it

 

However, in order to have access to the instagram, I need to change general.useragent.compatMode.version to 56.9 and lower, because the default 60.9 only displays the camera icon in the middle of the screen - but you probably all so have, so you also have to change to lower to have access?

Or create next user agent only for instagram:

general.useragent.override.instagram.com;Mozilla/5.0 (Windows NT 6.1; WOW64; rv:56.9) Gecko/20100101 Firefox/56.9

 

Edited by Seba21
Link to comment
Share on other sites

20 hours ago, Seba21 said:

However, in order to have access to the instagram, I need to change general.useragent.compatMode.version to 56.9 and lower, because the default 60.9 only displays the camera icon in the middle of the screen - but you probably all so have, so you also have to change to lower to have access?

The "instagram" issue in UXP browsers (NM28, Serpent 52) has been covered in fine detail in previous pages of this thread, when it first manifested itself ;); it's a case similar to player.pl, that is due to new UXP defaults (general.useragent.compatMode.version;60.9), instagram sends JS code the platform can't cope with...

The solution is similar to the one suggested for player.pl, i.e. use a SSUAO for instagram that advertises a Firefox < 60.0 version; DON'T touch the "general.useragent.compatMode.version" pref, just create:

general.useragent.override.instagram.com;Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

:P

Edited by VistaLover
Link to comment
Share on other sites

Mathwiz said:


I did not modify the app.support.baseURL pref because I couldn't find that one. Serpent doesn't need that one changed anyway; only New Moon. If / when I find it, I'll create another pull request to fix that pref.



For such stuff I simply unzip the 2 omnis and do a text search inside. Instant hit: palemoon.js in browser/omni.ja/defaults/preferences. But wouldn't it be a lot easier to just create a separate little prefs file in browser/defaults/preferences, as was already suggested? But perhaps I'm getting something wrong...
Link to comment
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...