Feature Requests [OLD]

You could just go to the last page.. Or use SiteJS

I'm well aware of what I COULD do. and this isn't exactly trivial to do in sitejs

reverse the page numbers, I guess anyway your suggestion was a good idea

You could just go to the last page.. Or use SiteJS

I'm well aware of what I COULD do. and this isn't exactly trivial to do in sitejs

reverse the page numbers, I guess anyway your suggestion was a good idea

lol you don't have to call my suggestion good because I got mad. and yeah, I guess I could just reverse the page numbers for a cheap hack whatever, it's called feature requests for a reason. let's see if they pick this one up eh

My original post made it seem like I thought your suggestion was bad I'm just not used to actually having suggestions added, so normally when there's a problem I don't even bother...

Can testquery be updated maybe Please.

What do you want testquery to be able to do? With the new query framework, it doesn't really need to be tested like that anymore, so I don't keep up the tester.

There should be a Module for when you're first in The Userlist you can do /brag and brag about it. Being first in the userlist is fun.

There should be a Module for when you're first in The Userlist you can do /brag and brag about it. Being first in the userlist is fun.

No

There should be a Module for when you're first in The Userlist you can do /brag and brag about it. Being first in the userlist is fun.

No

It was worth a shot.

Could we have better command error messages in chat? They don't have to be super specific, but there should at least be a difference between "that command doesn't exist" and "you used the wrong number/type of arguments"

And I would like to request better zooming on pictures on mobile. I cannot read the text on photos that are displayed. Even if they are only 50 pixels tall

And I would like to request better zooming on pictures on mobile. I cannot read the text on photos that are displayed. Even if they are only 50 pixels tall

Do you want them to expand beyond the post or something? I'd rather leave it up to the browser than to let photos become larger than the page itself. You can tap on a photo on mobile to expand it (Or at least, I can on mine). Also, you can usually long-press on a photo (on mobile) to view an image in a new tab. No need to reinvent the wheel on our side (even though we do that all the time).

Ahh yes. The hold. Forgot about that. I'm used to self scaling. Tapping it makes it go from teeny to tiny :p Disregard my previous post.

Could we have better command error messages in chat? They don't have to be super specific, but there should at least be a difference between "that command doesn't exist" and "you used the wrong number/type of arguments"

Oh sorry, with that whole craziness about regex, I forgot about this. Uhhhh maybe? I was thinking about doing this alongside command completion one day.

Could we have better command error messages in chat? They don't have to be super specific, but there should at least be a difference between "that command doesn't exist" and "you used the wrong number/type of arguments"

Oh sorry, with that whole craziness about regex, I forgot about this. Uhhhh maybe? I was thinking about doing this alongside command completion one day.

You could just make it that modules throw their own error messages up to the server and they get spat back out to you. C# exceptions could do that right? Unless this takes way more setup than I think.

Could we have better command error messages in chat? They don't have to be super specific, but there should at least be a difference between "that command doesn't exist" and "you used the wrong number/type of arguments"

Oh sorry, with that whole craziness about regex, I forgot about this. Uhhhh maybe? I was thinking about doing this alongside command completion one day.

You could just make it that modules throw their own error messages up to the server and they get spat back out to you. C# exceptions could do that right? Unless this takes way more setup than I think.

They already do that though? The only reason parsing errors are generic is because I don't want to have to parse commands within EVERY new module I make, so I preparse the command and arguments out in the server and store them into a nice structure so I can just say "gimme". There's already a little bit of nice error messaging with the whole "Can't find that user", but I haven't extended it to detecting commands or anything.

Oh, well that's actually a totally reasonable way of doing that.

Request: Add more public APIs for people like me that use Node.js. Maybe start with an API for the activity feed that returns the feed in JSON. The major problem with Node.js is that you can't send cookies. That's why more APIs that either don't require a login or allow then (username + (hashed) password) as POST parameters are a request of mine.

A lot of this is done now. You just pass your login information to /query/submit/login, and the result is your session ID. You can then pass around this session ID as a GET parameter to all the query pages instead of your cookie. For instance, you could do something like /query/submit/forum?session=43298fjdks-5435h (or whatever the session is). That session ID lasts for as long as a regular long term cookie (maybe longer), and can purposefully be removed by logging out WITH that session (/query/submit/login?logout=true&session=whatever). This should work on ALL query pages. Also, activity feed is now something you can request: /query/request/history

You've already seen this, but just as a reminder/something for you to take note of, maybe give us Public Chat Logs soon-ish. ^{No pressure}

Spoiler

^{Yes pressure}

Chat Image Hosting when? Anyway, Id like to hear about your process on the whole drawing collab thing you were talking about. I was kinda excited for it.

Is it possible to have the confetti theme AND the blue theme at the same time? That would be nice!