RIP Ask Jeeves πͺ¦
Ask.com aka Ask Jeeves has officially shut down on May 1, 2026, ending its 25-year run.
You will be missed π
Follow @TechLeaksZone
Ask.com aka Ask Jeeves has officially shut down on May 1, 2026, ending its 25-year run.
You will be missed π
Follow @TechLeaksZone
π’99π6π6π5π5β€4π€‘3
If Duolingo or Google would have built GitHub
People are really creative with ChatGPT images v2
People are really creative with ChatGPT images v2
β€74π€‘22π2πΏ2
GitHub but built by Apple, Instagram and P*rnhub would be like:
π₯76π€‘28β€7πΏ6π4
Forwarded from Mystic Leaks
Hey! We've been hinting at these for a while now... but it's time to drop the nuke β’οΈπ₯
Here, you'll find all the information we are currently aware of regarding the upcoming Pixel 11 (P26) lineup, including some news that might surprise you π
Without any further ado, let's jump into it:
βββ
π General P26 (Pixel 2026) Infos:
πΉ SoC β Tensor G6 (Malibu)
β Built on TSMC N2 node
β’ 1Γ ARM C1-Ultra @ 4.11 GHz
β’ 4Γ ARM C1-Pro @ 3.38 GHz
β’ 2Γ ARM C1-Pro @ 2.65 GHz
πΉ GSC β Titan M3 (Epic)
πΉ GPU β PowerVR C-Series CXTP-48-1536
πΉ Modem β MediaTek M90 (MT6986D)
πΉ New TPU β Codename: Santafe
πΉ New GXP β Codename: Metis
βββ
π± Pixel 11 (Cubs):
πΈ SKUs: GPQQ7 (MMW) / GUJ0N (ROW) / GV9X7 (JPN)
πΈ Colors: BLK (Black), GRN (Green), PNK (Pink), PPL (Purple)
πΈ RAM: 8 (?) / 12 GB
πΈ Display: 6.3" OLED, 1080Γ2424, 60β120 Hz, 240 Hz PWM, up to 2200 nits
πΈ Battery: 4840 mAh (minimal capacity)
πΈ Camera: New main β sensor: chemosh, lens: vesta β very likely 50 MP!
βββ
π± Pixel 11 Pro (Grizzly):
πΈ SKUs: G7SWN (MMW) / GM45K (ROW) / G9W5D (JPN)
πΈ RAM: 12 / 16 GB (two different SKUs)
πΈ Display: 6.3" OLED, 1280Γ2856, 1β120 Hz, 240 Hz PWM, up to 2450 nits
πΈ Battery: 4707 mAh (minimal capacity)
πΈ Camera: New main (bastet / vesta) + new telephoto (barghest / chonky)
βββ
π± Pixel 11 Pro XL (Kodiak):
πΈ SKUs: GBC0H (MMW) / G4HCD (ROW) / GER5L (JP)
πΈ RAM: 12 / 16 GB (two different SKUs)
πΈ Display: 6.8" OLED, 1344Γ2992, 1β120 Hz, 240 Hz PWM, up to 2450 nits
πΈ Battery: 5000 mAh (minimal capacity)
πΈ Camera: New main (bastet / vesta) + new telephoto (barghest / chonky)
βββ
π± Pixel 11 Pro Fold (Yogi):
πΈ SKUs: GZDQ6 (MMW) / GM2SN (JPN)
πΈ RAM: 12 / 16 GB
πΈ Inner Display: 2076Γ2160 OLED, 1β120 Hz, up to 2050 nits
πΈ Outer Display: 1080Γ2342 OLED, 60β120 Hz, up to 2450 nits
πΈ Battery: 4658 mAh (minimal capacity)
πΈ Camera: New main (chemosh) lens
βββ
β¨ And... one more thing! Or two, perhaps...
1οΈβ£ Both the 11 Pro and the Pro XL, as well as the 11 Pro Fold, won't feature a thermometer (RIP π₯). Instead, all of them will spot an RGB LED array in the camera bar β somewhat similar to Nothing's Glyph, but smaller.
2οΈβ£ Despite previous claims, Project Toscana (IR Face Unlock) likely won't debut on the P26 lineup, as it's simply still not ready for release.
P.S: The attached image is AI Generated, but it resembles the actual look of the Pixel 11 Pro's back cover
Do you think Google cooked with this one? Or is it below your expectations?
Let us know down below!
Here, you'll find all the information we are currently aware of regarding the upcoming Pixel 11 (P26) lineup, including some news that might surprise you π
Without any further ado, let's jump into it:
βββ
π General P26 (Pixel 2026) Infos:
πΉ SoC β Tensor G6 (Malibu)
β Built on TSMC N2 node
β’ 1Γ ARM C1-Ultra @ 4.11 GHz
β’ 4Γ ARM C1-Pro @ 3.38 GHz
β’ 2Γ ARM C1-Pro @ 2.65 GHz
πΉ GSC β Titan M3 (Epic)
πΉ GPU β PowerVR C-Series CXTP-48-1536
πΉ Modem β MediaTek M90 (MT6986D)
πΉ New TPU β Codename: Santafe
πΉ New GXP β Codename: Metis
βββ
π± Pixel 11 (Cubs):
πΈ SKUs: GPQQ7 (MMW) / GUJ0N (ROW) / GV9X7 (JPN)
πΈ Colors: BLK (Black), GRN (Green), PNK (Pink), PPL (Purple)
πΈ RAM: 8 (?) / 12 GB
πΈ Display: 6.3" OLED, 1080Γ2424, 60β120 Hz, 240 Hz PWM, up to 2200 nits
πΈ Battery: 4840 mAh (minimal capacity)
πΈ Camera: New main β sensor: chemosh, lens: vesta β very likely 50 MP!
βββ
π± Pixel 11 Pro (Grizzly):
πΈ SKUs: G7SWN (MMW) / GM45K (ROW) / G9W5D (JPN)
πΈ RAM: 12 / 16 GB (two different SKUs)
πΈ Display: 6.3" OLED, 1280Γ2856, 1β120 Hz, 240 Hz PWM, up to 2450 nits
πΈ Battery: 4707 mAh (minimal capacity)
πΈ Camera: New main (bastet / vesta) + new telephoto (barghest / chonky)
βββ
π± Pixel 11 Pro XL (Kodiak):
πΈ SKUs: GBC0H (MMW) / G4HCD (ROW) / GER5L (JP)
πΈ RAM: 12 / 16 GB (two different SKUs)
πΈ Display: 6.8" OLED, 1344Γ2992, 1β120 Hz, 240 Hz PWM, up to 2450 nits
πΈ Battery: 5000 mAh (minimal capacity)
πΈ Camera: New main (bastet / vesta) + new telephoto (barghest / chonky)
βββ
π± Pixel 11 Pro Fold (Yogi):
πΈ SKUs: GZDQ6 (MMW) / GM2SN (JPN)
πΈ RAM: 12 / 16 GB
πΈ Inner Display: 2076Γ2160 OLED, 1β120 Hz, up to 2050 nits
πΈ Outer Display: 1080Γ2342 OLED, 60β120 Hz, up to 2450 nits
πΈ Battery: 4658 mAh (minimal capacity)
πΈ Camera: New main (chemosh) lens
βββ
β¨ And... one more thing! Or two, perhaps...
1οΈβ£ Both the 11 Pro and the Pro XL, as well as the 11 Pro Fold, won't feature a thermometer (RIP π₯). Instead, all of them will spot an RGB LED array in the camera bar β somewhat similar to Nothing's Glyph, but smaller.
2οΈβ£ Despite previous claims, Project Toscana (IR Face Unlock) likely won't debut on the P26 lineup, as it's simply still not ready for release.
P.S: The attached image is AI Generated, but it resembles the actual look of the Pixel 11 Pro's back cover
Do you think Google cooked with this one? Or is it below your expectations?
Let us know down below!
π72β‘15β€13π€‘9π1π€1π΄1
Forwarded from vx-underground
Here's the thing no one wants to tell you about AI:
1. It's the worlds largest Python script
2. It runs on Linux, Windows Defender slows it down
3. It uses lots of numbers (nobody knows why)
4. It requires a bunch of GPUs (for gaming)
5. No, you can't have sex with it
1. It's the worlds largest Python script
2. It runs on Linux, Windows Defender slows it down
3. It uses lots of numbers (nobody knows why)
4. It requires a bunch of GPUs (for gaming)
5. No, you can't have sex with it
π73
Microsoft Edge loads all your saved passwords into memory in cleartext, even when you are not using them
In the video, the attacker has compromised a user account with administrative rights and is able to view stored credentials for two other logged-on (or even disconnected) users with Edge running.
When you save passwords in Edge, the browser decrypts every credential at startup and keeps them resident in process memory. This happens even if you never visit a site that uses those credentials. At the same time, Edge requires you to re-authenticate before showing those same passwords in the Password Manager UI, yet the browser process already has them all in plaintext.
In contrast, Chrome decrypts credentials only when needed and uses App-Bound Encryption to prevent other processes from reusing its keys. This ensures plaintext passwords appear only briefly during autofill, making memory scraping far less effective.
The researcher reported this to Microsoft, and the official response was that the behavior is "by design". He will soon release a simple & educational tool on GitHub to help people easily see that the passwords are stored in cleartext in memory.
Follow @TechLeaksZone
https://fixvx.com/L1v1ng0ffTh3L4N/status/2051308329880719730?s=20
In the video, the attacker has compromised a user account with administrative rights and is able to view stored credentials for two other logged-on (or even disconnected) users with Edge running.
When you save passwords in Edge, the browser decrypts every credential at startup and keeps them resident in process memory. This happens even if you never visit a site that uses those credentials. At the same time, Edge requires you to re-authenticate before showing those same passwords in the Password Manager UI, yet the browser process already has them all in plaintext.
In contrast, Chrome decrypts credentials only when needed and uses App-Bound Encryption to prevent other processes from reusing its keys. This ensures plaintext passwords appear only briefly during autofill, making memory scraping far less effective.
The researcher reported this to Microsoft, and the official response was that the behavior is "by design". He will soon release a simple & educational tool on GitHub to help people easily see that the passwords are stored in cleartext in memory.
Follow @TechLeaksZone
https://fixvx.com/L1v1ng0ffTh3L4N/status/2051308329880719730?s=20
vxTwitter / fixvx
π 8.51K π 1.26K
π 8.51K π 1.26K
Tom JΓΈran SΓΈnstebyseter RΓΈnning (@L1v1ng0ffTh3L4N)
Microsoft Edge loads all your saved passwords into memory in cleartext β even when youβre not using them.
π€‘106π12β€3π1
Tech & Leaks Zone
Microsoft Edge loads all your saved passwords into memory in cleartext, even when you are not using them In the video, the attacker has compromised a user account with administrative rights and is able to view stored credentials for two other logged-on (orβ¦
Proof of Concept for 'Dump Edge Cleartext Credentials' showcasing Microsoft Edge dumping all your password in memory in cleartext is now available on GitHub
https://github.com/L1v1ng0ffTh3L4N/EdgeSavedPasswordsDumper
https://github.com/L1v1ng0ffTh3L4N/EdgeSavedPasswordsDumper
GitHub
GitHub - L1v1ng0ffTh3L4N/EdgeSavedPasswordsDumper: Proof of concept to show that Edge stores credentials in cleartext
Proof of concept to show that Edge stores credentials in cleartext - L1v1ng0ffTh3L4N/EdgeSavedPasswordsDumper
π€£43β€6
Forwarded from ATT β’ Tech News (Ξgam)
Your Phone Number can easily be leaked on Telegram due to this default setting
If you hide your number from your Telegram profile, it can still be obtained. You may ask, how? This is because of how Contact Discovery works on any messaging app (including WhatsApp, Signal, Telegram, etc.).
If I save a random number on my phone that turns out to be yours, Telegram will automatically link the number to your profile. This is exploited by attackers, by saving thousands of numbers in the phone's contacts (with a
This is how some people's numbers get leaked on Telegram as this option is set to "Everybody" by default.
If you want to prevent this, change "Who can find me by my number" to "My Contacts" in Privacy settings. This way, your number won't be linked to your profile as long as you don't have the attacker's number saved.
π§βπ» @agamtechtricks
If you hide your number from your Telegram profile, it can still be obtained. You may ask, how? This is because of how Contact Discovery works on any messaging app (including WhatsApp, Signal, Telegram, etc.).
If I save a random number on my phone that turns out to be yours, Telegram will automatically link the number to your profile. This is exploited by attackers, by saving thousands of numbers in the phone's contacts (with a
.vcf file for a lot of numbers), and then syncing them in Telegram. If the contacts list contains your number, it'll be linked to your profile, and will be exposed.This is how some people's numbers get leaked on Telegram as this option is set to "Everybody" by default.
If you want to prevent this, change "Who can find me by my number" to "My Contacts" in Privacy settings. This way, your number won't be linked to your profile as long as you don't have the attacker's number saved.
π§βπ» @agamtechtricks
β€58π₯΄20π7
Forwarded from Winaero
The team behind Windows Terminal and PowerToys unveiled a rebuilt version of the Run dialog for Windows 11, developed from scratch with user feedback guiding the design. The interface adopts Fluent Design, aligns with Windows 11, and includes dark theme support.
Developers prioritized performance, reducing average window appearance time to 94 milliseconds, achieved through cross-team collaboration, UI and architectural optimizations. The tool navigates local and network locations rapidly, and users still access it via the Win + R shortcut.
Engineers added telemetry to the legacy dialog to measure rendering times and feature usage, finding the classic window averaged 103 milliseconds, only 0.0038 percent of 35 million users clicked the Browse button, and some users paste text into Run to clear formatting.
PowerToys Run prototypes and the CmdPal project inspired development, and CmdPal contributions now power the new dialog, which is a C# WinUI 3 application compiled with .NET AOT. The dialog supports ~\ (hello Linux users) to open the home folder, and the history drop-down displays application icons.
Developers prioritized performance, reducing average window appearance time to 94 milliseconds, achieved through cross-team collaboration, UI and architectural optimizations. The tool navigates local and network locations rapidly, and users still access it via the Win + R shortcut.
Engineers added telemetry to the legacy dialog to measure rendering times and feature usage, finding the classic window averaged 103 milliseconds, only 0.0038 percent of 35 million users clicked the Browse button, and some users paste text into Run to clear formatting.
PowerToys Run prototypes and the CmdPal project inspired development, and CmdPal contributions now power the new dialog, which is a C# WinUI 3 application compiled with .NET AOT. The dialog supports ~\ (hello Linux users) to open the home folder, and the history drop-down displays application icons.
β47β€25π€‘8π6β€βπ₯2π1
Forwarded from Mystic Leaks
Hey.. we need to talk..
The May 2026 update has been released today! As weβve leaked before, this update includes a bootloader update for the Pixel 10 series that increments the anti-rollback counter, preventing from downgrading to a vulnerable version of the bootloader.
While weβre out here warning you, thereβs a big brick issue that Google refuses to address publicly: b/507968853
As many of you developers know, once a Pixel enters one of these recovery modes:
Pixel ROM Recovery (Pixel 6-8 series)
Pixel BL1 Recovery (Pixel 9 series)
Pixel DBL Recovery (Pixel 10+ series)
The Pixel becomes a paperweight.
We know that Googlers have an internal tool (go/flash/tools/pixel/rom_recovery) and signed recovery images (signed/signed-recovery.zip) to recover a device from such mode.
However, external users donβt have them. Every complaint about that on the Issue Tracker gets a Wonβt Fix or a Duplicate of x status.
The primary issue (b/402455330) hasnβt gotten an answer from Google since April 2025.
The continued silence makes it look like the company doesnβt care about its users. The problem has been raised for years. Yet thereβs still no public statement.
Everything's changed when a developer (JoshuaDoes) has released a tool called tensor-usbdl that can work with a device stuck in Pixel ROM Recovery mode.
The catch?
- Currently, the tool only has the leaked recovery signed images for the Pixel 7 / Pixel 7 Pro and the Pixel 8 / 8 Pro.
- The Pixel 8 images only work if you have never updated your phone to the May 2025 update. If you did, well youβre locked out for now.
The fact that an independent developer made such a tool proves that Google could do something about this but they wonβt, meanwhile no one we know of has taken advantage of it to break the device security.
What do you think about this? Have you ever bricked a Pixel? Let us know in the comment section!
By the way regarding the leaks, we know and we're dropping another bomb soon so stay tuned
The May 2026 update has been released today! As weβve leaked before, this update includes a bootloader update for the Pixel 10 series that increments the anti-rollback counter, preventing from downgrading to a vulnerable version of the bootloader.
While weβre out here warning you, thereβs a big brick issue that Google refuses to address publicly: b/507968853
As many of you developers know, once a Pixel enters one of these recovery modes:
Pixel ROM Recovery (Pixel 6-8 series)
Pixel BL1 Recovery (Pixel 9 series)
Pixel DBL Recovery (Pixel 10+ series)
The Pixel becomes a paperweight.
We know that Googlers have an internal tool (go/flash/tools/pixel/rom_recovery) and signed recovery images (signed/signed-recovery.zip) to recover a device from such mode.
However, external users donβt have them. Every complaint about that on the Issue Tracker gets a Wonβt Fix or a Duplicate of x status.
The primary issue (b/402455330) hasnβt gotten an answer from Google since April 2025.
The continued silence makes it look like the company doesnβt care about its users. The problem has been raised for years. Yet thereβs still no public statement.
Everything's changed when a developer (JoshuaDoes) has released a tool called tensor-usbdl that can work with a device stuck in Pixel ROM Recovery mode.
The catch?
- Currently, the tool only has the leaked recovery signed images for the Pixel 7 / Pixel 7 Pro and the Pixel 8 / 8 Pro.
- The Pixel 8 images only work if you have never updated your phone to the May 2025 update. If you did, well youβre locked out for now.
The fact that an independent developer made such a tool proves that Google could do something about this but they wonβt, meanwhile no one we know of has taken advantage of it to break the device security.
What do you think about this? Have you ever bricked a Pixel? Let us know in the comment section!
β€47β€βπ₯4π€‘4π1
Google Teases Liquid Glass inspired design coming with the next Material You Design language MD4 in Android
https://fixvx.com/avstorm/status/2051755703916786080?s=20
https://fixvx.com/avstorm/status/2051755703916786080?s=20
vxTwitter / fixvx
π 5.44K π 204
π 5.44K π 204
Andreas Storm (@avstorm)
One of the biggest Android updates ever is coming.
π€‘85π₯24β€5π³3π1π1
Xiaomi HyperOS 4: Monkey See, Monkey Hyper!
While Google, Samsung and other Chinese smartphone brands stayed away from adding a liquid glass mess to keep the user experience clean, Xiaomi will prove that they have NO ideas without Apple. They are the only company brave enough to steal the design everyone else hated except Huawei.
Follow @TechLeaksZone
While Google, Samsung and other Chinese smartphone brands stayed away from adding a liquid glass mess to keep the user experience clean, Xiaomi will prove that they have NO ideas without Apple. They are the only company brave enough to steal the design everyone else hated except Huawei.
Follow @TechLeaksZone
π€£95π€‘15β€9
Your regular public service reminder that "WinUI 2" is now referred to as "WinUI for UWP" and "WinUI 3" is now simply "WinUI".
THANK YOU FOR YOUR ATTENTION TO THIS MATTER
Follow @TechLeaksZone
THANK YOU FOR YOUR ATTENTION TO THIS MATTER
Follow @TechLeaksZone
π€‘59π13π€£5β€2
Forwarded from Mystic Leaks
This media is not supported in your browser
VIEW IN TELEGRAM
π
4π€‘82β€24π4π€―3π2