I asked them and they said the plan is to make the spec public. I'll leave it up to them to say when that will happen. I'll say the spec is pretty flexible/configurable. You can swap our payment providers, it does not have to be stripe. And you can configure who does kyc and you can do that yourself.
I'm no expert. But I think it's the same thing that makes it easier to use for humans. So, `stripe projects --help` and then `stripe projects catalog` is super easy for me to grok and use versus reading some api docs and curling some endpoints.
It's provisioning expressed as an API, but wrapped in a cli that agents can very easily use. Then anyone that implements the API is added to a marketplace of services. And the ability to pay for service is baked in because it's stripe. The end result is that as an engineer I can ask an agent to use the stripe cli to discover and provision, including paying for, a wide variety of services and it mostly just works.
Wow, the amount of reactionary doomsaying in this thread is offputting. I built the Stripe Projects agentic provisioning integration (what this post is about) at Inngest and when I saw it actually work in action I thought it was actually kind of magical. Basically, hey agent, use my stripe account to provision a pro plan at Inngest, build me an app and deploy it. The agent does it and logs me into the Inngest dashboard. Agentic provisioning seems inevitable given the way we work now, and deferring to Stripe for kyc seems a reasonable way to do it.
I'm building an AI DJ for Spotify called Listen to Luther. It's open source here: https://github.com/jacobheric/luther. Currently it responds to prompts with a list of songs that can be queued, played or added to playlists on Spotify. Next I'll give it proper memory and the ability to adjust and remix on the fly. I built it because I was frustrated by the mostly passive experience of Spotify's own AI DJ. There is no path to commercialization here as Spotify's TOS does not permit it (I asked them). So I host it for myself and a few friends and made it open source for anyone who's handy enough to run it themselves.
If you use AgentKit + Inngest then you can do all the things you normally do with the Inngest dev server like observe runs with AI metadata and rerun functions and rerun functions from steps with edited inputs. We do have a step-through debugger coming pretty soon here as well. Note you don't have to use AgentKit with Inngest though.
Thanks! Yeah we don't currently augment the result data only the arguments. But its on our TODO list as we need to to send back stuff like error info about pipelines runs. Prisma has type utilities for this, see the Result<> stuff at: https://www.prisma.io/docs/orm/prisma-client/client-extensio...
We sort of do this with WASM for just in time pipelines. We write pipeline rules in WASM...for things like detecting/masking fields...then we import and execute those wasm rules in a variety of language SDKs. As a sibling comment indicates, it's pretty difficult getting data in and out, but it's doable. See here for an example: https://github.com/streamdal/node-sdk/blob/main/src/internal.... We do this sort of thing in node, go & python and are adding other languages.
Thank you! I wrote the UI! It's a pretty tricky UI stack as we update everything to the browser realtime in protobuf over grpc streaming (using grpc-web and protobuf-ts). There is a lot mapping we have to do to shape the data properly for React Flow so we do that server side in Deno before passing it along to the browser. We still have some optimization to do to keep the live tail view zippy, but it's a pretty solid foundation.
In the node-sdk, process pipeline is async , see: https://github.com/streamdal/node-sdk/blob/main/src/streamda... (I'm the author of that). I believe this is also the case for the python and go sdks as well. So you can call it asynchronously for passive observability.
However, we implemented the pipeline rules in wasm with the goal of keeping the overhead as minimal as possible. So you could also use it as more of a data security or governance tool and invoke the pipelines synchronously and mask or prevent sensitive data before passing it along.
Hey there! I wrote the node sdk for this, you can use the node-sdk to to execute wasm-based rules on your data and interact with the data in real time. With the wasm rules you can do things like detect and mask PII, etc. The node-sdk is here: https://github.com/streamdal/node-sdk. There are some minimal examples of these pipelines in the readme and examples/sandbox directories.
While your experience is interesting and instructive in general, I think it's not completely relevant to the specific loans outlined here. These loans are issued directly by the SBA, from federal treasury funds, for the purpose of assisting businesses that might otherwise not survive the economic impacts of covid. For any small business in that situation, it seems a reasonable option.
IANAL, but the collateral terms as I read them are very specific and limited to business machines and such, not your house or your car.
Yes, I believe this is correct. This post is outlining the details of the economic disaster loans that are offered directly by the SBA and described in the link by the parent. The current legislation refers to these existing loans as 7(b). I believe the new stimulus bill, at least the senate version that I skimmed, deals largely with loans made by other financial institutions and referred to as 7(a). Those are covered here: https://www.sba.gov/partners/lenders/7a-loan-program/types-7.... Of course that information is now made out of date by the just passed legislation.
I my experience, at least for an individual, I think saying no is exactly the opposite of dangerous. I’ve been contracting exclusively for 10 years and said yes about 6 times and no dozens or hundreds of times. As long as you say no frankly, with a reason, and offer some names of people who can help, people are happy with you and will more often than not ask again in the future. Saying no, especially for bad fit, is one of the most important parts of success I’ve had in consulting.
I didn't even realize google had a podcast app. I just installed it and you're right, I can't subscribe to a podcast since I have disabled web activity history. That's a particularly egregious dark pattern.
Interesting. I never really had a firm grasp on the overlap in functionality of ublock origin and privacy badger. I threw privacy badger in the mix at some point as I like the EFF and wanted to give it a whirl. I haven't noticed any sites loading slowly, but I'll do a comparison on some of the sites I use and see if it's slowing things down.
I use firefox with ublock origin and privacy badger and I can't recall the last time I ran into a site that was broken because of it. But, I visit a fairly narrow section of the internet regularly so there might not be much overlap between what I browse and you browse.
I also use the multi-account container add on and the temporary container add on. This allows me to pin a few big sites to their own containers (google, amazon, etc) and open all other new tabs in temporary containers. This setup works great and appears to help keep firefox fast over time. I use duck duck go to search but firefox makes it trivial for me to re-run a search with google if I need to.
I also run an ad blocking vpn on google cloud using Algo. I use google cloud because the vpn can run on the permanently free tier and I only pay for network traffic (which is near zero), and I also enjoy the irony of it. I have wireguard clients setup on all of my devices to use the vpn either permanently (phone) or on demand (laptops). Having this vpn is nice as it makes it easy to block ads in apps on my kids mobile devices.
This vpn setup works ok but not quite as well as when I ran the same thing using Streisand and open vpn clients. I only say this because I have a homebrew whole-house audio setup with a bunch of google audio chromecasts and no matter how I tweak the wireguard client settings I cannot get that casting to work properly. With open vpn clients, those settings are a cinch.
I agree and think all the "shocking" and "bizarre" assessments are clickbaity. He did a similar thing against Karjakin. It's a smart strategic move given the situation and his advantage in the tiebreaks. Having watched the Karjakin tie-breaks, I can't wait. It's going to be so exciting. Having said that, if Caruana should defy expectation and prevail it will also be a great story and counterpoint to Carlsen's strategic calculation.