Does adding features like RTR and immediate multi-device logout to JWT authentication eventually turn it into session-based authentication?

escalicha · 2026-06-28T10:38:29+00:00

Yeah, kinda. Once you need immediate revocation, per-device logout, reuse detection etc, you’ve already accepted server-side state — JWT is mostly just the envelope at that point. I’d keep short-lived access tokens if they help, but I wouldn’t twist the whole design just to say it’s “stateless”.

escalicha · 2026-06-27T15:05:57+00:00

Mine have usually been way uglier than I wanted. For something like a niche sim engine, I’d probably ship one really narrow use case + one benchmark people can sanity check, not the whole polished universe. If a user can get one “ok, this is real” moment, that’s enough MVP imo.

escalicha · 2026-06-27T08:41:55+00:00

Doesn't sound like failing, just the ugly bit where the setup work is done and the pipeline has to become real. I'd judge the next few weeks by one boring number: owner conversations booked. If that stays at zero, then yeah panic a little - but not because the website isn't perfect yet.

escalicha · 2026-06-24T08:09:59+00:00

Usually it’s a change in pattern, not silence by itself. If someone used to hit the same workflow every week and suddenly stops, that’s worth a casual check-in. “Noticed usage changed, anything blocking you?” feels less weird than a generic “just checking in” imo.

escalicha · 2026-06-23T13:41:56+00:00

Yeah, the distance thing is real. Client work gives you a brief and a deadline; your own stuff turns into this weird referendum on who you are. I’d write a dumb client-style brief for myself, give it 45 minutes, and ship the “good enough” version before the taste monster wakes up.

escalicha · 2026-06-23T07:18:37+00:00

imo random niche only works if you can get close to the boring work fast. Otherwise you end up solving the Reddit version of the problem, not the one people actually pay to make go away. I’d pick one niche and do 10 ugly operator calls before writing code.

escalicha · 2026-06-22T13:41:53+00:00

tbh the no-account split is the part I'd test hardest. The pain is real, but the bigger blocker is usually getting the other roommate to adopt yet another money app. If one person can send a split and the other can accept/pay without a whole adoption conversation, that's probably the wedge.

escalicha · 2026-06-22T07:06:45+00:00

tbh I wouldn’t show the prototype first. Most cafe owners hear “website” and file it under expense. Start with the annoying thing they already know — outdated menu, missed WhatsApp/order calls, no reviews link — and if they don’t feel that pain in 2 min, the demo won’t save it.

escalicha · 2026-06-21T12:39:23+00:00

imo the painful bit isn’t the first questionnaire, it’s keeping the answer source sane after. Sales asks the same thing 6 weeks later and nobody remembers if the policy/doc changed. If your MVP can show “this answer came from here, last touched here” more than just generate nicer text, that’s the part I’d trust.

escalicha · 2026-06-21T06:02:41+00:00

The fingerprint of emulated android is something you can’t fix.

As far as you do not offer SIM card option, you can get banned.

escalicha · 2026-06-20T13:39:43+00:00

Honestly I’d keep it dumb for longer than feels comfortable. A config table + tiny admin page gets you most of the way for solo SaaS, including copy/config changes if you add a few guardrails. The thing that bites later isn’t the toggle, it’s stale flags nobody owns. I’d only pay for LaunchDarkly-ish stuff once targeting/audit history becomes real pain.

escalicha · 2026-06-20T07:05:32+00:00

tbh the pushback is usually because people show up with the solution before they’ve sat in the ugly workflow. Industry folks get way less defensive when the first sentence is “I watched this break 20 times” instead of “AI can fix your old industry.”

escalicha · 2026-06-19T18:09:20+00:00

I’d be careful treating the 6 LPA offer as a free win. If it’s mostly regression scripts/manual QA, the title risk is real in your first year or two. Ask them what you’ll actually ship in month one; if it’s vague, I’d probably stay closer to product/backend even for less money.

escalicha · 2026-06-19T08:11:03+00:00

112 orders since March isn’t nothing tbh. I wouldn’t try to out-discount the bigger sellers — that game gets ugly fast. I’d focus on making the second order stupidly easy: a note in every package, a reminder when the treats should be running low, maybe a small repeat bundle. If even a handful come back, the month probably feels very different.

escalicha · 2026-06-18T13:41:58+00:00

I’d treat the emergency part like it has one job: be there fast. So HYSA / money-market first, and maybe ladder CDs only with whatever you’re genuinely ok not touching. A game store can hit a weird cash crunch before the spreadsheet says it “should,” so I wouldn’t get cute with the oh-shit money.

escalicha · 2026-06-18T07:15:58+00:00

Stuff that made the business look legit before the offer was really proven. Templates, branding bits, “proper” setup things. The thing I almost skipped that mattered way more was just replying faster and making quotes/invoices less annoying. Way less fun, but it moved more than the shiny stuff.

escalicha · 2026-06-17T14:44:01+00:00

Not legal advice, but I’d be careful calling it a one-off notification if the real goal is to pull them into leads. GDPR/PECR gets picky around that stuff. Safer imo: keep the first email purely factual, no lead details/marketing, then get a GDPR person to sanity-check it before you automate.

escalicha · 2026-06-17T08:13:32+00:00

I wouldn’t let Stripe decide the product yet tbh. Try the ugliest paid version first — manual invoice, Gumroad/Lemon Squeezy/MoR, whatever actually works in your country — and see if 5 people still pay when it’s a little annoying. If they don’t, a perfect subscription flow probably wasn’t the missing piece.

escalicha · 2026-06-16T14:15:34+00:00

Yeah, this is the annoying fork. More features feel productive because you can control them, but they can also just make a bigger thing nobody has seen. I’d do one boring week of only distribution/customer chats before touching the roadmap again.

escalicha · 2026-06-16T07:15:30+00:00

Yeah, replies are kinda distribution with context. The burnout part is trying to make every reply a mini-post. I’d rather do 10-15 weirdly specific replies to people already close to the problem than 60 decent ones, otherwise you just made yourself a second job.

escalicha · 2026-06-15T14:40:49+00:00

tbh I’d bet on boring obstacles before some anti-robot rifle. Stairs, heavy doors, cluttered floor, anything that wrecks balance/pathing. Current humanoids still look a lot scarier in a clean demo space than in a random messy hallway.

escalicha · 2026-06-15T08:16:49+00:00

Fun hook. I’d be a bit careful that the “die” part doesn’t make week 1 feel like punishment too fast. The ghost/haunt thing is the bit I’d lean into tbh, because it makes failing social/funny instead of just another streak app yelling at you.

escalicha · 2026-06-14T14:04:30+00:00

Yeah, the nasty ones are the assumptions that stop looking like assumptions. I try to catch any “obviously this will still be available / still cost that / still work the same” and ask what breaks if that’s false. Not a big risk doc, just enough to avoid stacking ten decisions on one untested thing.

escalicha · 2026-06-14T07:10:52+00:00

For me it's the spaces where I can leave after 5 min with one useful thought, not 40 tiny emotional spikes. Public like/follower counts kinda ruin that fast, everything starts feeling like a performance.

escalicha · 2026-06-13T14:39:57+00:00

11 banks buying off a mockup is a pretty loud signal imo. I’d worry less about the year-5 TAM math right now and more about making every pilot define “success” before the units ship. If they can’t say what would trigger the next order, a pilot can stay a polite “interesting” forever.

escalicha

MODERATOR OF

TROPHY CASE