Haha, yeah 16 is actually pretty long.
I guess I’m just used to being forced 16 characters long passwords at long.
Haha, yeah 16 is actually pretty long.
I guess I’m just used to being forced 16 characters long passwords at long.
Consider shortening your passwords. Random passwords longer than 20 characters is a complete waste of time.
I typed it like that with the slim hope that someone would misinterpreted it, lol.
No VNC
Moode maybe.
Yeah, absolutely!
I actually like the change.
It’s just that it will create a lot of work for us (especially for me and my colleague) short term. I would very much appreciate it if Google actually bothered to give an exact timeline (optimally a few months or a year in advance).
PSA: All public certificates (private internal certificates won’t be affected) will have a lifetime of only 90 days soon. Google is planning to reduce their lifetime in 2024 but considering that they haven’t given an update on this since early this year, I doubt it will happen this year.
But it will happen soon.
This will be a pain in the ass for my workplace because we primarily use Digicert and manually renewing certificates every 90 days is just impossible for use. We are currently looking into a way to switch to letsencrypt or similar.
Yeah, that’s also fair. I have a tendency to overcomplicate things like this when all I wanted was a simple service.
Fair enough.
But personally I would recommend trying to setup wireguard if your router doesn’t have it integrated. It’s just so much faster than OpenVPN (usually the only built in option).
Moving to another port isn’t a bad idea though. It gives you cleaner logs which is nice.
You don’t have to host the VPN on the router. You can also host it on a separate machine or the same one that’s running the Minecraft server.
You don’t have to have a technical background though. Anyone from any background could learn it if they wanted too. A technical background obviously helps though.
But why are people even discussing that?
This is about an ICANN decision. TLS has nothing to do with that. Also you don’t really need TLS for self hosting. You can if you want though.
They didn’t make this too be easy to use. They don’t give a shit about that. That isn’t their job in the slightest.
They reserved a TLD, that’s all.
You can use any TLD you want on your internal network and DNS and you have always been able to do that. It would be stupid to use an already existing domain and TLD but you absolutely can. This just changes so that it’s not stupid to use .internal
Because that is a different feature.
And did you notice they call them “mitigation” and not “protection”? 🙂
Yeah, typo on my part.
You claim that Cloudflare doesn’t live up to their words. Please cite where in the terms of services it says that the DDOS mitigation is limited on the free plan or sources of free customers being affected by this. Or are you just saying “read the fine print” without having read them yourself and you are just using that as some magic way to win all arguments?
Anyway, I really don’t understand people’s obsession with DDoS, particularly self-hosting people. The chances of their little website ever being the target of a DDoS are astronomical. Many of them don’t take proper backups, and don’t worry about theft or fire or electric spikes, which are far more likely, but go frantic when they hear about features they’ll never use.
Yeah, I absolutely agree and I have said that to some in this post. But it’s even more worthless to argue about the free plan. It’s not like some private person is ever gonna be DDOSed so aggressively that Cloudflare would even notice. If an enterprise (like where I work) is in real need of ddos protection they would already be on the enterprise plan or they would be forced to it by Cloudflare.
Do you have a source for all your claims?
Everything I can find online says that cloudflare DDOS protection is unlimited and unmetered on their free plan. https://www.cloudflare.com/plans/
But honestly, even if you are not prioritised I doubt Cloudflare will ever run out of resources due to ddos attacks. And if they did the whole internet is pretty much down anyways.
I wouldn’t worry about DDOS attacks at all.
People simply don’t care about whatever small website you plan on hosting. Unless it’s something extremely controversial and you gain a lot of exposure suddenly.
It’s worth worrying about if you ever get big but until then just forget it.
I.E. do something about it when/if it happens and not before. A ddos is fairly harmless unless you need to stay up for some reason (and you don’t need to stay up).
Everything I have read before says that there is no limit for cloudflare free.
Are you sure about that?
A dude who’s very picky about whitespace.
As they said the app needs ongoing maintenance.