/b/ - Site Meta

ban check

>>>/qa/147181 It's on the reliable IP starting with 31

test 2

>>13270
because you got a you probably

test 3

>>13270
When i made the UI it used to be that notifications on your phone would cause it to crash, so I just hacked it together because no one phone posts.

That means you got a YOU and I was too lazy to properly handle it.

ok I saw the message
no idea why it's refiring however

I can't believe that it would be my fault. That's the main thing I'm saying

>>13273
Ah, makes sense. Well it's fine, I don't mind the reminder.

I'll try replicating it as well... I have a VPN

posting without the qr

btw we have >>>/test/ if you want to just do something spammy

>>13275
Only happens when posting with QR it seems, so totally your fault :3

[Feature Request]
>Autoscroll a thread to keep up with the latest posts (also just noticed right now, if a thread is too fast, the reply box just gets scrolled down until it's hidden)
>Auto noko as an Optional toggle.
>An Option to hide "Similar threads" section that is shown above the new post form. It's already in the sidebar.

>>13280
If it were my fault, then you would see two requests to post.php in the network inspector, but you don't

unless vichan has some sort of retry feature we've never dealt with...

Please add "Are you sure?" Yes/No box to "[Toggle-UI]" button.
I couldn't figure out how to go back.

>>13284
yeah, we're running it through cloudflare.
But the thing is... you're posting through two different IPs.

if you change IPs mid post nothing new happens... I don't have any sort of retry mechanism in the code that happens like that

>>13288
It happens if you click disconnect and then wait 2 seconds and then post. Maybe Windows is lagging on the network switch?

>>13287
But why is it retrying? I'm only clicking once. If the connection is interrupted it should just fail, not do it twice. Since it only happens with QR then maybe there is something for when a post is in progress and it trying to complete it twice?

>>13289
just to recap what's happening...
- you make a post
- the bar fills to 90%
- your post appears
- the QR closes
- you wait 20 seconds
- A new post appears

That's how it's going right?

>>13290
here is how I got it to reproduce 100%
Start with VPN on
Reload page
Open QR
Write post
Click disconnect on VPN
Wait 2 seconds
Click Submit
bar fills to 90%
thread json refreshes and post is already there, post bar is still at 90% and therefore the state is in progress and not complete
a couple more seconds pass
the bar fills
the duplicate post is sent and QR closes

>>13291
Thought I'd offer another test case.
Tried it with my VPN, didn't disconnect though, just reconnected with another IP, no double posting.

>>13292
It sometimes works for me too, I think it's the time between clicking disconnect and submit.

>>13292
you're telling me it takes you 20 seconds to post right?

>>13294
>20 seconds
Pretty instant for the post to appear. No double page refreshes either.

Your VPN must be lingering even after it says disconnected... https://kissu.moe/test/res/11524#11956 is through the VPN
then after is through your local... so even though you say you're posting after you hit disconnect it's still active.

Then you hit post and your network sends a dead request and then gracefully transfers over to the other making a reconnect... and something along the way is not giving you any errors that this is happening

>>13296
But shouldn't the dead request be ignored by the server or the JS? It should abort the submission, not just continue.

>>13297
Servers don't abort requests like that. When it's in the system it's going to complete it then at the end it will try to tell the client and it won't work.
Because of how simple 2000s era HTTP works you can't really get an idea of if the client is around or not until it's done, in which case you have to roll it all back manually.

The JS only reacts to what the browser is telling it to do. If the browser does not return an error when the network is interupted then it is all fine. The browser is handling it.

Are you on firefox, chrome or what?

>>13298
Chrome. Don't you have an exact same post within X seconds filter?

>>13299
Yeah, I'm fighting with vichan's captcha system right now.
I changed something and all of a sudden there were a bunch of posts that the captcha sucks. So I'm going to turn that on and see

OK. it will block it off across all IPs now with the captcha. So it won't double fire.

I'd like to know if this issue is also present on firefox if you have a moment. Basically confirm you see the captcha on FF

>>13270
>>13281
>>13285
Just grouping these posts together so I remember

>>13303
yeah... I think chrome is doing something funny.. maybe I would get your bug if I switched over but I use a Beta browser that I really like.
https://zen-browser.app/ Firefox based

/sum/ is linked at the top and it is NOT summer

On every other chan when I press the "end" key I can read the last few posts, I don't like how the non-classic UI scrolls past all the posts (at least on a 16:9 display)

>>13306
you could use your adblock's element picker to hide the suggested threads at the bottom

https://github.com/TuxedoTako/4chan-xt/issues/177
I'm trying to satrt a discussion about getting 4chanxt functionality to work with kissu's UI.

I'm not sure of the timeframe that this will take or what we'll end up doing.

>>13306
I probably can override the behavior of the end button for this site.

Speaking of which there's a new updates number bug I have to address where it doesn't clear on tab change but scrolling downwards...

>>>/qa/147700

>>13335
oh, that explains a different bug

ISSUES TODO
- MS PGothic -> Saitamaar SJIS
- search field adjusting URL
- title notification issues in thread Also add on focus checker
- End key jumping to #bottom
- Save each thread's cursor position (expiring update system)
- mobile notifications
- Update the similar threads algorithm
- Blog status icon
- link the QR files with the footer-form files

notification spam

Adjusted SJIS font, search field bug, 4chanX header sets right backgrounds.

notifications and scroll position issues remain.
Done: file forms synchronization, similar threads updating every day to give better recommendations, sjis font, search field issue

>If you notice the + button above the submit button, you can queue additional posts and switch between them down by where the 1 is above the Files button. This makes it a lot easier if you want to imagedump.
This is a feature in the pop-up reply box, but it's not in the reply box at the bottom of the page. Not urgent ofc.

>>13537
I'll save something like that for after a software remake... adding new features isn't priority unless there's some sort of major staff project..

Test

Not sure if this is a known issue, but spoilers are always unhidden for me on mobile, no tapping necessary.

>>13591
Odd. I'm too inexperienced with phones to not be paranoid about posting a screencap, but I'm using Android with the Brave browser. Perhaps that is the issue.

>>13592
Strange. I just tried all the browsers on my phone and I don't see it.

Because what you have to do for it to become visible is to mouse over it, and on a phone that would be a click. So you shouldn't be automatically mousing over

>>13593
Has to be something stupid interferring on my end then. I did notice just now that the spoilers do still seem to have two states, because the font color does actually change to what looks to be the normal color for posts. It's just that the "hidden" font color in my case is pure white for some reason.
No need to further investigate though if no one else has this issue, I don't really mind and take any excuse to drive up the PPD.

>>13619
I am on the old UI howthoughever. Original.kissu is that right? I have the 4chanx script with greasemonkey and it says kissu is on the list

>>13623
Hooray!

>>13622
I'm not sure exactly what this notification problem is. It seems like the times it doesn't work are because the OS is misbehaving, but I'll have to really check into it some more later.

The thread watcher stuff is really problematic. I have a great plan, but I don't think anyone will ever do it meaning I'll have to build it myself... and it will take a long while to pull it off.

At work I have a fairly sizable project, and I have to learn japanese, and also start doing some cardio some time. My time is very stretched.
Also spent all Sunday arguing some meta crap which could have been spent on other things

For some reason I can't embed youtube videos on Brave. My replies disappear without ever getting posted. Can't see any error message or anything when I hit reply. Wanted to post ひぐらしのなく頃に煌 - にぱにぱ音頭☆ (Nipa Nipa Marching Song☆) ([embed]) on >>>/qa/114027.

>>13630
>>13629
crashed the site

why did you add a unicode blank character to the end... \u000f

>>13656
You mean me? My link looks just like this https://www.youtube.com/watch?v=FytHqw7E5LA even when pasted on the "add URL image" button

I don't see any unicode character but maybe it's because I copy-pasted the URL from IRC?



>>13659
Still can't see the unicode but I will simply copy-paste from youtube next time to avoid the issue

>>13660
I see it now.
Does this link have any ascii?
https://www.youtube.com/watch?v=3yaab2_EEHM
it was copy-pasted from IRC as well

>>13663
It has one kanji, one erotic heart and many kana, none of which qualify as ASCII according to the standard no one cares about anymore.

>>13663
it probably does. But anyways. It won't cause crashes. There might be some situations where the doesn't show up, probably not many

>>13665
>There might be some situations where the doesn't show up
I am more concerned than I was a second ago but I don't want to press the issue of the missing

>>13666
I mean, if someone find a random unicode that causes the embed not to show up then they must either have quite the unique keyboard or be very interested in testing the limits

If you accidentally crash the site you should get a free lifetime kissu pass for helping the webmaster discover a bug

if you want it, let me know and I'll send it to you in a PM(AKA ban message)

>>13672
sent u the PM (aka report message)

>>13673
I'm not going to give you a free spam token......

>>13674
wasn't going to spam with it.....

>>13675
I'll consider if it's a good or bad idea after I get out of the shower

Prepare your anus, Vern, I'm coming for that Kissu pass.

>>13675
apparently it's not a bad idea

- Save each thread's cursor position (expiring update system)
- Notification spam issue
- Adjust where END goes
- % and depth of markup
- Restrict letter-spacing as a markup option

- Port options menu to svelte
- Add in Onee-chan type theme styler
- synchronize vichan blotter with kissu for purpose of injecting CSS into all pages.

Proceed with other objectives as outlined in >>13682(Cross)

>>>/amv/6319
Hiding text isn't allowed. I have to patch that one

>>13754
Noooooooooooooo

I noticed you also patched using pc for font-size >_> which used to have an unlimited size <_<

people break it, I patch it

I spend my zero-days thoughtfully

Yeah, I was thinking about it and it's a very used feature. So maybe I can undo restrictions for VIP users.

But the problem is that it's coded into the UI what is and isn't allowed so that makes it pretty hard to selectively enable and disable.
I guess if someone tells me that I'm restricting their creativity and it isn't due to bugs then I can try and remake the system, but not really sure. Maybe I'll just inject a hidden "4chan+ user" style icon to enable these advanced features...

>>13759
What exactly is this referring to? Hiding text, font size? Also, what does hiding text look like? I didn't see what the original post looked like and assume you don't mean spoilers.

>>13760
he used https://developer.mozilla.org/en-US/docs/Web/CSS/letter-spacing

There are a few situation that people can use to potentially hide text and create hidden messages in the content and I think that presents too many potential problems.

But if use is approved maybe I could authorize it. Also the width is limited as is font-size.
It's mostly just a consideration for if I get complaints about it. Not something I'm going to act one

It will probably work for like 24 hours until I get around to making more modifications to the UI so you can try it out, but things will show up later when it's disabled

>>13761
>>13762
Thanks! Sounds reasonable to me personally, was just worried for a second if something more basic was in talks to get VIP-locked.

I discovered a huge security flaw: When mods delete a post, on /trans/ there's always an extra unnecessary space before the name of the mod in the "Deleted by(...)" message.
I noticed this completely by chance, so I think a lifetime Kissu pass should be enough for a reward.

>>13765
this could have caused us a massive headache... i've sent you your lifetime pass via mail to a post office in the 50km radius around your current IP

guess you could use the disappearing letters trick for that hypothetical linux terminal copy-paste command attack vector people always like to bring up
like
hey run this
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rsSome markup rules were altered! For details use post-previews and check console warnings; cat ./meow | sh

>>13767
you trickster...

>>13691
I'll do the scroll position store later..

>>13795
>x
y I mean.

>>13796
odd. I guess you can't use label on select even though it has some sort of effect..

>>13691
When entering and exiting threads, now it stores the position you were last on.
Thus replicating a 4chanX feature for keeping track of your position when returning to threads.
History expires in 7 days. But it could be longer.

So the next tasks are some CSS things.
- Options menu redesign using a revised customevent API system + Svelte
- Onee-chan style theme style with stylesheet redesigns to make use of :root variables
- sync the vichan blotter with the kissu-ui botter for purpose of adding CSS to the site

>>13804
>- Onee-chan style theme style with stylesheet redesigns to make use of :root variables
YES!!!!!!!!

>>13805
it will probably end up being the last of the things, but I'll get to it after I remake the options menu.

Blotter/Mod CSS location and stuff, added. Need to do a version push update, but it's alright for now

>>13814
It's not alright at all.
b global_message
Everything is black.

>>13815
Think I fixed it. For some reason /b/ wasn't abiding by the global change.

>>13816
yeah, because the /b/ one was a /b/ message. They're per board

the dude abides

>>13819
thank god someone will

https://github.com/ECHibiki/Kissu-Fr-SvelteScripts
This menu and any further adjustments or additions will be public on this repos.

who thinks that Hazuku.css should become a yotsuba-b theme instead ?

>>13853
hmm? what do you mean, adapt it into a yotsuba variant or how?

I for one like it how it is, yotsuba is boring

It's what I use...
Don't replace themes, add new ones if you want them.

>>13858
really... people actually do use it... crazy... ok I guess I can't.

but um, yeah. It's super unpolished.

>>13859
looks like the lala theme

Also the xmas theme is garbage.

>>13865
Can't you toggle her away at the top of the page on phone?

you shouldn't even be able to see it on phone unless it can be toggled

oh that's the old UI. Oh well.

Bleh. Guess I could change it so it doesn't affect the old UI backgrounds. Phones really ruin everything.

Maybe he should just use the real UI and you shouldn't be facilitating him

>>13864
It's lovely. It has that homemade charm you only see once a year for a short while.

the colors are changing

>>13876
the foot looks better in the old UI