So, the backstory:

Ever since I first started working on where milky left off with Ponychan X, there was always the concern of whether or not the script is efficient enough, or if we simply have too much attention on it. Though I was inexperienced with javascript when I started, I was at least capable of finding out what had to be done to make it faster. My first major change to that was when I made the main function select all of the valid reflinks first, then sending that data to other functions so they wouldn't have to be reselected. As I got a deeper understanding of it, the greater and more drastic the changes. You could probably load a thread with 1000 posts in version 1.5 without any problems. But then it all ended in one overarching concern, of whether or not the jquery library was worth using here. Basically, using jQuery is frowned upon if the vast majority of the workload is manipulating html on the page, especially when its organized in massive recursive loops. I mean, sure, when you're using jQuery for simple DOM structures, the performance changes won't be noticeable. However, when you're selecting hundreds of elements in organized loops, then its time to consider finding ways to optimize performance, and pX couldn't fit the bill any worse. But finally upon reading some articles regarding web designers' views on using jQuery properly, including the article here http://blog.korynunn.com/javascript/the-dom-isnt-slow-you-are/ (I swear to god if Ion-Sturm was reincarnated as a web designer, that would be him - the author of that article), I finally decided, damn it, let's just get this over with.

It was a gradual six week long process, which along the way yielded the most bizarre results until all the pieces finally came back together in the end. And here we are, over 6000 lines later, with what is essentially a complete rewrite of the original. Well, now let's put its performance to the test with some side-by-side comparisons.

Last edited at Mon, Apr 14th, 2014 18:33

So here we got the javascript profiler for the current version of chromium-based Opera, which uses Google's V8 javascript engine. No extensions are installed other than Violent monkey and adblock, but I have adblock disabled. Let's load an uncached version of /oat/'s board index. In comparison to pX 1.5, it runs at a healthy 100 ms faster.

Yeah, that's nice and everything, but what's the point? Because either way, the overall browser workload of loading the page (like what, 1.5 to 2 seconds? Or in MLPchan's case, maybe a half a second?) makes that 100ms negligible.

But the whole javascript overhaul matters in the long run. Now let's do a stress test with a number of threads across Ponychan. I used /p/ad from two nights ago for reference here, which at the time, had 485 posts in it.

And shown here is a "flame chart" of not just the javascript runtime, but everything being executed on the page. If that comparison doesn't tell you enough, the profiler is telling me that it took 10.08 seconds for native pX to execute, which greatly differs from the mere 677.5 milliseconds of pX2 runtime.

I'm not going to bother doing further tests here to prove it when you can do just that on the comfort of your own time. But I will tell you it gets exponentially more efficient as the threads get larger. So if you want to open up one of those 3000 post "How are you" threads on /gala/, by all means go right ahead.

Here's a few more from /arch/ where we know the post numbers aren't going to change, and don't have to process client rectangles to see if the browser has hovered over them yet.
http://www.ponychan.net/chan/arch/res/2514767.html
old pX - 12.16s script only, 21s total
new pX - 834ms script only, 8.5s total

http://www.ponychan.net/chan/arch/res/1.html
old pX - 7.71s script, 11.2s total
new pX - 803 ms script, 5.5s total

http://www.ponychan.net/chan/arch/res/2501288.html
old pX - 10.11s script, 16.1s total
new pX - 692.3ms script, 5.9s total

Then outside /arch/, it just gets a little ridiculous.
http://www.ponychan.net/chan/rp/res/40371391.html
old pX - 2.4 minutes script, 2.5 minutes total
new pX - 3.04 seconds script, 21 seconds total

So, here's what you'll find new about 2.0:

• In order to resolve one existing site-end issue and to make potential browsing easier (if or when the script would be made native) I modified a few things on the navbar. The board list, for example, can now stretch or squeeze to whatever your window size may be, without overflowing behind the main dropdowns. The thread refresher is now moved to the top left of the page.

• Speaking of which, the thread updater has been optimized to be more bandwidth-lightweight. And it goes about this by taking three measures -
1) by only performing a HEAD request rather than a GET request to check if the html file was modified since the previous update. Only when the dates fail to match will a GET request run.
2) by utilizing a timer with a cooldown much similar to the one on 4chan X
3) only the +50 link requests are fetched, unless, of course the thread has less than 50 replies. And why should this be a concern of us, you may ask? Because...

• pX2 brings ajax fetching to Ponychan for the very first time. I wrote the algorithm for this ajax fetcher entirely from scratch so it might not be perfect yet, but it's getting better. You'll see improvements over time as I find better solutions to optimize this function.

• In the new theme dropdown, you will find a new option to change fonts, for anyone that isn't really a fan of that default Times New Roman font here, feel free to choose a different font that may or may not suit you better.

>>155310
cont'd

Then in the pX settings dialog, you'll find a few new things under the new "Style" tab.

• Customize spoiler/nsfw image covers
• Customize the text that appears on each backlink and each menu head
• Write your own style. The script runs on document-start so, unless I missed something, there should be no flashing of unstyled content.

>>155311
cont'd

Regarding the mini-menu dropdowns...
• I decided to completely rewrite them from scratch. As a result, they can now adapt to your theme, and some options in the menu body are divided into sub-dropdowns to save space
• There's a few new algoritms that are used to find the direct source of the image. I've noticed that two of the most often used filenames here that don't come from images saved from Ponychan are either from Derpibooru or deviantArt. If that is the case with the post you clicked on, it will give you a link to the source, like seen in the image. I'm not sure how useful this feature will be to you guys, but nonetheless, it's there.
• Links to a new search engine in the catalog that I like to call the Deep Search. It puts the name in the field for you. But what does the deep search do?

>>155312
cont'd

• Catalog deep search
So here's what the catalog deep search looks like. This search engine performs ajax fetching every 1.5 or so seconds, not to dig up the threads, but rather, the thread expanders, to match your search query. So it can match OPs and replies. And don't worry, it's not going to hog up server bandwidth, as the longer you have it running, the longer the time intervals between ajax requests.

I'm gonna go right ahead and demonstrate it by picking on Starshine, and as you can see in the screencap, you can choose when you want the deep search to stop running if you don't feel like waiting the amount of time it takes to crawl the board at its entirety. Now unfortunately, when you search by name, you can't crawl the contents of the OP because they don't appear in the catalog index. But if you don't remember what you found that post in, you can always hit the view button presented in the posts returned in the search results.

However, if all you want is to organize your threads by topic, then maybe you'll like what's been done with the tags found in /art/, /rp/, /ooc/, /fic/, and /dis/.

>>155313
cont'd

So, what is the implied action of clicking a hashtag on any other site? Doesn't it usually redirect you to a list of filtered content based on the tag you clicked on? Is there a single site out there that chooses not to follow this implied behavior?

That's the one aspect that I found peculiar about Ponychan's tagging system. I mean sure, they do a good job at making it clear what the topic is going to be, and it declares the rules captained by the OP, that of which violating them could even result in mod intervention (i.e. invading a closed /rp/ thread), that give the tags a purpose a little beyond arbitrary, but aren't tags meant to be organized?

• What you'll find in tag-enabled boards is a systematic tag tabber, where you can make it display threads based on the tag that you've chosen, and it will remember the tag you've selected. So, if you're only on /fic/ for the reviewer threads, or if you're only on /art/ for the galleries, this option might be right in line with your tastes. Let the paginator fill the void for hidden threads.
• You can also organize threads by sub-tags, like "Canon: Donut Bar", for example.
• In case you want to take further action to sort out threads, the filter system can now filter out threads based on what's in the OP.

...and that's all I got! If you guys are getting any issues or have any questions, leave them here, and I'll get to them whenever possible.

