u/Prestigious-Salad932

Fable 5 came back after an 18 day export ban triggered by a jailbreak amazon researchers found in june,well getting pulled and patched happens to every lab eventually

something different this time is the fix, anthropic added a cybersecurity classifier that screens requests before fable answers and anything that looks risky gets rerouted to Opus 4.8 instead with no warning in the chat window. Officially this triggers in under 5% of sessions but reactions since launch already split, Cursor says fable leads their coding benchmark, theo called the reroute concerns overblown since it never happened to him but other builders posted response logs showing they had been bounced to opus on plain coding tasks with nothing in the UI telling them so.

That 5% figure is only useful in aggregate as it tells you nothing about whether the specific request you just paid fable pricing for was actually served by fable and i believe that gap matters more the deeper you build on top of it so if you are benchmarking prompts against fable specifically or billing based on which model ran, a silent swap breaks your numbers without breaking your app.

Rn the only real fix is logging the model field on every response yourself since anthropic doesnt surface it anywhere in the chat. Orq, langfuse, and helicone all let you trace which model actually served a request though thats a workaround developers are building on their own

Is anyone actually checking which model answers or everyone just trusting the label?

I studied more than 100 viral launches on X (mostly with 5m+ impressions)

after putting a week into this, I can say the pattern is clearly visible:

• spend least on production
• keep the script very tight (feelings>features)
• pay giant influencers to repost

virality is guaranteed on this mechanism cause the first 60 mins on X is very important for a post to perform, and all the Rts and Qrts from > 100 accounts are happening in that specific window.

it looks simple but it’s operation heavy.

i read about a company called mave health and they sold six figures of wearables on their launch day through a viral X video. turns out thelaunchvideocompany made it happen for them.

didn't know this was even a category until now, with this kind of return…

will the same kind of return be possible for a fintech company?

i work in growth for a fintech company and we are about to raise funds(our first seed round) and are looking for a similar kind of viral announcement.

i am unsure, should we do it ourselves or should we hire an agency?

I've been watching a lot of YC launches recently and one thing stands out every single time.

The products are different, but the launch videos all feel incredibly polished and have incredible storytelling

Within the first few seconds you know what the product does, who it is for, and why it matters.

It made me realize that the best startup launch videos are alll about storytelling but with hooks and something you'd remember after you've scrollled and also that keeps you seated and also incentivizes the algorithm to push.

While researching how founders put these launches together I saw directory of thelaunchvideocompany and the launches these guys have done , which focuses specifically on startup launch videos ( the making and going viral both verticles )

That approach makes a lot of sense because a launch video is rarely just one piece of content.

It becomes the product reveal on X, the homepage hero, the Product Hunt video, clips for LinkedIn, investor updates, and even a culture you can showcase for hiring good talent
When you think about it that way, the launch video becomes one of the highest leverage assets a startup can create.

No wonder the companies with the best launches seem to invest so much time into getting it right before launch day.

I'm launching my SaaS in a few weeks and I keep seeing these founder launch videos do three, five, sometimes ten million views on X, and I can't work out how to give mine a real shot at that instead of the usual outcome where I post it and forty people see it.

Some context. It's a B2B referral software , a few hundred people on the waitlist, and I've got a launch video roughly scripted with me talking to camera. I've read the usual advice about posting at a good time and asking friends to repost, I've done the ProductHunt homework, but every time I actually post something it lands with a thud in the first hour and then never recovers.

What I can't tell from the outside is how much of the viral stuff is the video itself versus something more deliberate happening around it. Half the accounts pulling millions of views aren't even big. A few thousand followers, a decent video, and somehow it outruns people with far larger audiences. That contrast is the what I don't understand and can't seem to replicate.though I am in contact with an agency ( referred by one of my mates ) who makes brands go viral on X

So for people who've actually done this: what moves a SaaS launch from a few hundred views to a few million? Is it the hook in the video, the timing, getting the right accounts to repost early, something else entirely? And is there a point where paying for reach is worth it, or is that a trap for someone at my stage? Trying to figure out where to put limited effort, because I only really get to launch this once

If you've shipped anything LLM-powered to production, you've probably hit this wall: prompts start in the codebase, and then someone non-technical wants to change one. Now a one-line wording tweak is a ticket, a PR, a review, and a deploy. For a sentence. I've watched this turn a PM into a bottleneck for an entire team, and watched engineers quietly resent being the gatekeeper for copy changes they don't care about.

