siria

addon resurrect_pages: Interesting discovery! From your description this sounds very much that it could be the origin of an ancient K-Meleon macro, which I've just recently tried to update a bit too too! To get past the TLS-blocks of course the retrozilla-veriations should help, and with KernelEx some much more modern roytam1-forks too or Opera12.12 (but didn't try as FF-addon yet, only as extremely simple KM macro) Just wonder from your description, does the URL list not contain googleweblight yet? First saw this extremely helpful resurrection proxy only in the same, extremely ancient KM macro myself: https://googleweblight.com/i?u=$url Just a quick copy of my macro notes: Google weblight is a PROXY, pages are modified by Google to reduce content for 2G phone connections Except: video pages, or cookie pages, or complicated pages.... INFO: https://support.google.com/webmasters/answer/6211428?hl=en Older link was: http://googleweblight.com/?lite_url=http... Attention: needs a mobile UserAgent! (or never stops loading?) Attention-2: Google-Search now ALWAYS shows hits as weblight links if UA=Mobile, no escape!! examples: Mozilla/5.0 (compatible; MSIE 9.0; Windows Phone OS 7.5; Trident/5.0; IEMobile/9.0) Mozilla/5.0 (Android; Mobile; rv:38.0) Gecko/38.0 Firefox/38.0 Opera/9.80 (Android; Opera Mini/28.0.2254/66.318; U; en) Presto/2.12.423 Version/12.16 And figured out the same fix for waybackmachine just recently too (/web/http), but sure could have direly used this trick several years earlier already! Another wayback URL trick: if several date versions are stored, an older one can be accessed without JS too, by just typing any other old date, e.g. /web/200305/http... or even /web/1000/http... The server will automatically find and deliver the "nearest" archived date. Great URL syntax info here: https://en.wikipedia.org/wiki/Help:Using_the_Wayback_Machine One HUGE prob I can't escape yet: if the server has no stored version at all, it will immediately redirect to a new "save" link, creating a new version of e.g. a useless error404 page or addon-not-found page :-( It's even possible to get a list of ALL stored wayback-pages with a direct API link, guess was something with "ctx" or similar in the name, but that's a whole different topic again. Also created for my userContent.css or in KM rather adblock.css: @-moz-document url-prefix(https://web.archive.org/save/) { div.App-content-wrapper {background-color: yellow; border: 6px dotted red;} } @-moz-document url-prefix(https://web.archive.org/) { a[href^="/save/"], form [action^="/save/"] {background-color: yellow; border: 2px dashed red; outline: 2px dashed red; padding: 1px;} } @-moz-document domain(archive.org) { div#upsell-popup {position: relative !important;} }

roytam1 said: > some little experiment: tried to build non-SSE2 build of UXP > (Notice: even it is pushed to its own branch, no regular builds will be created > as whole thing is actually walking a tightrope and anything can be happened) Cool. Of course makes me wonder now: could this possibly mean the hope for KM is rising a bit too...? ;-)

This whole topic contains tons of gems (although most far over my head, when system and DOS knowledge needed, major pity) I just keep thinking it's a bit sad that it's aimed mainly at "just for fun" users, for theoretical use. Mostly by and for people who use modern systems for real stuff and only play a bit with this old OS for nostalgic reasons and "fun". But users who really depend on it daily and exclusively would be rather lost when strictly sticking to a "vanilla" version only, without any updates, just for an ideal of "purity". IMO that's just not realistic in real life. Am not meaning to add all sorts of complicated system stuff which needs expert knowledge (excludes me too), to turn 98 into a semi-XP, with all up- and downsides and especially just too complicated for ordinary people. But just a few tiny, easy updates make it already so MUCH more usable! Of course, talking especially of that miracle update with the old, official KernelEx version, incredibly tiny with less than 1MB, and the dll for unicode. Which was already delivered decades ago as official Windows update for Win98 (although always denied to exist when an app is declared "not compatible with 9x" merely due to supposedly missing unicode, while funnily no one ever insisted that their apps were "not compatible with XP as a whole" if not compatible with pure Vanilla first version without ANY official updates ever, but that's offtopic) Just mentioning since I keep thinking it's a bit a pity this is aimed at just-for-fun users of "vanilla" 98 ;-)

