Description

I don't know if that is possible via the api or if the pages must be parsed, but i think those are the most visited pages

Expected Behavior

the app should boot aup when cargo tauri build executes

Actual Behavior

i have installed rust

i did this:
i downloaded master
pnpm install
cargo install tauri-cli

but when i start the next command
cargo tauri build

gives the next error

i wanted to try it in my computer

Steps to Reproduce the Problem

download master

pnpm install
cargo install tauri-cli
cargo tauri build

Create a docker image for easier self hosting #2

Expected Behavior

Being able to access the web application upon logging in

Actual Behavior

network error upon logging in the API with an user's API key

I already tested it with google chrome and it works there, but not on other chromium browsers.

The browser used was Brave

Steps to Reproduce the Problem

1. open a chromium-based browser
2. Access web app
3. Browse posts
4. Open settings
5. Reach API access
6. Log in with your account
7. Open Home tab

Description

As far as i can see there is no simple way to star a single post, so adding that before/after the context.emit("set-post-favorite" -code would solve that

Expected Behavior

something like "anthro male fur tail claws clothing" would have many results but "anthro male fur tail claws clothing touching_cheek" would have roughly 3 results.

Actual Behavior

It ignores the last index of tags and only uses the first 6. And in the example of "anthro male fur tail claws clothing touching_cheek" it produces several thousand results rather then just the 3 it should.

Steps to Reproduce the Problem

type "anthro male fur tail claws clothing touching_cheek" in material search bar......
I believe createTagQuery.ts
return allTags.slice(0, 6).join(" ");
is what causes this.

I know the API used to be at a 6 tag limit on the old system but its been updated to 40 so I assume it should be
return allTags.slice(0, 40).join(" ");
or just return allTags if the API calls can work with ones longer then 40.

I don't know if this is intentional or a workaround of something else, but I'm assuming its not desired to have fewer tags then what E6 can support.

Should there be a desktop app?

Advantages

• Fewer e621 API restrictions
  • Post favoriting would no longer need a proxy
  • The bulk downloader could be implemented again

Disadvantages

• Could cause security issues if it is not properly maintained
• Automatic updates will be more complicated than with the web version
• Electron is way too bulky and other solutions (like tauri) are not ready for production yet
• Someone would have to test windows and mac versions

Anything else I missed?

Description

I think having a menu-item to view all favorite images/videos would be useful, since the original site has that too

Description

I am unsure if you could do this using the API key, so I won't focus on that here.

The blacklist is composed of elements, separated by line, which can be copied by the user.
This can easily be converted into the json file used by the importer.
Here is an example blacklist:

low_res
anthro -tail
standing

You can add quotes around every line,

"low_res"
"anthro -tail"
"standing"

Put a comma after every line, (except the last one)

"low_res",
"anthro -tail",
"standing"

Remove all line breaks,

"low_res","anthro -tail","standing"

And insert it into the blacklist section.

"blacklist":{"mode":0,"tags":["low_res","anthro -tail","standing"]}

Modifying the file like this, and importing it, has worked on my end.

Expected Behavior

Tags like order:score and order:favcount continue to place posts in order after the first page.

Actual Behavior

Tags like order:score and order:favcount seem to stop working after loading the second page

Steps to Reproduce the Problem

Search for something like order:score or order:favcount, scroll down and load the next page either manually or automatically

follow artists and notify when there are new submissions (see #2)

Description

If a picture is part of a pool, show those informations below the image or in detail-view. A click on that should show the pool

Expected Behavior

blacklist work properly and block post with blacklisted tag

Actual Behavior

although most blacklist work as intended (e.g. blacklisting 'female' tag would hide all post with that tag), tag(s) like 'the_magnus_archive' does not get hidden

Steps to Reproduce the Problem

1. open home (default settings)
2. scroll down, found post with 'the_magnus_archive' tag
3. click (i) button and find 'the_magnus_archive' tag
4. click the three-dots menu
5. click add to blacklist
   6, refresh page with CTRL-R
6. post still available to be seen

Alternate option: Manually add the tag in the settings

Expected Behavior

I can mark an image to My favorite.

Actual Behavior

Using 142eed1
OS:Windows 11
Webbrowser:Edage

After using API login e621,I cant mark favorite whatever "builded desktop app" or just "npm run preview"in local website and It shows "network error",but nothing show up in console.
Other feature is working well,and I can do it on https://material-e621.vercel.app/#/
Did I miss something?

Steps to Reproduce the Problem

No response

Description

Instead of clicking "load next" load the next part when reaching the bottom of the posts

Description

File: src/worker/api/index.ts -> "https://material-e621-proxy.vercel.app/api/favorites" for example

with that https://hub.docker.com/r/redocly/cors-anywhere could be included in the Docker-Image

Expected Behavior

I expect when I logged in my account I would be able to see hidden images

Actual Behavior

but instead I get network error pop up

Steps to Reproduce the Problem

This happens when you log in you e621 account and APL key

Description

Surprise! There's a new instance of e621, directed firmly at AI generated art. Makes sense, keeps the main site clear of this form of art.

Hopefully adding support is as simple as adding a new item to that drop down.

Thanks!

Description

I just did it to show a red heart when it's a favorite. I guess it can be done via css, but that feels cleaner.

https://github.com/avoonix/material-e621/blob/49b348527fa1f8a55456680b1b979a2b3055b999/src/Post/PostButton.vue

Description

Auto-Push the Docker-Image

Example: https://github.com/tamaskan/material-e621/blob/master/.github/workflows/docker-upload.yml

based on: https://medium.com/platformer-blog/lets-publish-a-docker-image-to-docker-hub-using-a-github-action-f0b17e5cceb3

Description

1. Docker-Container on hub.docker.com
2. Integrate e621-dl (eg. auto download favorites/pool)
3. Gallery with all downloaded Files
4. Apprise-Integration (eg. follow artists and notify when there are new submissions)

Description

I don't know if anyone would need it, but a docker-compose.yml could be just:

https://github.com/tamaskan/material-e621/blob/master/docker-compose.yml

Description

src/Post/PostInfoList.vue

that would show it in the details, but some kind of clickable icon on the post would be better