No deleted account found from 86 scanned users from this group 🚫👻

💬 Send /lang to change language of the bot

🌽 New Kernel 🧪 Pre-Release Uploaded
📦 Repository: WildKernels/GKI_KernelSU_SUSFS
✏️ Commit: fa51347f1e9a45275b2f99e6c9a2049d5632244c
🔗 View GitHub Release

Telegram has implemented strict rate limiting for third-party clients, especially when using VPNs or virtual phone numbers. If you are experiencing issues such as “Connecting…” or “Updating…”, try turning off your VPN and using a physical phone number, purchasing Telegram Premium may also help.

heads up

you can switch metamodules but with a caveat

mountify -> meta-mm ✅
meta-mm -> mountify ✅

these are both okay.
however

meta-overlay -> meta-mm ❌
meta-overlay -> mountify ❌
mountify -> meta-overlay ❌
meta-mm -> meta-overlay ❌

this is due to MODDIR/system folder hierarchy.
if coming from meta-overlay or going to meta-overlay
I recommend re-installation of systemless modules.

https://github.com/backslashxx/mountify/releases/tag/174

$ git log --pretty=%s 173..HEAD --reverse
scripts/metainstall: no-op handle_partition instead
webui: drop nomount and notmpfs
scripts/post-fs-data: respect skip_mount on metamodule mode
scripts/customize: add warnings inside flag files
README: update to recent events

with mountify 174, skip_mount is now respected but only on ksu metamodule mode.

for other managers, you can still use skip_mountify

or as I always recommend, mode 1, manually choose what you want mounted.

as for the dropping of .nomount and .notmpfs, this is only dropped on the webui, backend will keep support, I will likely keep it there for two or three months.

some kernelsu forks like rksu and kernelsu "next" are still not on metamodule.