Basically:

- /handoff file creates a short document with the important context from your current session and maybe next steps as checklist.

- You can then start a fresh session with /continue file

- You can also hand the work from Claude to ChatGPT, or the other way around. Very useful at time of session limits.

- Plus your handoff files becomes a useful piece of project memory that you can reference later.

I find this much more useful than /compact or /clear because the context is saved in something portable instead of being tied to one session and i've seen better results doing this every 20 messages or so than running long sessions.

For some reason, my brain follows it, and I fall asleep much faster. It works way better for me than box breathing or most other sleep tricks I've seen. Sharing in case someone else finds this useful.

> If your work isn't ready for users to try out, please don't do a Show HN. Once it's ready, come back and do it then. Don't post landing pages or fundraisers.

https://news.ycombinator.com/showhn.html

Session handling, auth, crypto, password hashing etc - all these are the exact areas where you should be the most allergic to rolling your own. Not because you're not smart enough, but because a simple bug like sanitizing in the wrong place and the failure is catastrophic like in this instance.

Use boring, proven, widely-audited solutions. Save your creativity for the actual problem you're solving.

Comments URL: https://news.ycombinator.com/item?id=47174318

Points: 2

# Comments: 0

Is this a cleaner look? I have always loved visible scroll bars because they act as useful guides for where I am on a page and how much content remains and just easy to drag. Now you have to hover over it first.

I am curious what UX changes have stood out to you lately, for better or worse.. Maybe some designers reading this forum will take notes.

Comments URL: https://news.ycombinator.com/item?id=46787079

Points: 34

# Comments: 36

It could be that I'm a bit old-school, but this really seemed to confirm that ready to play fun gameplay trumps realistic graphics any day!

Imagine just one link in a tweet, support ticket, or email: https://discord.com/_mintlify/static/evil/exploit.svg. If you click it, JavaScript runs on the discord.com origin.

Here's what could happen:

- Your Discord session cookies and token could be stolen, leading to a complete account takeover.

- read/write your developer applications & webhooks, allowing them to add or modify bots, reset secrets, and push malicious updates to millions.

- access any Discord API endpoint as you, meaning they could join or delete servers, DM friends, or even buy Nitro with your saved payment info.

- maybe even harvest OAuth tokens from sites that use "Login with Disord."

Given the potential damage, the $4,000 bounty feels like a slap in the face.

edit: just noticed how HN just turned this into a clickable link - this makes it even scarier!

Comments URL: https://news.ycombinator.com/item?id=45821977

Points: 1

# Comments: 0

Without updates, many sites will likely stop working with it soon.

Kiwi had some great features, like disabling AMP mode, rearranging the Chrome Store for mobile, and customizable tab layouts, etc. These features might interest others as well.

I did recently see this browser is unsafe when trying to open Gmail in it, so any chromium based update to date alternative there would be amazing!

The last time I used it one of the common hacks was adding 50 makers to a single app launch PH also openly condoned mass email blasts and tweets to drive votes which just rewarded whoever could push the hardest on promotion

In contrast Hacker News discourages asking people for upvotes and even treats it as a negative if you do That longterm focus on signal over hype is probably why HN still feels useful today while PH lost its way

Comments URL: https://news.ycombinator.com/item?id=44980760

Points: 3

# Comments: 0

- Big models like GPT-4 are split across many GPUs (sharding).

- Each GPU holds some layers in VRAM.

- To process a request, weights for a layer must be loaded from VRAM into the GPU's tiny on-chip cache before doing the math.

- Loading into cache is slow, the ops are fast though.

- Without batching: load layer > compute user1 > load again > compute user2.

- With batching: load layer once > compute for all users > send to gpu 2 etc

- This makes cost per user drop massively if you have enough simultaneous users.

- But bigger batches need more GPU memory for activations, so there's a max size.

This does makes sense to me but does this sound accurate to you?

Would love to know if I'm still missing something important.

Sure, they have huge GPU clusters, but there must be more going on - model optimizations, sharding, custom hardware, clever load balancing, etc.

What engineering tricks make this possible at such massive scale while keeping latency low?

Curious to hear insights from people who've built large-scale ML systems.

Comments URL: https://news.ycombinator.com/item?id=44840728

Points: 574

# Comments: 365

[1] https://www.viberank.app/

My browser just froze after scrolling half-way. Not sure if this is something to do with the scroll fx but i really don't understand why this simple site is maxing out my CPUs.

When some users burn massive amounts of compute just to climb leaderboards or farm karma, it’s not hard to imagine why providers might respond with tighter limits—not because it's ideal, but because that kind of behavior makes platforms harder to sustain and less accessible for everyone else. Because on the other hand a lot of genuine customers are canceling because they get API overload message after paying $200.

I still think caps are frustrating and often too blunt, but posts like that make it easier to see where the pressure might be coming from.

[1] https://www.reddit.com/r/ClaudeAI/comments/1lqrbnc/you_deser...