- Viewing Profile: Reputation: Pyro699
Pyro699Member Since 06 Oct 2010
Offline Ninja Mode!
- Group Administrator
- Active Posts 1,406
- Profile Views 14,983
- Age 27 years old
- Birthday August 16, 1990
Mainly creating Artificial Intelligence scripts to solve complex games :)
Posted by Pyro699 on 15 March 2018 - 02:32 PM
I guess I'm just excited to find a community outside of Facebook AND i don't have to hide that I cheat lol
Posted by Pyro699 on 14 March 2018 - 07:46 PM
I, along with a couple of others, use slack at our place of work and adding an additional workspace is easy. I am able to communicate quite quickly and effortlessly with members of this community while I am supposed to be working. This, if anything, has helped reduced some of the other pain points of the site where when something would go wrong it would take much longer to figure it out. I would need to be sent a pm or email and then have to check my personal email.
Salade and Romy - I do not see either of you being very active within slack
Posted by Pyro699 on 08 March 2018 - 09:46 AM
Posted by Pyro699 on 07 November 2017 - 09:44 AM
Posted by Pyro699 on 12 October 2017 - 07:07 PM
Posted by Pyro699 on 05 March 2017 - 09:13 PM
recapcha is done by google and i seriously doubt that there is any way around them other than the "robot" described above. The newest version of recapcha will actually only appear if it thinks you are a robot and not even require you to click every time.
Posted by Pyro699 on 12 September 2016 - 01:47 PM
Has there been any recent development upgrade on the site? Maybe it's a case of you something got fixed and broke something else scenario.
Another thing is you might want to check for the logs. That should give you an idea on whats going on.
And also might wanna check if the server had some automatic updates done. Sometimes those screw things up to and would require some hotfixes.
You guys are awesome! Keep up the good work. I know you'll be able to fix it.
a) No we have not done any upgrades or changes to the software.
b) We are knowledgeable enough to know what logs to look in. This included us paying close attention to the server access logs to see who was connecting from what ip and with what useragent. It was must more complicated than we originally would have though.
c) with where we are running our servers, we are in control of everything - there are no automatic updates that could have been applied. But I do agree with you that autoupdates suck and break a lot... Most recently windows 10 autoupdated and broke my virtualbox setups - great times.
We are planning some server fixes and updates that will hopefully reduce the possibility of this happening again.
Posted by Pyro699 on 10 September 2016 - 10:08 PM
The problem with that is that "pokecoins" are technically currency of what ever platform you are using.
android: playstore dollars
ios: itunes money
Not as simple as it might appear from the outside But if i can think of a solution - sure
Posted by Pyro699 on 10 September 2016 - 09:21 PM
We are not here to make money. The only reason we have any kind of monetary typed system going on is to help fund the uptime of the server and it has currently let us down. We didn't feel it was right to charge when the service was not providing what we had originally promised. It is nothing out of our pocket to give back to the community that has helped this place become what it is today.
If you guys can think of other things to try and make this place better, please let us know and we will see what we can do
And before you ask Drak - No, we will not bring back the negative rep system.
Posted by Pyro699 on 10 September 2016 - 02:44 PM
So as you may have noticed recently, Codex has been experiencing some downtime over the last few days. Yesterday, I finally went all in and turned a bunch of things off so that we could get a handle on what exactly was going on. Usually when something like this happens, the fix is quite obvious and I can take care of it in a couple of minutes. This time however, it required getting the old team back together and digging in real deep. Yeah, that's how bad things got - I had to call @Hydrogen (3 times - which brought back memories of the hydro-zone). @ShadowLink64 showed up to help us, and even @Waser Lave made a slack account so that we could talk and figure out what was going on. All very nostalgic and brought a tear to our eyes... However that tear was quickly wiped away by our frustration of the server unresponsiveness. No matter how many times we would bang on it, things just wouldn't shake loose.
At the root of the problem, something was taking all of the resources - and by "all of the resources" I mean that we would idle at around 160% CPU useage, so it was a little difficult to do testing while letting members onto the site. You might have noticed that there was a "403 Forbidden" message that appeared for you on the site earlier yesterday afternoon. This was in no way to imply that you were banned, we did receive an email inquiring about this and I wanted to clarify why it was that this was done at all. Basically, on the server you have the original contact on the server, then you go to the managing application and then you connect to a database of some sort. The usage spikes came in from the bottom two layers, so we cut off access for everyone at the server layer so that we could actually log into the server ourselves and figure out what was happening. I apologize if this caused anyone confusion yesterday, I am sure you eventually noticed that I replaced that message with one that had 'a little' more detail.
At the end of the day we still do not know what the root cause was, we have a couple theories but after 3 days of debugging we just decided to split up some of the server resources and have our database separate from the core of the site. I cannot promise we won't have another downtime like this, but if it does happen again, we will be able to track down the source a little easier.
With that in mind, I realize that some of you lost out on your subscriptions and would like some compensation for that. We are going to be extending all existing subscriptions by 2 weeks. We are also going to enable all advanced features (within the program manager only) for non-advanced members for a period of 1 week. Hopefully this makes up for some of the downtime that we have had.
Hope this explanation made a bit of sense to you.
- Neocodex Administration
Posted by Pyro699 on 02 August 2016 - 06:47 PM
Just a quick note to let everyone know that @Rocket has stepped down from her position as the private lead. Let's thank her for all the hard work she has done
With that position now vacant, I would like to also announce that I have promoted @Coops as the new private lead, I am sure she will do great.
Posted by Pyro699 on 09 June 2016 - 11:53 AM
As some of you may have already heard, there is a NeoCodex meetup planned for distant future. I have made my rounds across The US and Canada and met up with a bunch of you guys already but think that it would be a great idea if we hold some kind of event where we can all meet up together. We will spend the next few months picking out a location where we will meet and from there we can narrow down the specifics.
We have been having an active conversation on the topic in our slack channel, please feel to come talk about it. http://www.neocodex....x.php?app=slack (Join #codex2017meetup)
Here is a survey that will help us figure out where it is going to be. I have picked areas that are easily accessible to other members.
Update 1: I probably should have included this in the initial survey, but please fill out this survey so I can collect information about the locations of those interested in meeting up:
I have closed the survey, If you are interested in joining and have not had time to fill out the above survey, please send me an email at [email protected]neocodex.us. There are currently 17 people on the list.
The information shared in this survey will remain confidential.
List of people currently confirmed to go:
* This main post will be continuously updated as more details come through.