Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yande.re import fails with "Unhandled file type: 'application/octet-stream'" #56

Closed
G1org1owo opened this issue Jul 10, 2024 · 4 comments

Comments

@G1org1owo
Copy link
Contributor

I am not sure whether this is on the extension's end, on szurubooru's end or just because yande.re changed something about their images. I noticed when I tried to manually download the image from chrome I got a .htm file but wget could download the image with no problems at all.

@G1org1owo
Copy link
Contributor Author

G1org1owo commented Aug 16, 2024

Moved to rr-/szurubooru#674

@G1org1owo G1org1owo closed this as not planned Won't fix, can't repro, duplicate, stale Aug 16, 2024
@neobooru
Copy link
Owner

neobooru commented Aug 17, 2024

The newest version of SzuruChrome now has a built-in workaround for this if you select "[fallback] Upload as content" in the combobox. This will currently not import tags, as those are never imported with the [fallback] importer. But I'll enable the fallback mechanic in the moebooru uploader, so it works by default (with tags etc).

The difference between "Import as URL" and "Import as content" is that the first sends the URL to szurubooru, and the second downloads the image locally in your browser and then uploads it on szurubooru. So the second (content) way is slower, but usually more compatible.

E: Oh and sorry for the late response.

@G1org1owo
Copy link
Contributor Author

G1org1owo commented Aug 17, 2024

I see, I had tried building the latest version but still got the same error so I ended up looking for a workaround in the server backend, didn't notice the new fallback option lol

On a side note, I'm pretty sure this is specifically a yande.re issue (because of strict referer policies and whatnot) rather than a moebooru one, I don't know if it's worth enabling "Import as content" by default for every moebooru instance.

Edit: just reverted the change on my end and checked on konachan.com, I'm pretty positive it's just yande.re and not moebooru as a whole.

@neobooru
Copy link
Owner

Alright. I was a bit confused because I though I had already fixed the issue, and turns out I did. So in SzuruChrome version v0.12.2 this issue should've been resolved by default. So the default moebooru engine/uploader should work fine for yande,re

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants