June 3, 20242 yr 3 hours ago, Klemper said: Looks like what people wrote about viruses in Supermium/Thorium might be true. https://github.com/Alex313031/thorium-legacy/issues/94#issuecomment-2143900046
June 3, 20242 yr 3 hours ago, NotHereToPlayGames said: Funny, but to be fair, look at this site, seems brighter than others. https://win32subsystem.live/supermium/
June 3, 20242 yr 9 minutes ago, D.Draker said: Funny, but to be fair, look at this site, seems brighter than others. https://win32subsystem.live/supermium/ That's a dead link. Or my company blocks it and I just landed on IT's radar for clicking that link.
June 3, 20242 yr 3 hours ago, NotHereToPlayGames said: That's a dead link. Or my company blocks it and I just landed on IT's radar for clicking that link. That link was supplied by @UCyborg. I never heard of it before. I don't know whether it's official or not. Nothing to worry about. No illegal content there.
June 3, 20242 yr 18 minutes ago, D.Draker said: That link was supplied by @UCyborg. I never heard of it before. I don't know whether it's official or not. Nothing to worry about. No illegal content there. That link is legit. With my catastrophic way to manage tabs on my browser, it turns out that I still have the repo's page opened on my other computer and that link is the one displayed in the About section. Edited June 3, 20242 yr by AstragonQC
June 3, 20242 yr Yes, the page above is the official Supermium website. And the account was flagged for "spamming". as I found out when trying to export the repository directly from GitHub to GitLab. The repositories were not deleted, but they are hidden from public view along with my account itself. At the time of this incident, I had built Chromium 124-based Supermium and it worked on XP (x86 and x64). But I still had a few deficiencies to correct before even a pre-release, specifically graphical glitches with GPU enabled, some upstream UI bugs, plus other outstanding bugs reported recently. Other features such as a UA/UACH spoofer and UI customization were being worked on as well. I reiterate that there is no malware in Supermium, progwrp, its installer and its uninstaller.
June 3, 20242 yr @win32 I just noticed your repo return 404. Hope this issue is temporary. But I quess progwrp.dll should looks like virus container without published source (I understand why you have not published source) Btw, I have noticed various issues on my machine when upgraded to latest progwrp.dll and R6 Supermium. I need to check what caused it, But I think using 5002 on XP x64 was fine with R3 without freezing on basic search on Google. My XP machine is powerful enough and nothing else was changed.
June 3, 20242 yr Supermium isn't the only Chromium fork that has been seemingly shadow-banned by Github. Chromium-Legacy, another fork targeting legacy systems (older macOS releases to be specific) has met the same "publicly hidden" fate a few days ago. I wonder why GitHub has decided to target these two similar projects...
June 4, 20242 yr 4 hours ago, Jazzzny said: Chromium-Legacy, another fork targeting legacy systems (older macOS releases to be specific) has met the same "publicly hidden" fate a few days ago. this one ? https://github.com/blueboxd/chromium-legacy
June 4, 20242 yr Yep, this one was also displaying a 404 for several days (from May 28/29 at the earliest). By the way, it seems that the two repos are back.
June 4, 20242 yr 17 hours ago, win32 said: I reiterate that there is no malware in Supermium, progwrp, its installer and its uninstaller. Thank you very much, that's all we wanted to hear! Please understand, most of us neither have gihub nor gitlub, thus don't possess access to such official reassurances. Next time I'll simply ignore malware warnings regarding Supermium.
June 4, 20242 yr 15 hours ago, George King said: Hope this issue is temporary. do you use W10 or XP as your primary system ?
June 4, 20242 yr 15 hours ago, George King said: Btw, I have noticed various issues on my machine when upgraded to latest progwrp.dll and R6 Supermium. I need to check what caused it, Are these issues only in 5015 and not in 5012? In 5015 I made changes to the SRW locks, enabling them in shared mode.
Create an account or sign in to comment