No.10
Also this keeps happening when I try to post images.
"Caught fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 24000 bytes) in /var/www/sushigirl.us/inc/image.php on line 481"
No.11
>>9Fixed. Sometimes there's two catalog buttons right next to each other though, gotta figure that one out.
>>10Maybe it has something to do with a couple other users being unable to post. I'll look into it.
No.14
>>10I changed a setting, try posting images now.
No.22
>>16Looking into it.
>>21Sometimes the board index doesn't update right away when a post is deleted. Don't know much more about it.
No.39
>>22Thanks for fixing embeds! Although now I'm getting a different issue where the site thinks all youtube links refer to the same file so you can't upload more than one per thread…
And I'm pretty sure the bug with
>>21 is due to the overboard. If there's a thread from, say, /lounge/ which references post 12 in /lounge/ - has
>>12 in it - then if it's visible on the overboard front page then the overboard will think that all posts of number 12 are being linked, regardless of which board it is (so post No.12 on /hell/ will be backlinked to whatever number /lounge/ post in the overboard, but if you click through to the thread or use the actual board it won't be).
If you search the overboard for No.14 you can see a post on /silicon/ that contains
>>12, which is where the backlink on the /hell/ post comes probably from, for example.
This didn't happen too often on old sushichan because there was a reasonable difference in post numbers between the different boards (and I think the two posts have to both be on the overboard "front page" for it to happen), but I did notice it occasionally so it wasn't a problem Itamae or undoall ever fixed. As post numbers increase and the post ranges differentiate between individual boards it should start to happen less often.
No.139
It seems that Vimeo embeds aren't quite working:
https://sushigirl.us/tunes/res/16.html#38 No.141
>>140Fixed.
>>139I dunno man, I don't think anyone's maintaining most of the embed code. Just use Youtube until I can figure something out.
No.160
Is it possible to add a board or thread to my rss reader? I didn't see anything about it on the faq page.
No.170
I keep on getting this message when I try to submit a post in
https://sushigirl.us/tunes/res/112.htmlEven when I don't enter in any text this happens. Is there some way to prevent this from happening again?
No.631
In the FAQ, the link to the BBCode info is dead. I think the post it's supposed to link to is the following:
https://archive.sushigirl.us/archive/res/11.html#14On an unrelated note, Itamae's dancing squid tripcode a cute.
No.635
Hello!
I browse sushichan on my phone. The layoit of the site itself matches my screen resolution no problem, however some banners seem to be super big and they mess up with the width of the page (so instead of just scrolling down through the boards you can also scroll to the (empty) sides of the page.
I don't know if I am explaining myself correctly, I'm sorry.
Basically some of the random banners seem to be super big and it breaks the layout width on mobile.
No.685
not exactly a bug, but
https://sushigirl.us/faq/ and
https://sushigirl.us/irc/ still have links to lainchan
No.698
>>635This irritates me as well. I really just have to manually comb through the banners folder and delete the big ones but I keep forgetting.
>>685Fixed.
No.720
>>698From my quick search these are the wrong size:
1436666567803.png
1437017828825-1.png
1437017931528-0.jpg
1437552640709-1.jpg
1438227844136-1.gif
1438227844136-3.png
1438488143792-1.png
1438830426658-0.png
1439071215319.gif
1439083693656-0.gif
1439083693656-1.gif
1440294564992-0.png
1441441958577-0.png
1441441958577-1.png
1441441958577-2.png
1441441958577-3.png
cute_sushi.png
sushi-roll51.png
sushi-roll79.gif
sushi-roll80.png and sushi-roll81.png are for lainchan
1448374209297.gif and ezgif-3725406271.gif return a 404
No.721
>>718Lainchan and sushichan used to be partner sites. Banner never got removed, but it was originally supposed to be there.
No.736
>>720I've moved all of these banners out of rotation. Thanks for your help.
No.752
>Lost Cities Minecraft server now on 1.14.4! See <a href="https://lostcities.seisat.su/" /> for details on the new configuration.The link in the announcement is not closed properly. Links cannot be self-closing in HTML; it should be
<a href="
https://lostcities.seisat.su/">
https://lostcities.seisat.su/</a>According to Inspect Element, this causes some HTML elements further down to be wrapped in the link when my browser tries to parse the invalid HTML. Noticed it because it broke 4chan X on this site. Wouldn't be surprised if it causes other issues I haven't noticed.
No.773
So the wordfilter for the current trend-word rhyming with limp is broken, and matches regardless if it's part of another word, so anytime somebody uses words like man of tastele or man of tastely, well yeah
No.774
>>773Should be a man of tastele fix ;)
No.775
>>773I have fallen for one of the classic web administration blunders and tried to filter too short a word without thinking. I'll just disable it if I can't make it only match whole words.
Edit: Fixed.
No.846
Not really a bug, but is there a way to report advertisement posts like >>8178
No.847
>>846This. Ads outside of their proper thread have become too common.
No.849
Hey! Having issues posting multiple photos on the same post. Example here:
https://sushigirl.us/lounge/res/6562.html#8185The last picture is supposed to be a photo of just clear water on sand. For some reason it acts up and duplicates the previous image onto the last.
If it's any help, I am using Brave and PrivacyBadger, but I have Brave Shield and the plugin turned off for this chan.
No.850
>>849That happened when I posted in that thread as well.
No.864
>>855It'll be a cold day in hell when that happens
No.866
Infinite scroll makes reporting spam from /kaitenshushi/ very inconvenient.
A report button on the top of the page would be appreciated.
No.869
Please implement a better spam filter. Makes me not want to visit this site.
No.870
Did recaptcha get (re)implemented recently? I must've missed some action.
No.871
>>866You will need to visit the board for now to report the thread. I'm not sure if a report button directly on /kaitensushi/ would work without some extra coding.
>>869>>870Just re-enabled reCAPTCHA. Let me know if there are any issues.
No.872
>>871But why?
Are we getting a lot of kiddie pr0n?
No.873
>>871I think the captcha is preventing me from making new threads. The captcha gives this error whenever I try to make a new thread
>Undefined index: captcha_textI think other sushi rolls have this problem because /lounge/ "general topics" thread has hit bump limit for a while and no one has made a new thread. I can reply fine, but new threads run into this issue.
No.874
>>871Recaptcha is super glitchy for me and I need a VPN to even see the captcha
Why do we need this thing? Was there a lot of spam?
No.875
Not a big fan of google captcha honestly but if it's that necessary then so be it.
>>872>>874If it's what I think, there wasn't a lot of spam but there were a couple of threads with bad shit in them posted on multiple boards. I've seen the exact same kind of posts in the same number being posted in other smaller image boards during the same period, and other people have mentioned they've seen the same in other image boards during the same time period as well.
Unfortunately, unless these image boards are able to enforce a 24/7 mod presence or hold anti bot measures like google captcha, the same thing is bound to happen and people are bound to be exposed to that crap.
>>873>I think other sushi rolls have this problem because /lounge/ "general topics" thread has hit bump limit for a while and no one has made a new thread. I can reply fine, but new threads run into this issue.Isn't that more because most posters made a pact not to make a new thread for that anymore? Frankly most those posts should have been threads of their own, really make lounge one big lounge full of blogconvos. The only big problem is that soon enough /lounge/ would have hundreds of pages and people couldn't be bothered to lurk for a thread with a similar topic to bump.
No.876
Had to disable ReCaptcha again because of new thread issue. Yeah we were getting some bad spam, may need new mods.
No.877
>>875>Isn't that more because most posters made a pact not to make a new thread for that anymore?I thought it was just one guy saying that, I never saw anyone else agreeing with them. Honestly, I think those threads are nice and serve a good purpose, i.e. for posting stuff that doesn't really belong in other threads but also doesn't really warrant making a new thread.
No.879
I've noticed some "ghost bumps" lately, i.e. threads getting bumped without any new posts.
>>>/lounge/7233 is an example that got ghost bumped today. Is this the result of people bumping the thread then deleting the post (or the mods deleting the post), or is it a bug in the board software?
No.880
>>879The only thought I have is that a post got made and then deleted. Maybe one of the spam posts the other mods have been mentioning.
No.892
When did ctrl+arrows become for switching pages? I use that for moving between words as I'm typing and I keep doing it accidentally and having to rewrite my post
No.893
>>892Disable 4chanx or go in the settings of it and disable the keybinds.
No.894
>>893Oh… thanks sushi roll, I am quite dumb.
No.936
Site certificate expired…
No.940
What the hell is the criterion for a post "looking automated"? I'm trying to post a thread for the new season.
No.944
There's definitely something a little bit weird with posting, pls fix!!
No.948
>>944If you're talking about the error regarding the missing telegrams table, I've just fixed that. (Maybe the error was only visible when posting as a moderator, not sure.)
It looks like it cleared up some other posting issues too when I applied the fix on Uboachan.
No.953
>>952Weird, it looks like all of the reply links on /kaitensushi/ are doing that.
No.954
This morning my browsers are complaining about sushichan's ssl. I'm only on my phone right now so i don't know how to get more information but it's the whole "someone might be impersonating this site, your connection is not secure, you have to accept the risk to continue" thing
No.955
>>954Just a case of expired certificate.
No.995
hide nginx version plz, it's a security risk
>tecmint.com/hide-nginx-server-version-in-linux/strongly recommend that you block TLS 1.0, TLS 1.1, and also enable TLS 1.3 for future-proofing so that only TLS 1.2 and 1.3 are enabled
>www.cdn77.com/tls-test/result?domain=https%3A%2F%2Fsushigirl.us>libre-software.net/tls-nginx/e.g. put "ssl_protocols TLSv1.2 TLSv1.3;" to your server block, then test with "nginx -t", then "systemctl reload nginx", then check your site's tls with that link
read:
>www.packetlabs.net/tls-1-1-no-longer-secure/strongly recommend you make a robots.txt in your website root directory to tell search engine site crawlers (google bot, bing bot, yandex bot, baidu bot, etc.) to stop indexing media files so you no longer get DMCA complaints (or at least much less than before), as copyright troll bots scour through google images et al. regularly
>sushigirl.us/robots.txtUser-agent: *
Disallow: /*.bmp$
Disallow: /*.epub$
Disallow: /*.gif$
Disallow: /*.jpg$
Disallow: /*.jpeg$
Disallow: /*.mkv$
Disallow: /*.mobi$
Disallow: /*.mp3$
Disallow: /*.mp4$
Disallow: /*.pdf$
Disallow: /*.png$
Disallow: /*.webm$
it'll also cut down bandwidth usage because these crawlers download and parse every file daily
recommend enabling the catalog-link.js in instance-config.php (then click rebuild in mod.php) so ppl don't have to scroll all the way down just to access catalog, there'll be a link below board title
$config['additional_javascript'][] = 'js/catalog-link.js';
if you're using the linux program certbot to renew the certificate you could always just add a cron job to automate checking and renewing once a month
>www.nginx.com/blog/using-free-ssltls-certificates-from-lets-encrypt-with-nginx/#auto-renewale.g.
0 0 1 * * /usr/bin/certbot renew –quietplease disable
$config['markup_repair_tidy_bare'] = true; by setting it to false in instance-config.php, i can see that it's screwing up what i just typed above. i typed "DASH DASH quiet", not em dash. that certbot flag will not work if you put a single dash, it's double dash.
No.996
also maybe consider setting "$config['always_noko'] = false;" to true in instance-config.php, i hate it when it takes me back to the board's index.html when posting a reply to a thread
No.998
>>995on second thought the cron job needs to be every week, since certbot can only renew early within 30 days of expiry, this would be a problem for months with 31 days, so it should be checked once a week instead, e.g. 0 0 * * 0 /usr/bin/certbot renew –quiet (dash dash quiet)
No.1015
>>998made a mistake, you need nginx-ctl when doing it in cron, it needs to be:
0 0 * * 0 /usr/bin/certbot renew –nginx-ctl /usr/sbin/nginx –quiet
(dash dash for nginx-ctl and quet, not emdash)
and if you're not on root account make sure you edit crontab with
sudo crontab -e and not just crontab -e
