Eduard Besjentsev

Newsletter system that automatically creates different segments and assigns subscribers to them based on emails read and engagement, complemented with ideas to increase the conversion rate on a personal level

Yew Meng Yuen

Mar 6 •

AI Agent SaaS Challenge

Antropic settings

After @Eduard Besjentsev recommdation to look into Antropic console I found my api was never used or called, guess I missed the part where a workspace needs to be used? Am I to add the key in the workspace? Thanks fam

New comment Mar 11

Eduard Besjentsev

2 likes • Mar 6

@Yew Meng Yuen yes, either to the default workspace or the new one you created. The workspaces are just for extra organization purposes. You could have one workspace per project, and within create multiple API keys per environment (production, development, testing) or even per model version.

Eduard Besjentsev

1 like • Mar 7

@Yew Meng Yuen this could be due to a couple of reasons. It is best to start from the most obvious point, the button itself. - What is your client-side logic to deactivate it? If that's correct, you're most likely relying on "useSchematicFlag". - Are there any discrepancies in the naming of the feature flag on the client side and Schematic's dashboard?

Shaili Gandhi

Mar 5 •

General discussion

Stuck at this Next JS error

I am building a Next JS application for the first and am facing this error while adding an image, need help to fix it. Uncaught Error: Hydration failed because the server rendered HTML didn't match the client. As a result this tree will be regenerated on the client. This can happen if a SSR-ed Client Component used: Line probably causing the error: <Image src='https://links.papareact.com/a943ae' alt='Disney Logo' height={100} width={100} className='cursor-pointer invert'/>

New comment Mar 7

Eduard Besjentsev

3 likes • Mar 6

Please verify you have imported the right Link element from "next/link" and not from "lucide-react". The latter is an icon, so when you wrap an image inside it, it can cause hydration issues.

Digitl-Alchemyst Steven-Watkins

Mar 6 •

AI Agent SaaS Challenge

Fundamental Flaw in the App

Its not super terrible and buttoned up pretty nicely with the disabling of chatting. However a user can still create video pages by just entering the ID on the url and procced to the video analysis page. Could this open up potential for abuse? AAANNNDD yes it has. SO If I go to the video page by URL and then inspect source and go to the button and remove the disabled feature from the page source we can easily chat with our application beyond the limits and use the other features this way as well. SOOOO What we gone do about this papafam? Lets start brainstorming a solution to this here in this thread, and of course I will report back when I find a solid solution.

New comment Mar 7

Eduard Besjentsev

2 likes • Mar 6

It is important to note that malicious actors can also interact with the website outside the browser/UI (see screenshot). So we must have both client-side and server-side checks. That's why, in `actions/createOrGetVideo.ts,` we initially placed a guard with "checkFeatureUsageLimit," for instance. We should also apply it to other server actions! The question remains whether we want to limit chat interactions as well? To limit the number of chats, we could create a new entitlement in Schematic and add some extra guards in `api/chat/route.ts` before calling "streamText."

Yew Meng Yuen

Mar 4 •

AI Agent SaaS Challenge

Chat area

Not getting a reply, any idea what I did wrong ?

New comment Mar 5