tgindex
🌿 ReZygisk (δ) 🧬

🌿 ReZygisk (δ) 🧬

Статистика

🌟 Welcome to ReZygisk project! Let's save the world from LSP closing the sources! 🕊️ 🏆 №1 #FOSS Zygisk solution. ➥ 🛟 Join @ReZygiskChat! ➥ 📂 github.com/PerformanC/ReZygisk — official repository We are not racist. 😉

Последний пост
22 окт. 2025 г.
Последнее чтение
19:54
Постов за неделю
0
Всего постов
20
Тип
открытый
Язык
английский
Категория
Новости и СМИ (по похожим)
В каталоге с
15 авг.
Подписчики
3 706
−4 за 3 дн.
Сутки
0
0,00%
Неделя
 
Месяц
 
Просмотров на пост
14 тыс
17 постов
Вовлечённость
378,5%
к подписчикам
Постов в день
0,0
всего 20
Упоминаний
0
каналов
Охват размещения
оценка
1/24сутки в ленте
1/48двое суток
1/72трое суток

Оценка по просмотрам недавних постов: пост набирает почти всё за первые сутки.

Посты

  • 22 окт. 2025 г.13,4 тыс7930из performancorg_channel

    Welcome again, it has been some time since the previous RC (Release Candidate) release. However, it is worth the wait. The fourth RC has arrived. PerformanC ReZygisk Release Candidate 4 comes with many improvements to both ReZygisk performance and modules'. It also stabilizes many core systems while also enhancing furtiveness for module loading. The most notable changes in this release candidate are: - Added global module preload. - Improved module description for a more minimalist one. - Removed completely the (futile) maps hiding mechanism. - Fixed support for systems using Tango. - Added support to update from RC to RC from root manager app. Soon bigger changes are expected to come. Till there ReZygisk RC 4 will provide a solid and stable Zygote injection for its users. Special thanks for the users who allowed this release to exist by contributing with feedback on each ReZygisk CI (@rezygisk_ci) stability and test builds. The eyes met in disbelief. I could not trust what I saw. Before I realized, everything happened. We saw its flaw.

  • 🌿 ReZygisk (δ) 🧬 pinned «🚫 𝗦𝗧𝗢𝗣 𝗧𝗛𝗘 𝗗𝗜𝗦𝗧𝗥𝗜𝗕𝗨𝗧𝗜𝗢𝗡 𝗢𝗙 𝗙𝗔𝗟𝗦𝗘 𝗜𝗡𝗙𝗢𝗥𝗠𝗔𝗧𝗜𝗢𝗡!!! ⚠️ We, once again, urge people to stop making false claims about alternative groups having the status of ReZygisk support chats. @rezygiskchat is the only official and dedicated support formation. Everything…»

  • 21 июл. 2025 г.19,6 тыс6514

    🚫 𝗦𝗧𝗢𝗣 𝗧𝗛𝗘 𝗗𝗜𝗦𝗧𝗥𝗜𝗕𝗨𝗧𝗜𝗢𝗡 𝗢𝗙 𝗙𝗔𝗟𝗦𝗘 𝗜𝗡𝗙𝗢𝗥𝗠𝗔𝗧𝗜𝗢𝗡!!! ⚠️ We, once again, urge people to stop making false claims about alternative groups having the status of ReZygisk support chats. @rezygiskchat is the only official and dedicated support formation. Everything else is only associated with the ReZygisk project in the best-case scenario. We have already made such messages; we are tired of seeing people asking primitive questions that have already been resolved. People would have known, had they participated in the official group chat. ReZygisk support has never been promised and has never been conducted in the Play Integrity Fix chat, Magisk Modules Group, ReVanced support chat, Telegram support chat, iOS support email, 911 emergency hotline, PornHub, Brazzers, Instagram comments, BurgerKing restaurant — SUPPORT IS ONLY PERFORMED IN @REZYGISKCHAT. A SIMPLE FRICKING CONCEPT. We will not be responsible for issues that you do not let us recognize. You cannot find ReZygisk representatives on RacistFurry Fans chats (or whatever you look for) for them to properly file and address issues or bugs. Our job is to only help you in @rezygiskchat. 📢 Please, forward this to different groups and/or channels for it to reach wider audiences.

  • 1 июл. 2025 г.20,3 тыс528

    👥️ Why? Because we are open and not racist! It's always good to cooperate with a fellow FOSS project. 🤝 👑 ReZyzyayayzyza is once again ahead of everyone! We are innovative, we are honest, we are tolerant, we are bombastic, we are brave, we are just, we are ..! Uh… Playful! 🌸 💎 We play Minecraft and many other games, so we are concerned about cheaty-cheats! 🤩 Always play fair: don't steal diamonds, don't steal code, don't use AIs. 📩 Subscribe to ReZygisk channel 🦕 And join the group!

  • 17 июн. 2025 г.17 тыс1091из performancorg_channel

    Exactly one year ago, consolidated as what it is known now: ReZygisk, named by one of our maintainers and (ReZygisk) WebUI designer and creator, RainyXeon. (Special thanks!) Since then, numerous, and unpredictable, events happened with this organization and us: met a previously unbelievable amount of supporters, created alliances with important names and developed a liked and well known module in the community. Now, in June 16th 2025, we are beyond the hundred and the 4 zeros -- revolutionizing how the Open Source community is seen, and modifying the future of this not-so-small group. This, however, would not be possible without the assistance of numerous people. Some having created Pull Requests, others testing builds and giving feedback and others just to spread the project farther. Happily, due to the huge amount of awesome humans that contributed in some way, I cannot list them and everything done. It's not from my liking that due to the busy and stressful life of a highschooler, no event or gift could be made for the community. My most sincere apologies for that, but I hope this text will show my gratefulness for everyone and everything that has happened in here, with you. Happy birthday, ReZygisk. --- It was so bright at the first moment, unsure what could happen, with this judgment. But we were never alone, knowledge that, and we would do anything to change the matte. Popularity was never what we looked for, It was only meant for only us to adore. Never had we foreseen beyond much. After all we had never looked for such. Out of the blue, numerous cats appeared. Scared of what they would do, we feared. However, they made us feel the other way, helping us, since then, in every single day. Over time, our eyes adjusted to the sun light, and more than ever, sure about doing the right. Delighted that it wasn't only us in all this dark, And that we, together, could make our mark. Since then, we exponentially met new friends. Some not so mild, but the majority commends. And with just that, we continued this calm walk, hoping for the best of this all, to not end up awk. Now, this is where we are, where we never thought. Sure that it was the cats who brighten the nought. Certain this is not the end, but the start of the new. Here, at the snow mountain, to show that we grew. --- Loosing your arm is not the worst thing that can happen, When love is at your side, you will be sure it will all go right. It might not go well to you, but I promise it will all slacken. You don't live for yourself, you are a poem for others to recite. --- Don't make this be for nothing.

  • 8 июн. 2025 г.11,8 тыс372

    📢 Just like many of us, Perdo — the founder and main developer of ReZygisk — has a personal blog-channel of his own! ℹ️ On this channel, Perdosaurus 🦖 will be sharing some nerdy technical stuff on internal progress of ReZygisk, so that the community might learn. Apart from that, it is quite possible he will give a slight insight into his personal life, which is full of brownies and Brazil phonk tracks. 🇧🇷

  • без подписи

  • 18 мая 2025 г.12,8 тыс422из performancorg_channel

    https://github.com/PerformanC/ReZygisk/commit/ed347e879e562058e8e93af53619de2243009221 For almost a year, there hasn't been a way to properly assure if the build file of ReZygisk sent by some random guy was official -- or even tampered with. Later on, signed builds were distributed by ReZygisk maintainers while asking for testing, however this would only impact machikado, which could only be used to verify whether or not the runtime files were tampered with. Today, on May 18th, Misaki has been introduced in ReZygisk. Misaki is a ReZygisk that allows tools to check whether a zip has been tampered with in any way, and to check if it uses official public key, this makes impossible to inject malicious code in a ReZygisk build and pass SignSee -- previously possible with machikado only. Both methods will be available, as Misaki only works pre-installation. Once installed, some files are discared, rendering misaki useless. For that, machikado exists, although some improvements are necessary to it. SignSee 0.0.2 is now the official to check if a build has been tampered with. Instructions are available in the own tool. Node.js and @noble/ed25519 library, available at npm (npm i -g @noble/ed25519) are required for its use. https://gist.github.com/ThePedroo/b04f209696953b9a144455fb12b90265 Transparency at first -- be safe.

  • 18 мая 2025 г.9 358301из performancorg_channel

    https://github.com/PerformanC/ReZygisk/commit/4de1b443cf98d63b2acd5b24b612a3c5ceedcd6a I am delighted to announce that, after almost a year of almost forever going work, the ReZygisk WebUI has finally arrived to main branch. This WebUI is not yet another feature of ReZygisk, but one that more than 20 people helped come to reality, not only by testing this time, but by adding pieces of code and translations. Shall we recognize the contribution of the following GitHub users, aside from the ones that made contributions off GitHub: - ExtremeXT | Kirill Kuznetsov | Berlian Panca | GhostFRR - Emulond | SheepChef | Willow Hayley | ZGX089ッ - Fyphen | AJleKcAHgP68 | witch | thasave14 - WinCS | Blazzycrafter | Lucky | Flopster101 - CaptainThrowback | Igor | Kitty | Lxchoooo Your work won't go unoticed. And special thanks to RainyXeon, one of the ReZygisk maintainers, the one responsible for the entire WebUI structure, design and code. Always remember to look after one another, that way, you'll live the truth of your own life. It's never too late to try again.

  • AVENGERS, ASSEMBLE! ⏱ Hey, bombs! Give this build a try! 🚔

  • 📢 Huh! Might be something interesting for Android developers! Give it a try, and let us know. 💬

  • ⚠️ Beware of scammers! Remember, nobody should be paid for FOSS products: if you see someone doing this — do not fall for their tricks, you are being scammed! Kernels, modules, root solutions — all this should only be distributed as freeware. 🚫 Report & Block similar violators!

  • 27 апр. 2025 г.8 248662из performancorg_channel

    It was June. Rainy and I were troubled by the not-so-recent changes in Zygisk Next, making it closed source, leaving us dependent of it. Then a new idea appeared: What if we made our own, just for us? There ReZygisk started. We were extremely new to both this community and Zygisk world.. we would first select commits from already existing Zygisk Next forks and then apply to our own (which only some weeks later we would make our own changes) and that way be happy with our small creation. PerformanC Organization Discord is usually a chill place, without much activity, but then numerous people started to join, and we were confused of the reason behind that. Days passed, and curiosity reached its limited, and we asked for one of them why is that, which although they couldn't answer, they explained that they came from APatch Telegram. "APatch" we wondered, as, like previously said, we were new. And we then made our own searches, finding out that they discovered ReZygisk and was talking about it in the group (https://t.me/apatch_discuss/60234). We were amazed, as although we created ReZygisk for ourselves, recognition is something we should be grateful for. Since then ReZygisk started to grow in a rate I never saw in any other project of mine. Months passing by (and ReZygisk STILL growing), we reached a lot of goals: Improved hiding, so that it passed AppDome; started working on own our WebUI -- one of the most modern looking ones out of all modules; ported a good amount of the codebase; and especially: we were satisfied with what we created. At first sight, ReZygisk seems to only be a fork of a project, but it's more than this: It is the movement for allowing more freedom, to stop hiding knowledge behind code obfuscation, to allow people to depend you not because they're forced to, but because they like you. We forked it because we were unsatisfied, and instead of keep complaining, we took action. Hahah, who could guess one day we would be here? ... And that is thanks to you, be you just someone that is reading this post but doesn't use RZ; just someone using it, but never directly contributed; and even if you are a hater. All of you made this be possible, made the community once again fight for freedom, and there's nothing that can be said that can express how thankful and proud I am for that -- and you should be too, as part of this creation. Today we celebrate the mark of 1000 stars, but this is not about ReZygisk becoming famous, but about more than 1k people work together, so that this happens. Never forget what you are, and especially don't forget what you fight for and believe. With just another small act, help someone, and be, in acts, the better -- and real -- human you are.

  • ℹ️ Quick introduction into what LKM is (KSU & KSUN). «LKM — Loadable Kernel Module (.ko) that provides ROOT access from init_boot or boot partitions. To load that .ko module you need a custom init script to load the LKM, which is proprietary. That being said, we never know exactly what is in the code or what the issue is when it occurs», — RifsxD. 🛡 LKM provides little to no advantage and violates the transparency principle. That's our chance to help RifsxD make KSUN fully FOSS.

  • Channel photo updated

  • ⚠️ This is awful! We might just end up more exposed to cyber dangers than ever before! I guess politics sometimes does affect all of us… 🔗 Forwarded from @pontushub.

  • Real situation at the moment: 📩 Subscribe to ReZygisk channel!

  • ⚠️ Attention to the dearest FOSS community: the referred website is fake, we highly advise you against visiting unverified sources. ✅ The official KSUN website is available at ksunext.org. 📢 Spread the word and have a safe FOSS experience 💚.

  • Our project will not provide support for SukiSU users due to violation of open-source ethics and requirements. We do not support code thieves and impostors. If you use SukiSU — you are not welcome. We are only for fair and healthy competition [in the FOSS bounds].

  • 18 мар. 2025 г.61,8 тыс5889

    🕊️ https://exposelsposed.pages.dev — Spread the word. #FOSS #AgainstProprietary #Transparency #OpenTheSources #DontHide #DontSteal #DontLie #Safety #RespectAndroidCommunity #NoClosedSource