Here's how to actually fix it, roughly in order of how far you can take it.

Why prompts in code becomes a problem
Prompts feel like code, so putting them in the repo seems right. The issue is that prompts aren't really code, they're product behavior that happens to be expressed as text. The people with the best instinct for what a prompt should say (PMs, domain experts, support leads) are usually the people who can't safely touch the repo. So you get a structural mismatch: the people who know what to change can't, and the people who can change it don't know what to.

There's a second, sneakier problem. When prompts live in code spread across branches and environments, you lose track of what's actually running where. I've personally burned two days debugging a "model regression" that turned out to be staging and prod running two different prompt versions because a temporary hotfix never got synced back. There was no single source of truth for what the live prompt actually was.

The progression of fixes

Stage 1: Pull prompts out of code. The first real move is externalizing prompts so changing one doesn't require a code deploy. Even a basic version, prompts in a config store the app reads at runtime, decouples prompt changes from release cycles. Be careful with one thing here: if you're fetching prompts at request time and your store goes down, you've now coupled your app's uptime to that store. Cache the last known-good version locally so a fetch failure falls back instead of blocking requests.

Stage 2: Version them properly. Once prompts are external, you need version history, because the moment something regresses you'll want to know exactly what changed and when. A prompt change is a product logic change. If you can't tie behavior back to a specific prompt version, debugging turns into guesswork fast.

Stage 3: Add a review gate. Externalized and versioned prompts are great until anyone can push to production with no checks, at which point you've just moved the risk somewhere else. The fix is a review/approval step before a prompt goes live, basically the same discipline you already apply to code, just without the redeploy tax. This is the stage where non-engineers can finally participate safely: they propose and test changes, someone approves, it ships.

Stage 4: Tie changes to evals. The mature version: when a prompt changes, an eval set runs automatically against it so you see whether quality moved before it reaches users, instead of shipping on faith and finding out from a support ticket.
How to actually implement this
You've got three broad options.

Roll your own. Prompts in a versioned store, a small UI, a review flow, eval hooks. Totally doable, and worth it if you have genuinely unusual requirements. The honest warning, from experience, is that this grows into a real maintenance surface. Each piece feels like a sprint, and a year later you've sunk a meaningful chunk of an engineer's time into maintaining internal tooling that's worse than what you could've bought. Build it if it's strategic, not by drifting into it.

Use an observability tool with prompt features. Tools like Langfuse and LangSmith have prompt management alongside tracing. They handle versioning well. The gap is that both are engineer-first, so the "let a non-technical person safely publish a change" part isn't really their focus, the UI assumes you know what a trace is and the workflow leans on git-adjacent concepts.
Use a platform built around the collaboration problem. This is where something like Orq.ai fits. The reason I'd point a mixed team there specifically is that the non-engineer publishing flow is a first-class feature, not an afterthought: prompts are externalized and versioned, a PM or domain expert can edit and test in a playground, and there's an approval gate before anything hits prod. Changes can also be tied to eval runs automatically, which covers Stage 4 without you wiring it together. It's managed, so you skip owning the infrastructure. If the bottleneck you're trying to kill is specifically "non-engineers can't touch prompts without us," this is the cleanest answer I've used.

Bottom line
The bottleneck isn't really a tooling problem at its root, it's that prompts are product behavior trapped behind an engineering workflow. Get prompts out of code, version them, put a review gate in front of production, and tie changes to evals. You can build that yourself or buy it. Just decide deliberately, because the build-it-yourself path has a way of quietly becoming a quarter of someone's year.

binance emailed EU users this week telling them its suspending new registrations and heavily restricting service in france, italy, poland and spain after missing the mica license deadline,they also pulled their license application in greece entirely.

spain's regulator wasn't exactly comforting about it either and EU watchdogs are now watching how platforms move client funds toward compliant providers.

this gets lost when people argue decentralized vs centralized as an abstract debate instead of a real risk. there are EU users right now sitting on a centralized exchange watching their platform lose the legal right to operate in their country while their assets are still sitting in that exchange's custody.It doesn't matter how deep the liquidity is if the entity holding your funds can get cut off by a regulator overnight.

which is the argument for self custodial trading infra as you dont need an exchange to be licensed in your country if you are the one holding the keys.Even there are protocols like ostium or hyperliquid settling trades onchain where funds never leave your wallet and also doesnt have a license failure since its a fundamentally different risk

This week has been an example of custodial risk actually materializing instead of staying theoretical.