msfntor said: > My personal problem lived in Twitter distorted videos, now it's fixed > by user-agent override, cause I change user-agent in uMatrix Anyone can do a little test regarding uMatrix and UAs? When visiting one of the browser checking sites, look which UA it gets, then create a pref *manually* on about:config to change the useragent for this site: general.useragent.override.thatdomain.com = (some other string) When visiting now the same browsertest page again, without restarting the browser, does it show the new UA or not? (And which browser version and addon version this is) Just interested to know which, if any, of the UA-addons use the native Mozilla pref system. The few that I've examined closer in the past used only their own UA-storing methods and overruled the native UA-system, causing 2-3 major drawbacks. But perhaps other addons, or newer versions, use the native, simple pref-toggling system too?

No idea if already mentioned here (probably, but no harm if repeated) Just rediscovered in an older K-Meleon macro (servers2 on kmext.sf.net) two workarounds to load broken TLS pages from -gasp- Google directly: Google Cache (had wrongly thought for years it would only work from search results!) and Google Weblight (all new to me, cripples most pages to save 80% bandwidth for 2G phones) So at the moment am mainly trying those 3 quick macro-redirects if not wanting to fire up a fallback browser, which would be best of course, or if those fail too: 1) wayback machine without javascript, access page which is closest to cropped date: https://web.archive.org/web/2019/http://www....(URL) 2) Google Cache: https://webcache.googleusercontent.com/search?q=cache:https%3A%2F%2Fwww...(encoded URL) 3) Google Weblight: needs a MOBILE useragent string, and ATTENTION: all links in such a page will open weblight too: https://googleweblight.com/i?u=http://www....(URL)

Lots of great info as usual, major pity I'll forget most of it soon (just hoping to find it again later when some day needed), but a simpler lesson to take away from this: Contrary to previous theory, Mozilla-browsers are NOT the only ones supporting modern (?) ciphers on older systems. Just about every other browser can do it too - EXCEPT one: IE!

Caliber said: > now I have both gecko and firefox set to false and > have modified the UA individually for different sites and it seems to work. > but it's a pain of having to manually modify every site one by one... Not every site needs tweaking, only some. And once set, the prob is solved automatically next time. But one can certainly assume there are a lot MORE sites which are happy with gecko/Firefox as without. So personally I'd keep the compats enabled, to save a lot of tweaking, but of course that's bad for Goanna statistics ;-) Caliber said: > how can I solve this issue on Serpent 52 ? Your screenshot shows you've set compatMode.version to FF70. It's no wonder if some servers send you code which really requires FF70... And that compatMode for AppleWebKit certainly affects some sites too. It's a complicated balance which compatModes cause more good and which more harm, but have no own experience there. Perhaps other users of your browser can contribute more insights.

Caliber said: > the problem is that in some streaming sites the video miniatures are not displayed > with Firefox mode activated. With site-UA: > it has no effect, the problem persists Most likely either: - the page contains elements from other domains too, which must be tweaked too - or you have a useragent addon installed which disabled the native UA-system, but this can easily be tested

Caliber said: > how can I solve this issue on Serpent 52 ? > the sound is distorted in Gecko mode then I activate the Firefox mode to get it right. > the problem is that in some streaming sites the video miniatures are not displayed > with Firefox mode activated. Solution: set a DOMAIN-specific override UA for those sites. The "compatModes" only affect the general, default useragent if I'm not mistaken. There's an interesting new pref in your pic: "...compatMode.AppleWebKit" Can't find it by a quick search, is there any info somewhere what it does, and in which browser/version?

@VistaLover Highly interesting info, thanks! Especially this: > Perhaps Chrome 49 has native support for that cipher suite and only > uses the Windows Store for certificates, NOT using Schannel like IE does So far I thought this Certs+Ciphers stuff were somehow 1:1 related, and all non-Mozilla browsers could only use the same pool. But obviously only IE is completely dependent on the OS. Shocking for me to read: even Vista needs MS updates to get TLS1.2 support? I can understand that Win98 is much too outdated for native TLS1.2, but assumed all newer systems like XP had it long since by default, sigh. And will finally have to store those great ssl-test links!

Another spontaneous thought... 8-) If you just change a single or a few prefs, and post those lines here too, some users might prefer to just add only those lines themselves instead of downloading and exchanging everything again. But that's just my kind. Certainly some other users will greatly prefer the download.

