[X] My Assistant

Does the jump to top and bottom buttons interfere with the post reply button for anyone else?


This post has been edited by ntsa: Dec 17 2020, 08:32

Does the jump to top and bottom buttons interfere with the post reply button for anyone else?

yes, for me too. I had to disable them to be able to use the forum mod functions. Both versions of the buttons.

I don't use it since scroll wheel click and dragging gets to top or bottom quick enough, but I enabled it just now and its fine for me. You have to scroll all of the way to the bottom so it goes under the post though. Both versions do cover the forum navigation selector though, and the rectangle version covers the "go" button completely

I see you have a custom theme though, not sure if that is causing issues

There's a "up" button under each forum post that takes you to the top by default on the forum if you only really ever use that, though there's no go to bottom button by default unfortunately

This post has been edited by Angaver: Dec 17 2020, 10:13

yes, for me too. I had to disable them to be able to use the forum mod functions. Both versions of the buttons.

Uh how to disable?

Uh how to disable?

When on the galleries, click on Configure Master Script, look for:

Add _____ to the bottom right corner which will _____ scroll the page to the very top or bottom

It's under site wide features, about 13 lines down

When on the galleries, click on Configure Master Script, look for:

Add _____ to the bottom right corner which will _____ scroll the page to the very top or bottom

It's under site wide features, about 13 lines down

Thank you.

I am aware of this issue and the rectangular slide-in buttons can work better after the next update. I have been busy writing another script and testing LANraragi earlier, but now I can hopefully release the next update very soon.

This post has been edited by Mayriad: Dec 17 2020, 10:22

Merry Christmas and Happy New Year!

## Changelog

Design fixes:

- Disabled a fix for the expunge log that is no longer needed after the expunge system revamp.

Subjective fixes:

- Highlighted new message count on the forum in red for when it is positive to make it more noticeable.

- Fixed the spacing above the bottommost links, such as "terms of service", to use a consistent margin across page types.

- Fixed inconsistent tag input field and button when this feature is enabled.

Improved navigation bar:

- Highlighted unread counts in red for when they are positive to make them more noticeable.

- Fixed a bug with the unread MM count where an incorrect count would be displayed when the user is in a battle.

Jump to top/bottom buttons:

- Changed default setting to use slide-in rectangular buttons instead of fade-in circular buttons, because the latter looks nice but is likely to block page elements.

- Redesigned the slide-in rectangular jump buttons slightly to make them even less likely to block page elements.

Automated gallery downloads:

- Handled a rarely triggered download error caused by illegal characters in download filenames. Previously downloads would get stuck in the "downloading" state when this error happens.

- Removed leading spaces from download filenames, which are not accepted by GM.download().

- Limited the status code 200 error check at each step to relevant pages only, because otherwise error messages quoted in gallery comments can incorrectly trigger error handler.

Vigilante thread links:

- Pointed the "Expunge Assistance" link to the new "Expunging, Appealing and Reverting Assistance" thread.

- Fixed the height of the tagging area to prevent its side borders from overflowing when a tag is selected.

GUI control panel:

- Changed the wordings very slightly.

LANraragi metadata plugin:

- Implemented the newly added cooldown plugin parameter to use a 4 second delay. Note that this cooldown is only effective in batch tagging, because auto-plugin does not yet have a multi-process timer for this.

General:

- Updated script information a little.

- Slightly adjusted the gallery token part in all regular expressions.

Cool, thanks and merry Christmas to you too! I know there are more users of your script than post here, but we appreciate it! (IMG:[invalid] style_emoticons/default/biggrin.gif)

By the way, could the script be used to automatically save info.json and maybe comments and such to preserve metadata from galleries when the torrents or archives are downloaded? (Or maybe separately?)Cool, thanks!

By the way, could the script be used to automatically save info.json, possible torrent/archive file names and maybe comments and such to preserve metadata from galleries when the torrents or archives are downloaded?

This post has been edited by flugx: Dec 28 2020, 16:07

By the way, could the script be used to automatically save info.json, possible torrent/archive file names and maybe comments and such to preserve metadata from galleries when the torrents or archives are downloaded?

The syncing of metadata is done by a dedicated LANraragi metadata plugin I wrote for this master script. [github.com] LANraragi is a library manager for galleries and you should try it.