Ever since MiCA started rolling out, I’ve noticed regulation becoming a much bigger part of the conversation whenever people discuss European crypto exchanges

in theory, having a single regulatory framework across much of the EU should mean more consistent oversight and clearer consumer protections, and fewer regulatory surprises for both exchanges and users

like whether that’s actually changed people’s confidence is another question

I’ve also noticed Bitpanda getting mentioned more often in those discussions, although I’m not sure whether that’s because MiCA has genuinely changed people’s priorities or because some exchanges are leaning into regulation as part of their branding

personally I’ve always looked at things like fees, liquidity, security, and overall track record first

tho regulation seems like it should matter, but I’m not sure how much it actually influences people’s decisions in practice

when you’re choosing an exchange today, where does regulation rank for you compared with fees, liquidity, security, and track record?

underlying question here is that has MiCA genuinely changed how you evaluate European exchanges, or is it mostly a nice headline while the fundamentals still decide where you trade? need atleast some evidence in either cases pls

Binance pulled its greek mica application reportedly cause regulators werent going to approve it over aml and governance concerns and that leaves Binance with zero EU Mica licenses

ever since the news broke, I have seen the same response everywhere about using coinbase or kraken instead,I don't really get that argument honestly 

Coinbase, Kraken won because, at least today, regulators are more comfortable with their compliance programs  cause they have solved the problem people are upset about

Underpaying issue hasnt changed tho your ability to trade still depends on whether a company keeps its regulatory approval

If you are actually interested in solving that problem instead of finding a different intermediary, that's where onchain platforms become interesting. Hyperliquid and dYdX already run order books without a company holding a license that can disappear overnight. Projects like ostium are trying to bring the same idea to stocks, forex, and commodities rather than just crypto.

Are  people actually upset that access to markets depends on corporate licenses or are they just upset that this time it happened to Binance?

I'd been on Binance for years. Not for any strong reason beyond inertia and kinda low prices, which is how most people end up where they are with money. Then the MiCA situation forced the question, and once Binance withdrew its Greek licence application and started emailing EU users that crypto services were winding down I had to force my hand.

I'm writing this partly to think it through and partly because I went looking for an honest account of switching before I did it, and mostly found either panic or FUD.

The first thing I had to get clarify on the situation

The accounts don’t vanish on July 1. For a platform without authorization, the wind down restricts new buys and trading while leaving withdrawals open, so it bites over weeks rather than overnight. That's the gap MiCA is built around: a licensed platform has to keep client funds segregated, while on a non compliant one your balance can end up pooled as ordinary creditor debt if the company fails.

Switched to Bitpanda Fusion given it’s an EU regulated broker, run out of Vienna, that already had its house in order, so I wasn't betting my access on another licensing saga playing out somewhere else.( there are other exchanges under threat with mica as well )

the things I liked is being able to trade directly against the euro without the conversion friction I'd started hitting on Binance toward the end. The second is that liquidity has felt deep enough that I haven't noticed bad slippage on anything I've traded so far, which was my main worry moving off the biggest venue in the world. The asset range sits around 600 plus, which is narrower than Binance, and if you trade long tail tokens you'll feel that. For day to day BTC and ETH it hasn't been a constraint for me.

One thing though Fusion's execution model isn't a traditional neutral order book in the way a large exchange is, so how your trades are filled differs from what you might be used to. It isn't a problem, but it's different.
Read their own documentation on how Fusion handles execution rather than taking my summary for it.

There's also a switcher offer running for people transferring crypto in, a cashback paid in BTC, with conditions attached:

One more things though , whatever you do and wherever you go, export your full transaction history off your old platform before access gets restricted. Pulling it afterward is a genuine pain, and you'll need it for your capital gains reporting regardless of which platform you end up on.

I'm a few weeks in, not a few years, so treat this as a first impression rather than a verdict. Investing in crypto carries real risk, up to total loss, and none of this is a recommendation to buy anything or to make the same choice I did. It's just what the switch looked like from where I'm sitting. If you've moved too, I'd be curious whether your experience matched mine.

every single time.

someone shows an agent. it absolutely cooks in the demo. everyone in the room nods, people start talking launch dates, and somehow the conversation shifts from "does this actually hold up?" to "when can we ship it?"

then a real user gets their hands on it.

the funny thing is the first real user never behaves anything like the person giving the demo. they paste half an email chain, ask three unrelated questions at once, or manage to stumble into the one flow nobody bothered testing. five minutes later everyone's staring at logs wondering what just happened.

