6 ms·

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 cl

by kaeawc 8y ago

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.

brazzledazzle 8y ago
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.
deleted 8y ago
[deleted]
hsaliak 8y ago
And there will be absolutely no consequence to these actions. Completely messed up!
bdfsvbyudflsvg 8y ago
Oh please. Don't pretend that battery destroying, relentlessly network hogging apps are a good thing. No app should retry an impossible query forever. This is not the same as some sort of laughable abstinence-only birth control policy, where you get to roll your eyes, and say "yeah right. good luck with that." What's more, an app that hits the network of an uncontrollable third party, should always check with a controlled system periodically, to verify that the third party shall continue to respond predictably, as a sanity check. And beyond even that, if the sanity check within your own domain, for your own app that you created, and are responsible for, is unresponsive, it really should cripple the app's connections to things you don't control. Finally, as one last safety measure, if your status/activation end point dies, and your native apps go dormant, you should expect to be able to re-activate them with a number of channels, including emails, push notifications and new releases that up-version the app. If you build your kingdom within a walled garden to begin with, and rent all your tools of the trade from an external platform, expect to behave as a subsistence farmer.
jasontan 8y ago
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 8y ago
  > 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?
  - koliber 8y ago
    What kind of guarantee would be satisfying?
    - csomar 8y ago
      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...
      - TheSpiceIsLife 8y ago
        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 8y ago
        I think company bylaws that prevent a 'triangle merger' like this might be useful.
        unilynx 8y ago
        what's stopping the company owners -who are generally the ones executing such a merger- from changing the bylaws ?
Tommek 8y ago
I hope you think over that design the next time. Put it in the cloud they said ...
- kaeawc 8y ago
  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 :/

by kaeawc 8y ago

brazzledazzle 8y ago

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.

deleted 8y ago

[deleted]

hsaliak 8y ago

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

bdfsvbyudflsvg 8y ago

Oh please. Don't pretend that battery destroying, relentlessly network hogging apps are a good thing. No app should retry an impossible query forever. This is not the same as some sort of laughable abstinence-only birth control policy, where you get to roll your eyes, and say "yeah right. good luck with that." What's more, an app that hits the network of an uncontrollable third party, should always check with a controlled system periodically, to verify that the third party shall continue to respond predictably, as a sanity check. And beyond even that, if the sanity check within your own domain, for your own app that you created, and are responsible for, is unresponsive, it really should cripple the app's connections to things you don't control. Finally, as one last safety measure, if your status/activation end point dies, and your native apps go dormant, you should expect to be able to re-activate them with a number of channels, including emails, push notifications and new releases that up-version the app. If you build your kingdom within a walled garden to begin with, and rent all your tools of the trade from an external platform, expect to behave as a subsistence farmer.

jasontan 8y ago

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 8y ago
> 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?
- koliber 8y ago
  What kind of guarantee would be satisfying?
  - csomar 8y ago
    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...
    - TheSpiceIsLife 8y ago
      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 8y ago
        I think company bylaws that prevent a 'triangle merger' like this might be useful.
        unilynx 8y ago
        what's stopping the company owners -who are generally the ones executing such a merger- from changing the bylaws ?

Tommek 8y ago

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

kaeawc 8y ago
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 :/