https://www.cote.co.uk/ Hehe - LOL!! Am delighted to report that page OPENS in Win98 with roytams old K-Meleon-Goanna74! xD (this is not even KM76, but 74 with engine of Palemoon26/Fox24) And even with all my blocks up, incl blocked global javascript, which means the page looks empty but it does load the source, gets the page title, shows NO security errors, and a mini-content shows up when simply killing stylesheets. And with my usual UA of fake IE7. To avoid misunderstandings, that does NOT mean the page were usable that way, no menus nor FAQ page etc. are displayed, am merely getting a few links to facebook+instagram and phone numbers. It just means the access is not blocked completely. The page is chock full with all sorts of scripts, with interesting source code like using xxx.WRITE (doc.write is blocked at least since FF38, but may be contained due to my old useragent), or html tags "@onclick" Just meaning that pretty much rules out any required modern features or permissions as culprits for the completely denied access. Still suspect the certs, but if true, that makes me wonder if Iron has some embedded ones too? Or (no idea) if weak certs are not disabled in whole system, only by browsers?

I've read around here that most browsers are using the SSL/TLS capabilities of the system, except Mozilla Firefox family, which has that important certificate stuff embedded itself. So thought the site may just require some very modern cert. But interesting then that SRWare Iron runs too. If certs not culprit, perhaps different settings between the IE11 profiles, or some other OS module required?

Just a handling suggestion again ;-) After reading again the install-instructions on page1, those really look a bit complicated if someone doesn't already know by himself where prefs are stored. Especially if his browser is portable or is not installed in the usual locations. As we've seen, normal users can be completely lost then, start blind guessing and land in completely wrong folders, not even aware that program and profile folders are completely different things. I keep thinking some screenshots of the file explorer would be easier... And perhaps include install instructions inside the zips, as a UOC_readme.txt? That wouldn't require to visit the forum (which may not always be possible or easy for everyone, or just too lazy) and search through long, long text to find the crucial paths. Additionally the paths could be included at the start of the js-files too... Or the readme could just say "Installation instructions also found in file.....js (right-click file and edit to read as txt) Am not quite sure what the system does if users just "open" js-files... Just as idea, in UOC_Patch_38.js something like... // UOC_Patch_38.js for Firefox 38 ESR based browsers // Developed by Looking4awayout - Version vN2I - 2019-11-16 // Forum: https://msfn.org/board/topic/178306-uoc-patch/ // //======= INSTALLATION: // Copy THIS file to your PROGRAM folder, where your browser creates DEFAULT settings: // FIREFOX: C:\Program Files\Mozilla\Firefox (contains FIREFOX.EXE) // \defaults\pref\UOC_Patch_38.js // PALEMOON: C:\Program Files\Moonchild... \palemoon (contains PALEMOON.EXE) // \defaults\pref\UOC_Patch_38.js // K-MELEON: C:\Program Files\K-Meleon\(KM-Goanna?) (contains K-MELEON.EXE) // \browser\defaults\preferences\UOC_Patch_38.js // // ATTENTION: after next browser start this will change your OWN settings in profile // //======= BACKUP your PROFILE settings first: // FIND PROFILE: // Open address "about:support", click on button or link to PROFILE FOLDER. // Copy 2 files "prefs.js" (has date of today if correct folder) and "user.js" to a safe place. // (prefs.js will be modified by THIS file after next browser start) // (user.js gets replaced completely by the 2nd UOC file "enforcer") //======= And in "Enforcer" file... //======= INSTALLATION: // FIND PROFILE: // Open address "about:support", click on button or link to PROFILE FOLDER. // BACKUP: 2 files "prefs.js" (has date of today if correct folder) and "user.js" to a safe place. // Replace "user.js" with THIS enforcer file and restart browser. //=======

