No.7884
Resolved an issue with user delete speed,
was very slow and is now back to being fast
No.7885
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.
No.7895
I'm beginning some tests on the server so performance might be degraded
No.7896
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.
No.7901
>>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
No.7902
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
No.7907
>>7906yes, I wrote myself a spam script to test how the site performs under heavy load and listed /test/ to get a real number.
No.7911
>>7910Say 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.
No.7913
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.
No.7914
>>7913Well, if /test/ becomes visible I need to move temporarily uploaded CSS stuff to a more... secret board. I guess it could work.
No.7915
>>7914I don't mean it needs to be visible, but I think keeping it on the sidebar wouldn't hurt anything would it?
No.7916
>>7915Uses up page space on something that no one cares about
No.7924
>>7883looks 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
No.7939
>>7924If it were me, I'd still try to get the preview feature as close to complete as reasonably possible.
No.7940
>>7937Syncing post forms is not straightforward, but this might be something to try.
>>7939Finishing 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.
No.7941
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
No.7943
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 [s fa-anchor][/s]
Fixed simple preview bugs/weirdness(no new features yet)
No.7946
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=freeIf 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]
No.7947
apparently a bug that i'll have to resolve
] is ]
No.7949
[/s]
[/s]
No.7950
I said the &# 93; is a bug for ]
No.7952
>>7950I don't have a degree in CS, I'm just a mere nuclear physicist.
No.7953
The markup system is very free form, as a result if you input things wrong it might render the entire post as garbage.
No.7955
>>7950oh, I thought that putting HTML entities into [code] wouldn't convert them but it did
>>7947 No.7957
>>7956yeah, [sjis] and [code] aren't doing what I want them to. There's a chance I can edit-fix it quick
No.7959
Syncing is awesome! Thanks for finally doing it.
No.7960
>>7959the text is good, but doesn't sync the files yet
No.7963
i'm trying to test something while cool's stream is happening
No.7964
resolved a bunch of markup issues (i think)
Last things on my list for today are the 4-5 preview additions.
No.7965
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?
No.7966
>>7965uh, 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
No.7976
So with that out of the way, all issues have again been solved.
No.7986
>>7983The current version's way better, what are you smoking?
No.8002
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 No.8982
>>6746she has a big head lole