/b/ - Site Meta

>>7612
>I've abandoned or postponned the idea of implementing infinite scroll
Best news I've heard all day.
>Browsers in the Firefox 60(I believe anyways) should work on Kissu now.
Seems to work. Posting using the new UI on 61.0.1.

>>7615
The feature will break too many systems to be worth adding. Full catalog searching is a small stepping stone, but likely infinite scrolling won't ever exist because it doesn't resolve a problem that simpler presentation changes can do just as fine at.

i pledge not to ignore my ssl renewal warnings this quarter

Highlighting some text and clicking a post number pops up a reply box with that text already there and quoted. In a thread the quoted text has a newline after it so you can just start typing; but when you do this on an index there's no newline.

>>7618
yay i did it.

>>7620
k noted.

One bigger thing is on the table to create kissu's last reserves of disk space. Then the smaller issues such as this.

accidentally posted this in the wrong thread

Upgrades to site have been done, updating to 3.14.0 shortly

notes for the next update I'm working on

- 1-5 bug fixes
- Setting the UI to differentiate between a ban, warning and PM and general upgrades to that
- Update the system which hidden threads, scores and owned posts work
- Move prexisting files from boards onto the luna server to balance out the disk space and get a final idea of how the storage stand
- Make hidden boards work on the UI
- Update documentation on the FAQ

Aside from bugfixes, the future update will expand on existing features and resolve some of the issues that I had been ignoring for the past month or more.

>>7694
>- Update the system which hidden threads, scores and owned posts work
This alteration is making major changes to how hidden threads work.
I'm expecting a lot of things to break when I finally get past all the red text and can compile the code.
I'll try and get it to be perfect, but it would be nice if people were to hide threads and tell me if it causes the thread to catastrophically crash.

It's also making large changes to your score and owned post history so there's a smaller chance that these things will be broken.

I've considered backwards compatibility, but previous history on owned posts, scores and hidden threads will be reset.

Updated to 3.15.0 who's major change is altering how stored post data is handled for client.
Modifications made it so that hiding threads hides posts from the recent feed
Some other features like making it possible to use bans for Warnings and PMs.
Posting works as it did before as long as you're not banned.

Issues to fix:
- Hiding is functional but has an issue
- Notifications don't seem to be working on owned posts
- If you're banned there will be a crash
- owned, score and hidden posts not cleaning up after post's expire for some reason
- Return links back to the wrong board sometimes
- Pointless console.logs to be removed
- Some video expansion oddities

Next batch of maintenance and features:
- Relocate source media from main server to secondary server to preserve file space.
- Hide secret
- Update documentation/FAQ to account for recent changes

fixed a few of the bugs that were really annoying me when I woke up... going to actually eat something and continue

wonderful, mobile bug is not detectable on anything other than mobile. Guess I will eat food later

i need a better way to test on mobile...

I'm using samsung internet, and webms don't work. It shows a giant transparent block of nothing with no sound.

>>7714
Scratch that: only some webms don't work. Others are fine.

>>7715
Which ones are working and which don't?

>>7716
The ones in >>>/jp/20409 are broken. The ones in >>>/jp/20358 are fine, albeit a bit laggy (although that might just be my internet acting up).

I suspect it has something to do with sound. I'll try and find more sound webms to confirm.

what's your mobile browser?

nvm samsung internet is a browser

>>7717
I think it has something to do with me moving that thread, but I'm not sure how that'd effect it.

I'm working on something else at the moment, I'll look at what's causing problems in an hour i guess.

how odd, can't even save them correct

I'm not convinced that moving caused the problem, but if the guy can post the original before he moved it then it would help

k, so the webm just breaks on mobile in general.
I tried it on Steam and here, both cases only audio works.

I won't force people to upload files that work on mobile at this point in time, but I doubt that was anyone's intention for it to not work on mobile chrome and samsung

