T.R.M.'s Flexes
T.R.M.'s Xiaomi Edits - Perf Neon Weekly "The Journey of Umamusume Dreams" > Information > Releases TL;DR > Built on: 2026/03/24, Unix Timestamp 1774337122 > ReSukiSU version: v4.1.0-b04aba6f@ReSukiSU > ReSukiSU KPM: false > SUSFS version: v2.1.0 > Baseband…
BORE Scheduler have been added into Perf Neon. it will be available on the next weekly build.
🔥1
https://www.reddit.com/r/linux/s/mNkZJYIdKw
I guess ubuntu is finally on par with Fedora and Arch in terms of NEW devices
I guess ubuntu is finally on par with Fedora and Arch in terms of NEW devices
Reddit
From the linux community on Reddit: Ubuntu 26.04 LTS Beta Released: Powered By Linux 7.0 + GNOME 50 + Mesa 26.0
Explore this post and more from the linux community
T.R.M.'s Flexes
https://www.reddit.com/r/linux/s/mNkZJYIdKw I guess ubuntu is finally on par with Fedora and Arch in terms of NEW devices
And this shit comes up
https://linuxiac.com/canonical-plans-controversial-grub-changes-for-ubuntu-26-10-secure-boot/
https://linuxiac.com/canonical-plans-controversial-grub-changes-for-ubuntu-26-10-secure-boot/
Linuxiac
Canonical Plans Controversial GRUB Changes for Ubuntu 26.10 Secure Boot
Canonical plans changes to Secure Boot GRUB in Ubuntu 26.10, removing support for LUKS, LVM, ZFS, and other features.
T.R.M.'s Xiaomi Edits - Perf Neon Weekly
> Information
> Releases
TL;DR
SUSFS Enabled Features
ROM Compatibility
Device Compatibility
"The Journey of Umamusume Dreams"
> Information
> Releases
TL;DR
> Built on: 2026/03/29, Unix Timestamp 1774762374
> ReSukiSU version name: v4.1.0-575ea1a1@ReSukiSU
> ReSukiSU version code: 34681
> ReSukiSU KPM: false
> SUSFS version: 2.1.0
> Baseband Guard version: be030b29
> Compiled with -O3, LTO, LLVM=1
SUSFS Enabled Features
"CONFIG_KSU_SUSFS_SUS_PATH=n"
"CONFIG_KSU_SUSFS_SUS_MOUNT=n"
"CONFIG_KSU_SUSFS_SUS_KSTAT=y"
"CONFIG_KSU_SUSFS_SPOOF_UNAME=y"
"CONFIG_KSU_SUSFS_ENABLE_LOG=y"
"CONFIG_KSU_SUSFS_HIDE_KSU_SUSFS_SYMBOLS=y"
"CONFIG_KSU_SUSFS_SPOOF_CMDLINE_OR_BOOTCONFIG=y"
"CONFIG_KSU_SUSFS_OPEN_REDIRECT=n"
"CONFIG_KSU_SUSFS_SUS_MAP=n"
"CONFIG_KSU_SUSFS_TRY_UMOUNT=n"
ROM Compatibility
> Official LineageOS
> /e/ Community Builds
> Official LibreMobileOS
Device Compatibility
> Redmi Note 10 Pro/Pro Max (sweet)
> Redmi Note 8/8T (ginkgo/willow)
> Redmi 4A/5A/Note 5A Lite/Y1 Lite (mi8917)
> Redmi 3/3S/4/4X/Note 5A Prime/Y1 Prime (mi8937)
🔥5❤1
Oh yea if you are using distrobox on your system, and your xdg-open, distrobox-host-exec, or even host-spawn did not do anything, and you check you already installed flatpak, try to upgrade host-spawn on the container to it's latest version.
Do be noted that you need to download the binary manually from the github releases and replaced the one from distrobox built in host-spawn.
Also you need these variables on your host system or else distrobox might freak out when you try to kickstart the container after a host restart: DBX_SKIP_WORKDIR=1
Do be noted that you need to download the binary manually from the github releases and replaced the one from distrobox built in host-spawn.
Also you need these variables on your host system or else distrobox might freak out when you try to kickstart the container after a host restart: DBX_SKIP_WORKDIR=1
GitHub
GitHub - 1player/host-spawn: Run commands on your host from inside your toolbox or flatpak sandbox
Run commands on your host from inside your toolbox or flatpak sandbox - 1player/host-spawn
Forwarded from Tech & Leaks Zone
EXPOSED: Source Code Evidence of Nekogram Phone Number Harvesting
1. Exfiltration Logic: The function uo5.g() (reconstructed as logNumberPhones) silently collects the UserID and Phone Number of every account logged into the app (up to 8 accounts).
2. Transmission: Data is sent via Inline Queries to the bot @nekonotificationbot. This is done programmatically, so no message appears in your "Sent" history.
3. Target Bots: Three bots embedded in the client's obfuscated code:
@nekonotificationbot: Receives the automated phone number uploads.
@tgdb_search_bot and @usinfobot: : An OSINT bot mentioned in the obfuscated classes.
4. Security Token: The app uses a hardcoded secret key 741ad28818eab17668bc2c70bd419fc25ff56481758a4ac87e7ca164fb6ae1b1 as a prefix for the stolen data, likely to authenticate with the bot's backend.
5. The image shows that Nekogram always wants to get the "reg date".
Unfortunately the Google Play Store version is also affected!!!
Follow @TechLeaksZone
1. Exfiltration Logic: The function uo5.g() (reconstructed as logNumberPhones) silently collects the UserID and Phone Number of every account logged into the app (up to 8 accounts).
2. Transmission: Data is sent via Inline Queries to the bot @nekonotificationbot. This is done programmatically, so no message appears in your "Sent" history.
3. Target Bots: Three bots embedded in the client's obfuscated code:
@nekonotificationbot: Receives the automated phone number uploads.
@tgdb_search_bot and @usinfobot: : An OSINT bot mentioned in the obfuscated classes.
4. Security Token: The app uses a hardcoded secret key 741ad28818eab17668bc2c70bd419fc25ff56481758a4ac87e7ca164fb6ae1b1 as a prefix for the stolen data, likely to authenticate with the bot's backend.
5. The image shows that Nekogram always wants to get the "reg date".
Unfortunately the Google Play Store version is also affected!!!
Follow @TechLeaksZone