Sadly this is still the case. Cloud Run helped us get off the ground. But we've had two outages where Google Enhanced Support could give us no suggestion other than "increase the maximum instances" (not minimum instances). We were doing something like 13 requests/min on this instance at the time. The resource utilization looked just fine. But somehow we had a blip in any containers being available. It even dropped below our min containers. The fix was to manually redeploy the latest revision.
We're now investigating moving to Kubernetes where we will have more control over our destiny. Thankfully a couple people on the team have experience with this.
Something like this never happened with Fargate in the years my previous team had used that.
Then you can go to that platform’s page for reporting abuse or spam (find via search) and fill out their form. Sometimes those platforms will say they can’t do anything since it is a different platform that isn’t a direct customer but yet another platform, so ask them to name them. You may then need to find that other platform’s reporting page.
Just be aware that after all of this, you may not actually fix your problem. Some of these companies seem to repeatedly send spam because they have customers that just perform the same abuse from a different phone number or different account with that platform. That’s why the reports to the FCC and FTC matter, to investigate platforms for broader issues.
1. BoxyHQ wants you to do SAML-over-OAuth. We support this -- especially for NextAuth compatibility. But we don't think it's always helpful.
2. We think our service is easier to use. We most commonly hear complaints from users/customers about complexity, so we try really hard to make SAML obvious and simple. Ultimately, it's up to you whether we meet that bar.
Would you mind elaborating a bit why you don’t think SAML-over-OAuth is a fits-all solution? To me it sounds like eating your cake (SAML) and having it too (not having to use SAML)
Very cool! I built a no-code version of this for my friends' birthdays where all of the clues were about them (inside jokes, dumb bets, catch phrases, etc). I just printed out categories in a grid on a sheet of paper and had a bunch of questions listed out in OneNote on my phone and manually kept score. I didn't put penalties in place if somebody got it wrong to encourage people to participate vs just optimizing for score. "Jonpardy" and "Joshpardy" are two of our friend groups most cherished and repeatedly cited events from the past 10 years.
I've dabbled with the idea of creating some real implementation of this. I most recently put together an @Midnight / After Midnight no-code game for a friend's bachelor party. The buzz-in mechanics and score-keeping are somewhat similar. Maybe you could repurpose your core logic for several different game show themes?
Yeah, I made a category for a game night with friends called “Who wrote this Facebook status in ‘09?”, which was very popular.
Repurposing the logic for different game shows is definitely interesting. Although I’ve matured Buzzinga in the last seven months, there’s definitely still room to improve, but eventually I can see this transition!
It's pretty rare to give someone 10%+ equity after a business has been operating for several years. Even if you brought on a professional CEO, I wouldn't expect to see that. I've seen some founders put together special agreements to transfer some of their own shares to a person recognizing that they'll be taking over a big part of their own role and that it wouldn't be fair to dilute the rest of the company.
Regardless of what you do, make sure there is a vesting schedule in place (e.g. a 4 year vest + 1 year cliff).
For anybody else who also hadn't come across the term RVC before:
"The RVC model is a Retrieval-based Voice Conversion system using AI for high-quality voice cloning. It utilizes artificial intelligence to modify or clone voices in real-time."
Source: https://speechify.com/blog/rvc-vocal-models/
I enjoyed this blog. I think it provides a great succinct overview of various approaches native to Postgres.
For the "capture changes in an audit table" section, I've had good experiences at a previous company with the Temporal Tables pattern. Unlike other major RDBMS vendors, it's not built into Postgres itself, but there's a simple pattern [1] you can leverage with a SQL function.
This allows you to see a table's state as of a specific point in time. Some sample use cases:
- "What was this user's configuration on Aug 12?"
- "How many records were unprocessed at 11:55pm last night?"
- "Show me the diff on feature flags between now and a week ago"
spoiler: Of the 6 cars they tested, Tesla Model Y had the best performance in terms of miles per kWh and total range. But it still clocked in at only 81% of claimed range.
I rarely have to use Superchargers because I have charging at home. But when I do, it's about $25 for an 80% top up (e.g. going from 10% -> 90%) in my Model Y.
Just looked it up: $0.45/kWh the last 4 times at Tesla Superchargers in California.
I don't use Svelte, but I appreciate the principled approach and the clear explanation.
I primarily coded in Python for 4 years. Then I founded a company that didn't need as much data science and my primary language switched to JavaScript (2 years) then TypeScript (4 years). Overall, I really like TypeScript. But I do absolutely miss being able to cmd + click into a function/class from an open source package and see the actual implementation and not just a type definition. This is probably the biggest day-to-day frustration I have with TS compared to JS and Python.
What if TypeScript could compile to JS/JSDoc instead of source maps? I'm also not a fan of 'go to definition' bringing me to a dead end d.ts file, but also there has to be a better solution than verbosely JSDoc'ing all the things.
There was talk about introducing type syntax as valid but ignored in the JS language, making TS valid JS.
It would take forever to become mainstream but if node and major browsers started to support this tomorrow, along with ESM modules we could drop TS compilation and bundling entirely during development, safely publish npm packages as TS (even a bundled TS) and simplify tooling for monorepos, IDEs, etc.
Unfortunately that wouldn't solve dealing with templates like JSX/TSX or future language syntax/features.
Right yea that solution would be many years out and doesn't work for JSX. As opposed to compiling to JS/JSDoc which could be done today and should solve our problems with stepping into NPM package code without dead ends.
We're now investigating moving to Kubernetes where we will have more control over our destiny. Thankfully a couple people on the team have experience with this.
Something like this never happened with Fargate in the years my previous team had used that.