It seems unlikely… The vessel wasn’t up to the challenge of anywhere near that depth, and they intended to go that deep from the get go.
I mean, it could be, but Bluetooth shouldn’t work like that - it’s a digital signal with a bunch of failure modes in the spec. You’d have to code it particularly stupidly to have that kind of problem - it’s a very time-synched protocol, even a sudden disconnect with no disconnect signal is something a coder would have to confront explicitly if they were using off the shelf components
I’m not one to bet against bad code, but the decompression seemed to be pretty much instant and within the planned trip, it just seems like it doesn’t survive oscams razor
Well that’s one layer, but when you decode a url, you’re probably going to get a url, and then it’s going to go to that url
So now you just made them to to a website. What’s there? Whatever you want. Maybe you ask them for Facebook/Google/GitHub or whatever authorization to see their name and email, which a lot of people would do. Then redirect them to a page saying “now I know who you are, delete the photo, <user>”
Or you could send them a payload based on fingerprinting their request, you could give them a fake page to steal their password, etc