Richard Gaywood

https://infosec.exchange/@penllawen

Reformed SWE, now a privacy engineer at Android.

I mostly post about tech, cooking (especially BBQ), dogs, and games. I'm always on some nerdy hobby, currently it's Home Assistant. I'm often joking. He/him.

I have a not-well-used side account for TTRPGs: Richard Gaywood (npub1w5t…2ea0).

Public Key

npub1tcuq6px6c3l9nwvng2dzzldtvvvlmkuvc9vxy97j8h47zuuw93vq362uw2

NIP-05 Address

penllawen_at_infosec.exchange@momostr.pink

Profile Code

nprofile1qqs9uwqdqndvgljehxf59x3p0k4kxx0amwxvzkrzzlfrm6lpww8zckqpr9mhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmnt9uq3samnwvaz7tmjv4kxz7fwdehhxamgv4ex2tnrdakstrss83

Publishing to

relay.momostr.pink

relay.noswhere.com

relay.nostr.band

Author Public Key

npub1tcuq6px6c3l9nwvng2dzzldtvvvlmkuvc9vxy97j8h47zuuw93vq362uw2

Show more details

Last Notes

2024-05-24 09:03:37

- reply

I doubt it, personally. MS will know this will be heavily scrutinised and even the barest of off-device logging will kill it stone dead. I think it’ll be squeaky clean from that angle.
The threat models I see around Recall are about access to the local files: either malicious (malware/hackers), abusive (partner abuse), or compelled (law enforcement.)

2024-05-24 09:03:37

- reply

2024-03-22 18:47:18

I must confess, I am not seeing the reason for quite such a "the sky is falling" reaction to Threads starting to interop with Mastodon. I have friends there, and I would like to read their stuff (and have them read my stuff) without subjecting my eyeballs to the Threads UI, or contributing ad views to the house of Zuck. I'd also like to gently encourage them to migrate to Mastodon in the future, which seems a lot more likely to happen if they can still see all the stuff they care about that's currently locked inside the Threads walled garden.
Inside any Big Tech firm, there will be people arguing for and against open platforms and protocol interoperability. We're not helping the people trying to open things up if we attack the outcome when they make progress.