Posted under Bugs & Features
evazion:
I'm not hitting the 403s anymore (I assume you implemented User-Agent checks as you indicated so that things that're explicitly clearly not-bot like "Danbooru User DarknessEternal" or such are OK), but if some of us have tooling that runs from specific IPs, would you be able to permit static IP ranges if we end up hitting the 403s errantly again? Just curious for the future since all my infra has Static IPs (even my home, yay business grade internet!)
DarknessEternal said:
I'm not hitting the 403s anymore (I assume you implemented User-Agent checks as you indicated so that things that're explicitly clearly not-bot like "Danbooru User DarknessEternal" or such are OK), but if some of us have tooling that runs from specific IPs, would you be able to permit static IP ranges if we end up hitting the 403s errantly again? Just curious for the future since all my infra has Static IPs (even my home, yay business grade internet!)
I’m pretty sure evazion won’t start whitelisting specific IPs on request, considering that this whole issue with mass downloaders is already consuming too much of his time. If he whitelists one user, everyone else will request to be whitelisted as well.
If you set your UA and/or referrer correctly, it’s supposed to work, unless it doesn’t because you got blocked intentionally. If it’s working erratically, it’s a bug that needs to be fixed, not worked around with whitelists.
You need to set a custom User Agent if you want to use a download manager. I quick Google search tells me that Free Download Manager doesn’t support setting a User Agent and instead pretends to be a browser, which is forbidden on Danbooru. Therefore, you can’t use Free Download Manager on Danbooru.
Hey @evazion, I'm the creator of the Rule 34 App
I agree with you, and I've followed all the guidelines that you posted here, but hotlinked images are receiving 403 error response
Can you take a look and tell me if anything is wrong?
https://r34.app/posts/danbooru.donmai.us
See forum #263939:
evazion said:
[...] Things like building apps and alternate UIs for Danbooru are allowed, as long as they're not monetized [...]
Your app is blocked because it's monetized. It has popup ads. It has a paid monthly subscription. It has paid links (the link to ThePornDude is paid; he offered me a few thousand dollars once and I declined). You can take some of the money you're making and use it to pay for your own storage and bandwidth costs.
evazion said:
See forum #263939:
Your app is blocked because it's monetized. It has popup ads. It has a paid monthly subscription. It has paid links (the link to ThePornDude is paid; he offered me a few thousand dollars once and I declined). You can take some of the money you're making and use it to pay for your own storage and bandwidth costs.
Thanks for your response
I meant what I said, ads do not run when browsing Danbooru, check the source code: https://github.com/Rule-34/App/blob/488cf19c45ff9746e69d9742bd32bd4d9efa0870/pages/posts/%5Bdomain%5D.vue#L422
Yes, it does have a monthly subscription, but has nothing to do with browsing Danbooru, its additional functionality for advanced users, browsing Danbooru on my web is 100% free without monetization
ThePornDude link was not monetized at all, it's just a backlink, on which I did not receive any money at all
And to be fair, the link is quite separated from the usual flow of using my web
You're completely on your right to block my site, I just wanted to let you know that I do abide by forum #263939
I hope someone smarter than me can figure out a FreshRSS workaround like for ttrss (or can share a userscript). Something I noticed that could possibly help is that images are broken on FreshRSS in browser and in NetNewsWire on macOS, but *not* broken in Reeder (iOS).
Also, as far as the Custom user agent string thing, is what's meant by that that they'll be whitelisted per-site?
6pmnap said:
I hope someone smarter than me can figure out a FreshRSS workaround like for ttrss (or can share a userscript). Something I noticed that could possibly help is that images are broken on FreshRSS in browser and in NetNewsWire on macOS, but *not* broken in Reeder (iOS).
Also, as far as the Custom user agent string thing, is what's meant by that that they'll be whitelisted per-site?
Just in case anybody finds this thread while searching like i did, I'm actively working on an extension for FreshRSS to fix this issue: https://github.com/GwyndolynMarchant/freshRSS-siteExtensions
It has restored functionality in the browser itself, however NetNewsWire is still struggling. I assume this is because NNW is probably sending some kind of garbled UA or stripping the repaired referrer policy
hellgnoll said:
Just in case anybody finds this thread while searching like i did, I'm actively working on an extension for FreshRSS to fix this issue: https://github.com/GwyndolynMarchant/freshRSS-siteExtensions
It has restored functionality in the browser itself, however NetNewsWire is still struggling. I assume this is because NNW is probably sending some kind of garbled UA or stripping the repaired referrer policy
wow, it works for me! thanks so much for this and for going out of your way to post here. you rock.
