Jump to content

VistaLover

Member
  • Posts

    2,243
  • Joined

  • Last visited

  • Days Won

    93
  • Donations

    0.00 USD 
  • Country

    Greece

Everything posted by VistaLover

  1. ... Going by his recent post , equally unhelpful as it consisted only of screengrabs with "the browser" localised in Russian, I'd hazard a guess and say it's New Moon 28 ... @Slavich : Please , when filing "not working" reports: 1. Provide details of OS and its architecture 2, Provide details of the browser used (name of, bitness, build version) 3. Post actual links of misbehaving websites 4. Describe in more words the exact nature of the error(s); what were you expecting to happen and what actually happens... 5. If the website in question requires a registration for the "bug" to be witnessed, then understand that other members here and/or the browser maintainer won't be able to replicate the bug without such a website account... 6. Because of "current world situation" (won't say more, politics is NOT allowed in this forum), Russia-based websites/services might be inaccessible to "the rest" of the world, this fact imposes additional hurdles for "us" to troubleshoot your reported "bugs"... 7. This is an English "speaking" international forum, try to refrain from posting "localised" debugging info (let alone inside images ) ... 8. Resort to posting images where absolutely necessary (and images should be accompanied by "explaining" text) As a rule of thumb, whenever possible, avoid UXP-based browsers to conduct financial transactions on line, as those "services" (banks, etc.) are known to be "pretty particular" with the user-agents/clients they allow ... In closing, it's now the second half of 2023, you shouldn't treat the roytam1 offered browsers as a "panacea"; they can accomplish many things, but not everything you throw at them (especially on older H/W); while the "upstream" devs try to tackle UXP's shortcomings as best as they can, often times these efforts (commendable as they may be ) are not enough to compete with recent Chromium/Firefox (many websites/services are designed against) ... Many XP users here have attested they have to resort to a recent browser on Win7+ or on Android to complete successfully all of their online tasks; I. personally, have come to consider, especially in recent years, the UXP-based browsers I use (St52/NM28 & St55) as more of a "palliative" on my 'legacy" Vista laptop rather than full-blown browsing "solutions" (no disrespect intended at MCP devs and Roy ) ... Best regards .
  2. Thanks for your feedback ; your image proves that, at least, the main sTunnel executable launches/loads as expected in your system; what I do remain doubtful about is the correct functioning/loading of the openssl DLLs (v1.1.1u=1.1.1.21) shipped originally with the 5.70 package... Can you show a "Log Window" screenshot like the one I provided in my previous post? And, more importantly, does your current 5.70 setup work as intended for whatever you use it for? Apologies for being somewhat pushy , this isn't just for me, the whole XP community here should be certain that: Kindest regards
  3. ... But with latest UXP builds:
  4. That one was using openssl-1.0.2p (file version 1.0.2.16); yes, XP-compatible, but can't "do" TLSv1.3 ... Not all hope is lost for you ; if you are able to install stunnel-win32-5.70-openssl-1.1.1u under XP (can't test myself), this comes with DLLs libcrypto-1_1.dll and libssl-1_1.dll of file version 1.1.1.21; you can try to overwrite those two DLLs with the similarly named ones from this package below: https://rwijnsma.home.xs4all.nl/files/openssl/openssl-1.1.1t-win32-xpmod-sse.7z This package has been compiled to support XP SP3 and because it's of version 1.1.1, it also "does" TLSv1.3; as I instructed you already, you do have to check with DW (dependency walker) that the main sTunnel EXEs (stunnel.exe+tstunnel.exe) BOTH load OK under XP after the openssl DLLs have been replaced... Please report back ! Cheers.
  5. If on a UXP-based browser (Serpent 52, NM28, etc.), the "Download" button depicted is unresponsive ; it works, though, in Serpent 55 and 360EEv13.x ... If on a UXP-based browser, click on either the "Raw" button or the "View raw" link in the middle... @Ben Markson ; Which OS do you plan to use stunnel-win32-5.70-openssl-1.1.1u on? AFAIAA, this package requires Windows Vista SP2+; I don't have an XP box to test currently, but openssl-1.1.1* alone won't load under XP, and this is a known fact in the XP communities... Once you download the package in question, extract it with 7-zip and then inspect EXEs and DLLs with dependency walker ; I'm quite confident you'll find it has "fatal" issues under XP (assuming you want to deploy it under XP, per the thread's title ) ... Cheers PS: Below is a screengrab from my Vista SP2 32-bit laptop:
  6. The majority of these forked extensions are being accompanied by an online "source code repository", where it's easy to inspect/view the modifications applied; e.g., Stylem is a fork of the old Fx extension Stylish (by Jason Barnabe); Stylish was licensed initially with a GNU GPLv3 licence; prior to releasing Stylem, Lootyhoof created a fork of Stylish on GitHub, keeping the original licence: https://github.com/Lootyhoof/stylem This forked repo contains all info regarding the initial and current licences and provides easy access to the modified code; hence, one can do away with an "in-package" patch file; where Stylem is listed now in, e.g. ABBO: https://addons.basilisk-browser.org/addon/stylem/ , there's a prominent link to its Source Repository ; you're not inclined to start a "proper" GitHub repo, are you?
  7. I'm no authority on this ; some relevant links from "upstream": https://forum.palemoon.org/viewtopic.php?f=46&t=13655 https://forum.palemoon.org/viewtopic.php?f=46&t=26433 AIUI, if you modify the original source code and intend to distribute your mod in binary form (e.g. XPI), you have to, under the MPL-2.0, include in your redistribution package a) a copy of the original licence (or link to it), b) a detailed record (in the form of a patch/diff file) of the modifications you applied on the original source code and c) if you were granted permission from the original author(s) to keep the original "name", provide clear proof of that or, in the opposite case, use a "new" name for your own fork... As I said, not an expert on Open Source licencing ... Kind regards.
  8. ... You can add: https://dictionary.cambridge.org/ to the list of online dictionary "services" that don't properly load on UXP-based browsers, due to them not "sanctioning" the Goanna useragent slice ; below, a screengrab from a fresh NM28 profile: OTOH, with a SSUAO applied that doesn't contain the Goanna slice:
  9. ... Technically speaking, Sandboxie can't/shouldn't be regarded as a proper Antivirus/Internet Security Suite and/or a third party firewall application, as is the case with the software on the list you linked to ...
  10. ... You'd be surprised (I wasn't ): https://www.amazon.com/Smart-Toilets/s?k=Smart+Toilets
  11. +1000 ; and those "people responsible" (read Google) are currently in the process of making it (Web) even an uglier "monster" : https://msfn.org/board/topic/184944-could-web-enviornment-integrity-block-old-operating-systems
  12. Many thanks, then ... ... before? BTW, the EXEs have SHA-256 digital signatures of June 7th, 2023 ...
  13. ... You're just being biased there, like the uninformed masses ; they're not "obsolete" just because they're not based on a Chromium-type web engine... These browsers are a) still in demand (obviously "meager" ) b) still in use by those that use them c) still being maintained actively, thus I'd call them non-mainstream myself... The UXP application platform and the browsers built on it are open-source and freeware; as for the funding sources of Moonchild Productions, the main "entity" behind Pale Moon and its development, these are also public knowledge and easily searchable/find-able ; Partnership with Start.me, the default new tab page in PM, partnership with duckduckgo, the default search engine in PM, private donations by members of the PM community, as the first two income sources are not enough to cover infrastructure costs (server maintenance costs for various services related to PM, e.g. main website, forum website, extensions' website, internal update server, binary hosting services, etc.) ... For more detail, visit: https://www.palemoon.org/donations.shtml ("inside" joke easily understood by the UXP/Pale Moon communities) ... Kind regards
  14. x86: https://www.google.com/dl/release2/chrome/adjs6spifue5dxngiogotsz633pq_109.0.5414.149/109.0.5414.149_chrome_installer.exe x64: https://www.google.com/dl/release2/chrome/oeecyq7z2j4yyfoa4cev5c4o7e_109.0.5414.149/109.0.5414.149_chrome_installer.exe Source: reddit ...
  15. While your technical analysis is correct , what "I" think was meant by Milkinis was: Website authors of this era target/expect their sites to be opened by a browser based on a "recent" (or even the latest) version of the Chromium engine (I'll throw recent/latest Firefox into this mix), which is "multiprocesses-capable" and has multiprocess turned ON by default; it's even more "effective" in Chromium, as there's a separate process for each tab (by default) ... Website authors of this era are also "lazy" and would not design a page from scratch, instead they use pre-made templates and frameworks/webpacks, that also target a "recent" (or even the latest) version of the Chromium engine ; website authors of "today" don't particularly care about backwards-compatibility with older browser engines, especially since, some years ago, Internet Explorer 11 was thrown out of the picture (in favour of yet another Chrome clone , [Chr]Edge); and I'm sure we'll both agree that Pale Moon and the rest of the UXP-based browsers (even more "marginal" than PM itself) are well outside their "radars" ... In the comfort/knowledge a recent Chromium engine (especially on recent H/W) will be able to handle whatever one throws at it (and, even more importantly, will not alert the user if it struggles to render said webpage), these website authors will throw in "metric tons" of Javascript/CSS code, still and moving graphics galore, etc., bloating it considerably, succumbing to the recent web-design "trends" that are "supposed" to attract more viewers/"clickers" ... Invariably, these "over-bloated" websites are expected to lag considerably on the likes of Pale Moon and its "cousins", due to them being designed as single-process and having inherited several unresolved bugs (which have been discussed on and off in the relevant threads) from their initial fork-point of Mozilla ESR 52.6, that Mozilla left to bit-rot, as "they" had moved on to a different engine with Quantum onwards... In closing, I think this was the gist of: Regards ...
  16. ... FWIW, that "Original download link" now produces a "Server not found" error ...
  17. ... Indeed , but your (GitHub/MSFN) username (roytam1) isn't explicitly mentioned there, just a link (8a0897d23f) to your GitHub repo and code .,,
  18. Serpent 52 is a browser application built on (a fork of) the UXP platform, the same platform the official Pale Moon browser (by Moonchild Productions) is built on; more technically, Serpent 52 is a fork of the official Basilisk browser application, but these two forks have somewhat diverged from each other over time... While UXP was forked from Mozilla 52.6esr initially (and that was years ago), UXP-based browsers have been equipped with a plethora of recent web API technologies and the XP-compatible forks (New Moon 28/Serpent 52/a few other) have empowered "legacy" OS (XP/Vista) users to surf a very large chunk of the 2023 WWW ... Be that as it may, no UXP-based browser will be a perfect match, webcompatibility-wise, for recent versions of Google Chrome and Mozilla Firefox, especially on the many, JS-infested , "popular" sites of this era... The XP-compatible UXP-forks are being maintained by roytam1, more info can be found in the respective thread(s) ...
  19. ... and: ... Today was less hot here , thus I had a second chance to research this more diligently ... According to MDN: https://developer.mozilla.org/en-US/docs/Web/CSS/:where#browser_compatibility the ":where()" pseudo-selector was first implemented in Mozilla Firefox 78 and Chrome 88; but, as most of us know, Kafan MiniBrowser was based on Chromium 87 ; some investigation revealed that my own copy of it is able to display properly the MediaMarkt laptop/notebook entries because, in tweaking my MiniBrowser copy, I had enabled below flag: chrome://flags/#enable-experimental-web-platform-features Turns out that flag activates (among other things) CSS features that have been officially introduced in Chromium 88+; indeed, with that flag disabled (the default setting): but with it enabled (i.e. how I have it myself): Sorry for any eventual misunderstanding ...
  20. FWIW : It's quite possible something inside Dixel's browser profile isn't "liked" by imgur servers; but if he's fine with it, so am I ... Sorry again for the misunderstanding, have a good night all of you ...
  21. ... Right; so it's something along the lines of: Apologies for misinterpreting your post, but, in my defense, it was "just an image" post; the imgur links continue to display properly for me here, thus my IP has not abused their servers ; if you're impatient, you could restart your modem/router to get a new IP address from your ISP (if possible), or use some other means to evade imgur's block (assuming it's IP-based); also, several privacy-enhancing extensions/settings are known to not go down well with third party services like image-hosters ... I always upload to imgur as an unregistered/anonymous user, I have no account with them; if a "view limit" is being imposed, then it's solely on their side ...
  22. @Dixel : I can't seem to understand the gist of your latest post ; my post you seem to have referenced has 3 "linked" images (hosted on imgur) that display properly here in both Serpent 52 and 360EEv13; these image attachments won't become "dead" unless imgur go out of business... https://i.imgur.com/qNoCUd1.png https://i.imgur.com/S02zeSn.png https://i.imgur.com/pyWLAMH.png If you're somehow blocking imgur or it's simply a regional CDN issue for you, obviously I have zero control over it... If you simply wanted to comment on NHTPG's practice of: who's been using the native (but size-limited for "plain" users) file-attachment feature of MSFN, then you should have chosen one of his posts with deleted image attachments, e.g. that one ... In any case, I wasn't amused at all ...
  23. Is that Proxomitron "talk" ? Can you offer code to implement this for UXP in the UCyborg userscript implementation? PS: I can't catch up with both of you exchanging "instagram"-type messages while I prepare a "normal" post with images (which have to be edited and uploaded to a third party service) attached ...
  24. ... Please read my previous post here and try the same "laptop" entries in: https://www.mediamarkt.de/de/category/notebooks-362.html I've tried myself ca. an hour ago and the same issue (image overlap on text) manifests itself in the Ch86-based forks : ; additionally, if you had paid closer attention to the screengrab UCyborg posted here, you'd have spotted the still missing images of the notebooks themselves: Since those laptop entries display OK in [Chr]Edge 94, the CSS/JS feature "mediamarkt.de" rely on was implemented between Chromium 87-94 ... But, guess what? Kafan MiniBrowser seems to display correctly those laptop photos (I have enabled dark mode there): ... so, by pure chance, we now have an answer to your previous question in another subforum : So, it's a feature first implemented in Chromium 87 (actually, in Chromium 88; kindly read this followup ...)
  25. In case no-one here noticed it already , "our" roytam1 is now formally mentioned inside the "official" UXP repo: https://repo.palemoon.org/MoonchildProductions/UXP/commit/7f8ea9ae2f92b71eefcd1dc286baaf529cc5686a Thanks to Brian Smith (aka dbsoft), the MacOS dev member of MCP ...
×
×
  • Create New...