joshgermon

It's great for development environments or scheduled jobs, the 15 second start up time limits it for most other things I'd imagine. Is it still minimum cost of ~45/month for the lowest instance? I guess this will help that but it would be great if it was priced closer to V1.

Yes, we know increased profits always go to the worker. Particularly when the business needs to rely on exploiting them to make those increased profits.

Let me try your logic here...

Employees benefit from no paid annual leave! How you ask? The employer is able to offer better service to customers, and make more money, and the employee can negotiate a higher salary from the more profitable business.

Am I doing this right? Workers give up more rights but in theory they can negotiate higher pay because the business is more profitable?

Keep in mind all the low-income employees who are harassed after work for trivial reasons that can absolutely wait by power-trip managers who will now feel a tiny bit more empowered to say no than they did yesterday. I think it's a great thing even though it doesn't benefit me directly.

If you rely on exploiting the fact that your employee does not have the right to ignore your call outside of hours, your business shouldn't exist. What kind of take is this? It says it gives them the right to ignore, not to sue the business if they do call.

Congrats on the product - looks great! I'd love to hear more about your experience using Tauri for this? What are the pros/cons and do you feel like it was the right choice so far?

Nope, just saying it's not something I need in the alternative. Doesn't need to be a full stack/backend framework - just focus on frontend and SSR.

What are the viable alternatives for those who don't care about the API routes but still want some level of pre-rendering / SSR? Staying in the React ecosystem that is.

Remix is always touted as the alternative but it seems like a whole new approach to learn and it's own strong opinions.

I've been using Next for 3+ years but I don't feel confident to start a new project today. Do I go to the dying page router? Or trail blaze with the app router with all the teething issues and issues everyone's encountering (myself included).

Yeah which honestly I don't mind the middleware approach for authentication although the route matching is pretty bad for fine grain control.

However another thing is the middleware is all through the edge runtime. So things like regular postgres drivers don't work (although I did hear that Cloudflare workers added TCP so maybe that's coming).

I will say Planetscale and the hottest db as a service platforms all seem to have an edge adapter to allow for this but your SOL otherwise.

Hey really appreciate this advice! It's quite refreshing to here someone who works at an Auth provider not understating the usability of some of these libraries and frameworks.

FusionAuth seems really great too, in my journey down this path I've come across quite a few people using your hosted service on very large apps who have nothing but praise, so kudos!

One question I have is, when you say multiple apps, are you speaking in a sense of they are at all related? Or every small app/project you have related or not?

Appreciate the call out, will definitely check this out. I haven't seen them mentioned much before..

Very interesting to have a per request model, instead of MAUs. I think I prefer that too.

Oh really? I mean I'm almost to relived to hear this because the "never roll your own auth" crowd is honestly deafening.

You ask any question on a lot of sites and communities (twitter, reddit, stack overflow) just about anything to do with auth and you'll get slammed with comments preaching about this.

I think Hacker News is somewhat an outlier in this I will say, as in previous threads this doesn't seem to be anywhere near as common.

They always have the same "you think you know better than the 1000s of auth and security experts working on Auth0 or xyz". Which, no obviously not. But there's clearly defined standards such as bcrypt and how to handle sessions etc; and even the OWASP cheatsheets too.

I feel I could implement an auth service wrong too with calling their API if I really tried.

This is timely. I am stuck on simple authentication for my small apps. Everyone tells me - "Don't roll your own auth EVER!!!!", and then tells me about some easy-to-use Auth as a service.

Ok, great. Well if I'm buying my auth I at the very least need some kind of 2FA, MFA or something. I don't care about anything other than user/pass and MFA. But every service wants to charge you well over $100/mth for any kind of MFA. Why can't they just forward the transactional SMS/Email charges on? Or better yet just give the authenticator app options.

I feel like user/pass + MFA isn't asking for the world and not including any kind of MFA to me feels like potentially worse security than "rolling my own" simple bcrypt + regular old sessions and then can add on MFA too using well defined standards and libraries.

Now I do like these open-source options but again, they seem faaaar too complex for what I want. I could definitely implement simple session and hashing auth much quicker than setting up any of these. Which I completely understand as this is complicated enterprise identity systems here. I don't need that though!

Anyway rant over. Anyone else have this experience or am I alone?