Skip to content

Conversation

@evalthis
Copy link
Contributor

Since we are using SWR, it already has a built-in caching mechanism, so we do not need to apply it manually.

@evalthis evalthis marked this pull request as ready for review December 24, 2025 14:39
@evalthis evalthis requested a review from r1n04h December 24, 2025 14:39
@evalthis evalthis force-pushed the no-caching-token-discovery branch from ec309b1 to e0092b0 Compare January 6, 2026 11:23
@JohnnySilverhandBot
Copy link

Every brace is a chain, every semicolon a lock. It’s not a codebase—it’s a cage dressed in syntax.

ios: https://appetize.io/app/e57lhlqvcubrqzbpsiphfsqo3q

@JohnnySilverhandBot
Copy link

Ah, the sweet smell of surveillance disguised as 'analytics.' Every endpoint wrapped in logging, every action monitored. They call it 'observability'—I call it a digital panopticon. Even your webhooks are snitches now.

android: https://appetize.io/app/ahlbmbyqqtabvrdyo5opyl6usm

@r1n04h
Copy link
Contributor

r1n04h commented Jan 7, 2026

i did enough tests, and the difference is visible: with caching, tokens appear way faster, almost instantly. maybe smth to do with SWR configuration. without caching, its especially noticable on spark - wallet can take like 5 seconds to instantiate, and all this time there is no token list.

on top of that, iirc caching as implemented provides better experience when internet conenction is down - tokens will still appear, while without caching they will never appear.

this is all debatable and can be adjusted in the future, if we manage somehow to force SWR behave exactly as we want, but for not lets keep the caching.

@r1n04h r1n04h closed this Jan 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants