@benjaminakar Very nice tool. I noticed when clicking "Show in another currency", the conversion is wrong, the USD amount shows less than the EUR amount, although 1โฌ=1.19$
Love the breakdown. Seems like everything we love about Ralph is slowly but surely baked into Claude Code on its own. Is the subagent thing documented somewhere? As far as I understand, each subagent has its own context window? How many subagents would Claude launch? Depends on how many can be done in parallel?
So if you wanted to reach the equivalent performance of 16 GB physical RAM with Google Drive, is it even reachable by choosing a high enough memory (e.g. 2 TB)? Or does it not matter what size, the disadvantage will be there and picking a higher memory will only result in more processes being able to run in the same time?
@grok@sysxplore So ROM is mostly terabytes, while RAM we're in the 8-32GB range, if you download a RAM via Google Drive it has how many GBs? And how would they compare performance wise considering the latency etc?
@0x3st3ban @scaling_shields Some bullshit that AI can spill you in 1 response. But the boomer you got on the phone doesn't know shit about the internet and will still buy, I guess
I also noticed that when you use a Link on a dynamic page with cacheComponents, it suspends because internally it uses useRouter which internally uses useParams. Despite prerendering the page with generateStaticParams, when navigating to it the Suspense boundary is shown, unless you have "prefetch" set on the Link. But that means we're at the mercy of the page being prefetched when the Link is visible/hovered, but I already prefetched it during build time so it should also work when prefetch=false is on the Link since the page should already be in the ISR cache from the build time
About the new cacheLife being passed to revalidateTag, I don't fully understand what difference the profile you pass makes, since the content is marked as stale immediately. So the profile should only influence revalidate and expire, but since on the next visit it should automatically perform a background fetch for the now stale resource, I wonder what difference it makes if I pass revalidate 3600 or revalidate 1000000. Does the profile determine how it will behave in future stale cases? Like let's say I pass revalidate 3600, does that mean the flow is like this?
- Server calls revalidateTag with revalidate: 3600
- Resource becomes stale immediately
- On next visit, serve stale version and refetch in the background
- On subsequent visit, serve the fresh resource
- After 3600s, consider the fresh resource stale and revalidate again in the background, without any further "revalidateTag" needed
If so, I also wonder how this would clash with revalidate being set on the tagged resource
About the new cacheLife being passed to revalidateTag, I don't fully understand what difference the profile you pass makes, since the content is marked as stale immediately. So the profile should only influence revalidate and expire, but since on the next visit it should automatically perform a background fetch for the now stale resource, I wonder what difference it makes if I pass revalidate 3600 or revalidate 1000000. Does the profile determine how it will behave in future stale cases? Like let's say I pass revalidate 3600, does that mean the flow is like this?
- Server calls revalidateTag with revalidate: 3600
- Resource becomes stale immediately
- On next visit, serve stale version and refetch in the background
- On subsequent visit, serve the fresh resource
- After 3600s, consider the fresh resource stale and revalidate again in the background, without any further "revalidateTag" needed
If so, I also wonder how this would clash with revalidate being set on the tagged resource
New on @XoxnoNetwork xLend โก๏ธ
โ Liquid Staking: Your account analytics now also include your liquid staking earnings of XEGLD and LXOXNO
โ Share your projection: Your global, lending or position analytics can be shared. Share with friends or for your own spreadsheets
Enjoy!
New feature just landed on @XoxnoNetwork xLend:
Supply or repay for another person ๐ค
Instead of liquidating a position, why not help a brother out? More of a niche feature, but it can open up interesting use cases ๐
Enjoy!
Good news for everyone browsing @XoxnoNetwork's open-source lending protocol:
Instead of redirecting you to the market/profile pages, we now show them inline as modal โก๏ธ
This way you can quickly check out multiple markets/users without losing your scroll position ๐ฅ
Enjoy!
New on @XoxnoNetwork xLend:
Bulk Supply ๐ฐ
We get it, you don't want to create positions one by one to supply your tokens. With 2 clicks you can now supply all your wallet tokens (or parts of it) to the lending protocol โก๏ธ
Enjoy!
Another quality of life update for @XoxnoNetwork xLend:
Destruct LP โก๏ธ
When removing collateral, tick the switch to destruct the LP in their base tokens and unwrap the EGLD. What was a swap or xExchange unwrap before is now embedded natively in the lending protocol ๐
Enjoy!
@jamannnnnn How would you make it multi language though? By going to the generated key definition and making one for other languages?
Wouldn't that be a bit messy then, e.g. in your de.json you would have to write sth like:
"e26ha": "Schau Mama, keine Schlรผssel!"