This image is cryptographically attested to be completely real
*adds a third eye on your forehead*

Inspired by Google?!

I used to say that the only sites without a numerical article ID or dates in URLs are an obvious SEO spam, but now it's more and more frequent. The syntax of your URLs has completely valid reasons to change over time and any measure that prevents link rot should be appreciated. It's great when a dead URL gives you a clue.

Btw, if you'd want to increase the chance that a conspiracy in your device gets found or simply inform the public about new or exotic device, proceed here and send a message with captured file to that channel (as long as your device isn't there yet):
https://news.1rj.ru/str/cam2caps/331

Word is spreading that you should absolutely stop updating your Snapdragon devices if you want a bootloader unlock on previously not unlockable models.

First, SHIFTphone 8.1 got two IMX766, now Vivo resurrected it for a main. Isn't it already a longer market lifespan than with IMX363?

For a while, I could've sworn that I've seen a 50MP sensor smaller than anything else with an obscure name, coming from Sony. Looks like today I found it again. It's called IMX852 and it's just 1/2.93".

Bonus: meet a Realme with a smaller main camera sensor than the one on front.

List updated to include a rarity like Solana Seeker, it has a 6.36" screen, but I had to stretch the width requirement.

Google? Monopoly? No! Their own store invites you to install an app ripping off their icon xD

Remember this? https://f-droid.org/packages/me.zhanghai.android.untracker

A challenger appeared.
https://github.com/blankdotdev/sidestep

It's totally not an UEFI integration state experiment on NexPhone.

https://archive.is/2026.02.09-140317/https://www.theverge.com/tech/875309/discord-age-verification-global-roll-out

All corps will KYC you at first opportunity if given social acceptance. Your role is to not give it to them. What do you expect to happen otherwise?

It also reminds me how a friend wanted to buy a phone from Amazon and they wouldn't let him xD Thankfully it was their loss.

To anyone developing an exploit (chain?) for this, make sure to claim your authorship on release so that no one takes the undeserved credit. Even if you don't care if it's attributed to you.

Either way, diff the manifests and bootloader branches. OEMs worried about this are unlikely to be any more bothered than they are now.

And to OEMs: bootloader unlocking won't be a news-worthy vulnerability if you streamline it and make it official (you'll also lessen the incentives of public exploitation in first place). Take note of HMD constantly trying to block it only to fail again and again, it's a bad look, for no good reason. Open source is widely understood as healthy for privacy and security, any sign that you're in favor of it, even if only as symbolic as allowing unlock and releasing squashed kernel modules, is a good business. Let people wait two weeks since activation, display a nag screen, it still won't hurt you.