Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Days Won


siria last won the day on October 10

siria had the most liked content!

Community Reputation

74 Excellent

About siria

Profile Information

  • OS
    none specified
  • Country

Recent Profile Visitors

924 profile views
  1. That reminds me: the typo in 45 line55 probably makes that all following lines are ignored. Had the same prob in my own personal files, and noticed it only accidentally, probably much later. Then invented a little trick to make it visible on about:config if the file was damaged: pref on top of file: pref("aaa.CHECK.mysettings.COMPLETE", "*** BROKEN! *** CHECK! ***"); pref at end pref("aaa.CHECK.mysettings.COMPLETE", "OK"); :-)
  2. Size from over 40kB to 2-3kB, great! Finally. Am glad that this is now not a personal profile anymore, complete with all custom addons and custom install paths, but now really just focused on the prefs for the purpose :-) Now it's becoming more interesting, perhaps for myself too, after recently having run into black screens on another machine. When I get around, may try it... Just a bit typo remarks after taking a short look inside (not pref-related) patch45: at start of line 55 patch38+45: the first 2 comment lines start with #, that should be // for javascript (like in enforcer) patch38: the comment on top prohibiting to edit is a remnant from prefs.js, it doesn't belong into UOC. In general it would be helpful to also add a few comments to some of the single pref lines. E.g. for this: user_pref("browser.sessionstore.restore_on_demand", false); Wondered if that may mean it's on, or off... not sure. But was just general interest, not for myself. Offtopic: sessionstore in general seems to be much more dangerous as one would assume. Even for hardware: have read the Firefox method is infamous for writing completely INSANE amounts of data to disk: even Gigabytes without any browsing, just idle, as some experts have tested. No wonder that lots of supposedly supermegarobust SSD-disks are self-destroying after 1-2 years, although manufacturers and fanatics still insist SSDs would live forever, at least 20years - ha ha... (And they also claim it were 1) harmless and 2) necessary for FF sessionmanager to write such amounts to store sessions, even without browsing... Insane or what?!) IIRC one of the victims of 1-year old dead SSDs was also the K-Meleon project. It crashed on our main dev, for unknown reasons, and when he tried to restore a backup, the backup disk got destroyed/formatted by modern Windows OS... Lost quite some work, and seems interest too, since afterwards the KM-development was completely dead again (until roytam came.) Have no clue if he used FF and sessionrestore or not, it's just yet another supposedly undestructable SSD living only a year.
  3. A european domain is the last choice I'd personally consider today! Not sure if a chinese, turkish or russian one would be better or worse nowadays. But EU laws have become extremely suppressive against honest people, getting worse every year. While at the same time greatly favoring evil people. Far beyond what anyone could have imagined a few decodes ago, and most still can't imagine today. Far beyond any common sense, and harming society badly. One of the latest highlights: A new EU law declares it a CRIME if someone quotes even a headline of e.g. some newspaper article, or even just 1 sentence! ONE! This is completely incredible, but the mass media (all politically correct today) didn't cry out. Instead they hardly even mentioned such tiny details and made it sound as if all protesters, who learned the truth in the internet, were allying with real criminal pirates! And so that law passed too, as lots of other society harming laws before. At the moment it's just not active yet, but the single countries are now forced to put this into national laws soon. The prob is, those are not just some crazy theoretical laws, that no one will really enforce. Not sure about elsewhere, but at least in Germany it's an extremely successful business model of some shark companies to try and find as many as such peanut-lawbreakers as they can (of insane laws that no one with some common sense can imagine), then demand the victims to pay them a fortune as 'punishment', into their own private pockets, or otherwise drag the poor victims to court. Which always rules in favor of the evil ones, because law is law, and obviously it's also some law today (not sure if only in DE, or all EU) that those sharks are allowed to put the money into their own pocket. HUGE sums, completely out of relation to the supposed 'crime'. Regardless if such perpetrations, which no person in their right mind would imagine, are harming anyone or not. Or quite often are even positive for society. The first event may be free, victims get only an official 'warning', but once someone or a little shop landed in this spider net, he's lost anyway. The sharks will observe him very closely trying to catch a second event, some most harmless and unexpected bureaucracy-breaking event, like e.g. forgetting to refresh a fading marker line around a car selling spot, or some harmless, accidental little mishap in times of great stress, or just cluelessness about the newest traps in that jungle. And it even has happened that some sharks faked such events themselves, which is hard to prove of course. Now the victims are really lost, must pay some extremely exaggerated amount of thousands or tens of thousands euros. And the newspapers will either not mention it at all, or omit details and just imply the victims were breaking laws and shouldn't complain. Have read those evil companies already ruined countless little shop owners in DE already this way, using such legal (but to normal people feeling rather mafia-like) methods. Having committed no crime at all! With politicians still strongly supporting this business model, just recently the highest court ruled again in favor of such sharks. So that future EU law about quoting just a HEADLINE or ONE SENTENCE becoming a CRIME, a heavily punished one, ruining poor people, will be the ultimate tool for evil guys to destroy just about anyone they want. That much for extremly destructive and antihuman EU laws. Just one more. Although Switzerland is not officially part of the EU, they are not completely free to do what they want. Being a small country surrounded and depending on powerful neighbors, those can and do abuse their economic power to make them respect some EU laws too.
  4. It's dawning on me only now what a great business model this actually is: Domain marketeers give out cheap or free domains, but obviously still own them all themselves too, and can still do whatever they want with them! So they can just wait a bit until one of those domains becomes popular and successful, then just take it away from the supposed 'owners' again, pretending some invented or peanut reason, with no chance to appeal - and now start earning money with it themselves! Either put up nasty stuff themselves, or redirect, or why not SELL the successful domain now for bigger money to any really FRAUD or malware spreaders! While the true domain owners are left wondering if they may have done anything wrong, and what exactly.... What an irony. The implications are absolutely horrible: Evil new owners of those domains can put up whatever they want on those former trustworthy domains, while clueless visitors still keep reading in old articles and posts and archived website versions that this site is a GOOD and trustworthy one! So they visit and trust and unknowingly download now dangerous stuff :-( With greedy new owners usually not putting up a big message telling visitors that the ownership has changed. And visitors being just lucky if it's as obvious as in this case - but who knows for how long yet. I suppose future new owners can just as well restore former original linked download paths, just with exchanged file contents - GRRR After all such fake or pretended identities (legal or not) happen all the time now with all sorts of former great products and names :-( See it all the time in RealLife that names and logos of once great, now long since dead traditional companies, are now (ab)used even legally to sell products from completely different countries and producers and qualities. And of course in the software world too. Just remembered for example how the successful Stylish addon was finally sold to someone else, who probably seemed trustworthy to the former creator, but shortly after the seller just sold it again to a spying company etc. Actually a popular strategy of those companies, just take over former good products and secretly turn the new versions into spying tools. And recently an article about LOTS of new Firefox addons with stolen identities: https://www.ghacks.net/2019/05/29/another-malware-wave-hit-the-mozilla-firefox-extensions-store/ I'm opting for giving up as soon as possible the 3rd domain of this sort! Before it becomes too popular too, and "try" to get a less endangered one. Sigh, until some day all currently trustworthy resellers may be sold too, as usual today :-(
  5. Oh no, not again. Sigh :( Could it be bandwith-related? But guess doesn't matter if it's only the domain name, not the hosting server... no clue of such stuff. But I still keep suspecting that the original browser names in your zip packages are problematic! Whether that contributes to those domain probs or not, but sooner or later you'll have to rename them anyway, so the sooner the better. Am glad that KM-Goanna already has a unique name, although Dorian welcomed your builds very much. But who except a few insiders know this?
  6. Just to be sure, but you do have allowed all plugins by setting "plugin.load_flash_only = false"? And check the prefs "plugin.scan.plid. ...." which plugins the browser shall find, either all or only specific ones. And in another Mozilla-fork it was recommended to delete in the profile "pluginregs.dat", to refresh it. And if existing, also delete the StartupCache folder in the profile...
  7. No idea if this helps, it's just a pref for "dpi-scaling" Mozilla browsers, not the whole system.And am not sure if there's a difference between normal pagezoom and this dpi-faking. Anyway, perhaps worth a look as long as there's no easy solution for the whole system yet: https://www.ghacks.net/2013/06/24/firefox-22-0-find-out-what-is-new/ Pref: layout.css.devPixelsPerPx (String) 1.0 = use real resolution (everything looks sharp) -1 = automatic scaling (drove lots of people crazy when it became default and increased all image sizes, made them all fuzzy) Value can be smaller or greater as 1, in 0.05 steps, e.g. 0.8 or 1.25 or 1.5 etc. Since you want a HIGHER resolution, it means you want all elements SMALLER, that probably looks much less "fuzzy" as when increasing the size.
  8. To fake the OS which gets reported by javascript, hope this pref still works: general.oscpu.override = Windows NT 6.3
  9. Luckily even on oldest systems instagram videos are still watchable outside the browser, by opening directly the URL provided in meta tag "og:video". It seems the recent change is that inside the scripts is now a different URL as this meta URL. Until recently I used a complicated macro to show this second URL as a link to click (in K-Meleon 1.6), but now this URL produces an error "Bad URL timestamp". Suppose in my case that's javascript related (can't use anyway, too outdated). Your younger engines may not have that js-prob, just wanted to mention that there exist 2 URLs and the first one still works. It can easily be extracted by a little script, just not sure how to add it to the page then.
  10. Everyone since ages is bashing websites if they block users based on the useragent string, instead of checking features. I disagree more and more. The truth is: in today's web with the growing hostily and downright war against users of older systems and browsers, by big corporations and even Mozilla now, this is the best thing that can happen to us! We can be mightly GLAD that so far most websites try to kick us out "only" based on UA string. Considering that's no prob at all, just fake it and we get full access to as many parts of the website as really possible, even on the most ancient systems. If instead they'd kick us out based on browser features, users of older systems and browsers would get no access at all, without any fix possible. I just don't buy it anymore that all websites were inherently benign, just too stupid or lazy to check features. That's a fairy tale. Perhaps was true twenty years ago, for more or less sites, and probably still for some minor hobby sites. But today the big corporations and even formerly user friendly companies like Mozilla, have started acting so hostile and destructive towards us, fighting us with all they can, to me it's very clear they really want to just get rid of us. Then again, doesn't matter much anymore, they've won anyway. The Google bosses found the ultimate 100% successful weapon to kick out all users of old systems and browsers, once and for all: just command to encrypt the whole web, as if all pages were banking transactions. End of story. Poof - all empty. Old browsers would still be able to read almost everything, without getting blocked artificially, but that's war. For the moment a few of us are still saved by some special browser builds, but it's only a delay. So while still able to get in where we can, I'm just glad if the only joke-barriere is UA checking.
  11. Solution how to fix broken about:support and about:serviceworkers (NewMoon27 and KMG76 share the same engine) http://kmeleonbrowser.org/forum/read.php?20,144981,150059#msg-150059
  12. Broken download reported from 3rd user, from Romania (East Europe), in KM-Forum.
  13. (PM28, WinXP) Very interesting. Were the culprits some specific websites, or just in the sense of "too many tabs open"? Makes me wonder why this happens. Anyone have a guess?
  14. Sounds like a similar project as the 'UOC-patch' But makes me wonder, why edit so complicated inside omni.ja? greprefs.js only contains default prefs too, they can be overriden outside in normal ways (about:config, or prefs.js, or placing a modified js-file in the defaults/pref folder to get own default values) But perhaps works differently in CometBird, no idea. Something else I wondered for a long time: am I the only one who has (now had) major trouble seeing those embedded crosslink iframes to other msfn-postings, with older Mozilla browsers?? Finally got them visible now with a little css-tweak.
  15. While researching the kinda weird useragent result produced by my own, never-used ancient IE-browser, came across this really interesting site. Highly recommand for everyone interested in the useragent structure in general, what those "Windows NT" numbers mean exactly, or those ominious "NET CLR" elements, and especially how MSIE-strings are getting customized, etc.: https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/compatibility/ms537503(v=vs.85)
  • Create New...