@Matzwiz > Unfortunately, I don't have a system capable of building these browsers myself. > So I wrote that comment in the hope that @roytam1 will do a test build of both browsers, > and revert my changes if there are any problems. If it's only normal xml/html/js files, not CPP, you can most likely find and exchange those inside omni.ja In K-Meleon works fine, just not sure if those other/newer browsers allow changing omni.ja too or if it breaks some signature or whatever. Yeah that's the crux, max privacy and max features are mutually exclusive. One just cannot block at the same time all sorts of privacy related functions and still have all features working, if those require some of those functions. It's a dilemma. We understand this here but unfortunately, when looking around the web, most users still don't have the slightest clue! They keep thinking they could get a set of "flawless" privacy settings, then after adding some more magical prefs are soon disappointed to discover "bugs". They keep fiddling with new settings, only to fall into another trap shortly after. Never quite understanding it's simply not possible to block lots of stuff and still get everything working at the same time. And of course by far the best privacy protection is to just block javascript completely (causing a few 'bugs' too as expected 8-) Privacy settings are such a giant subject, a separate thread wouldn't be nearly enough. At least not for the endless jungle of Mozilla prefs, IIRC current browsers have over 3000 prefs already (yikes!) Makes probably a million possible combinations... many cross-influencing each other, and additionally users have different hardware and browsers, complicating things yet more... Can't imagine there's even just 1 expert left who still understands all of this with all cross-effects too. There are already lots of projects out there trying to find at least a good compromise of permanent settings for most users, although not really possible, considering everyone has different needs too (needing stuff like facebook and gmail or not etc). But still better than nothing. Like the famous ghacks user.js, or german site privacy-handbuch.de (oh great, which now blocks old browsers too, no TLS1.2) The only real solution for this dilemma is to toggle some settings only TEMPORARILY when needed. It keeps surprising me how few people even consider doing this. Although admittedly not quite easy, it requires some knowledge what those toggles are doing. Still it's the method that works best, and one of the reasons I absolutely love K-Meleon with my long row of toggle buttons, many self-created (mainly macros Blockeria and priv3buttons). Although I can only toggle a few prefs too, among the 3000, but as mentioned, blocking javascript (completely or partly) goes a very long way towards privacy already, and blocking 3rd party iframes etc. too.

Thank you for this precious little tip!! After many years of struggling with those d*** DOS windows opening only in fullscreen mode, without any buttons or taskbar, no mouse or anything and no screenshots possible, finally got that thing showing up as normal "window" again! It had not bothered me enough to start extended web researching, but still was really annoying.

Thank you for all that incredible work you do! Even in peace times I cannot imagine how in the world you manage to keep up that enormous workload, looking at those endless long changelogs for several different browsers, even incredible if someone could work 24h per day on them. And recently even discovered, completely shocked, that even 1 single commit, 1 little changelog line, can consist of 800 changed files! Let alone now in current semi-war conditions, with a lot greater sorrows as update schedules, and much less time too. Once more, I'm stunned. But really much more important now is that you hopefully remain as safe as possible. My thoughs are with all the amazing people in your country.

Frankly, I don't buy it anymore. Not in a case as glaringly obvious as this one (and countless others before), and not in general when looking around in today's world. That people who keep destroying good things again and again, without any need or reason, must surely be inherently good and honest people too just i-n-c-r-e-d-i-b-l-y stupid. There's a limit to stupidity at some point, if someone has a job that requires a minimum of intelligence. Long time afterwards it always turns out that in reality such people couldn't believe themselves how easily they always got away even with the most i-n-c-r-e-d-i-b-l-e lies and betrayals, and how much they looked down upon those who still believed them. Or if even knowing better, still trusted at least in their honesty. How it enforced their conviction that obviously people WANT to be betrayed and don't deserve better, so they happily continued yet worse, often while climbing up the power ladder even faster. The core prob is the conviction of most people that everyone else must be born just like themselves. Evil people keep insisting that deep down everyone else were evil too, just hiding it - no exceptions. Everyone else who claims differently is a liar or stupid or betraying themselves. And truly goodhearted people keep insisting the opposite, that deep down everyone else must be born goodhearted too - no exceptions. If too obvious that someone isn't, then he surely must be a poor traumatized soul, deserving nothing but sympathy and needing as much love and help as possible to be 'cured'. It's all rubbish, everyone is simply different, and deeds speak louder than words. So the continued destruction of Firefox since a couple years already is done on purpose (of course, just my opinion). No one in their right mind can expect success by driving away the own loyal userbase and hoping to replace them by users of another product, who can just as well keep the better original. Makes zero sense. But when looking at plain facts, what makes a very obvious sense is the completely unnecessary and continued destruction of useful features, despite all desperate protests, again and again, since years. And despite seeing the user base declining with the declining features too.

