roothide

3.8K posts

roothide banner
roothide

roothide

@roothideDev

Make jailbreak easier to use on daily devices. Discord: https://t.co/NTmmon7Eqr

Katılım Nisan 2023
1.8K Takip Edilen13.5K Takipçiler
Sabitlenmiş Tweet
roothide
roothide@roothideDev·
we updated the roothide api/sdk to make it easier to use, it allows your tweak to perform at its best performance and stability on roothide , and it is now automatically compatible with building rootful/rootless packages. (previously you may have nested roothide and rootless APIs/macros in one project, now this is no longer necessary) github.com/roothide/Devel…
English
73
22
181
104K
roothide
roothide@roothideDev·
@pierceboggan @code 3. The thinking effect and context window size toggle buttons no longer appear next to the model name in the chat panel.
English
0
0
0
155
roothide
roothide@roothideDev·
@pierceboggan @code The new model picker is even worse than before. In the previous version: 1. You could hide some models for the model picker in the model management list (very useful if your BYOK provider offers hundreds of models).
English
2
0
3
1K
Pierce Boggan
Pierce Boggan@pierceboggan·
BYOK keeps getting better in @code! New: - Context widget is populated for BYOK-contributed models - Configurable thinking effort for BYOK models that support reasoning - New model picker layout for quicker access to BYOK models #_language-models" target="_blank" rel="nofollow noopener">code.visualstudio.com/updates/v1_120…
English
7
5
78
7.7K
roothide
roothide@roothideDev·
@pierceboggan @code 2. The new model picker groups by configuration name instead of provider (allowing you to distinguish models from different BYOK providers added within the same provider extension).
English
0
0
1
213
roothide retweetledi
Ronny
Ronny@Lilnynho·
Introducing CCDNS — a native-looking Control Center DNS toggle for iOS 16 rootless jailbreaks. • Fast DNS switching • Clean stock iOS UI • Lightweight • Rootless support Built with Theos + Objective-C. @HavocRepo #jailbreak #iOS16 #Theos #iPhone #TweakDevelopment
Ronny tweet mediaRonny tweet media
English
4
5
36
3.2K
roothide
roothide@roothideDev·
we have updated the roothide/theos to be compatible with building roothide packages from existing tweak projects that use rootless path macros. github.com/roothide/Devel…
roothide tweet media
English
5
10
75
7.5K
roothide retweetledi
GrapheneOS
GrapheneOS@GrapheneOS·
Apple and Google are gradually expanding their use of hardware-based attestation. They're convincing a growing number of services to adopt it. Google's Play Integrity API and Apple's App Attest API are very similar. Apple brought it to the web via Privacy Pass, which Google intends on doing too. Google's Play Integrity API requires hardware attestation for the strong integrity level and is gradually phasing in requiring it for the more commonly used device integrity level. Apple already has it as a requirement. Over the long term, this will increasingly lock out hardware and OS competition. The purpose of these systems is disallowing people from using hardware and software not approved by Apple or Google. This is wrongly presented as being a security feature. Banks and government services are the main ones adopting it but Apple and Google are encouraging every service to use it. Apple's Privacy Pass brought hardware attestation to the web to help with passing captchas on their own hardware. Many people saw that as harmless since few sites would be willing to lock out non-Apple-hardware users. Apple and Google are both likely to bring broader hardware attestation to the web. Google's reCAPTCHA is planning an approach where they use Privacy Pass on Apple hardware, their own approach on Google Mobile Services Android devices and a QR code scanning system to require an iOS or Google certified Android device for Windows and other systems: support.google.com/recaptcha/answ… Banking and government services increasingly require using a mobile app where they can use attestation to force using an Apple or Google approved device and OS. Apple's privacy pass, Google's 'cancelled' Web Environment Integrity and now reCAPTCHA Mobile Verification are bringing this to the web. Current media coverage for reCAPTCHA Mobile Verification misunderstands it and the impact of it. They're bringing a hardware attestation requirement to Windows, desktop Linux, OpenBSD, etc. by requiring a QR scan from a certified smartphone to pass reCAPTCHA in some cases. They could expand it more. Control over reCAPTCHA puts Google in a position where they can require having either iOS or a certified Android device to use an enormous amount of the web. Google defines certification requirements for Android which includes forcing bundling Google Chrome, etc. It's enormously anti-competitive. Google's Play Integrity API bans using GrapheneOS despite it being far more secure than anything they permit. It also bans using any other alternative. This isn't somehow specific to an AOSP-based OS. You can't avoid this by using a mobile OS based on FreeBSD instead. You'll just be more locked out. Google's Play Integrity API permits devices with no security patches for 10 years. The device integrity level can be bypassed via spoofing but they can detect it quite well and block it once it starts being done at scale. The strong integrity level requires leaked keys from TEEs/SEs to bypass it. It doesn't provide a useful security feature, but it does lock out competition very well. Services requiring Apple App Attest or Google Play Integrity are primarily helping to lock in Apple and Google having a duopoly for mobile devices. Play Integrity is more relevant due to AOSP being open source. Governments are increasingly mandating using Apple's App Attest and Google's Play Integrity for not only their own services but also commercial services. The EU is leading the charge of making these requirements for digital payments, ID, age verification, etc. Many EU government apps require them. Instead of governments stopping Apple and Google from engaging in egregiously anti-competitive behavior, they're directly participating in locking out competition via their own services. Requiring people to have an Apple device or Google-certified Android device is anti-competition, not security. reCAPTCHA Mobile Verification will currently work with sandboxed Google Play on GrapheneOS but it clearly exists to provide a way for them to start using hardware attestation on systems without it. People without an iOS or Android device will be locked out when this is required even without that. This isn't about security or any missing functionality. GrapheneOS can be verified via hardware attestation. Google bans using GrapheneOS for Play Integrity because we don't license Google Mobile Services and conform to anti-competitive rules already found to be illegal in South Korea and elsewhere. Services shouldn't ban people from using arbitrary hardware and operating systems in the first place. Google's security excuse is clearly bogus when they permit devices with no patches for 10 years but not a much more secure OS. It's for enforcing their monopolies via GMS licensing, that's all.
English
156
2.3K
8.8K
323.9K
roothide retweetledi
Anubis Tweaks
Anubis Tweaks@AnubisTweaks·
[Paid Release] PhoneHub v1.0.0 Your iPhone’s call experience — reimagined. Advanced Caller ID — Truecaller, GetContact & more Smart SIM picker WhatsApp quick actions Auto redial & smart speaker Beautiful customizable UI Built for power users. soon on @HavocRepo #jailbreak
Anubis Tweaks tweet mediaAnubis Tweaks tweet media
English
1
10
44
5.2K
MEGA
MEGA@MEGAprivacy·
Google's reCAPTCHA now requires a QR code scan that only works with Google Play Services or a modern iPhone, meaning anyone without a certified device can't verify. They tried this in 2023 (Web Environment Integrity) and pulled it after public outcry, so this time they launched it as a commercial product instead of a public proposal. The old CAPTCHA methods are still accessible as a fallback for now, but how long Google keeps that option around is anyone's guess. 🤷‍♂️
International Cyber Digest@IntCyberDigest