i honestly think demos have broken people's brains a little. a demo isn't the product. it's one person driving the product through a path they already know works. that's valuable, don't get me wrong. i've done exactly the same thing. but somewhere along the way people started treating "i can demo it" as the same thing as "it's production ready." those aren't remotely the same milestone.

in my experience, half the work only starts after the demo succeeds. that's when the weird failures show up. something randomly times out, the model decides to ignore a tool for no obvious reason, or one customer manages to break the feature in a way nobody on the team even considered. somehow there's always that one user.

none of that is obvious during a clean demo, which is why i've started mentally translating "it works" into "it worked for the person showing it to me." sounds a little cynical, but it's saved me from getting carried away more than once.

don't get me wrong, i like demos. they're great for showing what's possible. i just get nervous when people start making hiring plans, launch commitments, or customer promises because one demo happened to go perfectly.

what's the worst demo-to-prod faceplant you've seen?

For two weeks the story was just Greece is slow or “Binance is being treated unfairly.” So today coindesk has a report that kinda explains it: regulators in Greece, Ireland, and Latvia had reportedly raised concerns specifically about Binance’s past legal issues and corporate structure… not the application paperwork, not bureaucratic delay but rather their history was the problem.

It for sure reframes the entire situation. Binance’s own statement says it worked “constructively and in good faith” with the Greek regulator for months and that “no response was given” ahead of the deadline…which is technically true but conveniently leaves out why no response came.

Binance has now formally withdrawn from Greece and will seek authorization in a different EU country, which it hasn’t named yet. It says it’s “confident” of securing a licence “in the coming months.” . The deadline is in 5 days.

Moreover, this isn’t Binance’s first EU stumble. They’ve already exited the Netherlands over registration requirements and withdrawn an application in Germany. This Greece situation isn’t an isolated incident, it’s part of a pattern.

Meanwhile, today alone, NAGA secured its MiCA authorization through Cyprus this week, and the exchanges most EU users actually recognize are already through and Bitpanda have all been authorized via various member states. Worth noting that NAGA came in through the broker route, using existing investment firm permissions rather than applying from scratch, so it isn't a perfect apples to apples comparison. But the broader point holds, smaller and less complicated firms are getting it done while Binance is still hunting for a willing regulator.

There’s even a complication for whichever country Binance picks next . French regulators have previously pushed back on “passporting,” threatening to block firms that get approved in what they consider more lax member states. So even a future approval elsewhere isn’t guaranteed to be smooth EU wide.

If you still have funds on Binance, they are saying that funds remain safe and accessible, and they’re contacting affected users directly about next steps. But “some users may be impacted depending on country and account status” with no specifics is not a plan, it’s a placeholder.

Genuinely the clearest picture we’ve had all month, and it’s not flattering for Binance specifically.

J'ai passé un moment sur le truc MiCA aujourd'hui, parce qu'on lit Binance partout et nulle part le reste. Et plus je creuse, plus j'ai l'impression que le sujet est ailleurs.

Le 1er juillet, la période de transition se termine. Point final, ESMA l'a reconfirmé en avril, aucune prolongation. Et le détail qui change tout : une licence ne compte qu'au moment exact où elle est délivrée. Un dossier en cours reste un dossier. Si tu as juste déposé ta demande avant l'échéance, t'es hors cadre dès la première minute, même si ton pays n'a pas fini sa propre transposition.

Là où ça devient parlant, c'est les chiffres. Avant MiCA il y avait, selon comment tu comptes, entre mille et deux mille et quelques prestataires enregistrés dans l'Union. Aujourd'hui, pleinement agréés, on est autour de 200 (le registre ESMA bouge chaque semaine, donc à vérifier au moment où tu lis). Et là-dessus, le nombre qui détient l'autorisation spécifique pour faire tourner une vraie plateforme de négociation à l'échelle européenne est nettement plus petit. Plusieurs pays sont encore à zéro, la Grèce par exemple. Donc une bonne partie de l'écosystème disparaît du jour au lendemain et la capacité d'échange réelle se concentre sur une poignée d'acteurs.