>>7727
might have something to do a tag mismatch or something (i have no idea, i'm literally just guessing). The webm itself claims to have a length of 6 seconds, but only plays for 3.

It would be nice on /poll/ for the results to show how many total people voted on polls that allow multiple responses, so that one can see what proportion voted/didn't vote for each option.

3.15.6 update coming which resolves bugs in 3.15.0 and other problems I noticed unrelated to .0

>>7738
Polls are often used for feedback on the site, in which case I can get that data for myself.
If polls were used for recreation I would have a stronger reason to do this.

have to bump the number a bit, will be offline for a minute again.

Final 3 tasks before I've done all upgrades that I would call Kissu-Fr 3.x.y -> v4.0.0:

- Write a script that will relocate haiji files over to luna to increase disk space
- Write a system to hide boards like xmas, secret and the 3 off season boards to not appear in the recent feed json, option boards or the overboard json. Certain boards should not be findable without URL or cite.
- Update documentation in the FAQ.. improve the style of FAQ pages to look less ugly.

- Additionally any extra bugs or issues I catch in the process of updating.

On desktop, >>7726 now breaks like it did on mobile but the sound still works.

>>7399
>>7398
Doesn't work. The message thing will say "post cancelled" it whatever but when you try posting again, there'll be the first version still there. Dunno if they appear at the same time, or if the message thing just lies.

>>7746
The server can't forget the message if it got it after you cancelled.

I suppose it would be possible to tell you when you can no longer cancel.

It's not uploaded yet, but there will be a point in the upload process where it prevents you from cancelling. Unless kissu uses a different type of server it's not possible for me to cancel posts while they're being processed.

it annoying when I make new reply suddenly direct to catalog, not on thread

>>7752
use the noko option

in ~30 minutes some old files will begin to dissapear as I do an automatic and mostly automatic DB update and transfer of files between servers

hate sage

sage

Files relocated, so main server and second server both have the same disk space used. Hopefully this will last kissu until the servers roll over and I can get something else

Have some small fixes to upload.

Seems like I'm going to slow down work on the UI soon. No new features, small reworks of existing features and bug fixes. Probably cleaning up the code and making it easier to maintain.
I'd like to rewrite the backend eventually, but I think this is something that could get started in a year ~2022 around when the server is set to expire.

Thread will be remade soon to something for feedback and bug reporting rather than dev blogging.

>>7770
>I'd like to rewrite the backend eventually, but I think this is something that could get done in a year.
Nice. Hopefully in something better than PHP?

>>7771
Rust, but the language is above my skill at the moment.

The API server is in GoLang, Vichan in PHP. Go is an alright language, but everything about it has always seemed arbitrary most particularly the error handling and type handling. Feels like a language that's trying to please everyone and being mediocre all around.
Rust is a good language and scales well but it takes me too long to make something mediocre.

Using Rust feels like it will take a lot of wheel reinventing. Data will be transferred from MySQL to a read fast DB, features will have to be redone, security has to be secure, both UI have to be handled.

It's a major undertaking and it's not like kissu could start using a work in progress imageboard engine like the split old and new UIs.

There has to be a reason to do it basically and the reason and means to achieve the reason both don't exist as yet

>>7772
GoLang has the same problem as Python, where it's very opinionated for no good reason, and a lot of said opinions are stupid.

>>7773
The reason is that Vichan's codebase is abhorrent.

>>7774
abhorrent yeah, but I understand everything about how it works and have made some security updates to it already such as moving the passwords that Vichan tells you to put into your code on a file that can't be requested. And updating the hashes to a modern standard.

>>7775
That's fair

It only took 268 bug fixes/feature reworks, but I think it's reached a good point where it competes with the traditional imageboard design.

>>7777
nice numbers to commemorate this accomplishment

>>7777
lucky!

Post about it if an image you post get caught up in an image block.

Adding ~22,000 sock4 proxies to the ban list

Altered the PHP server configuration to better handle bot spam

>>7785
The happenings thread is an exception case where the old ui is priority for ease of archiving

more technically, it's because the URL "/qa/res/4165" will always use old and "/qa/thread/4165" will use your choice. This means switching UI from that page is more difficult

>>7787
Speaking of archiving, as far as I can tell there's no way to check the archives in the new UI.

>>7789
I guess I can make the URL functional, but no one uses them and it took anyone about a year to bring this issue up.

https://kissu.moe/qa/archive/ will go to archive, it formerly was broken.

Added in a saftey feature to create hard limits on threads and soft limit on posts if there are no mods around

some more alterations to handle heavy site load better

UI v4.0.2 small css things

Ctrl+Return in the sage field (maybe even in name field) posts the post but shows the post posting was canceled.

neat bug catch

>>7795
>sage field
Just realized I called the options field the sage field...

fixed it a bit ago but forgot to restart the server

wanted to finish a bunch of small tasks but binged 24 episodes of shinsekai yori and i've only slept about 2 hours...

At least binge a show that doesn't suck next time.

>>7809
i liked it. It was an interesting take on romance, morality, politics and the ends justifying the means.

>>7811
actually something even weirder is happening, it's not showing the dimensions of the image properly so it can't compensate.

>>7813
>What's the bot you're getting the iamges from?
Oh hold on, I know what's happening, when it goes through captcha it can't determine image size properly

>>7812
Oh yeah.
>>7813
Its https://twitter.com/senrankagurabot
Though, I don't think its the bot since the problem doesn't exist >>>/ec/4743, but exists >>75596 and >>75597.

>>7815
I know what the problem is now, it will just take a few minutes to figure it out.

I can't fix the ones that were already posted, but new ones ought to be fine now.

Also not sure if my fix caused other problems.
TDD really is a must for server development.

Seems like I'm only finding one or two issues with the UI a week now. Most of my problems are server side spam tolerance issues which I'm hoping to write a tool to better analyze this.

Currently on V4.0.4, hopefully sit there for a while for the laughs.

>>7833
could you upload it somewhere so i can test it?

>>7836
https://files.catbox.moe/oull13.webm

>>7837
seems to be result of one of my modifications so I'll look into it sooner rather than later

How funny, the sticky from /ec/ has disappeared from a bug in the API server.

When previewing your post, .jfif files don't actually show a preview of the image, but instead show that one template image of Di Gi Charat. JPGs work just fine, though. Even though a jfif is actually just a jpg.

Been making a spambot to test on this site... found an issue with antispam filters that doesn't stop bot spam. A well made attack could possibly use it

>>7870
Yeah, it feels like that feature is still underbaked, generally speaking.

>>7871
>it feels like that feature is still underbaked
Maybe just a little. I use it pretty often to make sure I did my formatting correct if I use something like blue. One simple thing that could be fixed is just making quote replies look the way they should rather than just being green.

Does copying a threads URL automatically convert it into a link? What I mean is turning https://kissu.moe/<board>/thread/<number> into >>/<board>/<number> or whatever? Also, cross-board linking should be explained in the FAQ, since it works slightly differently than on most imageboards.

>>7878
why don't you just try it

>>7879
Okay, I did. It works, but it doesn't show up in the post preview for some reason.

>>7880
Because the conversion is done on the server, the preview is basically taking in API data that is used to create the threads and creating a custom post out of it. The URL cite-link conversion is done on the server and having that in the preview requires me to write some extra code I considered low priority.
There's actually a fair number of preview functionality(post previews and the now abandoned rich text functionality) that I considered not as important as improving how the UI works and getting onto optimization and security.

updated to 4.0.6 which fixes some issues with the cards that show up if you link this site from a chat platform with URL previews. Made it so that you can tab into the QR submit and file buttons since that was unclear.
Some mobile and summary notification bugs.

Also added JFIF to previews which someone should confirm for me.

Resolved an issue with user delete speed,
was very slow and is now back to being fast

Going to do a temporary listing of /test/ today or something so I can test how the site performs when getting a flood of posts and the capability of stopping bot spam under the assumption that none of the proxy/tor bans work.

I'm beginning some tests on the server so performance might be degraded

Test scenario: None of the anti-spam messures work
Result: MySQL will catastrophically fail

Reality will be that captcha, antibot and proxy bans will filter out spam, but it shows that the site performance will completely die at 4/r9k/ levels of activity.

>>7896
>Reality will be that captcha, antibot and proxy bans will filter out spam,
from the looks of my current test my basic filters prevent spam from slowing down site use

In fact it does look like it could handle 11PPM after I changed the posts database's to use InnoDB instead of the Vichan preset of MyISAM.

I'll try the previous test I did earlier soon

>>7906
yes, I wrote myself a spam script to test how the site performs under heavy load and listed /test/ to get a real number.

see >>7904(Cross)

>>7907
oh...

>>7910
Say if you notice it again later, I resolved some issues I had with handling bot spam so I won't be doing any floods again.

>>7911
Sure.

I think /test/ should stay listed. No real reason to keep it a secret I think, it encourages people to test out things on the site and play around with making posts.

>>7913
Well, if /test/ becomes visible I need to move temporarily uploaded CSS stuff to a more... secret board. I guess it could work.

>>7914
I don't mean it needs to be visible, but I think keeping it on the sidebar wouldn't hurt anything would it?

>>7915
Uses up page space on something that no one cares about

>>7883
looks like jfif isn't actually working so I'll fix that.

Aside from this:
I've been thinking and I'm probably completely done with the front-end software.

The only question is if it's worth spending more time on the previews. I'm tempted to say that it's not worth it for reasons.

The preview is something that works in most cases.
If I list the scenarios where it doesn't work right:

1) Youtube videos for images
2) Converting URLs into Cites
3) Video thumbnails
4) Handling CORS errors

