Xpektra

tinkerer | embeds | web dev | ee undergrad

[Xpektra @Xpektra7]

'Ubuntu slop'
@elxecutor @cracked_dan

[Swaroop Kumar Yadav @S2SmeX]

What first thing comes to your mind about this?

[Raheem. @raheem_d3v]

🤯

[Xpektra @Xpektra7]

Rule 99: If it exists, there is a linux themed distro of it. If there isn't, there will be. Only one known exception: rule 99 itself.

[Solomon @0xsolenoid]

Reading apps have trained you to never know what anything costs.
500 coins for $4.99 . Wait 8 hours or pay to skip. A subscription whether you read one chapter or fifty.
Charon just charges you a few cents for the chapter you read. That's it.
https://t.co/GDkYaGRBaI

[Xpektra @Xpektra7]

@cracked_dan @puruvjdev theme hunter 😂
I bet you'll change it after a week

[Xpektra @Xpektra7]

@FaDex000 😂

[Xpektra @Xpektra7]

@CodeCrafters11 Zed

[Xpektra @Xpektra7]

@thutmusx

[Xpektra @Xpektra7]

I do aesthetic and functional e-commerce sites to help take your akara or kuli kuli business digital.

Send a dm to book a slot.

[shadcn @shadcn]

What Makes a Great Streaming Chat Experience

Start here: Never move the reader against their intent.

1. Move only when the reader asked to move.
If someone is reading, don’t pull them somewhere else. Auto-scroll should never be the default.

2. Follow only while they’re following.
If they’re at the live edge, keep the stream in view. If they scroll away, leave them there.

3. Every interaction is intent.
Scrolling is not the only signal. Selecting text, using the keyboard, opening a link, searching should all stop the interface from moving.

4. Start a new turn near the top of the viewport.
This gives the new turn somewhere it can be read from the beginning.

5. Then stream in the answer.
The streaming answer can then grow into the available space.

6. Keep part of the previous conversation in context.
Enough of the previous turn should remain visible so the reader knows where they are. Context.

7. Let new content arrive offscreen.
The conversation can keep streaming without changing what the reader is looking at.

8. Show what’s happening out of view.
Make it clear when a response is still streaming or when new messages have arrived.

9. Make it easy to return to the latest reply.
A "Jump to latest" action should bring the reader back and resume following.

10. Let people jump anywhere in the conversation.
Long threads need message links, search, unread markers, and direct navigation.

11. Reopen where the reader left off.
A saved conversation should open at the last meaningful turn. This is usually the last user message. Not the absolute bottom.

12. Keep the reader’s place when layout changes.
Images load. Markdown expands. Code blocks render. Older messages appear above. None of that should make the reader lose their place.

13. Handle interruptions without stealing position.
Stopping, retrying, regenerating, branching, or errors should not unexpectedly move the conversation.

14. Stay responsive in long threads.
Streaming text, markdown, code, images, and long history should still feel responsive.

15. Be accessible without the noise.
Keep the transcript navigable, preserve keyboard focus, and announce important events at a comfortable pace.

It’s all about the scroll. Scroll Engineering.

[GK4lp @CaycGokalp11083]

@shadcn hey shadcn would you consider creating a new library for mobile app components for ios or android?

[Xpektra @Xpektra7]

no be abule-egba be dis 😂?

[Creepy.org @creepydotorg]

There’s an internet theory that claims this place exists in almost every city.

[Raheem. @raheem_d3v]

my new portfolio just landed
check it out and tell me what you think

https://t.co/Wi1CWF2nWJ

more projects coming🤞🏾

[Τhυτmυs ⚒ @thutmusx]

"SHE"

[Xpektra @Xpektra7]

@folonik_ The next big thing

[Xpektra @Xpektra7]

@trashh_dev peak! share how your rofi looks too.

[freeCodeCamp.org @freeCodeCamp]

Memory leaks are a common issue in React.

They happen when components leave event listeners & timers behind as they unmount.

Here, @_jongbo teaches you what causes leaks and how to fix them by clearing timers & more.

https://t.co/ihne2jNs0X

[Xpektra @Xpektra7]

@NikilKuruvilla @tannerlinsley @janmarshaldev @nextjs @tan_stack I've never thought of doing that,
I'll probably tweak Recall to do that specifically.
thanks man

[Xpektra @Xpektra7]

very few things can be funnier than @janmarshaldev using @nextjs docs to explain a feature he's trying to implement on a @tan_stack project

how bad can the docs be 🥲?

[Xpektra @Xpektra7]

@hokoridev @janmarshaldev @nextjs @tan_stack for streaming specifically I also prefer next js docs, it is *easier to understand* and it even has images