CHECKLIST
☑ Fix Safari Ninjakit/Firefox Scriptish page lock-up
☑ Set a timeout in the thread updater to ensure the user gets the update with their post in it.
☑ Investigate QR bug where the contents don't clear entirely
☑ Write a filter shortcut in the menu
? Patch scroll position error, likely an OS specific bug (waiting for response)
☑ Modify cookies to disable native pX
☑ Fix intrusive footer

Last edited at Sun, Apr 20th, 2014 14:37

If there's any topic more worthy of being seen first by the users of Ponychan, it should be this one.

Stickied for great justice!

>>155316
based !!Fluttershy mod!

>>155317
No problem, love the way it looks by the way! I like that the auto-refresh is part of the navigation bar now.

Oh, seems I do have a bit of a bug...does this sound familiar? Seems as long as I'm logged into my modtools, Display Status is checked on by default, with every new page or any refresh. I guess that one was never really fixed, haha...

>>155319
Oops, forgot about that. Fixed.

>>155324
Beautiful, thank you so much!

A bug I found. It looks like the ajax is taking the data from the wrong ajax request (I hovered over both at about the same time.)

>mfw all this.
I love you forever.

First of all great job this is obviously a ton of time and work.

I have a question though: why use jQuery at all when the base Kusaba library is prototype? Loading two heavy JavaScript libraries vs one is pretty heavy in itself. I always feel that was a mistake of ponyupz as well as ponychanx. My original ponyup used the libraries on site... and without lightbox which takes up 870 some lines, ponyup was only like 576 lines. I can tell you did all the "proper" things for javascript programming and it is a well written piece of code and I very much commend you for it. Ponyup is way behind in features vs this and I have had no intent of writing on that for years so I'm glad people picked up the torch and ran with it. I often feel there's a lot of bloat in most programming though and if you decide to take it further, perhaps getting it into less lines of code (as well as less overall items ran which you could run with a profiler for example). Anyway that's my only criticisms you did a great job.

>>155306

>>155358
I'm still getting crash pages all the time though...goddamnit Tampermonkey update already!

Gonna try switching back to normal Tampermonkey and see if that does anything.

Last edited at Tue, Apr 15th, 2014 10:47

Hm...Spoilered Images are still being hidden despite the fact that I have pX set to always show them.

