-
Find the Discord channel in which you would like to send commits and other updates
-
In the settings for that channel, find the Webhooks option and create a new webhook. Note: Do NOT give this URL out to the public. Anyone or service can post messages to this channel, without even needing to be in the server. Keep it safe!
If you share this list, please use this link instead: https://lambdaurora.dev/optifine_alternatives
It may still be only a redirection link, but it will have a better web display of the list soon. And the list being on GitHub/GitHub pages improves load times.
The gist version of this list will stop being updated.
RIAEvangelist/node-ipc is malware / protestware
The RIAEvangelist/node-ipc module contains protestware peacenotwar.
Excerpt from RIAEvangelist/node-ipc:
as of v11.0.0 & v9.2.2 this module uses the peacenotwar module.
Date: 02.09.2022
Last Update: 24.12.2022
Author: Aizistral
In collaboration with: ejaussie, also known as British Empireball#3906
While I wish this could have been conducted sooner, this is the first verifiable ban case where I could contact the person banned. Some couple weeks ago I even purchased second Minecraft account with the sole intent of committing what would appear as bannable offense and being reported by one of my friends afterwards, which I sucessfully did; however, no action from moderation team followed. At the time this lead me to conclude that reports are not yet actioned on, which was perfectly explainable by unfixed exploits with chat reporting in 1.19.2. This case might indicate that reports are indeed actioned now, at least since the date of this research, but it is also possible that ban occured due to automated chat monitoring on Realms (see [Our Commitment to Player Safe
| app_name | repo | electron_version | vulnerable | |
|---|---|---|---|---|
| 1Clipboard | https://github.com/wiziple/1clipboard | |||
| 1Password | None | 25.8.1 | FALSE | |
| 3CX Desktop App | 19.0.8 | TRUE | ||
| 5EClient | None | |||
| Abstract | None | |||
| Account Surfer | None | |||
| Advanced REST Client | https://github.com/advanced-rest-client/arc-electron | ^17.0.0 | TRUE | |
| Aedron Shrine | None | |||
| Aeon | https://github.com/leinelissen/aeon | 23.2.0 | TRUE |
This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.
Update: I've disabled comments as of 2025-01-26 to avoid everyone having notifications for something a year on if someone wants to suggest a correction. Folks are free to email to suggest corrections still, of course.
| #!/usr/bin/env bash | |
| # | |
| # fh6-safe-splash — Steam launch wrapper for Forza Horizon 6 (appid 2483190) | |
| # | |
| # FH6 crashes at the "Splash" scene under Proton when the NVIDIA Streamline | |
| # stack (NVIDIATech / DLAA / Reflex) initializes during D3D12 setup — a startup | |
| # race in the graphics-allocator path. This wrapper forces those settings OFF | |
| # in the saved graphics config *before* each launch, so the game always boots | |
| # past the splash. You can re-enable DLAA/Reflex in-game once you're in; they'll | |
| # be reset to safe again on the next launch. |

