Jump to content

Leaderboard

The search index is currently processing. Leaderboard results may not be complete.

Popular Content

Showing content with the highest reputation on 01/06/2020 in all areas

  1. "msfntor" - I would kindly suggest that your browsing needs are not the targeted audience for these forked browsers. What you "need" is Win10 and everything Win10 has to offer. WinXP "today" really should be considered as "Linux" - a niche audience that is NOT for "everybody".
    4 points
  2. Only for the nerdiest, windows codenames are not common knowledge.
    3 points
  3. Oh my God, am I turning into a Matt A. Tobin clone?
    3 points
  4. These forked browsers in-and-of-themselves are "not common knowledge" and "only for the nerdiest".
    2 points
  5. 'VistaLover' has a fairly valid viewpoint , IF expressed in a somewhat 'not quite friendly' manner. Your messages here in this THREAD sometimes do give the impression that RT has NOTHING else to do with his TIME than 'fine tune to perfection' the BROWSERS that he compiles and provides them FREE here. RT is NOT getting PAID MONEY to provide these RT BROWSERS , 'we' are CLEAR on this , right ??? ... It seems as though you 'show up' repetitively with a 'Laundry List' of 'Flaws' that you proudly discovered them. And somehow , RT is supposed to say like 'how high can I jump' while fixing them ??? ... Maybe my impression is not quite fair , but as *suggestion* , maybe you could 'tone it down' a notch or two ...
    2 points
  6. I got some ideas for branding.. Pale Moon could be called Whistler after the Codename for Windows XP Basilisk could be called Freestyle the Codename for Windows XP Media Center Edition because of the extra media features and Australis UI Borealis could be called Neptune the Codename for a developmental predecessor of Windows XP Interlink could be called Lonestar the Codename for Windows XP TabletPC Edition (writing, email, get it?) These are all UXP based applications for Windows XP and there you go a theme for all your forks of them. OH just call Basilisk 55, call it the codename for the repo.. Moebius/Mobius. Good name at any rate. Again for the four UXP applications.. I am willing to do the work for you, get em all in one repo, do the branding (yes I will keep the appdata paths as they are to avoid profile issues) and gift wrap it for you for Christmas. What do you say? EDIT: Thank you for removing the official branding from the modified-uxp repository. ALSO, if you go forward with this I will list you on thereisonlyxul.org in a special section for Windows XP users.
    2 points
  7. I have filed an issue at your github uxp repository that if you are not going to stay sync'd with UXP then you need to remove official and unstable trademarked branding from the repository. In other news, if you would like to unify your forked applications into a single repository as I have done you can use this as a base: https://github.com/binaryoutcast/comm-buildbase Since you are manually applying patches anyway you can make the paths whatever you want and use easy git commands to set the basepath of a patch on the fly then you can maintain and make these real forks and manage them from one repository. I am even willing to help set this up.. You could have it setup as the following tree: topsrcdir |- strata (palemoon) |- australis (basilisk) |- mail |- calendar |- navigator I would make all the build system path modifications for you and then set a submodule to your platform repo. It would be really easy to do especially since I am already in the mode for it with my recent work. I'd even (while still using generic assets) even rename the applications for you or if you finally give me names and an icon I will go ahead and change em all. I will do all the prep work and we can finally get this settled. You can rewrite patches to your heart's content then and stop having me harp on it.
    2 points
  8. it seems big speed-fluctuations woldwide. it seems i have a severe one(see my post) but one does not know yet whats the cause: censourship/hacking. e.g. when downloading from RoyTam1 i took 40 min.for a 30mb file/NM SSE. KM-Goanna very quick. This evening(1 Gbit/s golden double-shielded cable attached) i took seconds. Speedtest varying DL from 20/30 to 150Mbps- must be 1000( 1Gb/s)! collegue in D(i am in nearby CH) telling he is shown 90% or more of his 1Gb/s-line. its seems also speedtests are not precise. Will now check the answer(s) to my problem. will get mobile 4G-router. I am actually on old Winxp SSE. could switch to SSE2/winxp and Win7 on two HDDs. Can switch quickly to Win10s which is showing also slow Speedtests. Best would be downloading a large file. I my opinion multiple instances are slowing it down for different reasons. and they dont want to tell the truth. could damage their business. I am waiting speedtest of neighbour on Wlan nearby. I see it also listed. Since Win10s netbook is also slow it makes no sense to setup new Winxp.
    1 point
  9. In my opinion i am being slowed down since weeks. Winxp-sse-desktop is on cable. ok must get 1GB/s cable now. But: win10s- netbook on WLAN has the same 2% only speed. 20 up to 148 Mbps(other server) instead of 1000(1Gbit/s) since weeks if not months. didnt check with speedtest earlier thought its normal with my half-sick pc.. also removed cable end reset everything, only netbook on WLAN-notjhing changed. SLOW INTERNET. recognized only christmas (24th mnorning here) when it was extremly slow. I would understand themn slowing it down during holidays over newyear. to avoid total crash and everybody can still surf. upload almost inexistant reg. speedtest. I only criticized the internet-gigants...Provider has now my router-data. he could not ping it...! and will tell me if i should reset to factory default will get new speedy i7 laptop within one week. and could try out for free a new provider. maybe my provider is not guilty. signal telling i am getting full speed. 1 GBit/s. shop downstairs will check Wlan-speed on their provider-our monopolist. my provider yplay is not on their servers. So only be warned if all older OS-users will be slowed down considerably. everything is possible. And: regarding Protonmail(geneva). google them i mentioned it before. They dont have login-access on winxp. will slowly update and setup all three browsers correctly. is not the case at the moment. but i dont believe thats the reason. PC is clean. Could still be a network-problem here. only dont know where to look at. how to check is there a tool? renew drivers maybe. sfc /scannot done. Tks I am desperate. yes SSE2 reactivation underway. 1 mio other tasks.
    1 point
  10. I believe Windows code names were suggested to indicate the minimum supported OS versions of his browsers, as well as specific features of these versions that will run better on specific OS version. This helps users to choose the right browser version.
    1 point
  11. "safebrowsing" (as well as Tracking Protection) was/is a Mozilla Firefox feature that is reliant upon Google APIs/services; Mozilla, as is vastly known, rely heavily on Google to collect revenue, so they had agreed on "gluing" this feature onto their browser... It is currently only relevant to FirefoxESR 45.9.x & Serpent 55/Moebius forks and it's still present in (forked) Moebius because MCP had abandoned the platform before taking the time to remove it... In UXP browsers builds, these Google provided services (i.e. Block dangerous and deceptive content => Block dangerous downloads + Warn me about unwanted and uncommon software) have been removed by MCP and, if you ask me, that is a blessing in disguise... This is just me, but I consider (evil) Google to be a malware by definition, so I wouldn't want to be given advice by them on what web page to visit and what file to download... The average Joe, using the latest Firefox (in Win10, no doubt...) only gets a (false IMHO) sense of security because all-knowing Google are taking care of him in the background ( ) ... Common sense is to be exercised here, of course backed-up by an otherwise updated/secure browser engine, a set of updated privacy/security extensions, including in-browser content blockers (but not a myriad of them...), a supported and up-to-date Security Suite OS-wide and I humbly think no-one's in need anymore of the ever spying/tracking Google... You are entitled to a different opinion, of course ; as said, these are only my own views...
    1 point
  12. Netcraft extension, disconnect me, uBO
    1 point
  13. Thanks for your reply. A listing from the javascript console says that the "openerTabId" property in the "tabs.create" function is no longer supported. Apparently, the "openerTabId" property has been removed by upstream. I found the "openerTabId" property inside the Tampermonkey extension - only one entry in the file "\firefox@tampermonkey.net.xpi\rea\background.js". I removed the "openerTabId" property in this file (as in the screenshot below). This solved the problem. The Tampermonkey extension 4.9.5921 works fine in the latest Serpent build. Menu items now working. Thanks again for your builds.
    1 point
  14. @RoyTam1, Now, firefox-45.9.19-20200104-ddcd778f4-win32-sse doesn't have precedent problem, this tab problem is gone! BUT: In latest Moebius 55: basilisk55-win32-git-20200104-dc63b5b94-xpmod - have big new problem: download make 1 hour?... or 2 hours another file download? indication in download display.... So I've cancelled this download in the latest Moebius 55, downloaded with New Moon.... Then I dare to ask in Kitaro1's way: to make usable (by everybody) browsers, could you please give modifications to support HTML5 (H.264, MSE & H.264) in some of your browsers that miss this essential, crucial feature (bnavigator before all, then firefox 45, ArcticFox). Please. Working Link to test youtube HTML5 features ( yes I post this link for those of you who don't know this link, not for you): http://web.archive.org/web/20190805082454/https://www.youtube.com/html5 Edit: Latest bnavigator (Borealis) bnavigator.win32-20200104-beb2221f-uxp-26b297510-xpmod - check to remove uBlock O. - so NOT usable by me...I would like to have the uBlock O., uMatrix etc, sorry... - latest version of your Borealis working with uBlock Origin is from 20190907 ...
    1 point
  15. Why not making a poll? Instead of brainstorming to the infinity and beyond, IMHO a logical choice would be to choose the most viable proposals made so far and make a poll. The one that receives the most votes is the winning one and can be offered to Matt. I personally prefer his names, so I would vote for his proposal. But it is the majority that wins. Let's make a poll and settle this for good.
    1 point
  16. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200104-fd382bb-uxp-26b297510-xpmod.7z Win64 https://o.rths.ml/basilisk/basilisk52-g4.5.win64-git-20200104-fd382bb-uxp-26b297510-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rths.ml/basilisk/basilisk52-g4.5.win32-git-20200104-fd382bb-uxp-26b297510-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win32-git-20200104-d6dd25b5e-uxp-26b297510-xpmod.7z Win64 https://o.rths.ml/palemoon/palemoon-28.9.0a1.win64-git-20200104-d6dd25b5e-uxp-26b297510-xpmod.7z Official UXP changes since my last build: - Issue #1118 Part 1: Split out part of nsDocShell::AddState into a separate method. (027fbae80) - Issue #1118 Part 2: Allow UpdateURLAndHistory to work even if mOSHE is null, if we're doing a replace. (f5c848aa9) - Issue #1118 Part 3: Add a public RemoveAllListeners method on EventListenerManager. (80e4577e3) - Issue #1118 Part 4: Allow UpdateURLAndHistory to work even if there's no root session history. (c1013e912) - Update README (492624a71) - Forward to new tree structure. (54091ecab) - Issue #1118 - Part 5: Change the way document.open() works (dfa7af70c) - Bug 1341238 - Don't hang on to pointer from temporary NS_LossyConvertUTF16toASCII. (4e6294b24) - Issue #1118 - Part 6: Fix various tests that are no longer correct. (f71108680) - Issue #1118 - Part 7: Remove no-longer-used mWillReparent debug code. (b1c7cc07c) - Issue #1118 - Part 8: Remove no-longer-used mDidDocumentOpen and CheckForOutdatedParent() (e0f0b3492) - Merge pull request #1334 from g4jc/bug1333 (84f4806b4) - Issue #1118 - Part 9: Don't allow reuse of unlinked CallbackObjectHolder. (8b8862346) - Issue #1332 - Backport promise-based media playback (735418fa3) - Fix typo. (c3ed7420f) - Merge pull request #1336 from athenian200/html-media-hack (f60bbaf9e) - Merge pull request #1335 from MoonchildProductions/document_open (357405f63) - Bug 1176399 - Multiple requests for master password when GMail OAuth2 is enabled. (0395a076c) - Bug 1453643 - Enable proper retry on oauth2 authenication failure. (a4ab8fd19) - Bug 1597933 - clean up OAuth2 code: remove responseType which is always code. (3dae851d2) - Bug 1597933 - improve OAuth2 params parsing. (f532cec97) - Bug 1597933 - don't pass string constants to determine OAuth refresh token or not. (fd9d39ac9) - Bug 1597933 - use fetch + URLSearchParms instead of Http.jsm to request OAuth2 access token. (8fdd883f7) - Bug 1597933 - Use URLSearchParams for setting params for OAuth2 authorization request. (fb7de243f) - Bug 1599054 - allow callers to ommit sending OAuth2 client_secret parameter. (12eb1554f) - Merge pull request #1340 from g4jc/mailnews_enhance (26b297510) My changes since my last build: - patch from Sami<samiwieciekto at g mail>: Lowered mMaxTextureSize from 4096 to 2048 to allow older graphic cards (04671d8d6) - patch from Sami<samiwieciekto at g mail> with pref guard: Enable skipping loop filter and allow non spec compliant speedup tricks. to enable, create new boolean pref "media.ffmpeg.skip_loop_filter" and set it to true. (dd094ae55) - update NSPR to 4.24 and keep NSPR Bug 1586070 and win64 patch intact. (0b9855b84) - Update NSS to 3.48 while keeping vc2013 hackfix and no-sslkeylogfile intact. (171849c8e) - import NSS tip revs: bug1594965, bug1593167, bug1603027, bug1600144, bug1590001, bug1603257, bug1605545, bug1513586 (9778f15c7) There are no new Official Pale-Moon & Basilisk changes since my last build.
    1 point
  17. In the first builds of Windows 10, which did not yet have a name, there was NT 6.4. Then, when the name became Windows 10, then the kernel became NT 10. There were no NT 7-9.
    1 point
  18. That apple software update thingy always nagged on my mother's computer. With XP and now 8.1... But yeah, that would go well with this Christmas installation over here: I have no idea why they picked those two letters. And for more evidence that Windows XP dominated Christmas 2019: https://www.neowin.net/news/the-new-windows-ugly-sweater-has-a-windows-xp-theme
    1 point
  19. Something like 'Neptune' ... is that name already used somewhere?. ... perhaps ''MoonBeam'... I myself lean to an 'interstellar space' connected name but I can't think of too many at this time. Just not some silly name ... not too crazy about the name 'Whistler'. I'm only interested in New Moon 28 which along with K-Meleon ... is all I use currently. I like 'New Moon' but I guess it has to go ... there are so many browsers to deal with but they all have a 'purpose' for somebody. ...
    1 point
  20. The MOZ_APP_NAME would stay the same of course, that's fine. Same with application.ini who's values failing the existence of some alt build configuration dictate the location of the application profile. SAME goes with NSIS generated installer/uninstaller and helper.exe used by both NSIS and shellservice as well as shellservice its self. Unfortunately, this is set in stone and it is too unreasonable to change that stuff now. Maybe two years ago but not now as it would cause too much end-user trouble. Not to mention it would be annoying from a patch porting point of view. So that's fine. So just need to change the name in branding configure.sh, graphical assets, and l10n. Pretty simple once you have the name and logo. Now, I can sort of dig the circles with lines in em and perhaps do something with the concept though they MAY be a bit abstract. However, I hope that modified Firefox logo is not a serious contender because clearly that would not acceptable to Mozilla as it would get the the drones all fired up in a second and of course blame us not you for it. The general problem with the New Moon branding was it was intended to be basically like the Firefox Nightly branding and while yes it pulled double duty as generic branding anyone could use, it is still intrinsically linked to us and despite the feeling from some people here that there is and never has been any confusion, I can tell you there is.. People know that Pale Moon is the older Firefox-based browser with the interface of Firefox 4-28 and that builds are sometimes called New Moon. But with the divergent path of what continues to happen to support Windows XP what is produced isn't even going to be an unbranded Pale Moon for Windows XP as most people see it. Perhaps that is how you see it but as time goes on the differences mount. Let me put it to you another way, what if we had just kept the original non-trademarked Nightly branding for Pale Moon, both Basilisk's, and you also created your other half-dozen Firefox-based builds.. ALL called Nightly because that is what was there. How could you tell them apart then? Is it reasonable to put the burden on us to explain to people that the Windows XP builds you produce aren't the same as someone else producing Windows 7 unbranded builds or unbranded mac builds which also use the New Moon branding because mac isn't at the official level yet. The un-knowledgeable user who doesn't read more than maybe two sentences of a paragraph would assume New Moon == Pale Moon because they look the same and because despite being referred to as generic branding the name is too unique and intrinsically linked with us. This is the result of a decision made six years ago and it turns out to not have been a very good one on our part. Let me also say again, that this happens in the wild. THERE IS CONFUSION because I have specifically gone out of my way to berate and s*** on the confused user because it p***ed me the hell off and does every single time. Should I? No. Do I? Yeah. Should I continue to do so.. Well despite what one may conclude I actually don't know.. I do know that I don't really want to be angry about it anymore. I do know that over the past two years it has accomplished nothing. I also know that roytam1 took the unofficial branding as-is but hasn't been bothered to change it for whatever reason that may be. I do know I am a half-way decent designer and have the technical knowledge to implement it easily for roytam1 to slot into place. I also figured I had nothing to loose by str8 up offering to do it instead of expecting someone else to. A very common situation I find my self in a lot these days actually. I talked, bitched, complained, pleaded with and begged SeaMonkey for almost 10 years to not turn out the way it turned out and it accomplished nothing but in the Pale Moon project and beyond to the Unified XUL Platform, lots of things have gotten done through hard a** work via cooperation, coordination, and discussion and maybe that should be applied elsewhere. Especially to places that have historically annoyed the hell out of me for whatever real or imagined reason. After all, it is a process to better ones self and help make world at large better too. Can't have it all in a day but you can't have anything if you don't try. So I am trying (and yes there is likely a joke in there). Besides, I can't keep calling the paradigm "new" if it is the same old crap, eh?
    1 point
  21. If you delve back into the original 200-page thread, you'll find plenty of suggestions for new names. None caught on, probably because we soon had far too many to choose from! I tried to avoid that this time, figuring @Matt A. Tobin's suggested names were good enough and I didn't want to start another avalanche of name suggestions So far the leading alternative suggestion seems to be RoyFox and variations thereon. Which would also be fine by me. ================ Well yes, but I think the immediate concern is rebranding New Moon, Serpent, Navigator, and Interlink (mail/news). The others (FF 45 SSE, Arctic Fox, K-Meleon) can remain as they are for now. So maybe four polls (five if you consider Serpent 52 and 55 separate).
    1 point
  22. The @LoneCrusader is a dear friend and it grieves me to be pushed into arguing publicly with him about this, but I was never given any choice about it, since he seems to be the main (and, ATM, only) voice oposing the (re-)branding of the browsers. That said... True enough. But, while not forgetting, moving on is sometimes required, and I think this is one such case. There is a time for appeasing, and one for open confilct. I hope we won't keep arguing uselessly until we are beyond all possible compromise. Most of those in this thread are for the (re-)branding. I think that PoV has already won by acclamation. ... and you are the only one doing quite a strong effort to derail any compromise, when most of us don't see the facts in the same light as you do.
    1 point
  23. You're right, of course; those languages are closely related and I just got them mixed up in my head. Actually I just remembered: it's rey in Spanish; roy is French! Apologies to speakers of both languages. It sounds like JustOff (author of uBO Updater) is essentially taking over further development of the legacy branch of uBO while Gorhill concentrates on the WE branch. Probably just as well.
    1 point
  24. I personally believe the rebrand should take place, as well as sticking to the 28.x (presently New Moon) builds until 29.x becomes unsupported/surpassed by a potential version 30. When it comes to browser names, using code names from older Microsoft products does make sense (and shares a common theme), but I would prefer more original names.
    1 point
  25. Rebranding ect.: I've always had a clear opinion myself that different builds and versions should be easily discernible for users. And easily, without needing expert knowledge. Otherwise confusions are intended and will lead to completely unnecessary probs and wasting much time, without any need. Side note: similar prob by the way for K-Meleon. Before the version upgrade to 76.1, all modern Goanna builds declared themselves as "K-Meleon 76", exactly the same as the much older Gecko builds from 2016, which are also "K-Meleon 76". No way for users to tell apart, except at download time, before unzipping and running it (at least the 7z package has a different name, KM-Goanna, but that will quickly be forgotten.) Although our KM main dev had already suggested the logical next version 77 for those much advanced Goanna builds, before vanishing again. But I was rather lonely with that opinion too, and got attacked for it from several fellow KM fans, when daring to mention it 2-3 times. No idea why it's so hard to grasp that such intentional confusions are causing completely unnecessary probs for others and should be avoided, at least if requiring hardly any effort, only insight. Back to here. To me, this current conflict too just demonstrates all over again that almost all extremely one-sided black/white ideologies are just harmful. And again shows that strictly ideological parties aren't ready to move 1mm, no matter how much it harms others - as long as not forced by external circumstances. No chance if not yet harming themselves too much too, strongly enough, beyond their own limit. Luckily, this point and insight seems to finally be reached now - Yay! :D Tobin has done a GREAT step forward, although it's clear it's not a general change of attitude or end of war, but that doesn't matter. It's still a very positive and acceptable step forward (for now), much more as could be expected, with no strings attached (it seems, and hopefully no trojan horse) And finally there's also a real chance to move a bit forward from the other side too, taking the outstretched helpful hand for the benefit of both, and for less expert users too :-) Regardless that fundamental opinions and attitudes never change, but solving single issues independently is still possible and helps all sides!
    1 point
  26. The latest ArcticFox 27.9, New Moon 28.9, Serpent/Basilisk 52 - all are working perfectly! - all are RoyFoxes! - I see "Arctic RoyFox", "New RoyFox", and "RoyFox 52", too "RoyFox 55" (and beyond....) new brandings, what do you think about This is the first time I downloaded ArcticFox - this browser works very well, I want to customize it, add my lighweight theme, my extensions... then get my more complete impressions later. Thank you RoyTam1 for your HARD and FRUITFUL work!
    1 point
  27. Hmmm does this count? Image only link: https://pbs.twimg.com/media/EMMG-8aUcAAYo9i?format=jpg&name=4096x4096
    1 point
  28. Learned a new word today! Although in these parts, we still call it, uh, a still... It's a bit belated, but I wanted to say thanks for that tip! It's finally given me a way to maintain multiple Firefox versions on the same PC, each with its own profile, without a kludge like setting up separate Windows users (and having to log out and back in) to access each version. Just make sure to include the intended FF version in the name of each profile you set up. Very useful when you want to test FF versions ranging from 45 through Quantum to "Firefox Browser" (or whatever the name of the week is). Even on XP, I now have FF 45 SSE, FF 52 ESR, and FF 53 (patched to run with XomPie) all coexisting in relative peace.
    1 point
  29. No. We ain't. Of course one cannot be sure about anything, that's how things work in life. But when one offers to back his requests with his own hard work (and recognized expertise) , I reckon it's wise to accept. And I do agree there's no downside, whatsoever, to it. ======= Well, I do like most of the proposals. However, Serpent 52 might as well become Moonshine, which sure has a bite, as serpents do. And, if so, the brand might be an alembic. ======= Then again, to speed things up, the finished brandings might be sent to @roytam1 as pull requests to this current structures, so as to avoid having to decide on migrating build structures (or whatever that is called) at the same time the branding issue gets solved, at last.
    1 point
  30. Branding is hard work. You don't need just a name; you also need artwork, and you need to make sure your artwork doesn't tread on someone else's IP. I for one am glad @Matt A. Tobin is willing to do that work (and seems pretty good at it, too); it's not a field most of us have much skill at. At one time I created an icon for Moebius (I spell it with the e so I don't need an umlaut on the o); I'll attach it here. For Neptune, I'd go with the planet; plenty of public-domain Voyager images to choose from, and Neptune's trident might be too suggestive of the Devil for some folks moebius-triangle.ico
    1 point
  31. I'm all for your brands. Hope the others agree as well! ☺
    1 point
  32. Thank you. Well I have been awake for about 24 hours. I'll do some thinking and conceptualizing when I next awake.. You guys let me know what you decide on the direction of the all this.
    1 point
  33. The largest the logo icon would be anywhere is 256x256 which is the second largest size. At that resolution it doesn't look as chunky as it does in the 512 size. But let's see..
    1 point
  34. Edited previous post with a wordmark.. Notice the font THE REAL QUESTION IS.. can I do half as good three more times AND will people LIKE it.. hmmmmmm.
    1 point
  35. Looks nice! Simple and effective. I like it.
    1 point
  36. for me, I just want a working browser and naming is unimportant to me. If just changing the names and no artwork works need to be done in short period (as I have no time working on artwork and I have no sense about audio-visual), then it can be done. As I have no idea what name to use, I'd create a poll here and let people to choose use names that Tobin given, or a name by other forum member suggested, and also give out a "No" option for reference. if these can be accepted by people, then it can be proceeded afterwards.
    1 point
  37. I agree with all the line. A fruitful collaboration can be spawned out of this, and I hope @roytam1 will agree.
    1 point
  38. Okay, the olive branch is here, really. Two heads are better that one, right? It always helps to bounce ideas. United we stand, divided we fall, "we're all in the same boat here". Make hay while the sun shines.
    1 point
  39. I have never posted about this so far, but Matt is right. A unique brand for the browsers is the best way to make them stand out and finally get this issue sorted out for good. I have been in this forum for around a year, previously as a lurker and since this spring as a member, and I do believe that a tense atmosphere between the PM team and Roytam1 doesn't help at making things better (maybe he can also help you improve the shortcomings of some browsers, such as the infamous stuttering of 45 ESR SSE, that is a pet peeve of mine, you know 😛). Why not burying the axe of war for good? I know that between you and Matt there seems to be a non idyllic relationship, but in my opinion, Matt is offering a precious help @Roytam1 and his in-depth knowledge of the browser can help you further along the way. You know I use your browsers regularly on my RDD, and everything I want for those is to be even more excellent than they already are. In my opinion you should not ignore his offer.
    1 point
  40. Ok.. I just a few posts ago offered to help him simplify his entire process with a unified application repository as well as doing all new branding for four applications WHILE still maintaining the profile directory path already in use. I offered to do ALL THE WORK to accomplish this.. So I don't take to kindly to your assumption of my level of sincerity. I can totally understand wanting to put off doing branding as long as possible.. Hell I only JUST completed my Official branding for Borealis Navigator as I am planning to make a release of in the near future. I also know how difficult it is to come up with names and logos that are effective as well, though I have an easier time of it than actually implementing it. The fact is it does still cause confusion and lead to the wrong conclusions from people.. Not a month goes by that at LEAST one person wants something for a "Pale Moon for Windows XP" or whatnot. They don't understand the difference between what roytam1 is doing and what WE are doing. Users using these unofficial builds on Windows XP do nothing for us but take up our time and sabotage our efficiency with dealing with support questions from users who don't know any better. It is hard enough to accomplish when they are using our products. I gave you a totally unique concept for branding of applications all built by one person using one platform codebase and offered to do the work. I would have thought this would be great since it is obvious roytam1 has no problem whatsoever using other people's names, images, and work to produce what he wants. After all if I had called Borealis and Interlink Neptune and Lonestar respectively with their own artwork as the Unofficial Branding then he would be using it. How is this any different? So I am left with ONLY two conclusions both of which REALLY suck.. He is too lazy to change it of which I have offered to do it for him OR he is deliberately trying to damage us by continued association of which he and all of you don't believe anyway and I really don't want to believe is true anymore even if it is cause it is depressing. SO LET'S DO A THING AND FINALLY SORT THIS. EDIT- IF he doesn't want to use the COMM configuration and he wants to keep everything in the forked platform repo we can do it that way too. I know all the things that need changed and setting git patches for changed paths is easy. Also, I can reverse the alt packaging stuff for you and since you selectively take patches from us anyway you can just skip further ones relating to that. I can answer questions you may have like regarding the build system, let you know what is happening and why, etc.. All I want in return is for your projects to BE actual projects.
    1 point
  41. I really don't see why it is such a big problem to create an original logo/name. @Matt A. Tobin is extending the olive branch, THEN SOME, and being flat out ignored.
    1 point
  42. The name "New Moon" was built into the Pale Moon source repo as a placeholder for anyone making an unofficial build of Pale Moon. It was always recognized as a temporary name. In the original thread, I and many others made many clever suggestions for a permanent name, but none caught on, so @roytam1 just kept using the New Moon name. I'm reluctant to restart the cacophony of suggested names again. "Whistler" may not be that inspiring, but it's not bad and fits a theme. Let's get this done at last.
    1 point
  43. Many older devices lack support for eXecute Disable, which renders them incompatible with with newer versions of Windows. Only those who are fans of planned obsolescence, and landfills full of e-waste, would oppose an effort to keep old operating systems alive.
    1 point
  44. It's not Windows XP. If any version of windows, that thick taskbar, and the small, non-green start button would say that it's Windows 7 (Windows Basic theme) But its probably not windows. https://www.theinquirer.net/inquirer/news/2446733/russia-plans-a-switch-to-linux-to-rid-the-country-of-western-pigdogs https://www.defenseone.com/technology/2019/05/russias-microsoft-knockoff-gets-security-upgrade/157310/ Apparently some unnamed russian internet offical has confirmed it to be XP, but it sure doesnt look like it. I’m not convinced.
    1 point
  45. the best hackers work for him and can make the necessary tools to prevent any kind of hack regardless his OS
    1 point
  46. hmm, this appears to be 7/8: http://en.kremlin.ru/events/president/news/62124/photos/62208 The systray area looks kinda like Luna, but the start button? the icons don't really look like XP to me either. Or he is just proficient at skinning XP. He always seemed like a win2k guy to me. Anyway I saw XP in a dry cleaner's shop on Friday, located in one of the halls leading out of Central Station in Montreal. As it was the evening rush hour things were moving along briskly so I couldn't take a photo.
    1 point
  47. It's been a long time, but I finally managed to update the repository: Replaced Monthly Rollup with the new KB4530695 (located on the root directory of the repository) Added Security Only Updates, KB4516051, KB4520009, KB4525239 and KB4530719 (located in the folder "/Security Only (Post August 2018)") Added Servicing Stack Update KB4531787 (located on the root directory of the repository) Replaced Internet Explorer Cumulative Update with KB4530677 (located in the folder "/Security Only (Post August 2018)") Updated SHA2 update KB4474419 to v4 (located in the folder "/SHA2") Replaced .NET Security and Quality Rollups: KB4507003 for .NET Framework 2.0 and 3.0 (located in "/NET 2.0 SP2/Security and Quality Rollup"); KB4507001 for .NET Framework 4.5 (located in "/NET 4.5.2/Security and Quality Rollup"); KB4533012 for .NET Framework 4.6 (located in "/NET 4.6-4.6.1/Security and Quality Rollup"). Updated the TLS 1.1 and 1.2 enabling reg file to include x64 (located in "/Extras") I hope I didn't miss any updates. This should cover the 4 months of updates missing. I think all of these updates require SHA2 support, so be sure to first install the Servicing Stack and SHA2 updates found in the "SHA2" folder. After Server 2008's EOL there might be a chance to use Extended Security updates on Vista until 2023, thanks to @abbodi1406's "Bypass Windows 7 ESU" hosted on MyDigitalLife forums, though I don't think anybody has tested the bypass on an actual Vista install. Merry Christmas, happy New Year and here's to 3 more years of patching https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w
    1 point
  48. Sorry for the double post. Since you have installed all the browsers, you must use the 45 ESR version of the Patch + Enforcer with Firefox 45 ESR SSE and SeaMonkey. With Basilisk/Serpent/New Moon 28, you must use the 52 ESR/New Moon 28 version of the Patch + the 45 ESR Enforcer. The next version of the patch, of which the release is imminent, will eliminate the New Moon 28 version as I am going to release the 52 ESR version without E10S. With New Moon 27 and K-Meleon Goanna, you must use the 38 ESR version of the Patch + Enforcer. Could an IA-32 version be possible, much like how you are doing with SSErpent?
    1 point
  49. @roytam1: Could later releases provide a GPG signature? Security is quite a concern for browsers.
    1 point
×
×
  • Create New...