However it's main usage is:
0) Verify that your markup tags have worked properly
This, it does fine.

But I do realize that I made a mistake with enabling JFIF and the size of the thumbnails is off. That will take only a few minutes to fix. So I'll see how many of these issues I can cross off in a day.
In order of priority: 2 , 1 , 4 , 3

>>7937
And vice versa.

>>7924
If it were me, I'd still try to get the preview feature as close to complete as reasonably possible.

>>7937
Syncing post forms is not straightforward, but this might be something to try.

>>7939
Finishing all of those should make it complete. It would be an act of correcting discrepancies between what gets posted and what gets previewed after that, which is up to users testing the program.

looked into how 4chan handles these sorts of text walls
>>>/qa/76166
going to replicate their decision to autoinsert <wbr>, but need to also change the UI to accept those tags

Added in word breaks tags, meaning text walls get formatted properly
Added form synchronization. Syncing up files between forms will require another person asking for it.

Updated catalog CSS to look nicer and changed something about catalog hiding.

Altered CSS of font awesome icons that can be placed into comments

Fixed simple preview bugs/weirdness(no new features yet)

Looks like I've done the first set of fixes.
Markup might be broke somewhere I can't see, the usual, so report bugs..

Inadvertently, because of the custom markup functionality I added kissu allows you to add font-awesome icons to your posts. Icons from this set are available for posting.
https://fontawesome.com/v5.15/icons?d=gallery&p=3&s=regular,solid&m=free
If you think emoji suck because they're too colorful and want something more plain these are available.