I don't save a file like info.json, because:
- That information will be static and cannot reflect changes. Metadata are updated everyday on EH.
- Because we cannot determine and control what files are actually included in torrents, I cannot link this info.json to torrent downloads by filename or whatever.
- I also cannot place this info.json inside archives and torrents.

The syncing of metadata is done by a dedicated LANraragi metadata plugin I wrote for this master script. [github.com] LANraragi is a library manager for galleries and you should try it.

I already failed at pointing it at paths, it seems to insist on using its own single directory (IMG:[invalid] style_emoticons/default/blink.gif), Doesn't seem evident how this will work with often disconnected drives (data will be present or not) that will have their own paths. Maybe I'll figure something out, but I don't see how I can use it as-is. Thanks for the hint though!

I don't save a file like info.json, because:
- That information will be static and cannot reflect changes. Metadata are updated everyday on EH.

But the other data your script helps me save also is a snapshot at that exact date. No auto-updates on torrents or archive files. The metadata captured at the same time would be fine to have.

- Because we cannot determine and control what files are actually included in torrents, I cannot link this info.json to torrent downloads by filename or whatever.
- I also cannot place this info.json inside archives and torrents.

I think JSON with just the torrent+archive filenames known a the time of the snapshot appended (and any other metadata, wouldn't even mind an option for the comments) would do the job fine...? The archives should already be obvious, and filenames (and maybe torrentv2 checksums) from inside torrents can still be added vie external parsing if needed. Stashing the torrent files near the JSON for this purpose is not very difficult. Most will probably already be useful via text search though.

I already failed at pointing it at paths, it seems to insist on using its own single directory (IMG:[invalid] style_emoticons/default/blink.gif), Doesn't seem evident how this will work with often disconnected drives (data will be present or not) that will have their own paths. Maybe I'll figure something out, but I don't see how I can use it as-is. Thanks for the hint though!

If you are talking about LRR, you can use a symbolic link for the location of your content folder to load a remote library, which is what I have been doing.

But the other data your script helps me save also is a snapshot at that exact date. No auto-updates on torrents or archive files. The metadata captured at the same time would be fine to have.

Archives and torrents are basically fixed files and I have never seen a downloader that auto-updates downloaded files. They cannot be freely updated like gallery metadata and people don't usually call these a snapshot.

I think JSON with just the torrent+archive filenames known a the time of the snapshot appended (and any other metadata, wouldn't even mind an option for the comments) would do the job fine...? The archives should already be obvious, and filenames (and maybe torrentv2 checksums) from inside torrents can still be added vie external parsing if needed. Stashing the torrent files near the JSON for this purpose is not very difficult. Most will probably already be useful via text search though.

I have been using this script for years long before I made it public and I have downloaded tens of thousands of archives and torrents from EH. From my experience, such a feature will be either difficult to make (like the torrent parsing you suggested above) or not useful. If many other users also request this feature, I can add a simple version even though I don't find it useful, so you can wait for it.

Stashing the torrent files near the JSON for this purpose is not very difficult.

This is impossible in the first place because userscripts themselves cannot control download location, unless you forgo automation and ask the user where to save every file, which defeats the purpose.

Thanks for the great script.

Any chance to add a shortcut to exit MPV (back to the gallery page, just like the X button in toolbar) like ESC? This is one of the few things I don't like MPV since trying to click that button is somewhat inconvenient.

This post has been edited by fireattack: Jan 4 2021, 06:52

Thanks for the great script.

Any chance to add a shortcut to exit MPV (back to the gallery page, just like the X button in toolbar) like ESC? This is one of the few things I don't like MPV since trying to click that button is somewhat inconvenient.

This should be easily doable and I will add it at the next update. I am mainly working on another script, and the next update for this MEMS may be a big one, so you likely need to wait for a while.

If you are talking about LRR, you can use a symbolic link for the location of your content folder to load a remote library, which is what I have been doing.

I tried LRR just now an I got a temp ban for excessive page loads trying to get the metadata that way, even with the recommended 4s delay between requests. Is there some offline option that doesn't get me banned that I was supposed to use but missed?

I tried LRR just now an I got a temp ban for excessive page loads trying to get the metadata that way, even with the recommended 4s delay between requests. Is there some offline option that doesn't get me banned that I was supposed to use but missed?

Were you using auto-plugin or batch tagging when you got banned? And how many archives were you trying to tag?

Auto-plugin does not actually use a cooldown delay and Difegue is not planning to change this anytime soon due to technical challenges (see [github.com] [Bug] Auto-plugin not respecting cooldown parameter), so you should not use auto-plugin if you are adding hundreds of archives at once.

If you got banned using batch tagging, it would mean the 4s cooldown is not long enough. You can submit an issue to Difegue or I can do it for you.

Also, there cannot be an "offline option" because LRR can only fetch metadata from EH API online.

On an unrelated note, I have been very busy in real life, and I think I will only get time to work on this script (MEMS) in March.

Were you using auto-plugin or batch tagging when you got banned?

Batch tagging. Good to know I need to avoid the auto-plugin too.

And how many archives were you trying to tag?

I was trying to get tags for all archives eventually. But it was a quick initial test with only 10k files or so. Obviously it didn't work. (IMG:[invalid] style_emoticons/default/sad.gif)

If you got banned using batch tagging, it would mean the 4s cooldown is not long enough. You can submit an issue to Difegue or I can do it for you.

If you can do that - maybe it saves someone else. And perhaps the auto-plugin also should be disabled or have a very visible warning if it will get people auto-banned. I certainly would have walked right into that next since obviously I'd have liked to automatically get tags on import going forward.

The ban error message suggests the site doesn't even want to be scraped with "automated mirroring/harvesting software". Does they really only mean the rate of requests as per some explanation by the site staff somewhere? I was interpreting it as they just don't want LRR and other users to do this at all.

Also, there cannot be an "offline option" because LRR can only fetch metadata from EH API online.

So how did this work for you and other users then? Are the bans a new situation? Are you pulling tags off the other supported sites? (IMG:[invalid] style_emoticons/default/unsure.gif)

On an unrelated note, I have been very busy in real life, and I think I will only get time to work on this script (MEMS) in March.

Sure, thanks for your time!

I was trying to get tags for all archives eventually. But it was a quick initial test with only 10k files or so. Obviously it didn't work. (IMG:[invalid] style_emoticons/default/sad.gif)

Yoh, 10k is a lot.

If you can do that - maybe it saves someone else.

No worries, I have submitted an issue on GitHub.

And perhaps the auto-plugin also should be disabled or have a very visible warning if it will get people auto-banned. I certainly would have walked right into that next since obviously I'd have liked to automatically get tags on import going forward.

I have talked to Difegue about this and you can read the link I provided in my previous post. Difegue said he will add a warning.

The ban error message suggests the site doesn't even want to be scraped with "automated mirroring/harvesting software". Does they really only mean the rate of requests as per some explanation by the site staff somewhere? I was interpreting it as they just don't want LRR and other users to do this at all.

The standard metadata plugin for EH offered by LANraragi does work by harvesting pages from the EH website, so that warning is technically correct and the site does not want to be scrapped that way. A lot of users ignore that and try to rip images from EH, and that causes a lot of trouble for servers and other innocent users. Therefore, if you want to do it, you will need to do it slowly.

So how did this work for you and other users then? Are the bans a new situation? Are you pulling tags off the other supported sites? (IMG:[invalid] style_emoticons/default/unsure.gif)

4s is supposed to be pretty safe in batch tagging and I think it works fine in general. It is rather surprising that you got temporarily banned. Were you doing other stuff on EH when you let LANraragi tag your archives?

Also, do you sometimes get banned on EH without using LANraragi? It is quite possible that you were using a shared IP address and got banned because someone else on the same IP was ripping EH and causing the IP ban.

Are you pulling tags off the other supported sites?

You can try other metadata plugins on EH archives, but I have no idea whether that will work or not, and I do not recommend it.

Is there any plan add a button or some what that can one-click on thumb in gallary to download original image, because sometime I don't want to download whole gallary archive, only some of it, have to click thumb into ppt-slide page and click download original image on bottom.
The process discribed above have 1 page into, 2 mouse clicks to save an original image, which I want to one-click, thank you.

I think this script breaks the Clickable external URLs.

EH Gallery Quick Favourite
v2.2.0
https://forums.e-hentai.org/index.php?act=A...t&id=122954

https://forums.e-hentai.org/index.php?showt...p;#entry4493891
any solution.