UCyborg

You didn't. I'm not sure how much the web browser plays the part, I suspect not much, but I honestly don't care. When you're dealing with software issues all the time, you become apathetic towards them. The only real and permanent solution - throw it all out and smash it to pieces. And I mean all of it, computers in all forms along with the storage media. I noticed burst in "people going nuts" just about when May ended, like customers at work were crazier than usual and someone robbed the post office in Lendava. And there was news about the other guy that lost his s*** because the girl he was into wasn't returning love. I forgot all about it, he must be young, early 20s at least. Perhaps the reality hasn't hit him yet. So not all violence is "mental issues", that we have taken from this thread I presume, just old fashioned calculated deliberate purposeful evil. Also the word recently got out about violent incidents from the staff against the patients on the psychiatric clinic located in the craphole called Ljubljana. I don't know, the history repeats itself, the only thing that will break the cycle is the higher force. A big object from outer space, dare I hope? What is considered advanced age for humans? 60+?

No, I certainly did not write it that many times! What happened was that I clicked the submit button multiple times because I didn't get any feedback the first time, so ended up doing it again in another tab, where it did respond as it should. That's the issue with software in general, in development for decades and never works right. I also still get the notification popup at times after logging in about the PM I read and replied to years ago.

I don't think so, there was just NotHereToPlayGames and and six cars in my mind. Didn't think of any potential other people in his household. Marriage - yeah, I'm a loner and it won't happen and even if I wasn't, doesn't seem like something I'd want to bother with. Being like that for most of my existence, I imagine it would be hard to adapt to different patterns, playing single-player mode all the time. People are crazy, should be healthier to be alone anyway, LOL. Ironically, I work a job that involves dealing with them, remotely at least, but it's still totally against my character. The things we do for the money...

AFAIK, it would be possible for it to miss something if ran at document-start. Maybe it's different when dealing with HTML's head, but it's a documented fact that only after document-end (after DOMContentLoaded event is dispatched), entire page's HTML as received from the web server is surely parsed.

document-end in script managers should mean on DOMContentLoaded event in practice if I got the documentation right. So might as well be: 'use strict'; (function(){ const e = document.querySelector('link[rel="stylesheet"]'); fetch(e.href) .then(response => response.text()) .then(data => { const s = document.createElement('style'); const m = e.getAttribute('media'); m && s.setAttribute('media', m); s.innerHTML = data.replace('font-size:1.05em;font-weight:500;', 'font-size:1.05em;font-weight:400;') .replace('font-weight:500;display:inline;line-height:20px;', 'font-weight:400;display:inline;line-height:20px;'); e.parentNode.replaceChild(s, e); }) .catch(err => console.log(err)); })(); Just in case at least one those variables would stay lingering around if not wrapped in a function that will surely go out-of-scope in the end as the latter will surely mark them for garbage collection. And I think if I ever need to listen for DOMContentLoaded in the future, I might add the listener with document.addEventListener() rather than window.addEventListener() since it's technically the document that is ready, window contains it. Seems neater to use window.addEventListener() for window-specific events.

I mean, does the company do anything else? I'm not sure how you can run the business only on selling (and supporting?) such kind of software for an OS that belongs in the museum.

VS You might want to F12->Inspect those titles and see if font-weight property changes on the right where CSS properties are listed. On Pale Moon for instance, I don't see any difference between 400 and 500. I wasn't checking old Chrome specifically, though 800 should be high enough to make noticeable difference.

I have very quickly in a VM. After a bit of clicking around in the Settings app, RAM usage went back to normal Win10 levels.

They still sell this in 2023?

Depends on what you put there. It was just a template showing iterating over all stylesheet files on which to do search and replace on the file content. This script would put the old font-weight of certain titles on MSFN before the update (500->400): 'use strict'; window.addEventListener('DOMContentLoaded', (event) => { const e = document.querySelector('link[rel="stylesheet"]'); fetch(e.href) .then(response => response.text()) .then(data => { const s = document.createElement('style'); const m = e.getAttribute('media'); m && s.setAttribute('media', m); s.innerHTML = data.replace('font-size:1.05em;font-weight:500;', 'font-size:1.05em;font-weight:400;') .replace('font-weight:500;display:inline;line-height:20px;', 'font-weight:400;display:inline;line-height:20px;'); e.parentNode.replaceChild(s, e); }) .catch(err => console.log(err)); }); Executing on DOMContentLoaded event is necessary in the absence of advanced script manager, if it just runs right away, but I guess it works without being wrapped inside event listener with TamperMonkey if set to run on document-end. CSS with content of interest happens to be linked inside the first link element with stylesheet attribute, so document.querySelector(), which just returns the first element, works in this instance. replace() function can be chained to do multiple replacements since each call returns modified string as the result of it, on which it may be called again to do more replacements.