to input them create an fas or far(solid vs regular) and then place the icon inside them:

[s fas]
[s fa-2x]
[s fa-blind][/s]
[s fa-blind][/s]
[s fa-blind][/s]
[/s]
[/s]

apparently a bug that i'll have to resolve
] is ]

>>7946
kewl 

[s fas]
[s fa-2x]
[s fas fa-american-sign-language-interpreting][/s]
[/s]
[/s]

I said the &# 93; is a bug for ]

>>7950
I don't have a degree in CS, I'm just a mere nuclear physicist.

The markup system is very free form, as a result if you input things wrong it might render the entire post as garbage.

>>7950
oh, I thought that putting HTML entities into [code] wouldn't convert them but it did >>7947

you broke it https://kissu.moe/jp/res/21765#21767

>>7956
yeah, [sjis] and [code] aren't doing what I want them to. There's a chance I can edit-fix it quick

Syncing is awesome! Thanks for finally doing it.

>>7959
the text is good, but doesn't sync the files yet

><a onclick="return highlightReply('7959', event);" href="/b/res/6312#7959">>>7959</a>

i'm trying to test something while cool's stream is happening

resolved a bunch of markup issues (i think)

Last things on my list for today are the 4-5 preview additions.

I just noticed that you can't preview posts from the form at the bottom of the page. How much trouble would it be to add that?

>>7965
uh, kind of. There's only one preview so the toggles need to be linked and there's also the question of who's file gets used since those aren't linked at the moment

So with that out of the way, all issues have again been solved.

>>7983
>>>/qa/76166

>>7983
The current version's way better, what are you smoking?

>>7986
is joke

I'm going to be creating a new dev thread since the site's software is stable for the foreseeable future and dev' isn't a major issue. I guess just a generic admin and dev QA thread.

On this I want to resolve an issue relating to >>>/poll/1554
This issue is backed by the reasoning behind prior creation of >>>/jp/

Thread perma status off

>>6746
she has a big head lole

The rare bot spam