Since deletions are being taken into account for the trial report (which albert may or may not investigate why things were deleted) is there any way we can get a function to move favorites to a parent post without reapproving it? When gets stuff gets deleted for being a sample/artifacted or falls off the queue because it was a dupe those favorites should be moved but it can't be automatic since there's other reasons to parent stuff.
Since deletions are being taken into account for the trial report (which albert may or may not investigate why things were deleted) is there any way we can get a function to move favorites to a parent post without reapproving it? When gets stuff gets deleted for being a sample/artifacted or falls off the queue because it was a dupe those favorites should be moved but it can't be automatic since there's other reasons to parent stuff.
Done, it will appear under the Undelete link if the post has any favorites and a parent.
Seems uploading from pixiv is impossible as of some minutes ago.
Not limited to pixiv nor to uploading. The whole site has been crapping itself for the past 20 minutes and you can't make any changes. Wait a little while and come back.
Whoops, wrong thing. Meant that the Pixiv 1200px Manga Sample Fixer is busted so I can't extract the URLs for uploading as well anymore.
You don't need to get the original urls. Even if you try to upload a 1200px manga image Danbooru automatically switches it to the original so it's fine.
That "Pixiv 1200px Manga Sample Fixer" script I wrote was just a quick temporary measure. You could have stopped using it like 9 months ago.
btw, the reason it's busted now is because Pixiv changed their api a couple months ago, that script used the api.
EDIT: Actually it is both. But mostly the inline expansion of the Infinite Scroll program, which I don't think Endless Pixiv Pages has.
Infinite Scroll also relied on Pixiv's api which was changed a couple months ago. The script maintainer would need to update the script, though that could be difficult since I believe Pixiv's new api is unusable in userscripts.
Might be a minor bug, but the notes and comments' post count in user profile has become fixed to 1000000.
it show up as: Note Changes 3015 in 1000000 posts Comment Changes 220 in 1000000 posts
Clicking the 1000000 still work perfectly, though. I checked other user's profile and it also happens to them. Apologies if I'm not being clear enough.
There were changes with post count mechanism and pagination mechanism, see changelog. Also, it broke all "order:" searches starting on page 2 for all users below Gold, including anonymous. This is due to sequential pagination that doesn't work at all for "order:" searches and it should be fixed ASAP, but I can't log in to github now. Someone should open the issue there.
Ways to check: go to safebooru or any danbooru mirror, logout, do order:score search, go to the "next" page; ordering falls back to order:id_desc.
So do we need to pay 20 bux to be able to jump pages ahead now?
I don't get why basic functionality is being put behind a paywall now.
If it was lower I'd consider paying in but really it's making me wonder if even doing it would just encourage further feature removal for non-paying users as really I have no interest in lolicon/shotacon and that seems to be the main pull for going over the paywall.
So do we need to pay 20 bux to be able to jump pages ahead now?
I don't get why basic functionality is being put behind a paywall now.
If it was lower I'd consider paying in but really it's making me wonder if even doing it would just encourage further feature removal for non-paying users as really I have no interest in lolicon/shotacon and that seems to be the main pull for going over the paywall.
"Main pull" is tag limit going up to 6 and substantial timeout increase - 500 ms and 3s 3s to 6s is still a world of difference. I think that paginators are removed because asking postgresql to skip N records (that's how regular pagination works, FYI) is much slower than asking it to get "20 matching records for post IDs below N" - that's how that new "sequential pagination" works. Skipping records still means fetching them, so you would encounter timeouts often when you skipped to latter pages; this shouldn't happen with sequential pagination.
Regarding payments, I've thought about it for a long time - perhaps, some kind of subscription could be introduced in addition to regular payments? i.e. you pay $4 and get gold for a month. Thing is, I don't decide this. If both userbase and albert will be interested, it'll get implemented.
P.S. before you start, don't waste your time complaining about sequential pagination to me, I never liked it either. I have an idea how to merge it with regular pagination so that it's transparent to users, but that requires much discussion. Again, if you're dissatisfied, open a topic here on forums or an issue on github.