Thanks for the prompt reply!
I've got nothing to add to the points on the archive, thread updates, hovering, filters, AV and highlighting, so onto the subjects at hand!
>I am planing to do full overhaul of the json files, or at least clean them up. I have to do a little pondering regarding making the json files more tailored to our site or keep the backwards compatibility.
To be quite honest, the JSON API for most board software was always kind of lacking. A lot of the mobile apps for say, 4chan, infinity/OpenIB, and the various forks of vichan rely on grabbing extra necessary data from the full site and going outside of the API itself, which rather defeats the purpose of having an API in the first place. 8ch's API, for instance, has no support for any board's custom flag data in the API itself.
If you want my opinion, stick to the fundamentals in the stock vichan API that work fine, but if extras are required, overkill the shit out of them. Do it once, do it right.
If you (know someone who) happens to know Java/Android, you can have them spin off a quick extension for Dashchan (https://github.com/Mishiranu/Dashchan-Extensions/wiki/Extension-devepment-tutorial) to test whatever JSON changes you make against it. That way you can both test the changes for functionality, and get an mlpol/NPFchan mobile app out of the deal as well!
>This will also be overhauled. I don't suspect there will be many changes, but if you have wishes for specific test formating feel free to give suggestions.
No objections to the automatic pink text change. You could also add the 8ch formatting for (((them))), though I find it a bit garish IMO and wouldn't miss it being left out.
>>hashes for files
>I plan on moving to storing files as their hash codes so identical images will not take additional space (like they do now), but rather the same file is served and linked. So to avoid any possibility for collisions I will use 128bit hash and add filesize to the end of the filename (probably overkill).
Very nice, I can get behind some sweet deduplication action.
That being said, my point was more about exposing the hash in a text string alongside the image (preferably hidden under the post's ▶ menu) for the user to verify against. Just in case, say, a file is DL'd over a piss poor connection, and the anon in question wants to check the hash for themselves.
>At the moment I only have check on headers of files to see if they are valid. But I will look into making an function to list content of compressed files.
I'm not sure how zip files are operated on server-side (if they are at all), but if you need to pull in an extra dependency for this, consider p7zip (7-zip CLI), which may also add the possibility of 7z file attachment support as well.
Whatever method you use to do this, be sure to have checks to make sure someone can't just upload an endlessly recursing archive file, have the archive list program eat all the memory, and crash the system. Perhaps a 30/60 second wait for the list to complete before the process is killed, and providing a simple "unable to list files" error when it happens?
>I can also mention this as it is a change that will affect users and perhaps ease some "fears" if it happens to you in new code:
>>I am planning on making force-flagging of posters limited to individual threads. This way mods can be more free to forceflag people without exposing them sitewide; i.e. more fun for all especially mods..
I've absolutely no objections to this change. It's far less controversial than an idea I've had cooking up for a while!
>Keep the ideas coming, and don't hesitate to mention other areas I should pay attention to when doing the rewrite.
It'd be my pleasure.
ᐅ The desktop notifications are a nice touch, but I find the pings it gives on every single post to be overkill and less than useful. Call me spoiled thanks to 4chanX.
ᐆ Have the desktop notifications configurable to only fire notifications upon replies to (You)
ᐆ Have the desktop notifications configurable to only fire on replies to posts you want (maybe under a post's ▶ menu, having an option to notify on replies)
ᐅ The thread watcher is a little anemic, and it's position as fixed on top of the page makes it's usefulness limited when browsing a thread.
ᐆ Have the thread watcher pop out just like the Quick Reply window (4chanX conveniences, yay!)
ᐆ Have the watcher be a little clearer (current thread in bold, dead/archived threads in dark text/italicized/strikethrough)
ᐆ Have some integration with the above notifications: maybe an extra (coloured) number beside new posts for posts that would trigger a notification normally?
ᐇ Would it be feasible to make the watcher button change colours when this notification event happens?
ᐅ There's no catalog for the Overboard.
ᐆ If this is an intended feature, perhaps have a more compact overboard layout?
ᐇ Say, a configurable amount of columns to display threads in as you scroll down?
ᐅ Quick reply doesn't let you change between Files / Remote / Oekaki.
ᐆ Oekaki doesn't display in quick reply either - not that important to fix, but still worth noting.
ᐅ Flash files do not open correctly.
ᐆ Either it has you download the .swf file outright (Chrome/Opera/etc.), or opens in a new tab (Firefox)
ᐆ I suspect that the .swf files aren't being embedded properly, causing the browser to treat them like files instead of, well, Flash.
ᐆ Wizardchan (also running NPFchan) has a Flash section in it's options to configure .swf playback and default resolution. Worth looking into?
ᐅ Layering colours and spoilers does this.
ᐆ It's not a bug, it's a feature.
ᐇ N-no fix plz?
Thanks for your efforts Pupper, and here's hoping your undertaking goes smoothly! And that my sperglord ass doesn't bog you down in feature creep ^:)