Oh, didn't notice.

https://www.theregister.com/2023/05/26/windows_xp_activation_keygen/ https://arstechnica.com/gadgets/2023/05/a-decade-after-it-mattered-windows-xps-activation-algorithm-is-cracked/ https://www.tomshardware.com/news/windows-xp-offline-activation So, offline "phone activation" without having to actually call that number. That would've come in handy years ago, I still remember that "activated too many times" error and looking for cracks.

I looked at this again, they have classic <link rel="stylesheet" ... /> elements with links to CSS files further down inside <noscript> tags. Web browser only processes those when JS is disabled, that's why the page looks OK with JS disabled. I can't see what they were suggesting in that PM forum thread (server is down ATM), I remember messing about with Proxomitron since that's the only thing that came to my mind at the moment, I also remember there is an extension for manipulating network request responses, which I'm not familiar with, but anyway, another way around the problem is with a user script, something like this: document.querySelectorAll('link[rel="preload"][as="style"]').forEach(e => { const n = document.createElement('link'); n.setAttribute('rel', 'stylesheet'); n.setAttribute('href', e.getAttribute('href')); const m = e.getAttribute('media'); m && n.setAttribute('media', m); e.parentNode.replaceChild(n, e); }); Put the code in your favorite user script manager and make it run on document-end (should be default). Edit: One more thing, might be even more important, these link elements have attribute onload="this.rel='stylesheet'". On Chromium, this code runs and successfully replaces rel attribute. But why not on UXP? Edit2: OK, onload simply doesn't run if rel isn't initially set to recognizable value. According to the example at MDN, MS should just leave the links to CSS files in the separate tags with rel="stylesheet" (not enclosed by noscript tags like they did).

The latter is due to reliance on Chromium-only experimental feature - https://caniuse.com/mdn-css_properties_text-transform_math-auto - officially enabled since Chromium 109, but otherwise can be enabled by turning on web platform experimental features (chrome://flags/#enable-experimental-web-platform-features). Not sure what to say about the first, I only notice fonts being edgy, but that's Windows XP. Maybe a screenshot would help.

That test certailnly thinks it is. It's a tricky thing to exploit AFAIK, so if not impossible to exploit in your case, should be at least more difficult. Can't say anything more on this matter as I'm not the expert at these things.

