maxmorlocke

We review the web presence of a business as our core product offering for payment processors, etc. as they look to onboard ecomm merchants. This (and techniques like it) make a great way to find scummy actors and have a proveable piece of evidence as opposed to a 'yea, this looks off' or 'this doesn't fit the profile of what an established business looks like'. We leverage a lot of subtle signals like this.

ZoomInfo is in the same general area on quality and the price per record is competitive, but they have historically required a high minimum annual spend and have a reputation for litigiousness. There are a few other large players (e.g. apollo), a few medium sized players (e.g. coresignal, mixrank), and some smaller players (e.g. thecompanies, bigpicture). There are also a lot of other folks who are not as api-oriented and are more focused around the sales/marketing experience (e.g. seamless.ai)

For a typical db.t3.xlarge instance, you're talking about 29c/hour vs 27.2c per hour. That's $157.68 as the total difference for one year's runtime, when the whole instance cost for postgres would be $2540.4 for the year, or about 6%. The larger the machine, the closer to parity. Given the absolutely small difference, I hope this isn't the dividing line in any commercial project.

Generally speaking, it's inadvisable to 'discard' migrations with django. If the migration set is getting too large, the general practice is to 'squash' migrations, which is a django-supported function for merging the migrations down to a single app. You can do the less blessed, but more simple function of nuking the migrations, updating the migrations table, and remaking your migrations... but you have to coordinate that in every environment.

For an existing database, you can easily create django models for each table, etc. There's a --fake option to update the migration table to make it think you've applied these migrations, but not actually apply them. This convinces django you've brought the database in sync. May your deity or deities help you if you did not actually bring it in sync. I've used this quite a bit in some java ee->python migrations I've done in the past.

I think this is a really naive idea, I think you're seriously underestimating the level of complexity in a real estate transaction. You're dealing with what is for many people is the most impactful and expensive purchase of their life. In that transaction, they have imperfect, limited knowledge of the market and acquisition process. Further, there are varying levels of dishonest actors within the process - with an extreme range of dishonesty present. Top that off with the fact that you're actually negotiating with imperfect information as well... :exploding_head: Having an actual expert present who can enable you to be successful is extremely empowering and much more likely to result in a positive outcome.

Now, all that being said, it's obvious there's a deficit of actual SME's who are extremely helpful in the process. I've purchased two homes... one with an agent who I feel would fit right in with the culture of the used car salesman stereotype and another who actually was that SME. She knew the market inside and out, knew what to look for in the neighborhoods, and found the problems in each house we looked at. She had connections that got us through a weird mortgage issue (multiunit home converted into one with... sloppy paperwork), helped with specialized inspections (radon issues), and provided great advice when dealing with a cantankerous negotiator. I certainly didn't find my money wasted there and actively recommend her for anyone in the NW Columbus, OH area. There's a lot that could be done to improve the situation - higher requirements for education and qualification of realtors, prohibiting companies from being the buyers and sellers agents, etc. There's a lot to automate as well. But when there's serious complexity and life changing quantities of dollars floating around, an expert should be strongly valued.

Our latest release should have more clear language on airports and 'All London Area Airports' as opposed to 'City of London Airports'. The point about multiple airlines should also be addressed.

Your point about at a glance determination of the departure/arrival airport is really good. I expect to have a UX enhancement for that next week. Currency and manually selecting multiple airports are still a fair ways off.

Thanks. Our roadmap isn't currently public, but this is on it. That being said, this is a medium-term priority, so definitely not something coming in the next couple weeks.

Works in all Chromium browsers actually. Support for Firefox and Safari is on the way, but does require some more work.

As a simple example, United probably isn't going to offer a flight where one leg is on United and another is on American. Yet, it might be substantially cheaper or less painful to take that flight. Certain codeshares may be more profitable for them to hawk, to the point where they will only show certain legs when the more profitable flight is booked. They may also choose not to show flights that are already profitable based on bookings (e.g. takes 75 economy seats to make flight with legs A->B and B->C profitable) when a similar flight (A->D, D->C) is underbooked and could use some more folks aboard. There are probably a thousand other reasons...

Your gut reaction is not wrong. That being said, I think it's wise to pick the right time to leverage this capability. Our resources are extremely limited at the moment in comparison to one of the most aggressively litigious entities in our space.

I don't know which is the biggest, there are a lot of known unknowns still floating around. Will we run out of money before we monetize? Will we have to deal with constant lawsuits? Will other innovators in the space attempt to move in our direction? Are there enough travelers willing to install an extension? Will google be google and shut us down? The ever present bus factor. All of these are legit concerns that are going into our crowdfunding risks disclosures. All are things to manage.