To be fair, CF mainly develops defensive cybersecurity products, the extent to which their tools might be used maliciously is pretty on par with other regular tools.
But, it just has bad optics and potential COI/Racketeering when CF is at both sides of the counter.
To be explicit, in case it isn't obvious,Cloudflare emerged as a DDoS protection company, detecting attacks from distributed sources is part of the raison d'etre, and domains and IP addresses are a key part of that infrastructure.
By subletting their own IP addresses for navigation with warp, and their own domains for hosting of webcontent with subdomain hosting, they are providing pooled anonimity for their customers, which is precisely what makes it very hard for defenders on the other side to implement foundational security measures like IP bans, or IP block bans, or domain bans, or Whois/RDAP domain analysis.
I use better auth for a side project i'm working on. It's open source, you can pay them to manage your user/auth tables if you want or you can run it all on your own db.
Sure, I guess if I'm using a web framework that is not quite batteries included, that makes sense, but Django, ASP .NET Core, Ruby on Rails, and so many others are open source and have authentication / users / roles baked in out of the box.
Yup yup basically this. Being consistent is great but I'll be pedantic and say the key is actually following up and then also being right.
As far as how to do it confidently? The same way you say "that is a tree" when you're looking at a tree. You're 100% sure you don't know, just say it. The rest is probably in your head. That's been my experience at least.
Is there somewhere I can read more about your setup/experience with your streaming site? I currently run a (legal :) streaming site but have it hosted on AWS and have been exploring moving everything over to a big server. At this point it just seems like more work to move it than to just pay the cloud tax.
I'm not saying that Next.js is good or bad but we deploy our Next.js app in a docker container and it's never been an issue. I'm curious what issues you had?
It's been a year since I was on the project and have since forgotten. I remember it being related to configuring security and middleware with the granularity required by a high-security client. There were other things too that were very hard to configure as soon as you stepped off the Dockerfile template provided by Next.js documentation.
That makes sense to me. There's another post on the front page right now talking about shortening the work week (I haven't read it yet tbf, so I could be wrong about it's content) because of AI. People have been talking about shorter work weeks for a long time now, it just doesn't happen. What does happen is we get more done and the GDP goes even higher.
I think that in countries with longer workweeks, that would be an incredible thing. There was recently a story about Denmark raising the retirement age to 70. If you graduate college at 22 and work the average number of hours until age 70 in Denmark, that's the same as working until 59 in the US and 52 in Mexico. Shorter workweeks will almost certainly translate into longer careers.
