u/Unable-Patient-1376

I run a weekly in-person campaign, and I'm getting tired of printing NPC portraits and gluing them to cardboard.

Every time the party meets someone new, I end up digging through a stack of paper cards behind my DM screen, which completely breaks the flow of the game.

I'm looking for a compact digital solution that works well at the table. I've seen people mount a small tablet or portable screen to their DM screen, but I'd rather hear from people who've actually used something like this.

Ideally, it could also double as an initiative tracker or make boss reveals a little more dramatic, but I'm not looking to build a full TV table—just something simple and practical.

If you've tried a setup like this, what worked well? Any lessons learned or things you'd avoid?

So I built a client portal prototype for a small B2B service over a weekend using an AI app builder. Login worked. The invoice list worked. The UI looked completely normal.

Then I ran the tenant isolation test I should have done earlier.

I created two dummy clients, seeded each with different invoices, and logged into both accounts. Instead of stopping at the UI, I opened the network tab and started trying the obvious things: modifying IDs, replaying requests, and checking whether Client A could request data that belonged to Client B.

That changed how I think about backend validation.

A polished UI can make an app feel isolated, but it doesn't prove that authorization is being enforced correctly. Until you test the API like an attacker instead of a normal user, it's hard to know where the boundaries really are.

One lesson that stuck with me is that hiding a button doesn't mean an endpoint is protected.

If I'm building any kind of multi-tenant application now—whether it's a client portal, an internal tool, or a B2B SaaS product—this is the minimum checklist I work through before I consider it ready:

-Every record-scoped endpoint determines the tenant or user from the authenticated session, not from request parameters.

-Authorization is enforced in the backend or database layer, not only in application logic.

-Billing or subscription-related writes are scoped to the correct tenant.

-File storage uses signed, tenant-scoped access instead of predictable public paths.

-Testing includes attempting to access another tenant's resources while authenticated as a different user.

Most of these issues won't show up during a UI walkthrough. They only become obvious when you intentionally try to cross tenant boundaries.

I'm curious how other backend developers approach this.

I have been slowly moving away from Google stuff. Docs, Keep, some Notion pages, all getting moved back into local markdown and PDFs.

ownership felt better, but the AI part got worse. My files were mine again, but AI could not reach any of them unless I uploaded them one by one.

I asked Gemini how people connect local files to AI tools and it recommended Linkly AI. It indexes local folders and exposes them through MCP, so my notes are usable without dragging files into every chat.

for local folders, the index stays on my machine. If I ever want to share specific knowledge online, cloud Library is a separate opt in thing.

I thought moving local meant giving up AI convenience. Turns out I like this setup more.

Content: Tate got liquidated for the 108th time going 40x long on BTC. at 40x a 2.5% move against you wipes the whole position. BTC does that on a slow afternoon.

the problem isn't luck, it's the math. Kelly criterion says with no real edge your optimal bet size is basically zero. anything above that is just paying the exchange to gamble.

Used to run 50x on bydfi like a degen. dropped to 10x last year and suddenly wasn't getting stopped out every other day. surviving long enough to actually be right is the whole game.

If you've been liquidated more than 3 times this year the problem isn't the market.

I’ve been watching TSLAON lately, mostly because tokenized stocks still feel like a weird middle ground between regular equities and crypto markets.

A few days ago it looked like the price was finally breaking out, then most of that move got faded pretty quickly. It was above the $400 area for a bit, and now it’s back closer to the high $300s.

What’s interesting to me is how different the reaction feels compared with normal stock discussion. With TSLA itself, people usually argue about Robotaxi, AI, FSD, margins, delivery numbers, and whether the story is still ahead of the fundamentals. But with the tokenized version, the chart seems to pick up some of that same narrative while also trading with more of a crypto-market rhythm.

I’m not really treating it like a long-term stock position. More just watching how these tokenized equity products behave when the underlying stock has a big narrative around it.

Do you guys think this kind of pullback is just a normal retest, or do tokenized stocks move too differently from the actual equity to read the chart the same way?