[kaeawc]

We had 20 minutes notice, and then everyone was kicked out of the Slack support channel and API responses simply died. What the actual fuck. They have mobile client SDKs out in the wild that are now just eating up battery life as they retry an impossible query forever.

[jasontan]

That sucks. We (Sift Science) have been building something similar for 7 years and aren’t going anywhere. If we can help, please ping me - jason at siftscience dot com

[csomar]

> We (Sift Science) have been building something similar for 7 years and aren’t going anywhere.

But that doesn't come with any actual guarantees does it?

[glitcher]

> and aren’t going anywhere

Yet... that you know of.

Nothing specific against Sift Science whatsoever in my comment, but many, many times this sentiment has been conveyed by companies and it rings hollow IMO. There are a lot of different ways a company can change or disappear at some unforeseen point in the future, and claims that "you can trust us to be here forever" do not carry much weight for the large group of experienced users, devs, management, etc who have been burned multiple times.

[cortesoft]

So are you implying that you should never enter into a business relationship with another company?

Clearly, you need to always be prepared for your partner to go away, but you still have to work with other companies.

[sushid]

I think the parent commenter is just saying that it's not something you can actually believe, just like a company saying they'll never sell your data.

Sure, that's the intention but when someone comes around waving a checkbook, they can in turn buy you and shut you down, sell your customers' info, etc. Sure, its not YOU allowing that to happen but by ceding control you essentially allowed that to happen.

[rococode]

"You can trust us to be here (until enough money comes our way)" is just how it is for most businesses like this. An unfortunate, and in my opinion largely unresolvable, side effect of an ecosystem where specific useful tools are hard enough to create and manage that full companies have to be formed around them.

[koliber]

What kind of guarantee would be satisfying?

[scarface74]

A third party code escrow account with instructions on how to build the service and a contract that specifies conditions when a customer gets access to that escrow.

I've been on both the customer and service end of such agreements.

[nielsole]

Is there a popular provider for doing this? It sounds like a lot of work to find a solution in which both parties trust (both technically versed and reliability wise). A common notary probably wouldn't cut it, right?

[scarface74]

Both companies I’ve worked for - as a client and a customer - used Iron Mountain.

http://www.ironmountain.com/information-management/software-...

[detaro]

There's a bunch of companies doing it, some dedicated, some as part of larger related offerings. E.g. I know NCC Group (large IT security company) does offer it, TÜV (which does all kinds of certification and compliance work), ...

[csomar]

The contract should specify. The contract probably was sided on smytes favor. Screwing even paying customers.

You can have a contract where you specify indemnification of damage in case the business ceases operations, goes bankrupt, get acquired, etc...

[koliber]

A guarantee is only as good as the guarantor. A guarantor can be a company providing a service, as well as all sorts of assorted guarantees about said service.

In time, the situation can change. The product can get sold. Cash can be spent. The guarantor can no longer make good on its guarantees.

You're back to square one where the guarantees are as worthless as the original service.

You need 3rd party backing (insurance) in such situations, but that costs money. This money is a cost which makes competing against unbacked entities tougher.

In most cases, you can not have 100% foolproof guarantees of anything. The closest I can think of is governments standing behind their banking institutions. Even there though, governments have defaulted on their guarantees.

The world is not a stable, perfect, and cut-and-dry place as many would like to believe. It is dynamic, and ultimately backed by trust.

[raesene9]

It's much harder to mitigate this kind of risk in the world of services as against purchased software.

The problem has always been present especially when larger slower moving companies buy from smaller, riskier, companies.

In the days of software, code escrow was possible to mitigate some of this kind of risk. That's still got it's costs but can be an effective hedge against a supplier going bust.

[TheSpiceIsLife]

The parent comment is justified.

While you can have a contract that indemnifies that isn’t going to help your going concerns when the other party just pulls the plug.

[rocqua]

I think company bylaws that prevent a 'triangle merger' like this might be useful.

[tixocloud]

Do you have a high level overview of what I’d need to do to get started? Are there any specific areas you specialise in as opposed to general users and what information will I need to share with you?

[brazzledazzle]

Shockingly bad. I wonder if they shitcanned the whole technical team and they turned the lights off on the way out. Not that it’s really much better but at least it wouldn’t make sense.

[hsaliak]

And there will be absolutely no consequence to these actions. Completely messed up!

[Tommek]

I hope you think over that design the next time. Put it in the cloud they said ...

[kaeawc]

I actually ripped out Smyte's Android SDK because of how bad it was and replaced it with my own implementation against their API which has a hard limit on retries. But I imagine that other customers were using their SDK and still have live apps out there using it... not good :/