(No, it's not a real spoiler, that thread is a poorly-made trolling attempt)

i just found a little bug, it was only happening on one thread and i don't know why.

i was on the front page of /oat/ and i had moused over a reply link to a post that was in a thread and as soon as the (loading...) had finished, it whited out my screen
it wouldn't go away the whole page only showed white.
it was only happening on two links from one post, no where else that i've seen

it says i'm using firefox 28.0
the only thingies i have on it are greasemonkey and ponii-chan x

one more thing, i'm not sure if this is a bug but, whenever the autorefresh finishes it sets the refresh time to double the original time you had it at

>>155371
it seems to mainly happen with posts from Thauma

>>155373
>whenever the autorefresh finishes it sets the refresh time to double the original time you had it a

Ehh, probably not a bug. I can imagine it being programmed that way so that it updates a little slower every time it detects no new posts.

>>155357
Oh hey Arcs, and thanks for the feedback. I wasn't initially the one who started working with jQuery at first - that was actually how milky originally wrote it, but despite how easy it is to work with, yeah, there are better ways to keep the global namespace uncrowded. Though he did a tremendous amount of work for the six months that he worked on pX and MLPchan's inline extension simultaneously, and we wouldn't be anywhere near this far without him, so I hold a lot of respect for the guy.

Also, there's actually a good reason why I didn't use any of the site's existing libraries. It was either a choice between making the script embedded on the page's head inside a crowded namespace alongside the two site libraries or to reload the library inside Greasemonkey's empty namespace. So I didn't feel that either solution would be ideal so I just decided to go full vanilla. Besides, other scripts like 4chan X which are now over 12,000 lines long and still run multiple times faster than pX.

>>155345
I think I just found a solution for this, but before, it didn't unbind the event listeners for those links until the page loaded. Now they unbind immediately. But I'll be keeping my eye on it.
>>155361
Thank you for screencapping your settings when you reported this, because it wouldn't have been fixed anywhere near as fast without it. Because it was apparently a typo somewhere in the manual paginator and actually didn't involve the spoilers at all. It's fixed now though.
>>155371
I've never seen this happen with the reply fetcher but I've seen it happen with the paginator. I'm going to place my bet that there were mod shenanigans in that thread, and somewhere in that thread is a document.write function in it. Either way, I think I fixed it. If it's still giving you problems, just let me know.
>>155373
That's actually the cooldown you're seeing. Don't worry, it's just a safety measure to keep the servers from groaning, now that replies can be fetched from outside the page you're on.

>>155406
it doesn't seem to have anything to do with mods doing stuff
but it does seem to happen in threads where someone i have blocked is posting
it doesn't link to their post sometimes and it still does it

So, funny thing. I can't figure out how to cancel a post. Previously, I could press the reply button again while the percentages were showing and the post would cancel, allowing for alterations to be made. I'm not sure if I can even do this on this one.

>>155433
Unless your connection is terrible or your uploading a pretty big picture, the whole notion of cancelling I'm pretty sure is superfluous, as it takes less than a second for the request to be made, and at that point there's nothing the client can do.

>>155433
>So, funny thing. I can't figure out how to cancel a post
My fault, my fault. I forgot to rewrite the canceling code block in the QR.post function. It's fixed now.

Yeah, there seems to be a major bug where if you're on the front page of a board, and you hover over a link to a post by someone you have filtered, the entire page just goes blank white, forcing you to reload the page.

>>155439
Oh, I see. It appears that I fixed it now. Thanks.

so this just happened a little bit ago
it's nothing major, but it was kinda silly

>>155656
Is it persistent? Or did it only happen once?

it's not working for me on Safari. it loads the UI but it makes the entire site unclickable. i can still browse other tabs and such but ponychan is rendered useless.

>>155659
just the one time so far

i'm just guessing ponii-chan derped or something
but if it happens again i'll say something

>>155661
Which version of Safari are you using? I tested it on version 5.1.7 and got it to work, so I assumed it would be backwards compatible from there onward. (I'm posting this from Safari right now actually)

>>155663
It's fine. I think I have an idea on what the issue might be.

Last edited at Wed, Apr 16th, 2014 18:34

>>155664
I'm using the latest version of safari on mavericks 10.9.3

I just tried it on my Mountain Lion machine that runs the latest version of Safari for it (Version 6.1.3 (8537.75.14) and the result is the same.

maybe I didn't set it up right? all i did was copy the script and click on add script and paste it in.

>>155666
No, everything looks like a proper installation from what you're showing. It probably has to do with the fact that the GM based extension is so outdated. I guess, if you can, just try a different browser until I find a working extension.

This is super awesome!

But I think I found a bug?
When I have the catalog page open in another tab, trying to go to the front page of any board just takes me to the catalog for it.

>>155696
Thanks.

It was intentional actually, though I may make the catalog redirect an option in 2.1. The purpose of the redirect is to put emphasis on the fact that the catalog serves an equivalent use as the board index but is simply a different way to view the threads.

Minor bug, easily fixable by scrolling up, but I think I'll finally mention it: even though I have the 'scroll on new post' option disabled, it does just that.
That prevents a +1 in the thread's tab and I don't know what's going on in it until I check manually.
And like I said, fixable by scrolling up, so it only happens when I'm at the bottom of the page.

Another bug

After successfully posting via QR, the QR-box doesn't reset, everything I wrote in it stays. Not sure about pictures or how it affects Auto Mode.

happens randomly

>>155703

>>155704
What version of firefox are you using, by the way? Reason why I'm asking is because I tried replicating the bug on firefox with those same settings and I can't get either one of those bugs. In fact, there's a special casing where if the page is hidden, the notifier in the title appears regardless of where you're scrolled. But the object it uses to get this is so new that the IDE I use doesn't even recognize it.

>>155666
I found that this issue persists on scriptish, so maybe if I can get scriptish support working, it may work on ninjakit.

>>155712
Oh right, it's Firefox 28.0

>>155713
Ah, so it is the newest version. Well in that case, maybe I'll opt out of what I've been using (document.hasFocus()), and replace it with a more cross-browser compatible one. It'll have to wait until tomorrow though unfortunately because I have to leave for work right now.

>>155703
>>155704
this happens to me a lot too, it's pretty annoying

Soooo....am I the only one having a problem with the autorefresh timer? It keeps doubling in time for me...

>>155721
apparently it's supposed to be like that
i don't really like it either

it sometimes doesn't even update after you post

Also the stuff at the bottom of the page "[Return] [Entire Thread] [Last 50 posts] [First 100 posts]" does stay at the bottom of the page and ends up half way in the thread when new post come in. Is that a settings thing or....?

>>155723
From the looks of it it's updating despite the timer...buuuuuut....

Sounds great! One question though, how come we have to install it manually? Shouldn't the Ponychan site creator just update the whole site?

(Forgive me if I have displayed great ignorance in how Pchan site updating works)

>>155727
the admins are kinda dead or something
so i don't know if there's anyone on the staff who actually does coding stuff

>>155306
As soon as I installed the new version, the message fields at the top of the page disappeared. The only way for me to get them back was to enable quick reply, which I don't really care for because it takes up a part of the screen and it feels kind of in the way (though maybe I just need to get used to it, but grrrrr change I don't like it).
Also, it was giving me two "toggle posts form" options, as well as two quick reply boxes.

What do?

>>155731
>Also, it was giving me two "toggle posts form" options, as well as two quick reply boxes.

You still have the site version running. Turn it off.

>>155732
Oh, duh. Thank you for that.

And the new version seems to only have the QR box out when you click a post to reply to it.This works out a little better.

>>155733
is the filter feature working? I can still see names that I have blocked

>>155734
I should also probably mention that the filter is case sensitive as it currently stands, which is something I may change later while I'm fiddling with the filter options I'm going to add in the menu.

>>155727
Cause this is someone not affiliated with the site with his own program laid over Ponychan essentially.

It could be added to the site bould would require someone to look oer the code at least for backdoors and stuff.

And Orng is laaazy.

I love you, Orng <3

>>155736
I'm pretty much entering the name as I see it there. The only other issue I can think of is that they're using a font that I'm not aware of.

>>155739
Finally got it to work, apparently they put a space in front of their name. WOW that's sensitive.

>>155740
Yeah, the way the kusaba X template handles the name elements is a little screwy. Sometimes there will be a space in there, sometimes there will be an empty name element in there, sometimes there won't be. But don't worry, I'm putting a shortcut in the menu for 2.1 which is far easier to work with than typing names in manually.

>>155738
He actually did look it over back when I was at version 1.54 and tried getting a site version running in response to the email I sent him and showed me the script minified and ready to go /chan/lib/javascript/ponychan_x_1.54.js, then it failed to execute and promptly reverted the edit back to the old native build, told me what happened and I sent him back what I believed was a solution to the error ("var j=$.noConflict();" should be "var j=jQuery.noConflict();"). But by the next day I was already at version 1.55 that included the paginated thread hiders, which would have meant for him starting the process all over with the new version. I guess he couldn't keep up.

Hey guys, I found proper solutions to some of the more recent bugs. As a result, I have confirmed support for Scriptish, and Safari doesn't seem to be giving me any problems anymore either. Apparently, the main menu dropdown buttons on the top right were moving around for some odd reason in firefox and safari, and would be doing so literally right when the new dropdowns were implemented, forcing the script in an infinite loop. I'm going to bet that NinjaKit is a heavily modified fork of the Scriptish engine. It's been fixed now, and I'm almost entirely sure that Safari support has returned.

Also, to the person who was seeking support for Seamonkey, I did a little research and some people have said they had luck with this modified version of Greasemonkey 1.15 https://addons.mozilla.org/en-us/seamonkey/addon/greasemonkey/versions/?page=1#version-1.15 so perhaps you might see some positive results here. If you do, please let me know and I'll put a note of it on the OP.

anyone having issues with the "edit" button? Most of the posts I've made here I can click edit and go into the message box, but one other message I've posted just goes into "editing" and doesn't open the box for me to change anything.

>>155753
testing

edited

editing works, apparently, but the post doesn't get updated. I had to F5.

Last edited at Fri, Apr 18th, 2014 11:49

Would it be okay if I suggested an addition thingy?

It would just be maybe kind of neat if the ponychan settings opened up on the same page, in an iframe or something.

Woah, weird.
i figured out what happened: old pX and new pX were on at the same time. went to settings to turn the old version off, so tthat's fixed for me, but just wanted to bring this up. would there be a way to update the pX you can toggle on the site itself?

also have another issue--that'll be next post.

>>155759
ok, so how can i fix these links that are supposed to be at the bottom (as in, they don't get pushed down as the thread updates)

>>155748
Disregard what I said in the second paragraph there. GM support for SeaMonkey may no longer exist, but I do have confirmed support for one of the previous versions of Scriptish for that browser that I just now linked in the OP.

>>155753
Oh, I know what you're talking about. I've got that a couple of times when debugging the edit button. Every once in a while, the server with the edit API kind of goes into a timeout and makes the contents inaccessible...or something along those lines. As far as I could notice, these appear to be backend issues.

>>155757
It might be possible. I'll put that on the checklist and see what my options are about that idea.

>>155759
>would there be a way to update the pX you can toggle on the site itself?
It's a pity that things don't get done around here on a whim like that, because I'm not the one in the decisionmaking position to make site-end changes. That would be something for the admins to handle. Though until then, I can probably get the script to modify your cookies to turn native pX off on it's own.

>>155760
Ah, that thing again, didn't know that bug persisted on firefox. Alright, standby for a fix, and thanks for letting me know about that.

Just started trying it out, but one thing I really need to ask is.. Is there a possible way to make the post refresher as a static number, instead of this progressive thingy? I'd like to have it at a fairly low setting and to keep it there.

I like the refresh-timer like this.
The old one was too random, sometimes I had 2 seconds and other times 40+

I somehow went full retard and posted in the other thread accident, so here's my input:
Really liking it so far, but it does weird things sometimes with copying text from a post I'm replying to when it shouldn't.

Also, my desktop resolution is 1366 x 768, and on the viewing tab at least, I can't see the Apply button. Also, the update sound isn't working

>>155805
Yeah, I noticed that as well, it was pretty irritating.

>>155807
by copying text, I mean like this

>>1294670
Damn, sorry to hear that man. Any idea what's causing it?

>>1294689

I clicked on >>1294689, and it added the text from the post I made that that post was a reply to.

>>155805
But now it just doubles and makes the timer go to insane amounts. The old one for me was just the 5 seconds and refresh, rinse and repeat.

>>155810
It stays at 90 for me, tops
which is okay

>>155811
Which for an active thread that I only tend to post in, is way too much.

having an option to set a refresh timer would be very very nice..

>>155812
this

>>155812
>>155813
/gala/fags pls

Oh well, it's enough for me and not enough for you. I'm curious what OP has to say about it.

>>155816
i rarely even post in gala

now i'm upset and will sage this sticky

Let me do that for you.

>>155816
>/gala/fags pls
>implying Catty is a /gala/fag.
Haha oh wow, this is a joke right?

Last edited at Sat, Apr 19th, 2014 22:24

>>155838
>implying Catty is a /gala/fag.
well i used to be a /gala/fag...

then i kept forgetting to go there
and now everyone in my cereal is dead...slain by a demon called the butcher

>>155838
>this is a joke right?
Yes

>>155721
>>155803
>>155810
>>155723
Ah, and here it comes. You guys deserve an explanation for this change, and there's no way to do this without being blunt, so this is it.

So in pX2 I introduced a feature that is very, very common on imageboards that gets a lot of use known as ajax fetching, where basically, when you hover over a link to a post that isn't found on the page you're on, the browser behind the scenes calls up the html document of the appropriate thread, then searches its contents and pairs it with the link you hovered over, and after it's done with that, it pairs any other links that need paired with a post that are found in the same fetched thread. That's how it was implemented here, that's how it was implemented on Efchan, that's how it was implemented on MLPchan, hell even 4chan has it the same way. Generally, both this feature and the thread updater are the most server strenuous features found on a browser end script that you can find on an imageboard, yet also amongst the most useful.

I guess what it all blows down to is the fact that all these new features have been introduced on an imageboard that has never had them before, and now we have to acknowledge the fact that server cpu usage and bandwidth are never unlimited. You can't get the best of both worlds; you can only make compromises. Though kusaba X's inefficiency may be partly responsible for the current issues, this isn't a concern that's exclusive to Ponychan. On 4chan, they have an inline extension now with most of those features inspired by third party extensions, but in order to autoupdate, you still have to check the box at the bottom of the page. On efchan, they have a native ajax fetcher and an autoupdater, but the updater has a fixed timer. On MLPchan, they have all of the above without overloading their server, but in return, the browsers do the dirty work of generating image thumbnails, which don't always come out so perfect. It's not really a matter of throwing hardware at the solution so much as it is to find the best solution to get the most out of what you already got. And frankly, I really don't want to be held accountable (or at least feel like I am) for slowing down Ponychan's servers and ruining the fun for everyone else, just because people expect an immediate response out of a thread that has gone without a single post for over 2 minutes and 35 seconds (because to hit 90, you idle for 5 + 10 + 20 + 40 + 80 seconds) because that really doesn't seem fair.

However, what I can do, now that I see complaints saying that the cooldown is running a little too fast, and noticing that the cooldown approaches that 90 second ceiling at a degree quicker than the one on 4chan X where I got the idea, is that I can extend the duration of the cooldown period with a shallower algorithm. Maybe a pattern like, 5, 10, 20, 30, 45, 60, 90? I think that seems reasonable.

>>155807
Yeah, my bad, I fixed the settings box for you quickly, and I found out that some browsers aren't playing the notification sound because some of them are looking for mp3 files and others are looking for ogg's, which I'll take care of tomorrow.

>>155816
>other boards dead/shitpost

>>155845
Wait, you mean to tell me that things don't get fixed by throwing better hardware to badly optimized things? Lies!

And yeah, I know they've implemented such systems on pretty much all the other image boards. Real problem just was it capping a bit too fast, and sometimes not resetting when new posts appear and just keep at the 90's timer.
And yes, that kind of a pattern would be preferred, if you'd be willing to make it so.

Oh, also I keep getting this message after clearing cookies etc. and it pops up every time I post now:
WARNING: localstorage item 'settings.10' doesn't seem to be valid JSON.

>>155848
Woop, that was on my end!

>>155759
>>155760
The cookie blocker that sets native pX to automatically off is added now. And the links should be fixed as well.

>>155807
Oh yeah, the notification sound should be working now in 2.12. Not sure if I understand the issue with the highlighter though. Maybe it's a bug exclusively on firefox? I wonder if anyone else is having this problem because I haven't found it yet.

>>155813
Just to be clear, this feature has never been removed; only when new posts are added does the cooldown reset to your set value.

>>155847
The cooldown's been revised now, so now the sequence goes 5, 10, 15, 25, 35, 45, 60, 75, 90.

Is there any way to filter by specific word in a name? Kind of like a wild card? Like, filtering anyone with that certain word anywhere in their name.

There's just an annoying spammer that keeps changing his name and tripcode, but always has a specific word in his name.

>>155848
>>155849
I'm getting the same message, mind if I ask how you fixed that? :O

If you're on the board page, hover over a post number, when it says "loading" move your mouse.
Wait a bit, hover again
The "loading" bit doesn't disappear, but hey, you can look at the post now!

Hello there, thread.
I don't normally visit /meta/, but I just came by to say how much I like this new PonychanX so far! I can't really tell the difference it made with loading times, but it looks darn sleek and modern!
My only slight complaint, if that can count as one at all, is that the top bar with the board names change shape after about half a second of page loading, which kind of disoriented me a bit at first. Not really a big deal, but honestly I couldn't find anything else to bring up!

Whoever made it, keep up the good work, and let me know if you run some sort of a donation drive for your efforts!

I had some severe problems with the new integrated version some minutes ago on /oat/, apparently since my preferred Firefox pX setup only has one sole function (the filters) activated, but after some testing on /test/ and with default pX settings on IE (Thank heavens for IE 11 for testing purposes), I believe I have found a huge bug and one general problem.

Bug: If quick reply isn't activated, I can't post, because the regular posting mode doesn't appear. To get the regular posting mode to appear, I have to turn on quick reply and then click Toggle Post Form every time I want it. It should be perfectly feasible to use pX2 without having Quick Reply turned on.

Problem: The buttons for hiding, resetting hidden threads, and the post Reply button just sends me to the top of the page as if a browser function is too old (Java? Coding errors?).

uhm, is it me or the typing box all gone?
i can´t post!

>>155872
my bads, me being retard!
it was the quick reply box that had vanishes. so i had to open it in the menu!

Dear Ponychan X people.

Please fix the message box. I don't like quick reply, but I like auto-update.

Regards, EMF.

>>155871
I have this problem too. I hate quick reply and if I'm forced to use it, I will not be happy.
I'm using the latest version of chrome, by the way.

>not liking QR
But why

I just noticed this, putting it here since I don't know how I am supposed to give feedback.

The quick post box only refreshes/empties if you are making a post with an image. With anything else, like with embed only or only text, everything just stays there even when your post goes through.

The new pX is amazing, and I only have one minor issue with it. Before the update, I could press Tab twice after typing my post to select Reply, then hit enter, but Tab now seemingly prioritizes the top bar. Or maybe it's been selecting Auto mode all this time and I just need to hit Tab three times instead.

>>155878
>Or maybe it's been selecting Auto mode all this time and I just need to hit Tab three times instead.
It seems that this is the case after all.

>>155876
Because it's different. I know that sounds dumb but that's how I feel. But more importantly, if there's an option to not use quick reply, it should actually work instead of stopping us from replying altogether.

i do not like quick reply. please fix so i can use regular reply mode again

A few announcements here
• Yes, Orange just updated the native version of Ponychan X to 2.12 this morning.
• For anyone here that came in response to the site's updates presented with any bugs (the leading one being the disappearing post form when you turn off the QR) I can make those fixes on the extension pronto. In fact, I made those changes just now in 2.13. However, I'm not the one with FTP access to the Ponychan's servers and cannot make those changes directly to the site. If you want to keep the native version, I ask of you to please remain patient for one of the admins to install the update and just use the QR until this is fixed. I apologize if this is an inconvenience.

Oh yeah, in 2.13 I also changed the filter formula, so when you're filtering a name or subject, you only need a piece of the name to have it filtered now.

I'd rather have PonychanX 1 back. The Timer sucks, the tag system at the top is cumbersome.

Just dropping by to say I completely LOVE the new pX. A++ to those working on it and to Orange for making it native. Love love love love.

I'm not 100% sure this is related to ponychan x 2 but it started just recently, maybe a half hour to 2 hours ago.
Suddenly I can't highlight anything on the page on ponychan anymore. The cursor doesn't change to the capital i shape or pointing finger when I hover over things. I can still click links, but when I hover over thumbnails or post numbers, nothing happens. I can't even drag my scroll bar, though I can use my mousewheel or click on an empty part of the scroll area to go a page at a time. I'm using chrome.

Where can I download the version that was before this one?
I hate it and don't want to update. It's unusable to me, the auto-reply having many -unnecesary fields taking up my space; the auto-reply reducing the pace of RP's greatly, and the tag system hindering my ability to browse RP, without increasing efficiency in any way for me.

The options UI is also much more difficult to use, which is a shame because I shouldn't need to be a technical genius to turn off features I don't want.

Hey guys, the new pX breaks the Hide function. Unless I disable it, it just bumps me to the top of the page without hiding the thread.

How do I change the autoupdate frequency? With the last one, I just clicked on the number and typed in a new one, but with this one it doesn't persist and jumps right back to whatever afterward.

Might as well throw this out here...

I have two problems with using this.

1) In order to use the old Post form, I have to enable Quick reply, which is kinda dumb. Please in a future update allow people to choose the quick reply box or the old post form through the settings menu, because when I disable Quick reply, I can't use the old post form at all.

2) Whenever it refreshes the thread, the timer to refresh it again increases for reasons unknown. No idea why, but hopefully this will be fixed as well.

I am using a 2nd gen Jailbroken iPod touch, btw, and I somehow cannot download the GM thing provided for reasons unknown for safari.

Thanks.

Ok so look, I'm not an asshole.
My timer was always set at 45 seconds, enough time to not strain the server, without being a child poking their mother every 5 seconds. (1-30 seconds). I don't like being forced to a 90 second time simply because I'm polite. I'll set it to 1 to milk the formula as much as possible if I really am going to be forced to wait so long just because your worried about what a few inconsiderate twats might do. I'd rather you set a higher minimum time than punished those of us whom didn't have it low in the first place, in some type of a balancing act.

>>155898
See: >>155886 and >>155845

>>155897
Oh, okay I just read up the thread >>155845
This fucking blows.

I would prefer a static update time to Ajax fetching.

>>155901
Thanks guys I love loading Tags on the top of the/rp/ board..That was totally a needed feature...Definitely doesn't look cumbersome or quickly thrown together....Oh my refresh timer keeps being set to 90...I always wanted that.

>[Heavy sarcasm intensifies]

> the tags work for fic sort of.

>I don't think 30 seconds would stress the site out too much.

I don't like using the Quick Reply,Namely because I am a horrible human being, but unless I have 'Enable quick reply' checked, there isn't a post form.

>Make PonychanX 2.X sitewide.
>Discover all bugs.
>Implement fixed version.

Good plan in theory.

Horrible plan considering who is now stop-gapping the fixes going through, even if the stars align and all these issues are actually fixed before the week is out.

Anon, if you have a direct line to orange that he's actually answering, tell him to revert the changes back to version 1 until you've handled all the bugs.

>>155914
^This man gets it.

I'd like to say that whenever I set the refresh timer to 30s, it goes back to 60s, then 90s.

>>155916
That's by design: >>155845

>>155918
>>155845
Whoever thought that was a good design needs to have there ass kicked I tell ya what.

>>155914
I already got all the issues fixed and sent an email to orange to make an emergency update only six hours ago.

Enclosed in this last update was to the fixes for
>>155870
>>155871
>>155872
>>155873
>>155874
>>155875
>>155877
>>155885
And I can very quickly fix the thread hider which was only less than an hour ago pointed out to me.

And you can already opt out of the tag tabber in pX settings > view > uncheck "use organized tagging"

>>155920
In my defense, it uses the exact same sequence as the one on 4chanX and is far from being a new concept.

Last edited at Mon, Apr 21st, 2014 21:19

>>155921
Thanks for the good work.

>>155921
Do you even try hammers and WD-40 son?

I really don't like it.

>>155921
Get on skype faggot.

>>155918
>>155920
I agree with Hank. This is pretty fucking retarded, I'm sorry, but there's no better way of saying it.

Alright, before I go to bed, I'll give you guys one more announcement -
Inkwell just implemented 1.13 for me. In that update had fixes for all the bugs mentioned here except for the one about the thread hider, which I'll deal with probably Wednesday. I apologize for the issues you guys had today and hopefully the vast majority of them will be addressed and patched by the end of this week.

I'm sorry if this update went off on the wrong foot for some of you, but I will have this all sorted out. I promise.

Nightnight.

>>155934
I don't like the autoupdater change, but other than that I'm pretty happy with the new pX overall.

Sleep well, pX anon.

Um.

Thanks for fixing the message box at the top of the thread, but... is there any way you could add an option to have a consistent auto-update interval? For instance, I like my auto-update interval to be 15 seconds and stay at 15 seconds, but in version 2 it just goes 15, 30, 45, 60. And I don't want that. What if there's a thread that hasn't updated for 15 minutes and someone posts and I only know about it 15 minutes and 15 seconds after the fact?

>>155936
Waaaait a minute, that's by design?

Aw, fuck this noise, man. Imma try to see if I can't find version 1 floating around.

>>155886
>>155934
It's good to hear that most problems are pretty easy to fix. You're doing really great work, X Anon. The native version was still 2.12 when I checked ~five minutes ago, but I'll probably check again in a few hours now that Inkwell has picked up on it.

Edit: Speaking of which, it turned into 2.13 right after I had posted this. This is a good morning for me so far.

>>155896
Seconded, though I had probably mentioned it already.

Last edited at Tue, Apr 22nd, 2014 00:49

The board index on the top no longer follows the page. Is that intentional?

>>155936
>>155937

Damn, is that a thing that happens? That's pretty dumb.

Also, please see my other thread:

>>155882

It was suggested that I talk about it here.

>>155952
Was the post form blank too when the index bar didn't follow along? I had that happen to me too three times this morning, seemingly at random, the first was after I had posted a post on /oat/, and another when I simply opened /oat/ in my browser. A reload fixed it both times.

Edit: Plus a third time after I had posted this post. I need to test this closer...

Speaking of which, it's also like that when I go to specific pages in long threads (like if I go to page 2 of a 250-post thread), which in this case also happened in pX1. But at least the pictures are loading this time around, and even that is a huge improvement.

Edit 2: The testing took some time because I couldn't get pX2.13 to work on /test/, and so I cannot confirm that the following is a consistent bug or not, but basically both the post form is blank and the index bar doesn't follow along on the first page load after posting a post (or after similar actions, such as changing pX settings).

Last edited at Tue, Apr 22nd, 2014 03:21

How the heck do I change settings from a phone? The settings page really isn't very mobile friendly at all...

>>155888
>>155892
>>155937
Here >>150469


Still loving it OP

I dont see anyone else having these issues, but they didn't start until the update.

While pX is turned on:
-Load thread after posting doesnt work, instead just takes me back to board page
-My name field randomly get cleared/comes back. I'll make a post with my name, but then when I go back into the thread it will be blank. But weird is that it was randomly come back if I go to a different thread sometimes?
-pX itself doesn't work in some threads for some reason. I'll open one thread and nothing is backlinked and no auto update. Open a different thread and everything is fine

I really appreciate your work and all, but how do I change my auto-update interval? I'm not talking about it being inconsistent, I can't find where to change it at all.

>>155962
Top left corner, click the number

>>155963
Ah, thanks., been looking in all the wrong places Fuck, I'm retarded.

>>155306
>SeaMonkey
LOL Really?

I like it, but why are Sine and Koto the same?

Also I agree with the QR box. Why? This is weird. STOP IT..

>>155977
That was fixed in the newest version

>>155955
Works on my end
The old PchanX required a weird like ritual to get to work (as the settings page hardly ever showed up, only home)




Been using since the beta and really appreciate the work you've done! It is nice that this QR box actually works on mobile unlike the old one, however it doesn't allow you to post images (least the last time I tried). Least your latest update allows the regular box again

>>155979
where the 3 are at the top? What do?

>>155986
>where the 3 are at the top?

>>155990
the QR reply box.

>>155991
I really don't understand what you're trying to say here.

what about the QR?

>>155992
this

the new QR box

>>155993
Yes, I'm using it too..
What's the problem?

>>155994
i can get use to it, but it feels weird

Welp, now that the bugs are fixed, I'm completely satisfied by this new version.

Ok maybe not all the bugs. The navbar seems to stop scrolling with me randomly when I go to a page, and refreshing usually fixes it.
Also what does the "persistant subject fields" option do?

>>156000
Here's an example.

Filter + desktop notifications = still pops up on posts that should be ignored

Everytime I post, my QR box doesnt clear like it use to.
My timer doesn't stay the same at 5 seconds, it jumps to 10 then 15 then 20 and keeps going from there when I tell it not too..

>>156006
The second one is a feature, a cooldown. >>155845

aight out of here ill be in hay

>>156001
Figured it out, apparently there were two objects called Ponychan both in the pchan-x file and the kusaba.js file that were conflicting with each other, and were throwing errors when cookies were fetched, setting the navbar to unpinned. Just sent an email with the fix to inkwell right now.

Also the fix had a change to the cooldown formula, so depending on how high you have the timer set, the shorter the sequence. Then any time set above 30 seconds will have no cooldown at all.

Edit: according to what I found in the wayback machine, this is exactly how Mithent fixed the hider bug when ponychan x was first made native, so you'll probably see the thread hiders working again as well.

Last edited at Tue, Apr 22nd, 2014 19:07

>>156025
Thanks.

>>156025
Wait, so...

If you set a 5 seconds, it goes up to 90, if you set at 20 seconds, it goes up to something else, and if you set it at 30, it just stays at 30? Is that what the new thing is?

>>156029
Here's how the new cooldown will work when it's implemented, as how I sent the script to Inkwell:

At 5: 5, 10, 15, 20, 30, 40, 50, 60, 60, 60...
At 15: 15, 20, 25, 30, 40, 50, 50...
At 25: 25, 30, 35, 40, 40...
At 30: 30, 30, 30...
And anything above or equal 30 won't have an increment.

There's not going to be a 90 as a ceiling anymore, mainly because while the thread is only semi-active, it's still likely on the first page of the board.

Last edited at Tue, Apr 22nd, 2014 20:53

>>156030
Have we confirmed that letting us set our own timers will actually murder the server?

This new cooldown thing is definitely an improvement over the old one, but I would still much prefer just being able to set my own static time.

>>156031
>Have we confirmed that letting us set our own timers will actually murder the server?

I was always told that it was no problem for the server at all.

>>155306
Y U do dis? If it ain't broken, don't fix it! Hasn't anybody learned anything from YouTube's or Facebook's constant unnecessary changes?

>>156038
It's entirely optional?

>>156039
Do we have a download link for pX 1? I think the problem here is that people have been forced out of pX 1 for pX 2, and don't have an option to go back. They can disable pX entirely, but that's a shitty non-option.

>>156040
Here's the source for 1.25: https://dl.dropboxusercontent.com/u/20817027/ponychanx.txt

Anyway. I haven't used any addons for a long time. But I decided to try it out yesterday. I'm loving it. There are a few bugs here and there. But they're all related to the theme I use I think. Other than that I think it's nice. Especially love the message sound thingy.

1) Increasing refresh timers is hella stupid pls have an option to disable ;~;
2) Half the time I open a new thread the title bar gets stuck at the top of the page I need a rescue to team to retrieve it

