> OpenAI has closed many of its safety-focussed teams
A paper with "ideas to keep people first" was (coincidentally?) published today:
• Worker perspectives
• AI-first entrepreneurs
• Right to AI
• Accelerate grid expansion
• Accelerate scientific discovery and scale the benefits.
• Modernize the tax base
• Public Wealth Fund
• Efficiency dividends
• Adaptive safety nets that work for everyone
• Portable benefits
• Pathways into human-centered work
My mission was to create a Sci-fi Noir episode of the Twilight Zone by way of David Lynch and Phillip K. Dick. Big shout out to Dan Erickson and Ben Stiller for speaking to my soul in Severance. And of course to the enigmatic QNTM for sparking my imagination with the original story, "We Need to Talk About 55". Long live the SCP Foundation.
Microsoft 365 is a reasonable alternative. It's easy to buy and even tiny Customers can get a degree of real human (read: tier 1 is unhelpful contractors that you have to fight thru) support.
It's still repugnant to me, as compared to self-hosting, but I would never self-host for a greenfield SMB Customer today. The economics don't make sense and the talent pool of knowledgeable and reasonable sysadmins is dwindling by the day. (I wouldn't want to make a Customer so beholden to me if they were willing to pay for it.)
I miss being able to spin-up an on-prem email server on a box with reasonable hardware redundancy, some external USB disks to rotate for off-site backup, a UPS, a couple consumer-grade "business class" Internet connections, and a contracted "backup MX" to catch email in the event of an outage. It was a good enough for a lot of small SMBs who had a physical office, and was cheap.
It's not. Support is about on par with Google for SMBs. I had a client get locked out of the admin panel for about 2 weeks before getting through with support.
The difference is that everyone's account kept working during that time so business kept on as usual, just the admins couldn't change anything.
The sad thing is I don't think anyone did anything unusual and it was some kind of bug of Microsoft's end.
Good to know. I'm only dealing with 7 M365 tenants regularly and we have "break glass" accounts in each one (not tied to Customer's SSO, MFA unrelated to other admins, email address outside the tenant) to try to minimize the possibility of getting locked out, but I know it's always a possibility.
Moving the MX for the domain and limping along from backups is my worst-case contingency but given that there's no place other than M365 to restore the backups to it isn't a very good strategy.
The economics make perfect sense once "30 days of a suspended business email with no timely recourse" shows up as a line item. That USB disk and a UPS is looking pretty cheap right about now.
OP really should be moving the MX somewhere else and going into disaster contingency mode. It sucks, but there's a level of survival there they should be willing to accept, at least temporarily.
I was a long time k8s skeptical, but I think it's solid now. If there's good support for keycloak for k8s with support for backups I wouldn't think twice.
Not sure the state of keycloak now, but it was a lot of work to manage keycloak configs with the IaC pipeline. That could have gotten better now, but I think having access to the data is important because migration might not be trivial if for instance a provider starts acting up.
A paper with "ideas to keep people first" was (coincidentally?) published today:
https://openai.com/index/industrial-policy-for-the-intellige...reply