Jump to content

VistaLover

Member
  • Posts

    2,105
  • Joined

  • Last visited

  • Days Won

    93
  • Donations

    0.00 USD 
  • Country

    Greece

Everything posted by VistaLover

  1. ... Well, whaddayaknow? A page in 2023 still employing Adobe Flash Player (viewed in St52): ... "Downside" is the suggested app is a payware, with only a 14d trial period offered (in contrast to previous apps mentioned, all freeware ; and no, I have nothing against "payware", coders do still need to make ends meet) ...
  2. ... Yes, I know - you were perfectly clear in the first place: a fresh/clean St52 profile isn't able to display correctly/permanently the embedded auf1.tv video player; my post (you replied to) was meant for St52 users wishing to view auf1.tv video-on-demand (VOD) content (probably inside Germany and the German speaking, neighbouring, countries); at least one extension is needed for that, in my case I made it possible with uBO-legacy and a custom filter (other ways exist, e.g. with uBO-legacy and custom allow/deny rules, as suggested by UCyborg, or with eMatrix and special settings, as suggested by Astroskipper); personally, I find it quite inconceivable for a normal St52 user in this day and age NOT to have a content blocker installed , so my advice was geared towards them! Hope I made it extra clear now ; warm greetings...
  3. ... However, if you have just uBlockO-legacy installed, in the My Filters tab just create the one below: ! 2023-09 auf1.tv ||auf1.radio/api/get$xmlhttprequest,domain=auf1.tv Then, the auf1.tv embedded video player will stay put in St52, too (otherwise, it starts to load, displays briefly and then moves out of sight , resulting in the image you attached in your "previous reply" ) :
  4. ... Please, please , any chance you can also post the link to the 32-bit variety ? Thanks in advance!
  5. It'd be quite simple to create a portable version (in PAF format) of FxESR-102.15.1 Download https://sourceforge.net/projects/portableapps/files/Mozilla Firefox%2C Portable Ed./Mozilla Firefox ESR%2C Portable Edition 102.13.0/FirefoxPortableESR_102.13.0_German.paf.exe/download Install/extract it to a disk location of your own choosing. Navigate to .\PortableApps\FirefoxPortableESR\App\ The contents of directories "Firefox" (32-bit) & "Firefox64" (64-bit) would have to be deleted and substituted with the 102.15.1 ones. https://ftp.mozilla.org/pub/firefox/releases/102.15.1esr/win32/de/Firefox Setup 102.15.1esr.exe Download, extract with 7-zip; the contents of the extracted "core" dir should be placed inside the above "Firefox" dir https://ftp.mozilla.org/pub/firefox/releases/102.15.1esr/win64/de/Firefox Setup 102.15.1esr.exe Download, extract with 7-zip; the contents of the extracted "core" dir should be placed inside the above "Firefox64" dir You should be done! When you then invoke the portable PAF launcher (FirefoxPortable.exe), it should launch Fx-102.15.1-x86 (if on a x86 OS) or Fx-102.15.1-x64 if on a x64 OS... (Apologies for the OTs, but I, too, am responding to OTs, sort of ...). Kind regards ...
  6. ... But Firefox ESR 115.2.1 can also run on such WinOSes; it's Fx>=116.0 that isn't supported on Win<10; FWIW, Fx-116.0.3, launched via its "zip" version (extracted from its EXE installer), runs fine on my sister's Win7 SP1 x64 laptop - but, most sadly, 116.0.3 doesn't contain the libwebp patch, so I had her back on 115.2.1 (downgrade was possible, because a back-up of the 115.2.0 profile was created and kept prior to force-updating her to 116.0.3 ) ...
  7. ... I am, thanks (in Serpent 52) ... ... I have done so just now ; yes, very handy when going through various VPN nodes! But, in order not to abuse the IP-checking service, I set it back to "45min" or, even, "Never" when I'm done using my VPN ... Regards .
  8. Agreed on both ; as a consequence, I find the recent discussion in this page a bit "premature" ; as a Vista user, I have found out by now (often the "painful" way ) that both "officially" and "non-officially" (more so ) advertised OS compatibilities with "legacy" MS OSes are to be taken cum grano salis ; as the old adage goes: "the proof is in the pudding"; @WSC4, you shall have the last word on this ...
  9. The German media (TV) portal Tele5: https://tele5.de/mediathek was "overhauled" recently (you guess what comes next ), as a result UXP-based browsers now won't load at all their embedded (JS-based) HTML5 player, even when the geo-resrtiction has been circumvented (whitelisted DE IP address via VPN/HTTPS proxy, etc.); e.g., loading in latest NM28 below URL: https://tele5.de/mediathek/die-saeulen-der-erde-teil-1-und-2 one ends up with: Does anyone have any faint idea what type of "Chrome-ism" is it that they require now , as (yes, you guessed right again ) Chromium86-based 360EEv13 is quite capable of loading that JS player (and initiating playback as well):
  10. After Mozilla, in their infinite wisdom (), chose to make almost everything "async", user control over the length/size of saved history was removed in Fx-4.0+ ... E.g. read below: https://support.mozilla.org/en-US/questions/854680 https://support.mozilla.org/en-US/questions/864527 https://support.mozilla.org/en-US/questions/1059856 Thus, without an extension, you'd have to periodically purge older history entries inside Library yourself, i.e. manually ... For NM27/28, there exists an "official" extension below: https://addons.palemoon.org/addon/expire-history-by-days/ Haven't tried it myself , you can test it in a copy of your NM profile... PS: CAA holds a Fx-targeting version, caa:addon/expire-history-by-days (v1.3.0), which should be compatible with both St52/55; WE-format extensions recommended for Fx (that should work with St): https://addons.mozilla.org/en-US/firefox/addon/expire-history-by-days/ https://addons.mozilla.org/en-US/firefox/addon/history-cleaner/ https://addons.mozilla.org/en-US/firefox/addon/historia/ (again, NOT tested by me in St52) ...
  11. Thanks for your genuine concern ; I live in Northern Greece, in a region that was spared by that enormous physical disaster, whose magnitude was never before seen in European territories (but I do remember the floods in Germany a year or more (?) ago); Thessaly (and, especially, Magnesia), the most fertile Greek region, has suffered the most acute blow of Daniel, but the mourning sentiment is shared by the whole Greek nation (the floods only accentuated the sense of sorrow already caused by the August wildfires, which practically completely charred the last virgin forests of Dadia, in the Evros region, close to the Turkish borders... The infrastructure in Thessaly will take from 3-5 years to be restored, the estimated cost from the wildfires+floods is in the €2bn region ... Comforting to know , since, according to the media here, Saola was pretty intense ...
  12. ... Again, cautionary words from "upstream" : https://forum.palemoon.org/viewtopic.php?p=242821#p242821 ... So, as I've stated multiple times in the past myself, "use e10s at your own risk" (I'm not, if you care to ask ) ...
  13. ... Well. the Protonmail can't-log-in bug has now hit "upstream", with the release of PM 32.4.0 : https://forum.palemoon.org/viewtopic.php?f=3&t=30256 As is common in such cases , Moonchild was quick to put the blame on Protonmail rather than on his own browser ... It is also suggested there that @Mehmed's solution posted here isn't really foolproof, because the bodies of older e-mails, encrypted with the old RSA (2048) 4096-bit key, can't be decrypted with the newly created ECC Curve25519 key and, as a consequence, those older e-mails can't be read anymore by their original recipient ...
  14. ... According to my tests (and records of them kept ), the FB related PR#7890 was already present in your py3.8 : [debug] yt-dlp version nightly@2023.09.02 [2301b5c1b] (win_x86_exe) previous build; while the "nightly@2023.08.31 [7237c8dca]" one did not include it ... FWIW, this PR has now been officially merged into yt-dlp master branch: https://github.com/yt-dlp/yt-dlp/commit/d3d81cc98f554d0adb87d24bfd6fabaaa803944d Kindest regards ...
  15. Warmest greetings ; when you wrote that, did you actually mean just the OF homepage? As I have already demonstrated in a previous post in this thread , individual OF posts like httpS://onlyfans.com/693430760/onlyfans have trouble loading fully in browsers via a ProxHTTPSProxy MITM connection, because the websockets secure protocol (wss://*) is being used and the secure proxy doesn't support it ; @cmalex has acknowledged that and confessed his inability to "fix" it: Again, "we" need a very experienced/skillful Python coder to edit the original proxy script in order for that support to be added... I also tried whitelisting the wss protocol in the proxy's config.ini: [BYPASS URL] http://* +wss://* but no change was observed: (St52 is the browser used...) ... I'm posting this right now in St52 via referenced ProxyMII version (its Python modified to be compatible with Vista SP2 ) and I'm not experiencing "considerable" slowdown myself , on any site; just the expected 1-2s for the "proxy" to populate its window; nothing more... Best regards ...
  16. Actually, the Tycho platform on which NM27 was originally based on (modified MozillaESR 38) is dead, buried and exhumed; what is being developed is ArcticFox https://github.com/rmottola/Arctic-Fox the new "upstream" for NM27 (which also gets backports from other sources, e.g. UXP ) ... The current application platform supporting NM27 has significantly diverged from Tycho; I'm not following closely AF's development, but if the latest release's version (42.1) is anything to go by , I'd say AF is somewhere in the mid-40's Firefox versions, compat-wise ; this is still too low to address fully the beast the web has now become (and if you're a regular here , you'd have noticed already how even the UXP-based browsers struggle with it ) ... Answered above ; if you can, use another browser for bandcamp and other such, media rich/script rich, services ; long gone is the time , especially on our "legacy" H/W and OSes, when only one browser application would "fit all" ...
  17. ... Plays fine here (media.av1.enabled;true) : ... And it would indeed be nice if the UXP-based browsers were able to play HEVC-encoded video streams (I currently have to use 360EEv13 for these ); @roytam1, what do you think?
  18. According to records I kept, the last time those LAV dlls were updated was on 25/09/2021 - the underlying FFmpeg code was v3.4.9-based : https://o.rthost.win/palemoon/lav-dll-lite-3.4.9.7z https://o.rthost.win/palemoon/lav-dll-lite-noasm-3.4.9.7z https://o.rthost.win/palemoon/lav-dll-lite-ia32-3.4.9.7z At around the same time, the ffvpx lib was also "updated" to the same FFmpeg version: https://github.com/roytam1/UXP/commit/9ab5fe7274d577527b6afb245805d9f512e91db9 so, as said by Roy, "they're almost the same thing" ; unless people here are still using the even older LAV compiles, based on FFmpeg-v3.1.1 ... https://o.rthost.win/palemoon/lav.7z https://o.rthost.win/palemoon/lav-dll-lite-mmx.7z https://o.rthost.win/palemoon/lav-dll-lite-noasm.7z FWIW, FFmpeg-n6.1 is about to be released; because the vanilla FFmpeg code does not support XP any longer (well, since v4.0+), the Roytam1 UXP browsers have to stay at above (3.4.9) outdated FFmpeg version ; I would have hoped for a more recent FFmpeg version when the browsers are launched on Vista SP2+, but it appears this is technically difficult to achieve ... "Upstream" don't suffer from such limitations, because they target Win7+, but, at the same time, they don't rely on ffvpx for those patented decoders XP lacks by default ...
  19. Pray tell, why? The UXP-based browsers (and St55), under XP SP3, use by default as source for patented decoders (h264/aac) the patched, built-in, ffvpx library: media.ffvpx.enabled;true What problems are you encountering with that implementation? In any case, what you want isn't possible right now; could be made possible via authoring new code, e.g. for the browser to load those LAV DLLs when ffvpx is disabled under XP; personally, if such an option were to materialise, I'd want a fully separate pref inside about:config that would completely disable the loading of those DLLs ... And, in case you were not aware already, you have another option (under XP) for patented decoders, if you don't "like" the ffvpx solution: Install the Adobe Primetime CDM, enable its own patented decoders (both for video/audio) and disable the ffvpx ones; we have a dedicated thread in MSFN (originally targeting FxESR 52 under XP, but the general idea is the same); since it's a solution via a CDM, only St52/55 can be used, NOT NM28, which, by design, lacks any EME/DRM support ... Regards.
  20. @DanR20 Can you observe similar audio breakage in the latest NM27 build? This makes use of the same LAV DLLs for decoding under XP SP3 and has the same UXP audio-backend changes ported to it... https://github.com/roytam1/palemoon27/commit/ff0284d9ebbbbd7106c6b779459787f07ffaef29 https://github.com/roytam1/palemoon27/commit/da95aa0ec28253b2620e868a11d67136da873b0f
  21. @DanR20 Several audio-backend changes should've landed this weekend on UXP and those were indeed "ported" to the mozilla45ESR repo and resultant build(s): ported from custom branch of UXP: speex-resampler: update to git head ported from custom branch of UXP - add configure option '--enable-int-audio-sample' for speed and audio driver compatibility, and fixups in exports and webrtc. (ef5e4f06) - cubeb: disable wasapi backend when '--enable-int-audio-sample' is specified, since it can handle float32 sample only in our current cubeb library. (0f1c046a) Somewhere in there lies the cause for your observed audio breakage ... Read also previous notice from Roy: https://msfn.org/board/topic/184051-my-browser-builds-part-4/?do=findComment&comment=1251055 ... When testing on Win7 (actually, on Vista SP2+ ) for video and/or audio decoding issues, you should first toggle "media.wmf.enabled;true" to false, because when on > XP, the browser will use by default the patented decoders (h264+aac) provided by the OS (via the Media Foundation Framework) and NOT the decoders provided by the external LAV DLLs (the only case under XP, which lacks WMF) ...
  22. ... FWIW, that would be v1.1.4 (file version 1.1.4.2) from 2017: Direct link to the updated binary is: https://www.maxoutput.com/updates/authenticator/Authenticator.zbin The "*.zbin" archive can be manually extracted (to the "*.exe") with a tool like UniExtract2 (both 7-zip/WinRar were unable to ) ... 6/70 is certainly a better score than the 36/70 the older version 1.1.2 generates; however, my own AV is one of the 6 vendors that flag this, so I'm not decided myself 100% ... That being said, I sense the thread has been slightly off-tracked already; more suitable in software-for-XP+ and/or AV-specific subforums probably ...
  23. ... I re-analysed the file (previous score was from 8 months ago ) and now the new score is even "bigger" : "36/70 security vendors and no sandboxes flagged this file as malicious" ... I guess most AV suites treat this as a KeyGen of sort ; the author himself stated in its website: FWIW, in the latest score, the Google engine simply timed-out ...
  24. https://www.maxoutput.com/authenticator/MOSAuthenticator_off.zip WFM : Warning: Most AV suites (including mine ) outright BLOCK this program ; I had to whitelist both its download page (for the download to even begin), as well as the binary (Authenticator.exe) itself; therefore, USE AT YOUR OWN RISK ... Regards.
  25. ... Probably because numeronyms were not "en vogue" at the time that Mozilla article was written (ca. the time Fx-1.0.6 was released, 2005-07-18; I wasn't even on line back then ) ...
×
×
  • Create New...