lsofzz

You work within the confines of the process and the existing workflow.

If you can't do that, then, forking is the right strategy.

It does not suggest one strategy is better than the other.

Plenty of `grown ups` disagree; It's natural.

Sorry bud, feel bad for you. Ignore the f*ckin morons.

yes sorta

According to Cloudflare, US still accounts for majority of the bot traffic though. https://radar.cloudflare.com/bots?dateRange=12w#bot-traffic-...

Yandex is just a drop in the ocean bud.

<3

slight drop - probably. i'd wager the drop in the ocean is because majority of the bot traffic are from it's cousins in China :>

what a fucking stupid meetings with stupid accents and stupid people talking stupid corporate shit making it sound like they are engineering a rocket. ffs, you are the plumbers writing the cruds.

smart meetings have `pauses`, `thoughts` and `i don't knows`. this is so fucking stupid that i find it lame enough not to use it.

tl;dr but i <3 it. upvoted this shit.

Hah. Yeah, I agree. It's one of those things I admit is `lost in translation` for sure.

I read this the other day - definitely think it is the right direction Nvidia is taking.

Thank you NVIDIA - for once (not twice though - you've given us nothing but despair for Linux+GPU).

like for example, c*nt?

A small side note I want to raise:

Folks need to be sufficiently motivated to learn it. All hell break loose when `RTFM` becomes taken offensively; What do I know - I am just a weird guy with a beard.

And folks always wanted to type the commands without RTFM'ing - now we have two problems instead of one.

Also, these were hard learned tricks YOLO'ing until 3.30AM debugging a failed DNS clusters or why the HSM suddenly decided to trip up at 5AM! Nobody even cares about the things we learn these days - Google and then your AI agent already does 98% of what I know already. So, let them blow up the clusters and the racks - your pal AI agent knows. Go ask them instead.

Good one.

:(){ :|:& };:

I hear ya. However, that ship has sailed a long time ago and succumbing to this very idea is exactly why puritans in any form will not survive the next 50 years.

Please read past the LLM-ness of any given post.

The message of the post is what _should_ hopefully matter to a reader.

And, not the fact that it was written by an LLM.

I am a technical guy at heart; also an introverted extrovert. I hate writing docs that are to be written to satisfy someone else's metrics. For it to be a tickbox'ed item.

I delegate that to an LLM. I want to spend my time solving interesting challenges instead.

So, Mr. Cantrill, you got a problem with that? So be it.

Agreed!

> NVIDIA is one of the most open labs.

Dude, where's the src for GPU drivers and the firmware blobs?

Sorry, you can't say it is one of the most open labs without qualifying a proper response to the question above.

Awesome. Fuck these CEOs and their `yatchs`!

Let's replace these motherfuckers.

> [ ... ] if you're clueless.

Done it. Therefore, I flex. I was talking about clueless folks like yourself.

> Again everything you've said does not really apply here or is impractical.

YMMV. Always.

Let me make this so simple that a ten year old can do it. - https://pi-hole.net/ (good enough but not `hardcore`) - browser ublock plugin/extension

if you want hardcore - segment the VLAN, egress FW, put your stoopid LAN devices on their separate VLANs, cordone off using gateway FW, DPI the packets, nullroute/blackhole DNS the shit out of trackers/analytics

wtf are you allowing plex to initiate outbound connections to begin with?

and why is plex not in it's own VLAN with a egress FW rules to second with?

lastly, why aren't you running snort/suricata to inspect the packets originating at plex?

let me solve this problem for you - it probably doesn't bother you at all.

otherwise, you'd scratched your itch a long time ago.

> Clueless lol.

It's ok to be clueless. And, it's ok to be working for a FAANG and be clueless too.

> Rockchip calendars

>.< haha i remember this

Bad post. No information on how to resolve this situation.

Coming from someone who worked at FAANG, this is sub par post.

You block it at inside your network by having the domain name not leak to start with. Run a resolver inside your network, and have DHCP response send DNS requests to your resolver. The resolver only queries upstream if it is not your local network's domain(s). Then, block all outbound DNS from your local network using your preferred firewall.

No leaks.

It took me 30 seconds to write this. Basic stuff.

Haha made my day

MM is basically up-selling his _Signal_ trust score. Granted, Signal/RedPhone predecessor upped the game but calling this E2E encrypted AI chat is a bit of a stretch..

Go read a book on basic cryptography. Please.

> I'm a Tech Lead, and nobody listens to me. What should I do?

TL;DidntRead

Precisely. Take the `TL` title out the door. Take the `ego` out the door.

Then, step in the door - as a friend, with empathy, proactive listening and support the engineers.

Round-table `discussions`. Not Waterfall.

My 2 cents.

> The people configuring WAF rules at CDNs tend to do a poor job understanding sites and services that discuss technical content. It's not just Cloudflare, Akamai has the same problem.

I agree. There is a business opportunity here. Right in the middle of your sentences.

Hint: Context-Aware WAF.

Many platforms have emerged in the last decade - some called it smart WAF, some called it nextgen WAF.. All vaporware garbage that consumes tons and tons of system resource and still manages to do a shit job of _actually_ WAF'ing web requests.

To be truly context-aware, you need to compute a priori about the situation - the user, the page, the interactions etc.

Thank you.