Discussion in 'news' started by Mars, 17 Nov 2010.
deleted numerous spam accounts recently registered. more will be deleted soon.
tomorrow we will undertake an update to the core (v1.1.2).
changes made today:
changed the way we do rendering. the only advantage is it is now far easier to update the core without needing to manually check/revert/reimplement the scores of customisations we make to the core at every update. these customisations are now kept separate from the core and are injected into the core templates whenever templates are rebuilt
updated tapatalk. tapatalk themselves have migrated from vB to xenforo, so we expect tapatalk to make xf a priority now.
dropped forumrunner. forumrunner was recently acquired by internet brands (iB), the same company that acquired vBulletin then ran it into the ground. not only is iBs official vb app in a state of stagnation and neglect (with many customers demanding refunds) but iB have further been known to mine the usage data of their customers to further their oldest business practice; buying out communities and monetising them with advertisements and skim/vig links. they are also the same company that ripped off thousands of vB admins when they released vb 4.0 as a presale, then filed legal actions against xf for no other reason than to bankrupt the upstart. iB and their products have no place at gV.
made changes to conversations. it should now be easier to know who is participating in a conversation and whom was the last to reply to the conversation.
testing core 1.1.3 in a dev sandbox.
corrected an issue with the upload function.
there are currently no plans to update core to 1.1.3. the slight benefits do not justify the work required.
made further changes to the upload feature.
made updates to the server, including httpd, php, mysql, and various dependencies.
there has been a marked upswing in spam this week. we will be both deactivating dormant spam accounts (no posts and no avatar) and implementing less forgiving registration screening in the coming days.
we have been investigating the spam situation and have come to learn that one of the more infamous spambot tools has updated itself to be 'compatible' with xenforo. other sites have fared very bad, receiving hundreds of registrations and spam threads since saturday (actually that was friday in most of the world?). fortunately gotVirtual already had spam measures in place. while a handful did get through, we have successfully filtered over 400 spam registrations since saturday.
new registrations have been temporarily disabled.
registrations are open again.
seeing as how spammers are consistently cracking recaptcha, we have moved on to something a bit different: keycaptcha.
the gV culture regarding registrations and new user approval has always been to leave this in the hands of inhabitants as much as is possible. for that reason manual approval or an 'airlock' node for new arrivals that requires mcp intervention is not ideal. it is possible that in the future, should spamtrap apis and captchas consistently fail, we could airlock new arrivals and release them upon reaching 'inhabitant I' status (3 posts and 10 likes). hopefully that will not come to pass.
contact us and forgotten password captchad forms now work as intended.
changed the way spammers are submitted to apis.
working on expanding the current 'like' functionality.
in a few hours we will begin work updating various machine packages and software. this will cause the website to be up and down for approximately one hour.
a maintenance mode notification will be active for the duration.
after having been reviewed, three epic threads have been retrieved from /dev/null and can now be found in area17.
we are making various changes to the core. things should not seem much different immediately afterwards, but there are bigger things looming on the horizon.
sorry for that.
server issue fixed.
investigating server issue.
vbulletin vs xenforo lawsuit is over.
testing core 1.2b in a dev sandbox.
there are many new features, both back and front.
will update tapatalk and other 3rd party things once we are running 1.2.
sorry for the up/down time today.
testing core 1.3 in a dev sandbox. 1.2b was skipped due to the work:benefit ratio, but it looks as if 1.3 is going to happen beyond doubt.
just a quick note to address the 'heartbleed' openssl vulnerability you may have heard being discussed everywhere on the web: gotVirtual has not been impacted by this exploit as neither gV nor the gV server run openssl.
it would be wise to change any email passwd though, as a compromised email address makes it relatively easy for an attacker to use 'lost password' mechanisms to more or less hijack the majority of your accounts.
replacing a 3 year-old setup and laying the groundwork for core 1.3:
migrated gV to a 64-bit environment.
updated kernel 2.6>3.14
doubled our amount of ram to 2GB ddr3
vCPU is now 2 cores of Ivy Bridge E5-2680.v2 on each slice
moved to ssd drives
within the next 24 hours we will be undertaking all of the following:
updating the webserver
updating various ancillaries and dependencies
updated the webserver
updated various ancillaries and dependencies
next: update the core to 1.3.2