Unless you're sending your software to Mars, I say that saving 80mb of package bloat is not worth the engineering time especially for an OS that will be EOL in less than 2 years.
1,395 karma · joined October 6, 2016
Unless you're sending your software to Mars, I say that saving 80mb of package bloat is not worth the engineering time especially for an OS that will be EOL in less than 2 years.
I guess in the edge case where you are a legitimate but very heavy user of u2f keys and you happen to share one with a batch that is being abused for bad activity... you just get shown a regular captcha and continue with your day I guess.
The design of the system will surely reduce the percentage of people that get that experience however.
Pros: You can probably make it work in a day or two
Cons: You now have to manage resources for each school. With dozens it's no big deal, but with tens of thousands you've got a considerable deployment problem.
I have worked at a company that started with a few single-tenant instances and ended up with a thousand. We ended up building software to specifically manage deployments, do healthchecks, ensure isolation etc (it was a long time ago - I expect we'd just run a giant kube farm today).
So, this is a reasonable approach with a painful trade-off as you scale. I would do this in the short term whilst working on refactoring this into a multi-tenant app.
Perhaps it's not very exciting but it is reliable.
If I had my time again I might not have gone the startup route but I was lucky so not sad about that. Would I be lucky if I tried again? Perhaps, but probably not.
So, blocking communication is one thing you can do to help send a signal that this player is toxic. I guess eventually they start getting queued in lower trust factor lobbies but that's speculation.
VSCode continues to feel like a cheap alternative as opposed to the software I want to use to solve a problem. It takes the place in my life of the editor I use when I need something more complicated than Vim but isn't really project work.
The company seems to be doing very well and I read recently that the owners are now billionaires so I expect they'll be OK for this decade and probably the next as well. I expect the decline would be very slow if it happens at all.
However these days I see a hybrid model in which the truly sensitive stuff is in an on-site datacenter and there is a one-way "data diode" style transfer from the low security zone to the higher security zone.
They'll give you general information from your account with the support plan but can't investigate any resources or logs without you owning a support plan on the other account and opening a ticket there.
Also, many companies will have this set up on each account and hardly use it. I don't think it's a loss leader.
I'd say that SSO should be available on the cheapest or second cheapest tier.
However, I would then make SCIM support (automated provisioning/deprovisioning) part of the most expensive tier.
If you're a small business, say 20-30 people then you can manage that by hand, but if you're a larger organisation then SCIM is a must-have.
I run a SaaS business. When dealing with vendor qualification questionnaires, you can tell the small and large businesses apart by whether they want SCIM support or not.
It's my experience that SSO makes your customers very 'sticky', and keeps IT and compliance departments happy. You blend into the suite of tools they use. I'll never forget the first time I saw a client's Okta portal with our app sitting next to Outlook web access, Zoom and Salesforce.
This client has only ever increased the number of seats and usage of our software.
From my point of view as a SaaS CTO we're happy to pay extra for SSO (i.e. Slack) but not at "contact us" level pricing (for example, Smartsheet)
> Topic: Service X just launched
> Comment: LOL I just read X as Y, and was imagining Z as a far-fetched consequence
Sometimes the commenter doesn't even imagine a Z and just explains a brief moment of confusion instead.
Versus a more concrete example of something I enjoyed recently:
> Topic: I wish there was an unstable AWS region to test the resiliency of my app
> Comment: They have one already, it's called us-east-1.
That wasn't hated (as I saw it) or even necessarily off-topic.
* https://old.reddit.com/r/imsorryjon/comments/gqxe91/the_forg...
* https://old.reddit.com/r/imsorryjon/comments/e607or/godfield...
For rotating application passwords we use the same technique but we update the usernames, i.e. app_1@'%' becomes app_2@'%', and then rotates back to app_1@'%' to prevent issues with unsynced config files.
You can do the same with ElastiCache auth tokens, and ensure your application reads the token from a value in secrets manager.
I don't think I'm competing with Apple at all today, but who knows what they're planning for their next features?
1. I invest loads of time and effort developing an app
2. Apple rejects it
-or-
2. Apple approves it
3. I ship a new update
4. Apple rejects the update and now decides my app should have been rejected retroactively.
I'm especially concerned about what happened to Hey and others but my customers are demanding smartphone apps and there are still limits to what can be done with a mobile web browser.
However this is a catch-22 kind of problem: this platform needs people, but people won't join it unless there are people using it. So, how do you intend to get your first 100 users?
I told them they should take that off the internet and we wouldn't be proceeding with their application. It even had things like notes from standups, design documentation and future development plans - I guess their team took the monorepo thing very seriously.
I'm sure it's only a matter of time before these TVs require 'activation' and frequent 'reactivation' before you can use them though. Alternatively they may perhaps start connecting to cellular networks, which would be a lot harder to evade.