nice
Their ticketing system was breached https://blog.trezor.io/trezor-security-update-stay-vigilant-against-potential-phishing-attack-bb05015a21f8
use JADE open source
key point sending "signed npub" to an image or any file server to associate it with any exit IPs (which are always loaded in any server)
it is not the real deal - since many people post their real pic - location voluntarily themselves - issue here npub-ip mapping (any exit ip) - using craft url embedded in picture -Ā in DM - can do it outside of DM - not sure
Still testing Please ignore PVĀ šš
correct - but seems image url in DM can bypass image proxy settings maybe.
Hey nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z can we get a new application option to help combat potentially leaking IP addresses via image loading? Maybe add a following only option here? So that we can always load images from people we're following. Thanks.
#m=image%2Fjpeg&dim=1080x2400&blurhash=%5B02O%7CsNFD%25xu%3FHM%7B-%3Bxut6M%7B%252xut6M%7C%25Mxt%7EqM%7CD%24t7oeM%7B-%3Bt7-%3BM%7Bt7t7xuM%7B%25Mt7_3M%7BIUt7&x=efbb1ebe1e2ab671cc6816d40b9202649f11a43c0304dbd48959fe936a14a8de
most app default settings - keep images blur/ not load from global aka "not following npubs"
nothing special needed except user education/awareness for now
everyone donot click READ from unknown npubs in DM when u dnot wanna reveal current exit IP <-> npub until u turn some condom like tor/vpn/proxy