LLMON represents a paradigm shift from Network Security to Cognitive Security. As a Caddy middleware, LLMON invisibly proxies your traffic, injecting "poisoned" instructions targeting AI Agents (like GPTBot or ClaudeBot) while ensuring the experience remains undisturbed for human users.

Detailed Breakdown

https://x.com/jf0lkins/status/1895373379924041985

Tooling

https://github.com/jaredfolkins/llm-ambidextrous-shell-synch...

You know that daily podcast my daughter has been creating?

It's not actually her.

Yes, out of sixty-five daily episodes, all of them are Ai generated using elevenlabs.io.

All the episodes except one.

Your goal is to find the one authentic episode that she created.

If you do, please submit your answer using the following form for a chance to win a mac laptop.

Best of luck!

LOL.

Super timely. Even on my linux box I noticed yesterday that zoom, even though I had "closed" the application, was still running `ps -ef | grep zoom` so I killed it.

After reading this, I've deleted it too. Super weird.

I saw a tray icon after I closed it out when I ran it this morning, on Xubuntu with the Cinnamon desktop. I right-clicked it and selected Exit, and it did indeed exit.

ETA: Checking the dpkg file listing shows that everything goes into /opt/zoom except a /usr/bin/zoom symlink to /opt/zoom/ZoomLauncher.

True, I used zoom about a month ago and it's still running a process in the background.

Um, why haven't you killed it?

Please understand that if you vendor your dependencies inside your go.mod project, you own them and will need to support and audit them in the future.

The mod command does not vet any computed hashes of the dependencies found in your vendor directory.

Running "go mod vendor" just populates the vendor folder which allows local development with all tooling. It does not force you to check in the vendor folder (you can even .gitignore vendor). Doing "go mod vendor" is not the typical "vendor", it does not make you the owner and you do not need to support and audit these packages (unless you actually vendor them in the sense of check them in).

You own your dependencies and will need to support and audit them in the future.

Note the lack of conditions on that statement, up to and including the fact this statement isn't even about Go, nor is it even about open source! It is simply a fact. You own your dependencies and you need to support and audit them. You are free to support and audit them by not supporting them at all, not auditing them at all, and blindly pulling in whatever random mutations they may go through in the future. You own the consequences of such terrible support. You own the consequences of good support.

You are correct and I was unclear. My statement is that you and ONLY you now own them. You've essentially forked the project and lost your community.

Though of course if you don't use "go mod vendor" then "go build" will require an internet connection, which is a problem for most distributions (package builds generally don't have an internet connection).

Why aren't your go build tools pulling from the GOPATH/pkg/mod/cache directory?

This would alleviate the need for your build to have a internet connection no?

Fresh builds (in an "rpmbuild" for instance) don't use a cache, for obvious reasons.

Howdy!

I gave up drinking at the end of October because I felt it was keeping me from some life goals.

I basically txt my sponsor once a day.

Making it through Thanksgiving was kind of tough, but it's all good.

With the mixture of determination and accountability I've put in place, I know I won't go back.

Another benefit, using your beer money to do fun stuff for your kids is an awesome feeling.

That is a awesome attitude to have.

This is a solid perspective. Thanks for sharing.

As someone who used to be a senior engineer for an ISP, shout-out to all the STBs with hard coded admin creds :-)

Shout-out to everyone who's ever worked for a large to mid-size ISP, that has acquired and eaten/digested a smaller ISP which has already existed for 12, 15 or 20 years... So much weird legacy gear in weird locations, doing weird things. So many SDH circuits and OC-whatever transport systems.

HAHA Are you me? This is sounds creepily familiar..

Seems to be an endemic problem, maybe if zayo buys everyone else noone will experience it again.