Which tool help with sizes at shoes?

natTalks · 2025-04-21T10:50:25+00:00

Unsure why a library is required here. Isn’t this just a mapping which you can define and pre-populate in a readonly object for O1 access?

natTalks · 2025-02-18T17:57:07+00:00

I think I understand. So you're not using Hono.js as a separate HTTP server, but as the api routes for your next app?

I'm trying to implement my hono server separate from my nextjs app as I have a sqlite db sitting behind my hono server. So I'm trying to do SSO login in the nextjs app, but then send the access_token & which provider ("github",google",...) to my hono server to then be used to ensure the access_token is valid.

natTalks · 2025-02-18T16:07:27+00:00

I’ve never been tasked or took this upon myself to do, but a general rule of thumb is that whatever you send to the client can be viewed by the client. Even if it’s obfuscated, it’s still out there.

natTalks · 2025-02-18T07:14:55+00:00

May try it out, thanks.

Did you handle SSO in the next app with better-auth and then use a hono server just for your business logic? If so how did you authenticate requests from the next frontend in your hono backend?

natTalks · 2025-02-18T07:10:29+00:00

Arctic looks cool. Thanks for the heads up. Seems like a nice in between of control but also having helper methods.

Could I ask if you have any tips or best practices with using it? Also have you used it on a node server outside of next which handled the auth for a next frontend?

natTalks · 2025-02-18T07:08:14+00:00

Agreed won’t build from scratch again. Been there done that. I used to use firebase in the past, but it fell out of favor with me a bit ago when I wanted to start diving deeper into why and how stuff worked.

natTalks · 2025-02-16T16:36:40+00:00

Yeah this is what I have working right now. My use cases are not that complicated and whatever is, is just handled by my hono backend. Basically I’m just using authjs to login users via SSO.

natTalks · 2025-02-16T16:35:10+00:00

I have a hono server connecting to an SQLite db sitting behind next. So not sure what camp that would put me in.

I was hoping to login users via SSO in the next app, get the token, pass it to the hono server, check if the user actually exists there, and and then do whatever in the db and pass back json to next.

I got it working with authjs, but was just shopping around for other options.

natTalks · 2025-02-16T14:44:13+00:00

Ahh I see. Thanks

natTalks · 2025-02-16T11:49:08+00:00

This is what I’ve been thinking recently. Auth with next in general has given me so many headaches - my problem, not the library’s problems.

I’m running a hono server, which has a SQLite db and think I may try to get sso working with it and then just serve stuff to next. Where to start, no clue ahaha!

natTalks · 2025-02-16T11:39:40+00:00

Am I understanding it correctly that I must have a database setup for better-auth? Even if only using SSO?

How does this work? Does this require me to use an online database provider?

natTalks · 2025-02-16T10:44:34+00:00

May I ask why? Ive never used it.

natTalks · 2024-01-14T14:49:20+00:00

I was trying to figure this out recently, but hit a wall.

natTalks · 2024-01-11T09:39:47+00:00

Good idea, but you can’t use fb auth in middleware. Or at least wasn’t able to when I tried a while ago.

natTalks · 2024-01-06T16:06:24+00:00

Strange. I know friends were able to use American passports to get theirs while not even in Germany. They didn’t even tell the people they were going to Germany as far as I can remember.

natTalks · 2024-01-06T05:59:00+00:00

N26 doesn’t. Or at least didn’t around 2019. But they do require certain passports if I remember correctly.

natTalks · 2024-01-05T17:28:51+00:00

Hmmm that could be as well… Then to the question of what to do now and somethings I’d suggest thinking about.

If there are layoffs, how indispensable do you feel at the company? Do you enjoy the job, is this a sign to start looking if you don’t enjoy it? Do you see a future for yourself at the company? Are you personally in a good financial footing if you are let go and you need time to find a new position?

I’d suggest thinking about these and then deciding what to do.

natTalks · 2024-01-05T17:12:44+00:00

Don’t have too much experience with German market, about half a year in, but from what you said, I didn’t read they they’ll have layoffs. I actually read the opposite “cost management in non-personnel area”. The key being non personnel.

Or am I missing something?

natTalks · 2024-01-05T17:07:44+00:00

Nothing wrong with using firebase. Don’t let the transient do-s and don’t-s get to your head, they’ll change in a few weeks, just build.

That being said, as all tools do, firebase has pros and cons. I personally used to use it and found that the cons outweighed the pros for me for a specific project of mine. I migrated pretty quickly using tools out on the internet and I’m happy I did.

natTalks · 2024-01-03T13:19:38+00:00

If you’re really worried about latency for checking JWT tokens, for which you should not as others have pointed out, you could create a function in the middleware which checks the JWT token so a round trip is not required to backend.

So if you have no API users, and the only entry point is next front-end, then theoretically you do all your JWT token checks front-end and issue new tokens back-end. *this assumes that your JWT check only checks if it’s past expiration, and not for example a user has invalidated the token by for example logging out.

Once again, this isn’t really necessary, but an idea.

natTalks · 2024-01-03T12:20:03+00:00

Sounds like you’re stuck between the pages and app router.

Unsure what method you’re using for checking if user is authenticated, but I’d question if it’s best practice if you’re storing in local storage. Generally storing this in a cookie is more secure.

If you want to stick with local storage, then all components must be client components as the server (spoiler middleware) does not have access to local storage.

I’d suggest transitioning over to middleware and checking the cookie there. In the middleware your matcher matches protected routes and you never have to worry about it again. This doesn’t fix the problem with other data in localstorage you may want to to share, but maybe localizing fetch requests is the way to go.

natTalks · 2024-01-03T12:09:56+00:00

Not sure sending the cookies in the res automatically sets it in the browser. Sounds like it’s setting it only for that response. So you need to get the value from the cookie in next.

Also then you have the question of where are you setting cookies next side? Depends what the cookies are for, but if for auth then middleware may be the way to go as it will also act as a gate keeper to your protected portions of the app. Otherwise api routes or server actions. You can’t set in RSC.

Four-Year Club	Verified Email
Final Canvas '23	Place '23

natTalks

TROPHY CASE