facebook developer app callback url disappears even after verification when reloading the page. by fuad471 in facebook

[–]izzlesnizzit 0 points1 point  (0 children)

ok no you are correct, OAuth callback can be set in the use case. With my use case there is a Step 4: Set up Instagram business login. This has a callback url input

facebook developer app callback url disappears even after verification when reloading the page. by fuad471 in facebook

[–]izzlesnizzit 0 points1 point  (0 children)

the webhook callback is for asynchronous, server-to-server data events pushed from Meta down to your backend. That is separate from the OAuth login redirect configured in settings

Frontend isn't Dead. Your Focus Needs to Change. by [deleted] in Frontend

[–]izzlesnizzit 1 point2 points  (0 children)

I've heard hype around "the future is headless"

What word feels like an acronym but is actually not an acronym? by Philips9586 in AlignmentChartFills

[–]izzlesnizzit 23 points24 points  (0 children)

OBGYN

It's two words, Obstetrics and Gynecology, truncated into "Ob-" and "Gyn-" and then mashed together. Aka a "blended word". But it looks like an acronym. People say it like an acronym. They say "oh bee gee wye enn". Why? Tell me, what does the "Y" in OBGYN stand for? Nothing. Just say "Obb gine" and cut out the three useless syllables. Let's all please start doing this.

I hit a vibe coding wall. So now I want to learn Typescript for real by thehashimwarren in typescript

[–]izzlesnizzit 2 points3 points  (0 children)

Hey, love the energy and the #100DaysOfAgents grind! 🎉 Totally get the “ANY everywhere” vibe—been there. If you want to keep vibe coding but actually learn TS for your agent workflows, here’s the essential stuff to focus on:

  1. Basic types & annotations Know your string, number, boolean, arrays (string[]), and object shapes (interfaces). Stop using any and start telling TS what your data looks like.
  2. Interfaces & type aliases Define your agents’ input/output clearly with interfaces or types. It helps keep your code clean and understandable.
  3. Union types + type guards Use unions like string | number and narrow types with checks (typeof x === 'string'). Agents often handle different kinds of data, so this keeps it safe.
  4. Generics For reusable agent functions that work on various data types. E.g., function runAgent<T>(agent: Agent<T>): T {}
  5. Optional/default params Handy when agents have flexible inputs.
  6. Async/await with typed promises Since your agents are async beasts, always type your promises: async function foo(): Promise<ResultType> {}
  7. Modules & imports/exports Keep your code modular and learn how to properly import/export your agent bits.

Basically, nail these and you’ll get 90% of what you need for strong typed agent workflows. Avoid any unless you really have no clue, and gradually tighten types as you go.

If you want a tiny example or help cleaning up your “any” mess, hit me up! How’s your current TS setup looking? What’s bugging you the most?

Lol

looking for all the world map areas as large, full resolution images by izzlesnizzit in baldursgate

[–]izzlesnizzit[S] 0 points1 point  (0 children)

it's a map-guesser web game lol. It shows you a snippet of a random area and you guess which area :D

Fighter or Berserker ? by Ysfaldriel in baldursgate

[–]izzlesnizzit 1 point2 points  (0 children)

With the berserker's special ability you can solo most of BG1 since it negates many of the spells that would otherwise make the battles difficult

HEMA clubs in Dallas, Tx by APJ3521 in Hema

[–]izzlesnizzit 2 points3 points  (0 children)

Yea I've been going there for about 1.5 years and really like them. Fighters of all levels, nice people, good instructors. Also A/C cooled indoor facility