Still a very important service for many people who are alone.

Ai? Or a catch headline

We just should not use cloudflare. Why is everybody still trying to use cloudflare.

Counterpoint: I find networking challenging, and I'm not particularly accountable for the natural consequences of not knowing how stuff works.

This could end fine for everyone? Maybe an AI will understand it for me. (This is sarcasm. I agree with you.)

great article, and I had no idea that happened to Brian Krebs, of all people! o.O

I do think the EFF makes a good point though, and I think personally I tend to be biased towards content neutrality over moderation (at least, more strongly the larger the platform is, and Cloudflare is very large). Not to the point of Xitter, obviously, but I think there's at least a reasonable argument for Cloudflare in this case.

that said, after some searching, I did find the following two articles, and I find their arguments against Cloudflare very compelling:

• https://www.devever.net/~hl/cloudflare
• http://cryto.net/~joepie91/blog/2016/07/14/cloudflare-we-have-a-problem/

Fortunately I'm already using end-to-end SSL certs via Caddy, but now I'm considering just moving off Cloudflare entirely and instead providing regular backups to Internet Archive--most of the stuff I host is entirely static and very lightweight.

still hard. most projects still CDN online instead of packaging into a single application.

it's one of the most infuriating things about self-hosting. so I made my own self-hosted CDN and have rewrite rules that replace most public cdb domains and reroute them to my own local.

it would be great if I could just have something in the middle that would download once and cache locally on request, but it's effort that would be taken from my time afk.

Yeah, a great part of Lemmy's fundamental design is that it gives the user so much ability to block specific toxic users and communities and even entire instances from being seen by that user.

A user who is interested in self regulating or limiting that potential adrenaline overload ... is aided by Lemmy in doing so.

This is significantly different from how its nearest equivalent, reddit, operated untill about 2 years ago, when they finally added an actual block user ability.

Still don't think you can block the entire user group of subreddit communities, the way you can block an an entire Lemmy instance, if you want to.

(At least not without some third party script or software... which are probably all broken by now given how hard reddit is cracking down on its API?)

Also, moderation and admin logs are significantly less opague than on reddit.

To the best of my knowledge, on lemmy, you can't admin edit the post of someone you are arguing with to frame them, basically, and then turn them into a strawman of themselves, and then win that argument with them, and then ban them... as has happened on reddit.

Also Also, ... lemmy at least not yet does not appear to have a problem with a massive flood of ai bots posting god knows what % of the actual content.

...

Not saying Lemmy is perfect.

I'm saying its better.

And I guess I'm also saying there's a difference between being an alcoholic and enjoying an occasional drink from time to time.

Generally: Yes, of course, approach any online messsge board or social media with caution and skepticism... but different platforms can be significantly more conducive to generating negative mental health outcomes than others...

... short form video platforms collapse your attention span, anything that allows advertisements or 'influencers' who are basically just walking talking brand ambassadors lie to you to sell you all kinds of bs...

Thats not present on lemmy, at least not that I've seen... so in those ways, lemmy is the marijuana to say Tiktok's fentanyl.

That's how I read it too at first- and as bad as 'erotic role play' with a LLM chatbot sounds, the other one is so much horribly worse.

Jokes on you, my virtual girlfriend runs locally!

Cloudflare tries to enforce pretty strong vendor lock in by requiring you use their nameservers.

Also subdelegate domains are an "enterprise" feature, so no luck there.

Basically the CDN market sucks, not a shocker Netflix, Google, Valve, and many others operate their own.

No, she's just ghosting you.

You have a good boss!

Hmm.

I'm not familiar with the constraint.

I assume that the way that this works is that I host content at www.foo.com and they have their nameserver resolve www.foo.com to different IPs based on the geolocation of the browsing user's IP.

Is it possible to convert www.foo.com to a CNAME that can be redirected away from their nameservers? Like, I make www.foo.com be a CNAME directed at www.foo-cloudflare-cdn.com. They own www.foo-cloudflare-cdn.com, they serve A or AAA queries there on their nameservers. But if I want fallback, I update the CNAME to point at www.foo-backup-cdn.com, which is served by a different CDN.

Are there technical barriers to that, do you know?

It's a joke. I don't think there's really a website called Frank's Dildo Emporium. But if there is, lmk.

Quitting my last job for this one might be the best thing I've done since I tricked my wife into marrying down.

My mental and physical health has improved a ton.

I use it for DNS and domain hosting, but that's it, none of their proxying stuff.

The one downvote on this comment makes it like 20x funnier

I had guessed the nature of the site and "roleplay." It is a tad silly on my part to not have guessed "erotic"; thanks for getting me there (and not in an erotic way).

edit: Had left out the word "there."

Most people who dislike cloudflare do so for their centralization of the internet, rightly so.

Me? I HATE THE STUPID "VERIFYING YOUR REQUEST" PROMPTS. THEY TAKE WAYYY TOO LONG AND DONT WORK WITH MY USER AGENT SWITCHER. STUPID WEBSITES WITH 3 MONTHLY USERS ARE TURNING ON ADVANCED "DDOS PROTECTION" JUST TO MAKE EVERY FUNCTION OF THEIR APP TAKE 18 MONTHS

It also flags my DNS filter and nearly every site I go to has to "check if I'm human"

The way CDNs and virtual hosts work in general is to read the host field in the HTTP header, otherwise unless you dedicate an IP for each domain / "web site" there would be no way to know what to serve.

The issue is if you put the CNAME of foo www.foo-cloudflare-cdn.com. then it will just resolve to whatever the A/AAAA record is for that, and send the host of www.foo.com – which they will only service if that domain is hosted with their nameservers (they run automated checks to make sure you're actually doing so).
So there isn't really an easy way to just give cloudflare some subdomain, unless you pay them $$,$$$+ for the privilege.

Valve actually does that, ironically enough, for the steam community web assets they use Fastly, Akamai, and CloudFront, all on subdomains of course .