>>3810
>Fish, you got some 'splainin' to do.
Yeah, there's no ignoring this. I'll avoid mincing words or making excuses: I started this site with nearly zero relevant experience and have tried to solve as many problems as I could without leaning on anyone else. I absolutely could have done more but this coupled with my own bad habits obviously hasn't worked out well. So now I get to eat crow.
To address the thumbnail issue with transparent .gifs, ffmpeg 4.3+ needs to be installed and deb10 only has 4.1.8 and I didn't think to check. I'll need to build it from source to fix that, which I'm in the middle of reading about how to do cleanly.
>>3809
I don't blame you for getting annoyed with me man, but I'll still address your points here. I mean you absolutely zero ill-will and I appreciate the work you've put into jschan, and the help you've given to me. To address what you've said:
>"live" posts
This is going to require me to put more work into the nginx config for the proxies, which is something I do VERY carefully. The entire point of the proxies is to prevent what happened to the original fatchan, so accidental exposure is not acceptable. I'm sure it's fairly simple to get working I just need to fucking LEARN but until I fix the other issues this is low priority. This feature has been disabled in the meantime.
>Onion users, ID's and IPs.
My onion is setting the origin-ip header to 127.0.0.1 and the x-country-code to 'TOR'. It's then routing to the proxies (which I have verified are NOT overriding the headers) and then on to the appserver. My understanding was that as long as x-country-code was being set correctly jschan would recognize torposting. Is there something else I need to do or could this be related to the broader issue of scripts not getting updated correctly?
>Stupid styling problems
Yeah that padding was dumb and I've reverted it. Anyone still seeing it needs to clear their cache, I've purged everything on my end.
>Markdown issues
Here is the current set of markdown rules. Anyone reading this can tell me what I've fucked up here:
const greentextRegex = /^>((?!>\d+|>>/\w+(/\d*)?|>>#/).*)/gm
, pinktextRegex = /^<(.+)/gm
, boldRegex = /''(.+?)''/gm
, titleRegex = /==(.+?)==/gm
, monoRegex = /`(.+?)`/gm
, underlineRegex = /__(.+?)__/gm
, strikeRegex = /~~(.+?)~~/gm
, italicRegex = /||(.+?)||/gm
, spoilerRegex = /\*\*(.+?)\*\*/gm
, detectedRegex = /(\(\(\(.+?\)\)\))/gm
, linkRegex = /\[(?<label>[^\[][^\]]*?)\]\((?<url>(?:/[^\s<>\[\]{}|\\^)]+|https?\://[^\s<>\[\]{}|\\^)]+))\)|(?<urlOnly>https?\://[^\s<>$
, codeRegex = /(?:(?<language>[a-z+]{1,14})\r?\n)?(?<code>[\s\S]+)/i
, includeSplitRegex = /(\[code\][\s\S]+?\[\/code\])/gm
, splitRegex = /\[code\]([\s\S]+?)\[\/code\]/gm
, trimNewlineRegex = /^(\s*\r?\n)*/g
, escape = require(__dirname+'/escape.js')
, { highlight, highlightAuto, listLanguages } = require('highlight.js')
, validLanguages = listLanguages() //precompute
, { addCallback } = require(__dirname+'/../../redis.js')
, config = require(__dirname+'/../../config.js')
, diceroll = require(__dirname+'/diceroll.js')
, fortune = require(__dirname+'/fortune.js')
, linkmatch = require(__dirname+'/linkmatch.js');
>As of now, the thread watcher and other frontend stuff added in a recent update does not work. My latest correspondence with sturgeon was about how to fix this
I ran all of the diffs you suggested and nothing meaningful is any different. I have followed your update instructions to the letter and all caches have been purged. I don't know why things are still broken and am unsure of the best way to go about fixing them. Should I just start checking out the remote versions of affected files or what?
> As a matter of fact, I have a feeling he is just being dishonest and trolling
No, this is stupidity on my part, not malice. I won't beg you to change your opinion of me but at least know the actual cause of my failures.
>Sadly I can't spoiler that last part.... well, you know why.
Hey man that's not actually broken c'mon