SEN's unicode parser is a little inconsistent (particularly with name suffixes )

Looks cool af.
I need to redo SEN though.
So little time.

EDIT: Yup, I need want to redo SEN.

Post has been edited 2 time(s), last time on Jul 30 2015, 9:14 pm by Devourer.

I cannot write portal news. When I want to post it, it won't be added.

Bug report: uploading files to the DLDB gives the following error:


Where <mid> is the Member ID of the uploader.

Can someone fix SEN to not be amazingly slow, laggy shoutbox, laggy opening posts etc.? I don't know any other site like this that's not hosted on someone's potato in Slovakia. I'll do it after exams if no one else will/can.

- SEN is faster again, thanks to Roy.
- You can now upload files into our SC1DB again. Edit: something else is off; I'll get back to it.

Post has been edited 1 time(s), last time on Oct 2 2015, 11:45 pm by Devourer.

http://www.staredit.net/wiki/ wiki is gone ggggggggg

Quick adjustment: when enlarging an oversized image, it is now bound to be at most your window size in dimensions.

Resolved critical errors upon attempting to upload files containing certain characters to our system.

It would be nice, especially for mobile devices, to change the shoutbox form so that it is not considered as saved form data. Highlighting the form for typing in Firefox on Android {and on Windows) will bring up form history for the form, which is annoying and obstructive.

Someone mentioned they like having that history as an amusement -- I agree, but I think the present state of the form has hampered usability.

What's something someone could learn to do to help you with coding?

Right now, just PHP, HTML/CSS, and JavaScript would suffice for minor contributions. More specifically, we're looking at utilizing WebSockets, and since SEN runs on PHP, the most sensible option seems to be Ratchet. This would require a significant overhaul of our JavaScript and server responses, but it would be a major gain in terms of performance.

We also need to move the frontend to source control, though I haven't heard much on that front. Regardless, having basic knowledge of Git may be useful in the future if we ever move away from FTP hell. There is very little consideration in the works for setting up environments, so if you have any build engineering or continuous integration experience, that would be welcomed.

Another point that isn't oft discussed behind the scenes is the database. As you may know from the many errors from days past, we use MySql, and more than likely in an ineffective manner. I suspect we're lacking or misusing indexes in many areas (we didn't even utilize any full text searching until recently), but I personally don't have access to the database end (nor do I particularly want it, to be honest). Our data access layer is non-existent, and while we sanitize our queries I don't recall if we're actually using prepared statements. Making CRUD sprocs would probably give us a performance gain, even if it's the wrong way to solve the problem.

More ambitiously, if we can get Node on the server and utilize some useful packages like Gulp and Bower, it would really help manage easily automated tasks like minifying files (which we currently manage manually). Then we could even use a CSS language like Sass.

Our JavaScript would be a lot cleaner if we used a proper SPA framework like AngularJS, so if you want to learn that, feel free. However that's more of a Pipedream than something you should anticipate.

An issue we had after v6 launched was too many cooks (people overwriting each other's changes), so I can imagine Devourer being hesitant on pulling in more developers, at least before source control is in place. But if you're interested in contributing Someday(TM), those would be the areas to hit.

TL;DR: PHP, MySql, JavaScript, Ratchet, Git, JSON.

I know those. Can I help?

Post has been edited 2 time(s), last time on Apr 8 2016, 2:38 am by Roy.

Fixed. Also fixed an issue where some browsers weren't doing spellcheck on the textbox.

Not sure if this affected anything, but autocorrect no longer works for me in the shoutbox. There aren't even any suggested words that appear above my keyboard. I'm on Android using Chrome.

It did indeed: desktop and mobile browsers use the HTML 5 attribute "autocomplete" for different things, it appears. Applying it directly to the field caused Android to disable its word suggestions and autocomplete, but it seems to work if the attribute is applied to the entire form.

Tested on Firefox and mobile Chrome. Let me know if there are any more issues.

Post has been edited 1 time(s), last time on Jan 26 2016, 6:32 am by Roy.

I've been going through the bug list doing some housecleaning and trying to knock out some of the low-hanging fruit.

Unable to reproduce:

Let me know if any of these issues are still persisting.

Fixed:

Let me know if you spot any regression caused by these changes.

Features from v5 implemented since last update:


Post has been edited 2 time(s), last time on Feb 7 2016, 4:10 am by Roy.

Any chance Youtube embedding could be switched to HTML5 instead of Flash?

Updated recovery-scripts.

New posts and edits now use the youtube-HTML Player.
I'll eventually run a script to adjust the old posts.
Done


Post has been edited 1 time(s), last time on Mar 31 2016, 5:24 am by Devourer.