-
Notifications
You must be signed in to change notification settings - Fork 19
PolyMC lead devs have gone rogue! #87
Comments
ManyMC seems to not be maintained anymore so as soon as I heard the news I immediately went back to manyMC. |
Yes, I noticed the takeover as soon as this happened since I was kicked out of the PolyMC organization on GitHub. Let's be accurate, there is no sign of malware at the moment — the meta has not been touched. With that said, the takeover is an act of stupidity and you should not trust such people with anything. I advise everyone to stop using PolyMC immediately. ManyMC is unaffected by these actions as I have sole and full control over it. I have taken all safety measures and cut any ties between ManyMC and PolyMC. I also reverted ManyMC's meta to two weeks ago to ensure nothing sneaky was pulled in. |
Is anyone else having issues connecting obtaining Curseforge Packs via ManyMC since this happened? |
Yes, the CurseForge key used by ManyMC belonged to PolyMC, and it has been revoked. |
Makes sense, whilst an inconvenience, it's good from a security perspective. |
Sounds like most of the people involved in Poly have moved shop to PrismLauncher: https://github.com/PrismLauncher/PrismLauncher |
PrismLauncher just released its first release with changes provided by ManyMC. Works perfectly on M1. |
Yes, Prism is the continuation of PolyMC from the original maintainers. It is also the official continuation of ManyMC. More about this in the README and Discord. |
I'm sure you've already seen this, but some of the old lead devs of PolyMC went rogue—causing the main meta-server to essentially send users malware (see PolyMC/PolyMC@ccf2825 , warning for NSFW content and slurs being posted, because we can't have nice things on the internet)
The actually active devs have forked the pre-trashing commit version of the PolyMC development branch to https://github.com/PlaceholderMC/PlaceholderMC, so I suppose that's where things are going to continue? I suggest that ManyMC doesn't update any metaserver stuff with upstream commits for the time being, obviously.
The text was updated successfully, but these errors were encountered: