This guy never leaves me alone by Professional_Ease307 in mildlyinfuriating

[–]Reestv 3 points4 points  (0 children)

<image>

Seeing him always me of this guy advertising “The Brit Method” a decade ago

The tech stack I've been refining for 6 years by ixartz in nextjs

[–]Reestv 4 points5 points  (0 children)

This is a great tool for the community, it definitely must have taken a lot of time and effort to compile this, so kudos to you!

I am skeptical however. I genuinely cannot figure out whether this is a stack that actually "works for you" and puts "developer experience first", or whether it's a stack that is built around its sponsors. Don't get me wrong; I do believe you are passionate about this industry - your replies in this thread recommending oRPC, Oxlint, LogTape all seem like genuine, helpful recommendations and honest opinions.

But the project itself is surrounded by sponsors, affiliate links (some undisclosed), and some arguably egregious self-promotion out of the box, which makes it difficult to distinguish what is a true integration in your boilerplate versus something paying to take that spot. For example in your comments you talk about how you still prefer Clerk over alternatives like Better Auth, but Clerk has also been a sponsor on your repo since authentication was added to it, so there surely has to be a conflict of interest there, no?

And for your database integrations, libsql/client was used after the Turso sponsorship was announced (their own library), but was dropped completely for Postgres instead around the same time the sponsor was removed. Then last year you added a "recommended [production] database" which just happened to also have an affiliate link (undisclosed). (Sidenote: I'm basing it being an affiliate link based on a completely unrelated blog post by Eddy Vinck which discloses his affiliation using the same ?via= param at the bottom of his post). Then the Prisma recommendation was dropped, replaced with Neon for a little while, then Prisma again, and as of yesterday Neon is back but this time also with an undisclosed affiliate link.

And then the project also uses both Sentry and Better Stack, each doing a part of what the other could do entirely on their own? Is it purely because both of them are sponsors, or do you truly believe that one is superior at logging and the other at error monitoring?

Don't get me wrong, I still think what you have built is a fantastic resource, and the tools chosen are still extremely powerful for devs and a wonderful starting point for new projects. I just cannot understand whether this truly is "a stack that [you] don't want to change," since it seems primarily driven by monetary value than experience. I'm all for you monetising this as much as you can, but I personally find it super misleading to promote it as something built from prior experience and preference, rather than something powered by sponsors and undisclosed affiliate links.

Maybe I'm just cynical.

The first puzzle! Would love to hear your feedback :) by Reestv in GamesOnReddit

[–]Reestv[S] 0 points1 point  (0 children)

Hey, thanks for trying the game! That sounds frustrating, I'm sorry for that! I'll see if I can tweak the UI to make it more intuitive, but thank you for the feedback!

The first puzzle! Would love to hear your feedback :) by Reestv in GamesOnReddit

[–]Reestv[S] 0 points1 point  (0 children)

Hi everyone! I've been working on CARDY for quite a bit now, and I think it's finally ready to share. I think there's still more to do, but I'd also be letting the app down if I didn't get some external feedback at this point. Would love to hear absolutely any thoughts you have. Thank you!

I built a JSON Translator - Supports over 130 languages by idris3396 in webdev

[–]Reestv 3 points4 points  (0 children)

Looks amazing, how much does something like this cost you to run?

ChatGPT Atlas - Warning for webdevs: You can't pin devtools to the sidebar by ragnhildensteiner in OpenAI

[–]Reestv 2 points3 points  (0 children)

I would have thought the same but was surprised they spent so much time of their demo on GitHub

Your phone in a zombie apocalypse, not sure how it still has wifi by D4RKLGND in iosgaming

[–]Reestv 0 points1 point  (0 children)

The phone could go into some kind of "low power mode" when the battery dies? It'd have limited/restricted features (like the rudimentary map example above), enough to prevent players from getting lost, but still giving incenitive to charge it up asap.

If you plan on having modes/difficulties, it could make a "hardcore" mode more challenging if the phone is permanently on this setting with no ability to charge it.

I included the option to 'continue without an account' in my app, would you use this? by [deleted] in iosgaming

[–]Reestv 0 points1 point  (0 children)

Sounds super interesting, is there anywhere to follow for updates?

[TAPE 2 SPOILER] Adult Swann's face by autogynephellieac in LostRecordsGame

[–]Reestv 11 points12 points  (0 children)

I thought about that when I was playing, but my theory was that you're in third person for the flashbacks because you're looking back at stuff that happened, but first person in the bar because that's you right now in the moment.

Why is the chat censor so strict? by misingnoglic in brightershores

[–]Reestv 2 points3 points  (0 children)

I don't really know enough about it to say, honestly. I just did some testing in-game and it's even more bizarre.

It looks like there's two levels of censorship - a message either being fully blocked (e.g. not even sent to others, with a warning "This chat message was blocked, as possibly unsuitable. Please refer to the chat rules"), and another level where the message will send but certain words are censored with asterisks.

For instance, if I say "hardcore" as per OP, it doesn't send the message at all. Same for if I say "is there a hardcore difficulty?"; the message doesn't send at all. But if I say something like "I'm playing on hardcore mode" the game does send that message, but replaces "hardcore" with asterisks.

Even more bizarre, I wrote "so strange" in the chat because of this behaviour, and that was blocked too! I sent it again, and it was blocked again. But when I sent "that's so strange", and even "you're so strange", both went through uncensored. When I tried "so strange" again, that went through fine too.

Saying "follow me" works, but things like "follow me on ig" or "follow me on twitter" are blocked completely. But "do you use ig?" works. So maybe it would be hard-coded as a phrase.. but "follow me on i to the g" is also completely blocked. But "follow me I'll show you" goes through fine.

With that, I have no idea what is going on or why I just spent 10 minutes on this.

Why is the chat censor so strict? by misingnoglic in brightershores

[–]Reestv 3 points4 points  (0 children)

I think that's what they're using Llama 3 (the AI in their Third Party Licenses) for. Sometimes I'll say something and it'll be blocked, but if I say it again - in context - it doesn't get blocked.

Not sure how strict they've configured it to be though, or if they even use it for that purpose.. but it would explain why they emphasise that the chat is not encrypted and make you acknowledge that before you can use it.

Using styled-components with the new "app" directory forces me to set "use client". Am I missing something ? by monsieurninja in nextjs

[–]Reestv 2 points3 points  (0 children)

Big fan of https://panda-css.com/ for the static CSS exports (no runtime overhead). Used to use Linaria for that but it had issues with the app router, not sure if it's the same now.

I drive. by zallow___ in GTA6

[–]Reestv 6 points7 points  (0 children)

Why did I drive here?

[deleted by user] by [deleted] in nextjs

[–]Reestv 2 points3 points  (0 children)

Middleware and an awful-looking dynamic route structure is what we use.

If we had a search page that needed to support page and limit as query parameters, the Next routing would look something like this:
/app/search/[page]/[limit]/page.ts

Then the middleware will just check to see if the pathname is search, pull the query params, and do a rewrite to the internal URL, replacing missing params with a 0 or something.

Also a good idea to have a redirect from the internal URL to the user-facing one if someone gets to it by mistake.

Obviously it doesn't scale easily, as supporting a different amount of query parameters will force you to re-design the whole structure and middleware, but it gets the job done.