aquark
Joined 16 years ago
Joined 16 years ago
Locking in 4% AFTER TAX yield ... if you invest the $300K and it earns 4% you still can't pay the mortgage interest with those funds
I'm not a fan of OS X but seriously considering one of these just for the battery life and it-just-works portable computing.
It works great for email support, haven't tried their chat features, but is the sweet-spot for us in terms of features and complexity.
They have an API if you want to integrate, though for a web form just feeding it through email works.
Source: been there, done that ... there is no benefit to it and only pain.
Have a separate plunk-emails.com domain that is used for all emails. Or even have a bunch set up and rotate through them. This will mitigate spam impact too -- you will get spam issues even with 100% legit users
Assuming they did decide to quibble about the classification what can they actually do to an entity that has no legal existence in the US?
They do live chat too but we've never used that.
As a future product option I'd love to be able to treat these as standalone terminals, so we can offer a web based POS app (running on a different device) and the phone as a payment terminal without having to deploy our own mobile app.
Or is it more akin to the BBPOS Chipper readers and still needs a custom mobile app to interact with?
ie: can a platform built on Stripe use this for their customers without needing to supply a mobile app?
Then anything you do in OBS is feed into Zoom as a direct video feed and saves Zoom screen scraping and re-encoding the video. You can use OBS's screen capture or better yet pre-download the files and just play them back.
I think the best option might be to show something on the site when they are unsubscribed so they can easily undo that .
> The loop runs on stateless workers in the control plane. A worker runs one iteration > of the loop, either a model call or the tool calls it produced, then releases the > agent and puts the next iteration on a queue in Postgres. ... > Also unlike other harnesses, the machines that the workers (our agent loop) run on aren't > where the agent runs its commands.
It's late but don't think I am grokking this.
Isn't running the commands the heavier part of the work? The agent loop itself is mostly waiting for a remote model and then running the commands?
Why would I need a pool of workers for the loop when the constraining resource is likely to be the machines I am running the commands against (which can't be stateless like the workers are?)