12me21/sbs2

new new new sbs frontend. work in progress

sbs2's Issues

Add option to stay logged in for an extended period

The API has a short token expiration, it's something like one week. It would be nice if there were an option to set it for like a whole year, like the builtin frontend. I think you just set some kind of expire field on login, and you just need a checkbox. Here um, it's somewhere on this page: https://qcs.shsbs.xyz/api/run/index.html?t=login the function will be like... oh here, found it:

    if(document.getElementById("login-extended").checked)
    {
        loginParam.expireSeconds = LOGINEXPIRELONG;
        console.debug(`LONG token expiration set to: ${loginParam.expireSeconds} seconds`);
    }

image upload color quantization

sidebar.js:327

                <label class="sidebarUploadingFile item" for=$fileName>quantize:
                <select id=$fileQuantizeColors>
                  <option value="" selected>no</option>
                  <option value="2">2</option>
                  <option value="4">4</option>
                  <option value="8">8</option>
                  <option value="16">16</option>
                  <option value="24">24</option>
                  <option value="32">32</option>
                  <option value="64">64</option>
                  <option value="256">256</option>
                </select></label>

POST ?quantize=<colors>
leave off for no quantization
(maybe also 0 but don't count on it,)

Add permalink to blog pages (only if on production)

If a page is a blog (if values.share=true or if parent.values.share=true and literalType=resource), add a link to the blog. If it's a blog parent (values.share=true), the link is https://qcs.shsbs.xyz/share/(page-hash). If the page is a blog child (parent.values.share=true and literalType=resource), the link is https://qcs.shsbs.xyz/share/(parent-hash)/(page-hash)

Uh this isn't really important, it'd just be nice to have and it's a super easy add if you have like some kind of infobox on the page with additional information.

Add some way to go to the parent page for comments shown in the sidebar

The sidebar master message list at the bottom is cool for seeing what's going on, but without a way to easily see more context, I find myself never actually using it. I'll see an intriguing message and wonder what the rest of it says, or what the context is, but if I want to go find it, I have to hover of the message, memorize the ID, then manually go to the page using the id.

Unless there's already a way to do this? I know you're probably worried about having too many elements, but I think a functional sidebar is more important. What are your thoughts on that?

This isn't finished yet

oh my god what month is it

Show children of pages SOMEWHERE

It's really cool that there's a site tree now, that greatly increases navigation... or at least it would, if the child pages were accessible from the parent. Right now the tree shows only parents, and clicking on the parent brings you to a page that doesn't show the children. For instance, there's a lot more pages in "Off-Topic" than just the few children that show up in the tree, same for Obsolete etc. I don't know how you want to do that, whether it's loading more pages with some + sign in the tree on the search tab, or showing the child and parent pages on the real page when loaded, or something else, but as it is, navigation is still difficult, as we can't really see all the children inside a parent, even though you can navigate to the parent from the tree.

Thank you for adding the tree though

image upload buckets

index.html:139 - needs input for bucket name (searching)
index.html:146 - needs input for bucket name (editing)
index.html:318 - needs input for bucket name (upload)
request.js:213 - needs parameter for bucket
sidebar.js:52 - needs to set bucket on upload

"when you POST, you can add a ?bucket=whatever"
"if you don't include a bucket in the search, you get images without buckets"

There's no way to change the markup language used in the preview until you save

The markup language used by the preview renderer isn't updated when the language is changed in the page details, it's only updated when the page is first loaded. This sucks for when you want to update a page but you don't want to release an unfinished product.

Maybe the markup language, since the renderer is dependent, should be displayed alongside the other renderer settings because then at least it will be easier to be reactive with and also know the available options.

file upload blocking: doesn't unblock on failure

it seems there are cases where file uploads will never return
attempting to upload a webm, for one
in these cases the 'upload file' will never be enabled again

expected behavior: even if the failure is unknown, 'cancel' button should force-enable the button again, since the point is to block unintentional double clicking more than anything.

When token expiration is detected, logout user

Current, when a token is detected to be expired, you just get a broken user tab that you still have to manually log out of. I think it would be a better user experience if either a logout occurred or at least the UI was updated so you can log in again without going to the broken user tab. A reload doesn't fix it, it's just always a "bad token" alert with the broken user tab until you specifically press the logout button.

Display edited date on Page view

[mirrored from QCS}

Cherry:

I feel should there be an edited field?
if there is one and it's being hidden from overflow, I think the edited field should take priority over the created

12:
oh yeah i just haven't learned how the edit activity data works yet

Turns out that the edited date doesn't even appear, which I feel is a lot more important to know than created, especially when confused about whether activity was caused by a user editing their message or sending a message or whether the page was updated.

Show and allow votes on pages

IDK how important that is for the small community we have, just thought I'd mention it.