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

Queuing bypass for new theme membics. #32

Open
theriex opened this Issue Jun 11, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@theriex
Owner

theriex commented Jun 11, 2018

K mentioned it would be good to allow the first few membics for a new theme to bypass the queuing, like what happens when you first create a new account. It does look a bit anemic to create a new theme with just one post in it, so allowing a small queuing bypass could be worthwhile.

But even if the queuing process is modified to allow the first 5 posts in a new theme to go through, it can still be frustrating if you are trying to load up an entire reference reading list. Especially if you want to embed the theme as a page in your website, or provide the standalone theme page to a bunch of people eagerly awaiting it. Queuing up a lot of membics can delay things for quite a while. It's not the same use case as a catch-up day where you post 4-5 membics in a row.

There used to be a batch upload option, but that was disabled a while ago when it became clear the number of potential interactions and options would make batch creation more complicated then just entering the membics via the dialog. That's why when you mail in a membic you still need to ok it.

At the risk of making the dialog even more complex, there should probably be a radio box option for

[x] Queue [ ] Skip Feed (?)

when a membic is going to be queued. If the feeds are skipped, then the membic does not show up in the RSS or the main display. Clicking the help link explains what is going on.

Could be reasonable to use the srcrev -202 flag for this, but probably better to use a new status code in case batch gets resurrected for specific highly defined situations.

@theriex theriex added the enhancement label Jun 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment