-
chevron_right
Allo All!
chunkimo · Wednesday, 30 August - 08:29 · 1 minute
I am going to hope that with my previous experience with Movim that some of the odd functions appearing not to work are just going to "magically" work one day or at an hour of some odd time, whenever.
Last time I was like sigh shit just whyyyyyyyyy not it work, then a few hours later, poof! that one or two things that weren't quite working in this app did work then,, and after then on. Javascript being such a high level language this is sort of.. Pretty much untraceable and undebuggable. I'm sure maybe someone reading this would beg to differ, but would you really wanna try? I didn't think so.
It's 100% nice as hell to see this again though. Timothee (aka edhelas) the dude that wrote this original code, that I've only I've changed some CSS and some whatever stuff in the git repo, made this one hell of a nicely polished web application using websockets.
Also I'd like to add that I made this instance work VERY QUICKLY and EFFORTLESSLY. That was appreciated for sure, but apparently sometimes I know my shit and can hack it.. lool other times I am fail b0t. begin <segfault>
Lastly I putted some stupid stuff up in the Explore part of this app. I had debated a while before today already on whether I would make this web app (as it's configurable in my admin settings for here) just use chats, and not the pubsub extra features. I think a good amount of the reason for this is because TooFast.vip is currently less than 24hrs old and running Prosody. Prosody has a bunch of access control limitations that eJabberd doesn't. Hence last time I ran an movim places I used ejabberd and this app was a much much much better experience.
While u r here, watch out for those squirrelz. They're pretty big and gnarly lately, carrying knives and starting fires and sheiiz.....
#toofast #movim #news #chunkzwarez #morefast #hardcore4life #noreasongiven