ehacke

Hey, I built this. Let me know if you have questions.

Because the more powerful parts of the business want it to look green all the time, regardless of the reality.

It would be easier to automate it. But they want to pretend that they have fewer outages than they actually do because if they were honest about how often things break, it would make them look bad in comparison with everyone else who is also lying on their status pages.

To double-down on this, I wish companies more broadly would stop lying about their uptime on their status pages. It just creates chaos and confusion.

It also forces otherwise-honest companies to also lie about their uptime, because they don't want to be the one status page that actually shows all the little blips that naturally occur with an actively maintained product.

Yeah all my projects are down.

Really irritating that they never update the status pages automatically, or even in a timely manor. As if customers won't notice.

At a high level, this is how Google Pay and Apple Pay function now. They create a temporary card number that's used in place of your own to insulate you from being tracked (to some extent).

The primary issue with anything like this is going to be getting VISA and Mastercard to play ball. And if you try to do an end-run around them, they'll just get this whole thing made illegal, if it isn't already.

I think the only way to really make headway in the payment anonymization front is to eventually have something like a cryptocurrency, but without all the speculative garbage that currently comes along with it.

I'm always tempted to push people into programming. Mostly because I wish I had learned it in high school instead self-teaching in my mid-20's.

But really, at their age it's mostly just important that they try to make something. Doesn't really matter what it is, or if it's successful. Just pick an idea and fool around with it for awhile. They need to figure out what they like and what they don't.

For decades large portions of the US population have prided themselves on ignoring whatever the government says. Until the bodies start piling up in their own town, people will not take it seriously, and possibly not even then.

> Slack, Dropbox Paper, Google Docs/Sheets/Diagrams/Forms, Salesforce, LeanKit, Figma, Jira, Trello, Asana, Zendesk

RoleUp handles most of those, but some don't offer user APIs.

What type of data are you looking to coordinate between the applications?

One hack that I've seen people do, though it takes a lot of work, is to push all kinds of data out of each respective service using stuff like Zapier, and into a shared Google Sheet for coordination. Then the Google Sheet itself has macros that push everything back into the sources via Zapier or others.

It's kind of a hack, but can work for specific use cases.

If it's just keeping track of the users and who has access, I built https://roleup.io to solve that problem. And I'd be super interested to know which 60 services you use.

Beyond shilling my service, I'm not sure that there is a good way to coordinate data between these services. I know from building it that even something as relatively homogeneous as user data can have an enormous variability between services. Going to the next level and trying to sync application data seems like it would be basically impossible.

On top of that, most of these services explicitly forbid the syncing of application data out of their service in their TOS. Facebook is a great example, they want to trap your data.

Data freedom is becoming a large issue in SaaS services of all kinds. See Adversarial Interoperability for more info: https://www.eff.org/deeplinks/2019/10/adversarial-interopera...

Why not just use Okta or something?

I think it's a bit of a fake idea in the sense that you ALWAYS want to ship the most minimal thing you can, as soon as you can. But what that means will depend on the company, the product, and the market.

The tough part is figuring out what the MVP actually is for your situation. It might be a Shopify site that just sends you an email when someone bought your widget, or it might be a multi-year R&D effort that ends with Falcon 1 being launched.

I also think that the "Lean Startup" concept is often abused by people to justify cutting corners on things they should not. The prime example is paying zero attention to code quality and testing prior to launch, then failing to get traction because the product is so buggy and unusable that the customers don't stick around. Don't over-architect and over-test something that may not sell, but some amount of design and proper engineering is necessary to ensure that you have something worth buying.