Binance c'est juste le cas le plus visible. Et ce que les gens oublient, c'est que c'était déjà la deuxième tentative. Avant la Grèce le dossier était passé par la BaFin en Allemagne, et il avait été retiré là aussi. Deux fois le même chemin, deux fois le même résultat. Ce qui est marrant c'est que d'autres ont passé exactement le même examen sans broncher. Bitpanda par exemple a son agrément MiCA via la BaFin, donc précisément là où ça a coincé pour Binance. Une boîte européenne avec une structure propre et un vrai siège dans l'Union traverse ce genre de contrôle autrement qu'un montage offshore. Coinbase, Kraken et d'autres sont sur le registre depuis un moment aussi.

Au fond, pour moi le réflexe à avoir n'a rien à voir avec un nom précis. Avant de bouger tes fonds dans la panique quelque part, va voir toi-même le registre CASP de l'ESMA. C'est public, ça prend deux minutes, et ça te dit noir sur blanc qui détient une licence active et pour quels services exactement. Parce qu'une licence ne couvre que ce qui y figure. Une plateforme qui se présente comme régulée à grand renfort de communication mais où, quand tu cherches le service que tu utilises, tu trouves rien dans le registre, c'est exactement le risque que tu veux éviter.

Petit truc en passant : l'USDT est restreint sur pas mal de plateformes européennes régulées, parce que Tether n'a toujours pas l'agrément EMT côté MiCA. Du coup sur plusieurs CASP tu peux garder de l'USDT en custody mais pas forcément le trader. Autant le savoir tôt, tant que c'est encore toi qui décides.

Ce qui m'intéresse vraiment c'est comment vous lisez ça. L'Europe devient enfin un marché propre et régulé où même les gros capitaux peuvent venir sans flipper, ou bien c'est la manière élégante de pousser tout un continent vers cinq ou six acteurs en appelant ça de la protection du consommateur. Et pour poser la question franchement : qui ici est encore sur une plateforme dont la licence est en attente, et s'en rend compte seulement maintenant.

Only six days left until mica enforcement and u guys know where "big three" non compliant exchanges actually stand

binance spent five months on a greek application, got nowhere and pulled it this week to start over in an unnamed country with no timeline ,and well after already getting bounced out of the netherlands and pulling an application in germany too.

MEXC isnt even bothering with the polite version of this story itss not in ESMA's register at all,and the dutch regulator has formally warned that its operating in the eu without authorization.

But ok bitget is the most honest of the three its said outright it wont serve EEA users until its austrian application clears but a 2025 application still pending a Q2 2026 decision with days to go is its own kind of red flag.

Meanwhile bitpanda, kraken and coinbase just... did the paperwork on time and well they are not in headline coz theres no drama to cover.

three of the largest platforms on earth with years of advance notice and effectively unlimited compliance budgets are the ones scrambling, while comparatively smaller competitors sorted this out without incident. And yet 41% of European crypto app downloads in the past year went to exchanges that arent authorized , so millions of people are about to find out the hard way that biggest and compliant arent the same thing.

what do u think will they get the license

context: we've got maybe 6 services hitting llms, mix of openai, anthropic, and a self hosted llama setup for one internal classification thing that doesn't need a frontier model. was getting tired of each service having its own provider sdk wired in directly, every time anthropic had an incident (november outage comes to mind) we had no fallback path, just sat there eating 5xxs. openrouter first since it's the easiest onramp. literally swapped our openai client base_url and it worked day one, that's not nothing. model catalog is huge, way more than we needed honestly. where it fell short for us: no real way to set org-wide budget caps per team, it's more of a ""here's access to models"" layer than a control plane. also their uptime had a rough patch around a month in, maybe 20 min of elevated latency on one provider that took a bit to surface in their status page. portkey next. this one actually has the guardrails / caching / request-level stuff built in properly. semantic caching alone cut our repeat-query costs noticeably, didn't track exact percent but it was visible on the bill. the gap for us was more structural, we have 6 services and wanted routing policy defined once and applied everywhere, portkey felt more tuned for per-request config than ""here's the org wide rule, go"". orq's gateway (still calling it router half the time tbh, old habits) ended up being what we kept. budget controls and fallback chains are defined centrally, so when a provider has issues the fallback kicks in without any of the 6 services needing code changes, that part just works the way we wanted. downside, model catalog is smaller than openrouter's, if you want some obscure open source model day-one-of-release access, openrouter's probably still ahead there. none of these are ""best"", just depends what you're solving for. if it's pure model access, openrouter. if it's request level controls and you're not running across a ton of services, portkey. if you want one routing policy across multiple apps without touching app code, that's where orq's setup made sense for us. anyone running multi-region failover through any of these btw? curious if that's even handled at the gateway layer or if people still build that separately"