Humm. Well I've not seen it but...
Do you have auto media preview turned on?
...and if so I suspect it would be helpful if you can establish which post caused it because that really shouldn't happen.
I do (because I prefer it to the squished thumbnails,) but I can’t tell you which post triggered this or how I would know.
Edit: So it looks like it might be this post, as it seemed to pop up again as I was scrolling by, and it popped again when I clicked on the post (but not the link, obviously).
I concur. I also navigated to the site and can see the .mp4 file with that name.
However the video file is 13.5Mb, not 30b. It also has a valid .mp4 extension.
I still can't reproduce the pop-up.
My best theory this point is OP's browser is cropping the URL for some reason, which means the ".mp4" part isn't seen. The browser is then trying to save the 404 response to the request for a file which didn't exist, and had no extension.
Sorry OP, but at this point it looks like something your end.
Out of curiousity, it is an unusual browser, or any scripts/ extensions running which might have corrupted the videos's URL?
My best theory this point is OP's browser is cropping the URL for some reason, which means the ".mp4" part isn't seen. The browser is then trying to save the 404 response to the request for a file which didn't exist, and had no extension.
I looked at the actual web request url it's doing for me.
I don't know why they're getting a download offered in the first place for such a scam looking url, but the display on OP's image is clearly separating the url into its components and only displaying some of them (the domain and file name). The file extension isn't part of the url itself here but rather the parameters which aren't displayed here because there's usually no need to and they would take up way too much screen space on mobile.
I think hiding the parameters is a good idea. While comments suggest this is a real video file, this could have easily been a virus disguised as a video. By hiding the parameters, you're preventing unsuspecting users from putting too much trust into those parameters.
I don't know why your browser treats this as a download, seems to be incredibly insecure.
If I didn't know others already confirmed it to be a video, I'd assume this was a scam website, distributing a virus disguised as a video. The actual url is encrypted so you can't tell what it actually points to, while the file extension is mentioned in the url parameters to give the impression it's a video file when it could really be anything. And it's being downloaded from Russia.
I think it was definitely a good idea to post this. You should probably look for a better browser that doesn't treat every shady url as a download. One misclick and you can get a virus on your phone like this.
As for kbin, I recommend making an issue about this on the codeberg repository. That's the best way to get kbin to actually do something about this.
Browsers usually offer to download files with extensions they don't recognise, basically it's the browser saying "I can't display this, do you want to download it?". In this case the file appears to have no extension as observed by OP.
I think kbin is working fine, the preview did as expected and shared the URL of a video file (but unclear why OP doesn't see this as an mp4 video file).
My guess is OP will get the same popup if in navigates to the page with the video as he did from kbin. This issue is (I think) the video file's URL, not kbin.
Nothing at this point makes me think kbin could or would have included anything it shouldn't have in the preview.
All of that said - Would I be cautious if I saw the pop-up OP shows, yes absolutely. And while what I can see isn't hostile that doesn't 100% mean the website isn't convertly doing something on occasion, or for a subset of users. It is entirely possible to make a website show different people different things.
I agree, I also think kbin isn't doing anything wrong here. But it might still be able to take actions to prevent or mitigate this, so that's why I suggested posting about it to the codeberg repository.
Add comment