I can't really test this either since I happened to publish my games in alphabetical order, but yes, it is the default site behavior unaltered by the extension. Seems to operate on a delay, too, where the sort you select is applied only after you've selected a new one.
I might not have.
I normally just use the dark mode of the browser. An app would be nice if it could improve some of the other stuff like the extension does, but I imagine that it's not that easy to make.
I'm still using the site in its purest form and have not downloaded any app. In any case, when I bothered to click the link to it, I got warnings about potential viruses and shit.
Yeah, the conversion requires a lot of manual find & replace and I'm lazy lol
I have updated the FF extension to the latest version now (and then had to upload a quick revision bc of a problem with the icon). For anyone currently running 0.4.1, it should eventually auto-update, but here's the manual link anyway: CYSFFE 0.4.6r1
Edit: I feel like the auto update isn’t working for whatever reason, so here’s the second revision that fixes the item description saving problem: CYSFFE 0.4.6r2
Edit 2: Yeah, putting "r2" on the end of the version number was confusing it. This is now the latest version: CYSFFE 0.4.7
Yeah, there are just so many buttons that as the posts get more narrow, it all starts to overflow. So now the buttons will try to shrink to accomodate the post title (like in the image), and if all else fails, they'll float over the post text.
Oops something went wrong relating to CYSCE and FFE. I have no idea what could cause this in both Chrome and Firefox as they've been updated. I'm illiterate when it comes to code, so I tried to troubleshoot whether this is a problem with my browsers or my internet by loading up a fresh virtual machine. I installed Firefox, and then added its extension. This resulted in the same issues. Running Windows 10 if that's helpful at all. I'm gonna leave this here in case anyone has the same problems and its not just a me problem.
Ah that's fixed it! Looks good now.
I'm glad you brought up the second point! The typeface actually has an "uppercase" variant of its numerals that I'm going to use from now on because I definitely agree the default style isn't as great for heading-type text.
Also, I'm going to try a different format for the body typeface. My Ubuntu machine has had the same issue of not rendering its bold i but this new format seems to work.
I think it was decided that that would be too big a change in form from the classic CYS experience? If I did make light mode the default, it would also switch for anyone who already has the extension but never bothered changing their theme.
I'm also considering a one-time (or per-version) "welcome message" that mentions profile settings and maybe a changelog, etc. because that would also address the problem of users not realizing there actually are themes and settings to change.
Is this order okay? Or is putting New and Top above Fantasy better? Or something else?
It goes "Random, Search, New, Top, Fantasy…" now.
So yeah, I've been working on a separate set of SG viewer themes and decided to just do an invert brightness option in the meantime. Thing is, the FoUC problem I (thought I) fixed on the main site will still sometimes occur in the viewer. No matter what I've tried, the CSS injection can't always keep up with how quickly the page loads, or something.
Hope you don't mind an occasional quick flicker of white before the inversion takes place.
Changing the bar itself might be too much for a temporary fix, but I might as well add in a total "invert colors" options, too. It's actually less computationally expensive.
The latest version is now available for Firefox. Chrome forthcoming, for a change. Here's the link, but it should update itself automatically. The main changes are:
Just had an idea, could you guys add an option to get a url for a specific reply in forum threads? Would be useful if you want to grab a specific reply that's old and therefore not in someone's post history anymore.
Oh this one is easy. You can do it right now! Just open up the thread that has the reply you are looking for and copy its link.
Now you want to examine the link. e.g. http://chooseyourstory.com/forums/the-lounge/message/24660
But I hear you shouting, but Zake, why? I know how to get a link to a thread, I want a reply's link!
Don't worry, it is simple, for you see that last part of the link? The /24660? That is the thread id... and do you know what that means? It means posts have ids as well! OK, maybe that isn't necessarily the case, but they do on CYS, and all you need to do is append the correct post id to the end using a hashtag and the post id number.
Something like: http://chooseyourstory.com/forums/the-lounge/message/24660#829252.
But how do you figure out the post id? Well, the way I'm doing it is by clicking reply and noting the new url at the top (it ends with 'new-reply?postId=829252'). This is how I got the id to append to the thread.
You'll notice that when you are replying to a post, the thread is gone, there is only your reply box and the reply being replied to. Not sure why I'm mentioning this, I felt like writing a bit and it turns out I'm watching this thread... so there you go.
Anyway, granted, this is all default site behavior, so it might not work for you. However, I doubt the extension is changing urls (as that seems like a very weird thing to do, but I'm not an expert on websites so what do I know).
TL;DR Yeah it would make for a convenient feature. If you really want to do it right now, just click reply to the post you want a jump to, note the url which tells you its ID, then append that ID to the thread url (put a hashtag in front of the numbers, after the thread number). e.g. http://chooseyourstory.com/forums/the-lounge/message/24660#829252>
I know about that, and it's a pretty okay alternative, but for convenience's sake it would be better to have an extra button for getting a link to a post. Still, thanks anyway Zake.
You responded too fast... my post was formatted badly so I had lost paragraphs (or maybe something is wrong with my machine)! Here is the missing part (hopefully):
Never mind, the rest of it seems to be breaking something for me so I'll just leave it here... I had a tl;dr where I said it would be a convenient feature, that is the part that matters.
EDIT - The bottom link in my above post was missing a quotation mark... was missing another one later on as well. Don't click it, it won't work.
That is a good point! You can. For me it cuts off the last part so I can't see the full number, but I can copy the link and get it that way. Either way would be a bit faster.
Anyway it seems you fixed? From my analysis the issue was missing closing quotations for two of the links (the middle and last one). Appreciate the fix!
Sounds like you're describing the anchor button.
I am fucking idiot, I didn't realize that it did more than just anchor the page to that post lol.
Digit might find a use for it once he gets on that submarine.
Haha, I guess I didn't make it very clear? Since nobody seemed to know this. I've seen people post links with the id fragment pretty frequently so I suppose I assumed the button was getting used, even though I know there are other ways to get it.
Using "permalink" felt wrong to me at the time, but maybe I should rename the button and/or change the icon to something more intuitive?
Yeah, this would be a lot better done server side. The extension would have to make extra HTTP requests to comb through the points history, thus taking extra time. For current features only, it would need to further check each storygame to confirm the comment is still featured, and there'd be other things to worry about like the fact that older entries don't list the title, or that the title may have changed.
Agreed that it should be tracked.
That’s a weird assumption considering how vocal I am when I disagree and considering that I had specifically said I would be less active and only actively present when I was at home, lest someone I know discover the kind of company I was keeping. I’m in Vancouver on vacation so I don’t have a lot of downtime — pretty much back to back plans until tonight when I get back to Seattle.
Apologies that the latest FF version ended up really buggy. If all goes well there should be an update for both browsers really soon.
Okay! Ran into a little more trouble than I'd hoped, but the latest versions are now live for both browsers!
CYSFFE 0.6.2.1 (OwO)
Also @mizal or otherwise, can you update the FF link in the OP now that the latest version is actually working?
This is dope.
I told you about my tranny incest porn in confidence you poo poo nugget
Yeah, there are a couple permissions that Chrome will give this warning for, which I think is fair but kind of misleading. The specific permission that triggers this warning is "webNavigation," which I added in 0.6.0. Firefox describes it as "Access browser activity during navigation;" it lets the extension see the URI at the moment a user navigates to a page. I started using it to check when the user navigates to the storygame viewer in order to apply the inverted color themes as quickly as possible, since the old method was slower and more likely to apply the style with a visible delay (flicker).
In practice, it only listens for URLs that begin with "http://chooseyourstory.com/story/viewer/"
Just pushed a fix for the icons and CodeMirror not working in the new advanced page editor.
FF version is live; Chrome ver. is uploaded but still processing.
It's live for both browsers.
Thanks for the excellent response time.
Version 0.7.0 is live! A lot of focus on the storygame viewer this time around. Click the dropdown for the changelog.
The following text is here to illustrate the effects of the new "Text Visibility" option. Check it out with different settings!
Red Orange Yellow Lime Green Cyan Teal Blue Purple Fuchsia White Grey Black
Quickly save and restore multiple named storygame states
View the number of times a link has been clicked, and the history of pages visited
The quicksaves? As it happens, all the necessary data is right there on the page, so I can just grab it and store it in the extension's local storage. To load it, the extension opens the "Save" page, injects the quicksave data into it, and clicks "Continue Without Saving."
Version 0.7.1 is live! This revision fixes a couple issues, but it does also come with a new feature and the framework for some future additions.
The Firefox version of 0.7.1 is actually available on the proper site now and should auto-update for anyone who didn't download it via Discord. Turns out the FTP host name changed.
New update! It's been a while. This one adds a few new things, like the ability to apply a temporary theme to a single storygame viewer window, but it also rolls a few back that aren't needed anymore.
Not the main site, but yeah, in storygames. Click the “options” button and pick a theme, and it’ll last for as long as the window’s open.
Yeah, both Chrome and FF versions should auto update at this point, and if it's not gone through yet there should be an option in-browser to force an update check.
I've gone and pushed a new version, 0.8.1. New feature: the option "Compressed Sidebar". Uncheck it and the sidebar will be fully expanded again when the default site theme is being used.
For Chrome users, you don't need to do anything; this is the only change and it's already live. For Firefox users, I'm also going through the process of having the extension hosted on Mozilla's add-on site instead of hosting it on my own. This means that once it goes live, I imagine anyone using the FF version of the extension will need to install it through that new product page to continue receiving automatic updates.
It looks like it'll be some time still, but I'll post the link when the review process is done.
FF version is live! They want me to add some screenshots still, but it's available to install now. Access it here.
New update is live for FF and Chrome. Not much, just a few fixes, including the new Dark Fantasy category appropriately being swapped out for the old School-Based. The other changes besides that are:
Floating elements (e.g. images when inserted via the RTE) can no longer overflow out of forum posts
Yeah, it means that as long as you have the extension, they won't poke out of their bounds.
It's kind of the fault of HTML, though. Sure the RTE lets you make images "float" to the left or right, but HTML has just always treated floating elements weirdly. By default, they basically act like they have no "height" and until recently the best solution to that was very hacky.