Mozilla's restored boycott of site-specific useragents keeps showing their contempt of user needs. And keeps infuriating me :realmad: "it was just old code" ?! Incredible. Now they don't even bother anymore to think up some phony pretense why their continued destruction of useful features should be "necessary". Not that it would matter anyway, since the real purpose is always very obvious by the effect of their deeds: driving even the most loyal users away as fast as possible. Bugzilla said: > the technical burden of maintaining the code that does this (even assuming it's "bug free") > is not worth it. I agree that it was more convenient just to add a pref for what you wanted, > but webExtensions allows you to do that just as easily, and is well tested. What a phony lie too. At the same time claiming this task were super easy for addon hobby devs, yet for their mega-corporation it's supposedly a too heavy burden! Although they wouldn't even need to do anything new, just KEEP an already existing file :realmad: By the way this native function allows users to just toggle PREFS to use it. To give them a better GUI, this simple-pref toggling could also be done by addons in enabled builds, or if necessary xpi-addons could just enable it themselves with 2 lines. If already enabled anyway, as in roytam's builds, that pref-toggling can easily be done by K-Meleon macros too (like useragents2018). Yet all xpi-addons that I've looked at closer in the past, overruled instead this native browser function completely, rendering those native prefs useless. Never quite got it.

Whoah.... your stories are real drama! And the above sounds like you're not too aware what you're dealing with here, but it's not quite trivial. I think it's all described in detail on the first UOC page, and strongly recommend studying it. But it's been a while that I've read it myself, so just a few quick tips from my own understanding: What matters most, is to FIRST make a backup of your profile! Or at the very least of PREFS.JS and USER.JS (if existing). You will need those files again to restore your current settings if later you remove the patch again. You can find your current profile folder in a link on the about:support page. IIRC the enforcer file goes into that profile folder, contents to be added in user.js, but better read this in the instructions to be sure. The "normal" patch file creates different "default" values for the contained prefs. This file goes into your unzipped program folders, into subfolder ../defaults/pref/ or /defaults/preferences. You want new profiles? Regarding K-Meleon, if you use roytam's 7z build, those create the profiles inside the unzipped program folder. You can just delete that "profiles" folder and restart, but I recommand to keep the current profile and just create a second one: Menu Edit>Manage Profiles K-Meleon also has the specialty that some user settings are stored outside of the profile, especially when changing toolbars, but you don't sound like you customized very deeply. PS: your screenshot, is it really intentional that you have the file types hidden, the endings after the filenames?? Or only because it's that stupid MS default setting? At any rate that icon for UOC looks you did not unzip the patch yet, that means it simply got ignored. You must extract the contained files to do anything with them.

Nope, neither. If links matter, I usually start with the Activity list (recent postings everywhere): https://msfn.org/board/discover/

Reading about such killer probs on "full" facebook and even here on MSFN is rather scary. Am stuck on a yet older system and browser version, used to such pains on 'modern' sites and wasting much time finding workarounds, but didn't imagine that younger browsers are already so very badly broken too. But if you say K-Meleon (76.2?) works better there, that means NewMoon27 must be able to work the same way, since both use the same engine. Unless there are yet more probs involved? But probably just a matter of fiddling with different useragent-strings or css-tricks. Some special useragent strings for stubborn sites come already predefined in the browsers, and need newer strings occasionally. You could check those on about:config page, filtering just for 'override' or 'facebook'. Although those prefs only work if no "Addon" is installed, since those I've looked at closer all overrule that native useragent system with their own one. You can also open those problematic sites and check the really sent UA on scratchpad or whatever those non-KM browsers have, by a little scriptlet: alert(navigator.userAgent);

Palemoon28 lagging and GMail freezing, interesting read: https://forum.palemoon.org/viewtopic.php?f=3&t=20553 https://forum.palemoon.org/viewtopic.php?t=20843 https://forum.palemoon.org/viewtopic.php?f=3&t=20573 Regarding profiles again, if anyone likes to choose parallel profiles at browser start too: in older Gecko versions (but perhaps in current forks too? no idea) that setting was stored here: in the current profile's parent folder, in a "profiles.ini" file, this line: [General] StartWithLastProfile=0

@Kitaro1 I'm absolutely with you here. It's a real Killer-Trap that different browsers share the same profile, without any warning. Even advanced users need a LOT of experience to even consider such a possibility before trying a new browser. Even when fully aware it's a fork. Am just not sure how difficult it would be to change this behavior. Or if there's any chance that at least a new "parallel" profile is created? (Absolutely love being able to choose from parallel profiles at startup, a native Mozilla function since ages, no idea if still possible in 'modern' versions now) But IMO at the very least a confirmation/warning should pop up when installing/unzipping a new browser and it adopts an already existing profile. @3dreal: if not noticed yet, mobile facebook URL is "mobile.facebook.com" Some sites don't respect mobile URLs though and redirect to full desktop size, if the useragent is not a mobile string too. If you like a GUI to change UAs in KM, I recommand my useragents2018-macro ;-) It makes full use of the native engine functions, toggling only prefs, doing nothing else, and contrary to other macros allows to fake the global default UA too.

Addon-archives: as mentioned elsewhere here, but certainly not seen by all, legacycollector.org is closing too.