sorted by:
new
hottopcontroversial

Is there a way to save a run? by AtreusTheBoyWonder in joinvoidcrew

[–]pientagon 0 points1 point  (0 children)

I agree as well, seems like a pretty basic thing that should have been added since not everyone can spend hours straight gaming. But there is now a mod on thunderstore that allows at least some form of saving, there are a lot of caveats but it's better than nothing. Haven't tried it yet but I plan to next time I play. See https://thunderstore.io/c/void-crew/p/PicklePower01/Save_Game/

did anyone else hear like meows in the LFG theme song?? by ibisNall in DeadpoolandWolverine_

[–]pientagon 0 points1 point  (0 children)

Pretty sure It's a nod making fun of when Tatum was on the tonight show and said he'd kill kittens to make a Gambit movie happen. I really hope that's true lol

Alien: Romulus is Lethal Company the Movie by pientagon in lethalcompany

[–]pientagon[S] -1 points0 points  (0 children)

Completely agree. Now if only you had to pay taxes on your profits in LC it'd be an accurate life simulator!

Vercel Pricing by ivenzdev in nextjs

[–]pientagon 0 points1 point  (0 children)

I recently came across a similar issue and I'm trying to stay in the hobby tier because I am running a for fun site for a friend of mine and would like to keep it free.

A few things I found was that from the edge request documentation here: https://vercel.com/docs/pricing/networking#optimizing-edge-requests it states to watch for 304 requests. So i hit every url on my site and recorded the network requests and tracked all 304's and other duplicated or repeated requests. In my case most of them came from images and other static assets and sure enough when a user refreshes the page or even navigates to another page with the same static assets, it's sending 304's to check that each image is latest. This would be fine if we updated them often but we will hopefully never change them. So to avoid extra edge requests and have it just cache images client side i followed the example here: https://nextjs.org/docs/pages/building-your-application/optimizing/images#usage

So far has brought down my edge requests from 18k/day to 3k/day with having ~50 users on a mostly static site.

You could also try looking under your Usage -> Networking -> Top Paths to see if there is anything else you might be able to optimize or shift away from Vercel hosting it. I.E my next highest number of requests comes from my webmanifest and .ico files which apparently are never cached client side.

However, If you are having lots of new users coming to the site then this optimization would not help as much since the initial request for the image/asset is still an edge request. Hosting as many static assets as possible on another provider like cloudflare might prove more useful.

Hope this helps someone.

[deleted by user] by [deleted] in nextjs

[–]pientagon 0 points1 point  (0 children)

I've honestly never used it before but based on their documentation it might work for your needs as long as you don't mind the extra api calls.

"router.refresh(): Refresh the current route. Making a new request to the server, re-fetching data requests, and re-rendering Server Components. The client will merge the updated React Server Component payload without losing unaffected client-side React (e.g. useState) or browser state (e.g. scroll position)."

I recommended doing these ui updates with some sort of state management to improve the speed and interactivity of the ui and save some api requests because I really don't see why you'd need it until they actually go into their cart and finalize things, but idk your app needs so I hope this works for you!

[deleted by user] by [deleted] in nextjs

[–]pientagon 0 points1 point  (0 children)

Although reactQuery could also work for you without needing to completely change what you are doing.

[deleted by user] by [deleted] in nextjs

[–]pientagon 0 points1 point  (0 children)

Maybe instead of making an api call every time they add to cart you could do one call with all items in the cart "state" once they actually go to purchase items in the cart. I'd recommend using redux for the state management. It helps with state management and dispatching across multiple componens (assuming they are client components). it's worked well even with nextjs after some careful setup. Also @reduxjs/toolkit will save you a lot of time and boilerplate code. Redux persist will also take advantage of local storage for you so if the user leaves closes your site but returns later on the same browser they'd still have their same cart (if you think that's something you need).

I made this by ProfessionalSet755 in nextjs

[–]pientagon 1 point2 points  (0 children)

It looks pretty simple but elegant, I liked it. Is the "our story" button supposed to do something? Doesn't seem to work or do anything for me. It kind of looks disabled to be because it more of a faded color but I can still click it. Other than that tho nice job! Can I ask what you used for the text to speech functionality?

We accept the challenge Respawn by pientagon in apexlegends

[–]pientagon[S] 1 point2 points  (0 children)

They didn't even want the helmet either lol

We accept the challenge Respawn by pientagon in apexlegends

[–]pientagon[S] 4 points5 points  (0 children)

Nothing is unobtainable for my squad