>>156039
I didn't even download it, and I have it now!

>>156025
>Figured it out, apparently there were two objects called Ponychan both in the pchan-x file and the kusaba.js file that were conflicting with each other, and were throwing errors when cookies were fetched, setting the navbar to unpinned. Just sent an email with the fix to inkwell right now.
Let's hope that he can implement it as fast as he did with 2.13. It doesn't appear to me to have been implemented yet when I write this sentence.

>>156039
Everyone who used the integrated pX1 (I can't remember the version number, but was it 1.2x-ish?) was upgraded automatically to pX2 (2.12 at first, then 2.13 the following day) within a matter of minutes and with little known warning.

>>156038
But it was broken. This version is better in every way.
I fail to see what everyone's problem is and no one* explains it - just 'it's bad and you're bad for doing it'

*alright, almost... one reason was "it's new"


>"If it ain't broken, don't fix it!"
>"unnecessary changes"
>posts Ticket

Last edited at Wed, Apr 23rd, 2014 05:28

>>156049
Related: https://medium.com/design-startups/461772fbcac7

>>155867
Sorry for the late reply Ammie. I went to my browser history, and cleared specific site data from ponychan!

>>156049
There are significant functional changes with this version. I'm sure some of the backlash is AHHH NEW STUFF, but there have been repeated specific complaints about the way things are implemented (esp. the increasing countdown timer for the thread timer) that have nothing to do with it being new. You can easily see that specific, functional complaint repeated over and over if you read the thread.

So don't be a dick bruh.

>>156057
>increasing countdown timer
Yes, that's suddenly important...
It's sorta-patched for a lower countdown already, still no one satisfied until it's two seconds MAX.
Meh, this site is no instant-messenger, if 4chan can live with a 30 second refresh then ponychan can just as well

>don't be a dick
Don't mean to, but I guess I get pissy when good work gets stomped on for no reason

>>156058
Even if you think it isn't an important complaint, it is a functional complaint that is not about the thing being new.

>>156059
...Sure
I'll continue to be happy about the damn thing finally working as intended and keep it at 90 seconds

>>156061
So your original hostile post was wrong. That's my point. And you're kinda being a douche. So stop it.

ech, nevermind

Last edited at Wed, Apr 23rd, 2014 10:39

>>156049
>I fail to see what everyone's problem is
Well I am still having >>155959 these issues on my phone

The new extension keeps freezing my browser. Like, it'll completely freeze a tab while trying to update a thread, and I can't scroll or do anything. Sometimes it un-freezes after it updates and sometimes it doesn't. I have to close the tab and entirely reload the thread.

I'm gonna have to disable pX if this keeps up.

No desktop notification appears if two different posts refer to one of your posts.

I'd suggest something along the lines of
[image of the first post, if there's one, if not, keep looking] X new replies from A, B, C, D.

Last edited at Wed, Apr 23rd, 2014 14:09

>>156043

these are the suggestions that will be ignored

>>156071
>>156070
I'll be getting back to addressing these posts later, but right now my biggest concern is actually getting the native version running properly. Don't worry, I'm not ignoring these suggestions.

>>156072

oh I thought this was an official pchan thing

that's why i assumed they'd go unseen

>>156074
pX anon is on top of his shit, yo. It's actually getting his bug fixes implemented on the site that'd the problem.

>>156074
It was entirely unofficial until Orange responded to my request to make the working build native from a few months ago.

>>156041
Am dumb. Wat do with source? Source cannot be dragged into Chrome. Want install thing.

>>156082
I checked OP and installed TamperMonkey but it's still not installing. Halp.

And now it's installed but it's not running.

Pls halp

>>156083
>>156084
Are you getting the tampermonkey on the toolbar with the "1" in it? If not, it may be installed but not on.

>>156085
It looks like it's on. It says "enabled" when I click on the icon.

>>156086
Oh, wait... grandil removed the metadata in the header by accident. That's why. Ok, one moment, I got a pastebin of the old version somewhere...

>>156085
>>156086
It's saying "Unable to parse this!" if I try to import it from Tampermonkey. It refuses to save if I try to copy/paste and save in the create new script area of Tampermonkey, and it'll install if i rename it "px1.user.js" and drag it into the regular chrome extensions field, but then it doesn't do anything.

>>156088
Open up the tab with the script in it and copy-paste the contents of this pastebin in it http://pastebin.com/PdRbfrXa and it should be working

>>156089
That did it! Yaaaay! Thank you anon!

>>156090
Sure, no problem

once in a while i drop screen shots from my wii u.
I can't any more. What do?
all it says is "Drop file here"

>>156098
It may be possible that the Wii U doesn't support multiple files maybe? Not sure what could be the problem about that yet, but until then, you can still use the old post form for uploading images, right?

>>156101
you mean here? here. On the computer
When you click on the Choose Files it will pull up the TV and the Wii U Pad. When this happens, you click the image you want. It use to pull right up in the box. now it doesn't.

It just says "Drop file here" on the wii u

I've gotta say....the new ponychan X, fucking wow guys. That is like a really good job outta you, whoever made it.

>>156087
I missed all of this. But I think mine is just a copy/paste of the one that was used on Ponychan. Didn't consider that it needed metadata.

But you sorted it out :)

Oh and once more.. Liking it more and more, it takes a little getting used to but it's growing on me.

>>156025
Umm... Is it fix implemented yet? because I'm still getting the problem.

Okay, so something has gone very wrong. The quick reply box was following my cursor when I tried to move it. As in once I moved it to where I wanted it, it wouldn't stay and was stuck to my cursor. And now after clicking the x it's just gone. The settings say it's enabled, but nothing is there... so yeah.

>>156117
OKay hang on, I got the box back, but it still gets sticky if I try to move it.

>>156118
Well that's a new one on me. What browser are you using.
>>156110
Possibly soon. Inkwell appears to be online at the moment.

Last edited at Thu, Apr 24th, 2014 21:42

>>156119
Chrome.

>>156120
Strange. I use chrome a lot and never had that happen to me. Can you show me what comes up on the console as it happens? (F12 > console) Sounds like an error is being thrown and it can't remove the event listener.

>>156121
Tampermonkey started VM543:44
event.returnValue is deprecated. Please use the standard event.preventDefault() instead.

That's the only thing popping up. Wait now "Uncaught ReferenceError: Ponychan is not defined " Did too.

hey Dev.
something that is bugging me.
I'm getting use to the new QR box, but why does the text remain?

also using opera.

>>156123
most of the time.

1 other. Why does my time double at the top when ever the thread isn't getting any love?
I set it to 0 and 0 is 0 so 0x2?!

but if I close the thread, it resets. What do?

Also this is a 2nd test to see if the text stays in the box.

>>156124
I have a solution for this one. I'm just waiting for one of the admins to respond. Though until then, I found out you can work around this bug by going to pX settings > Post > uncheck "Hide quick reply after posting" until the update is made.

>>156124
It's this bandwidth safety net I call a cooldown, where the timer increases as it becomes less likely that a new post will appear in the thread. Though you'll end up seeing the increment ceiling decrease to 60 rather than 90 when the update goes through.

>>156126
i think I got it for now, but i hope he fixes it.
I'd love to meet inkwell

>>156127
It appears that !!Woona made the update overnight. I'm glad to see everything is going as planned now.

And now that these changes are coming into play, I think it's time to redefine the purpose of this bug report thread. The external builds at the time of this thread's creation were the only builds out there. And they came with the convenience of having a direct line with the development, which is why I'm not planning on scrapping the external builds. As it currently stands, the external version will be the nightly build of Ponychan X and the built-in version will be the neutral build. I think that seems reasonable, right?

>>156117
That happened to me before; I fixed it by reinstalling Tampermonkey and reinstalling the script.

But now the site's built-in pX is updated to version 2.13, so there's no reason to use Tampermonkey anymore!

Last edited at Fri, Apr 25th, 2014 11:50

So I'm still having problems with this...

When I type out a post and the thread updates with new post what I'm typing glitches out a bit.

Also have problems mousing over links to post that are out of thread or past the +50 mark and it causes my browser to die....like...some times I have to restart it.

Not sure if anyone else has that problem of if theirs a fix...

I've noticed that the top bar doesn't follow you on the way down the page on large threads. This is annoying because I have to scroll all the way up just to refresh the page (at least, refresh the page without reloading the entire thread). Can this be fixed please?

>>156162
Is this occurring with the built-in version? Or is it coming from the extension? I can see how that could be possible in larger threads, since the larger the threads, the longer it takes to get the content it's looking for, which I can fix by putting a time limit to stop it from overloading your browser.

>>156163
I had a fix submitted for this problem last night. Is it still getting stuck there, even today?

>>156164
No I installed it. And that makes sense since the threads I'm on go to like, 2000-3000 post threads...but I never have threads opened with more then 100 post.

>>156165
Try the native version and see if the problem persists. I've been hearing complaints about some GM clients crashing people's browsers recently.

>>156166
I'll see. I know I had way more problems with the built in version then I did having Px installed...

>>156169
>quick reply box isn't working.
Is it refusing to submit post content, or is it not appearing on the page at all?

If it's not appearing at all, try resetting QR position? (That's the one thing I know would carry on past a browser restart), unless there's something else I don't know about. deleted post. Well, carry on I suppose