Seems inset-inline-end support can be enabled in Chromium 86 by turning on experimental web platform features (chrome://flags/#enable-experimental-web-platform-features). I think more technically correct approach in this case in the absence of support for that property would be having another 2 selectors checking HTML document (text) direction, like so: html[dir="ltr"] .ipsWidget .ipsDataItem_main.cWidgetComments .ipsCommentCount { right: 0; } html[dir="rtl"] .ipsWidget .ipsDataItem_main.cWidgetComments .ipsCommentCount { left: 0; } Regarding replacing, I'm not sure it's possible to directly intercept the network request initiated by web browser when it encounters links in page's HTML to external resources from user script, extensions can do that, but what can be done: document.querySelectorAll('link[rel="stylesheet"], link[rel="preload"][as="style"]').forEach(e => { fetch(e.href) .then(response => response.text()) .then(data => { const s = document.createElement('style'); const m = e.getAttribute('media'); m && s.setAttribute('media', m); s.innerHTML = data.replace(...); // replacement logic here - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/replace e.parentNode.replaceChild(s, e); }) .catch(err => console.log(err)); }); Basically replacing link elements linking to CSS files with style elements, embedding content of linked CSS files, which may be manipulated before put in place.

I imagine the browser without own mitigations won't appear vulnerable on a newer CPU while it may appear so on the older CPU. And just how effective are these software mitigations? https://forum.palemoon.org/viewtopic.php?t=25059 I run an OS from 2020 and still vulnerable. Maybe the issue is that the OS was released during COVID-19 pandemic (pun-intended)? Or there are tricks that the small team (Moonchild Productions) simply isn't aware of, given that it doesn't happen in either Firefox or Edge and there could be a combination of OS level and browser level mitigations behind the scenes. But then again, I always got the impression that the only real fix is a new CPU as far as those particular vulnerabilities go.

After our conversation was ended abruptly in the other thread by the oppressive dictators...new update, new changes. Yes, @mina7601, I also noticed, wanted to reply there, but couldn't for obvious reasons. Correcting reply counter position on the main page under Topics section for browsers not supporting inset-inline-end CSS property, most notably Chromium <= 86: .ipsWidget, .ipsDataItem_main, .cWidgetComments, .ipsCommentCount { right: 0; } "right" indeed works, @NotHereToPlayGames. I suppose new property would be useful in combination with other properties mentioned on that MDN page. Another change with recent update is font-weight set on elements with the class .ipsDataItem_title, it's used for thread titles on pages where forums threads of specific sub-forum are listed. Noticeable particularly on newer Chromium based browsers. Before - font-weight: 400 After the update: font-weight: 500 Reverting to old look: .ipsDataItem_title { font-weight: 400 !important; }

I guess forum software was updated, which will surely be appreciated by the fans of the old web browsers here. /s Behold, insert-inline-end CSS property is used under the Topics section now to align replies counter, which is not supported by the latest Windows XP supporting Chrome.

Probably that checkbox is only relevant if you actually use chrome://inspect page on the regular basis. When the checkbox is enabled and the page is opened, the browser establishes ADB connection with connected Android smartphone, that's how you debug websites from the computer that are displayed on the smartphone in Chrome browser. Can't test it currently since I don't have Chrome on my phone, but ADB connection prompt does appear on the phone.

I don't know anything about Netflix, but it's possible their server assumes Chromium based clients don't do NPAPI and don't even attempt to detect it properly.

Probably timings simply don't add up in your particular case, hence reading non-vulnerable. But this is a hardware thing and unless the CPU was put together after vulerability was disclosed, it won't have hardware-based safeguard to surely prevent leaking in absence of other mitigations. 32-bit Pale Moon on Windows 10 and Serpent from January 2023 on Windows XP both read as vulnerable here, also 360Chrome 13.5.2022. 64-bit builds of the first two browsers don't. Or if 32-bit builds are restricted to run on the single CPU core. 32-bit Firefox 110 doesn't and neither does 64-bit Edge 94 (both run on all available CPU cores).

@NotHereToPlayGames It was just a thought that formed in my mind at the time as it put some pieces of your posts I read in the past together. And no, I don't recall ever even actively thinking about your marital status.

USA is obsessed with forced cutting off parts of babies' penises, even without anesthesia. I prefer the term FGC (forced genital cutting). Million excuses for it, it's disgusting, from faux "medical" reasons that even doctors in some other parts of the world have fallen for (I don't buy that phimosis is pathological condition) to puke-inducing religious reasons. Going too deep on the latter would be against the rules, but I like what Brother K wrote on his Facebook years ago, I don't remember the full quote, but goes something along the lines: My religion requires me to have an intact penis. And something...I don't remember anymore... The point is, it's no one's business but the penis' owner and if he really wants, he can go chop his junk up when he's old enough. And yet, you participate. You also spoke about minimalism in the context of yourself at some point while owning not 1, but 6 vehicles!

I wonder how SSDs hold up over time. I guess only time will tell. 10 years old SSDs at this point in time were earlier models. I'm not determined to keep my computer equipment for something like 20 years, so in that regard, it doesn't matter as much (to me). Guess what I tried to say, if it works, great, if not, well... Though this whole computer (bought in 2009) is holding up pretty well compared to the 1st from the late 90s (1997 I think) and the 2nd one from 2001. Corrected hardware error on AMD Northbridge is reported on every boot and resuming from hibernation though for several years now, no idea when it even started. Kinda like a permanent CHECK light on the old 2001 VW Polo, which still ran reliably for several years, until it didn't.