‼️🚨 ALARMING: Google now treats privacy as suspicious behavior by default. Users of GrapheneOS, CalyxOS, /e/OS, and other deGoogled Android phones are being locked out of millions of websites unless they install the exact Google Play Services software they deliberately removed. GrapheneOS is recommended by the EFF and used by journalists, lawyers, and activists in high-risk environments. The audience most likely to read Google's data practices and refuse its terms is now flagged as fraudulent for that exact decision. What happened?: ▪️ Google announced "Cloud Fraud Defense" at Cloud Next on April 22-23, 2026, branding it "the next evolution of reCAPTCHA." Existing reCAPTCHA customers were auto-migrated. ▪️ When the system flags traffic as suspicious, the old click-the-bus puzzle is gone. Users get a QR code instead. ▪️ Scanning the QR code requires Google Play Services running on the device. Internet Archive snapshots show this requirement has been live since at least October 2025, silently rolled out for 7 months before anyone noticed. ▪️ No Play Services = no QR scan = locked out. The bigger picture: ▪️ Google already tried this in 2023. It was called Web Environment Integrity (WEI), and it would have let Google decide which devices were "real enough" to access the web. Standards bodies and the public pushed back hard, and Google killed it. Three years later, the same idea is back, just hidden behind a QR code instead of a browser feature. ▪️ reCAPTCHA runs on millions of websites. Every developer who keeps using it is now, by default, telling deGoogled Android users they're not welcome...

English
51
699
4.6K
261.6K
roothide
roothide@roothideDev·
We've moved the LLVM related packages from Procursus(roothide) repo to the release page repo. This should be sufficient for apt to handle them correctly. If you need them now, you can now manually add them to sileo/zbera/apt:
English
3
6
40
7.4K
roothide
roothide@roothideDev·
we updated the roothide api/sdk to make it easier to use, it allows your tweak to perform at its best performance and stability on roothide , and it is now automatically compatible with building rootful/rootless packages. (previously you may have nested roothide and rootless APIs/macros in one project, now this is no longer necessary) github.com/roothide/Devel…
English
73
22
181
104K
roothide retweetledi
ONE Jailbreak
ONE Jailbreak@onejailbreak_·
🗞️Even Apple uses AI to write code now 🤖 onejailbreak.com/blog/apple-acc… Apple accidentally shipped internal Claude Code files inside the Apple Support app update.
ONE Jailbreak tweet media
English
7
15
137
19.9K
Xint
Xint@xint_official·
Patch your Linux boxes! Copy.Fail is a trivially exploitable logic bug in Linux, reachable on all major distros released in the last 9 years. A small, portable python script gets root on all platforms. Found by the teams at @theori_io and @xint_official More details below xint.io/blog/copy-fail…
English
24
365
991
246.6K
82Flex
82Flex@82Flex·
iOS 18+ kernelcaches ship inside encrypted AEA OTA assets that can exceed 7 GiB. This fork adds a streaming HTTP-Range path so libgrabkernel2 can extract only the kernelcache chunk (~60 MiB) without downloading the full asset. github.com/Lessica/libgra…
82Flex tweet media
English
1
15
128
16.5K