Last edited at Fri, Apr 25th, 2014 18:01

What the fuck...

Somehow, Chrome is still having extension crashes with the site's built-in pX, even with Tampermonkey completely uninstalled. Same deal of just randomly getting the "Oh snap!" page upon refresh/reload.

Last edited at Fri, Apr 25th, 2014 18:15

>>156171
The only idea I can think of (do I dare give such a conventional answer?) is to restart your computer. Every once in a while for inexplicable reasons chrome often fixes bugs after a restart, for example, with the breaking zoom-hover image expansions, which is also I think a bug with chrome that has yet to be fixed. Whatever is happening is not only odd and out of the ordinary, but also beyond what javascript is even capable of controlling.

Great work with the updating and new version and stuff and such.

One thing I'm wondering about: My refresh timer is set to 60, but lately I've seen the timer drop down to 5 seconds. This seems really odd to me.

I don't necessarily mind it, but I'm curious as to what happened.

>>156175
Well fuck, it's a bug. Thanks for pointing that out, Dragon. That bug completely jumped the radar on me.
>>155803
Now's your chance apparently.

I'm having a bit of an issue with the reply button. As you can see, I made a post, and I have it set to close the QR after I click submit. When I clicked Ponny's reply, it didn't delete the previous post from the QR message box

I think I've found something that triggers a crash.

