sfteus

That's interesting, I appreciate the heads up. I'll have to see if I can find some other workaround whenever that pops up.

Even more scary with the Yahoo account in particular, I have it set up as an app-based authentication, so I get a popup on my phone if someone tries to log in. However, when they (I assume) clicked the "I don't have access to this, send an SMS instead" message, that notification immediately disappeared, so I didn't even have time to hit the "don't allow" button before it was no longer an option.

Google at least seems to have this right, in that when they attempted to do the same with those, the notification was still there. I also received a separate "request to reset account password" which stated it would take like 15 days to occur, and I was given the option to cancel it.

Regardless, I think I'm going to try to go hardware key with an TOTP app backup for 2FA going forward, wherever possible.

Yes, we have a PIN on the account. They did ask for it in store when I went to get a new SIM card.

The main e-mail they targeted was included in several breaches, specifically of note the CafePress and Yahoo breaches, but various others as well. I would wager they just compiled data from each until they found something that worked.

Had this happen to me last week. Thankfully they only tried to get into a few e-mail accounts, which I was quick enough to get into, kill their session, and recover them before any real damage was done. AT&T of course claimed it was impossible for that to happen, despite a different phone showing up in my account, a bunch of unexplained SMS messages I never received, and two calls accessing my voicemail that I didn't make.

Currently working on finishing moving passwords from a Google account to my password manager and resetting them all, as well as replacing anything that uses an SMS 2FA with a time based authenticator or other alternative where possible. Planning on getting a FIDO key to use where I can. Also setting up a Voice number on an account that's used for nothing else besides 2FA in the instances where there is no better form of authentication.

To keep it simple, it was originally created as sort of a helper instead of a full-fledged language, and just kind of grew into that. As such, its early years were plagued with architecture, security and performance issues, as well as many "gotchas" that could wreak havoc on amateur programmers that tended to gravitate to the language. Couple that with the fact that the maintainers drug their feet in implementing modern paradigms found in other languages and fixing the latter issues in the name of backwards compatibility, and that at the time most PHP knowledge bases were years out of date, and it was a recipe for a poor ecosystem all around.

PHP 7.0 took a huge step forward by straight up removing old extensions that weren't maintained, focused a lot on performance and allowing more strict standards, and tons of new improvements. In addition, more modern frameworks like Symfony and Laravel started to pop up, which helped reduce the stigma of it just being a "scripting" language and made it very pleasant to work with.

I maintain a PHP app that was originally written in PHP 4, and one that was created in PHP 7 and the difference is night and day. I maintain a few Ruby and Python apps as well, but even having used these more often PHP still tends to be my go to for prototyping.

Correct, assuming a dedicated circuit in the US, code dictates that it'd be 1440W and 1920W for a 15A and 20A outlet, respectively. Continuous loads can only pull 80% of the max circuit load.

In theory, you could also run a 100% rated breaker to pull more power, but the car would have to be able to support it as well.

Cool idea and presentation, especially considering the state of some other game server companies.

However, I, along with probably many other people, would not give you any personal information without seeing a pricing scheme up front.

On top of that, it's the difference between monthly costs for the company. Netflix, Spotify and Gmail all have monthly costs in terms of storage space, bandwidth usage, server maintenance, etc that users are directly affecting. You're paying for the content to always be available, to be available quickly and to not have limits on what you can and can't access.

Desktop software on the other hand has no direct monthly costs other than phoning home once a month. You could definitely argue that iterating development costs should be factored in here, I can't imagine that being a deciding factor in moving completely to this business model. I'm sure if they offered a low cost monthly subscription and a perpetual license option, they wouldn't have any issue offsetting development costs. At this point, they could even raise the price of perpetual license (hell, I seem to remember paying $200 for mine). I'd gladly pay an increased price with the knowledge that my software wouldn't stop working, especially given how many hours of productivity I gain by using their software.

If you don't mind me asking, do you populate the initial listings on the job board by your self (by finding job listings and posting them), or leave it empty upon launch and just offer a period of free listing to get started?

Location: DFW Area, TX

Remote: Yes

Willing to relocate: Not Currently

Technologies: PHP, Javascript (BackboneJS, jQuery, Node), MySQL. Basic linux server administration skills including cloud services, some knowledge in other languages such as Java, Python and Ruby/Rails. Some experience in Android/iOS. I pick up new languages and frameworks quickly.

Résumé/CV: http://tinyurl.com/lz66zbm

Email (Base64): ZXRoYW4uc2FycEBtYXZzLnV0YS5lZHU=

Full stack developer for a small start-up like company sponsored by a University. Looking for a similar environment.

I see on the about page that you built the site with Waigo and Mongo. If you don't mind, could you go into a little bit of detail about the hardware you're running the site on? I had a similar scope site in mind (a few static pages and a form or two) and would like to get an idea of what it would take to run it with minimal issues or bottlenecks.