I turned off the auto-refresh, and almost every time I post and then hit F5, it crashes.

Yeah, I'm getting like 5x more crashes with the built-in pX than with Tampermonkey.

Thanks a lot Chrome for not giving me any debug information about the crashes whatsoever.

Last edited at Sat, Apr 26th, 2014 08:22

Okay, so new comment from me (I haven't read the whole thread, so pap me if it's been mentioned already), but everyone knows how it shows the number of new posts in a thread at the top, right? Well it used to be that it would go down as you scroll so you could always see how many unread posts you had (unless, of course, you had to scoll up a ways from the bottom, but that's a whole different issue), but now it shows how many new posts there are and then it goes away when you click the tab, and you can't really see how many posts there are in there.

It's kind of another minor complaint, but I thought I'd mention it.

>>156181
>Thanks a lot Chrome for not giving me any debug information about the crashes whatsoever.
Isn't Chrome supposed to show errors and debug info in the console?

Also, with the site's version of pX, the auto refresh timer keeps resetting to 5 seconds over and over.

>>156330
I have no idea how to access that.

>>156333
F12

>>156334
I can't access that while on the crash page.

Every time I get a crash,

>this

is all I get. No info on what caused the crash or what went wrong.

>>156333
Yeah, Dragon pointed it out for me. just uploaded a fix for this on the extension.

>>156005
Got this fixed in 1.17 as well

Uh iunno if this has been reported but whenever the timer goes to zero and it finds new posts the page freezes for a second and whatever I type there is missing leading to gaps in my posts.

>>155310
>The thread refresher is now moved to the top left of the page

I wasn't going to whine about this but I really miss having it at the bottom since I like to keep my nav bar from scrolling since it fucks with my screencaps. Also, the random trip thing sticks to one trip when I'm in a thread now instead of changing from post to post like it used to. I dunno, they're minor issues so it's no big deal really. I just wanted to bring them up... *nudge nudge*

Anyhow, thanks again for the random trip thingy cuz it's so much fun.

>>155310
>>156378
I, on the other hand, really like it being up there. Especially now that it takes up to 50 seconds to refresh. The bottom right is where the mod tools are, and it blocks my ability to refresh using Pchan X.

*cough*
>>156180
*/cough*

>>156381
Correct me if I'm wrong but I think I found a fix for this in version 2.17? If you're using the native version, the fix hasn't been submitted yet, but it'll be there soon.

>>156378
Got it working again in 2.18

>>156380
>The bottom right is where the mod tools are, and it blocks my ability to refresh using Pchan X.
Oh wow, guess you learn something new every day, don't you? My initial reason for the move was actually to make it more visible to mobile users and had nothing to do with mod tools.

>>156380
All I ever wanted was an option, not a straight up forced change. As I said, though, it's only a minor thing. I just use Home and End to make my life easier.

>>156382
Thanks so much! I have my attention whoring back!

Last edited at Mon, Apr 28th, 2014 23:47

>>156383
Options are always good.

>>156378
>Anyhow, thanks again for the random trip thingy cuz it's so much fun.
Yeah thanks for that! It's super fun, iunno if anyone but Mein and I even use it but it's cool!

Having issues with Quick Reply again, despite updating to the latest version.

If I click it to move it, it sticks to my cursor and never lets go unless I close the tab.

>mfw trying to get the QR box off my cursor

Last edited at Tue, Apr 29th, 2014 05:56

>>156389
so its not just me!

I seem to be having a problem with the autorefresh...
Previously, on the site's version, if I set the timer to anything greater than 60 seconds, it would count down once, and then go past 0 and start counting negative numbers.
>pic is the timer at -3505 and still going
Now, after installing version 2.18 with Tapermonkey, whenever I try to set the timer higher than 50 seconds, it always resets to 50 and works normally after that.
So, currently I have no way to set the timer to a higher number, say, 120 seconds.
I guess it's better now than not being able to refresh at all, but still.

>>156389
>mfw it's caused by yet another Tampermonkey bug.
Yeah, I'm not even kidding you, it's another bug caused by TM. And to confirm, I took an exact copy of the site's script that previously worked without problems on chrome as a TM build and reopened it, which also presents the new bug despite the fact. It previously never did, and even more telling is the fact that the bug can't be replicated across any other GM client on any of the other browsers, not even chrome-based Opera. And here's the kicker - the initial bug that would crash the browser was triggered by event listeners being tripped. This current bug is being caused by the browser trying to remove these event listeners. The only two places I know where there is the case of event listeners being removed are when you drag the QR around and when you slide the volume knob. And both of those are affected by the bug currently on TM exclusively to chrome and no other browser whatsoever.

However, I'm just going to write a work-around for this issue now and just call it a day. It won't be a problem.

>>156410
Yeah, I noticed that bug and made a quick patch for it to prevent any values any higher than 50 from giving those bizarre results. I'll bring back the unlimited counter soon.

>>156368
Yeah, that happened to me too. I mentioned it a while back and nobody ever responded.

>>156382
I had the manually installed version. I just now updated it from 2.1 to 2.18 so I don't know if it's fixed. Isn't it supposed to update itself?

>>156416
That depends, are you using Greasemonkey or Scriptish? I'm gonna assume you're using firefox judging from the screencaps.

>>156417
Greasemonkey

>>156384

Options are definitely good. And on that note, is there any chance that those title bars I was bugging folk about could be customizable? Just a couple variables to place into a text box for things to reference.

And I guess I'll link to my last post, too:

>>156191

I hope I don't sound too bitchy, you're really doing a great job and I love what's here so far.

>>156412
Get your shit together, Tampermonkey.

>>156415
>>156368
Pls respond

Also this combined with the 5 second timer bug is annoying.

Last edited at Wed, Apr 30th, 2014 12:37

>>156428
I just reinstalled pX 1 as a separate add-on. The freezing thing made pX 2 pretty much unusable. I might recommend doing that and just using pX 1 until the bugs are worked out.

>>156433
>>156368
Is the page freeze bug a really prevalent issue? I've been looking for it but so far I haven't encountered it, not even on firefox. Does it only occur in larger threads?
Edit: oops, forgot to clear the name field from when I was testing that trip cycling feature. OP here.

Last edited at Wed, Apr 30th, 2014 16:54

>>156437
I do believe I was mostly having trouble with it in larger threads, yes. Upon reload the whole page would completely freeze up, I'd lose what I was typing, couldn't scroll, etc.

>>156438
And does it freeze up whatever you're typing in the Quick Reply, or just in the old post form?

>>156439
Quick reply, since I don't think I've used the old post form in years. It'll freeze up on reload even if I'm not typing at all, though.

Last edited at Wed, Apr 30th, 2014 17:13

>>156437
Not freezing for me, just a slight pause whenever the timer hits zero and reloads and it cuts out some words. Say I want to type:

"The horse jumped over the fence"

If it reloads while typing it might come out as:

"The horse jumpr the fence"

or something, with some bits cut out

>>156499
Oh, so that's what was causing that. I thought my keyboard was acting up.

>>156416
>>156418
I found out the problem here. Apparently the current versions of Greasemonkey mandate update URLs with an SSL certificate. I guess maybe one easy workaround for this may be to just redirect the nightly version update url to a public dropbox file, since they already have SSL out of the box (and I've seen it successfully update there before).

>>156191
I can't tell if you're referring to a bug that I might have missed or if you're asking why the behavior of the post counter in the title has changed. For a while, there was a bug where if an idle thread hidden in your tabs had new posts triggering the counter and you clicked on the tab, the new post counter would hide prematurely even if you didn't scroll over them yet. If you see this happen, then it's a bug.

Though if you're referring to the new behavior of the post counter, whereas the loading thread flashes how many replies there are ("[x replies] /board/ - headline" then idles to "/board/ - headline" as opposed to "(unread) /board/ - headline") that behavior was intended. In the previous pX thread, I suggested the possibility of rewriting the counter algorithm and the guys in the former thread seemed to like the idea. >>153062 >>153063 >>153074

>>156421
Oh don't worry, I'm open for as much feedback as I can get. I've just been a little busy lately with some personal concerns that kind of been keeping me away for a bit. I put an option dropdown under the style tab so you can change the title, though it's implemented kind of awkwardly which I'll deal with when 2.2 gets pushed out soon.'

>>156438
>>156499
>>156549
Try it in 2.19 now. I'm guessing that some browsers didn't like the fact that I set it up with two synchronous requests running when new replies were fetched. It doesn't appear to lag anymore in the new version.

Soo um, sorry to ask this, I'm not sure if ots been asked already..

Changin the QR's placement Makes it impossible to drop it down from the cursor.. It's a bit annoying. :c

>>156553
...If I understand what you're saying, I think I was just about to come here to say the same thing, haha...

Yeah, so, clicking on the quick reply box to move it doesn't work. I mean, it works, as in, I can move the box, but...the cursor is then forever stuck on the movement of the box, and there's no way to click off of it. Even right clicking to get the mouse away from it doesn't work. I don't know if it's just my browser (Chrome) or whatever, but I only just recently noticed this glitch. It means I can't change the position of the box, really.

Last edited at Fri, May 2nd, 2014 00:26

>>156554
I'm using Chrome as well, maybe it's tapermonkey or whatever it was.. It's just a bit annoying.. I guess..

>>156553
>>156554
>>156555
It's fine. I explain it here >>156412 that it's another bug with Tampermonkey sadly. However, since I'm changing the update url in 2.2 when it gets posted anyhow, the next version will have to be updated manually anyhow.

Until then, for any chrome users that still would like to use the nightly version, your best bet would be to just install it the old fashioned way - saving the file and dragging it to your extensions menu.