thevinchi

This is the way. If you’re not running your agent harness/framework in a container with explicit bind mounts or copy-on-build then you’re doing it wrong. Whenever I see someone complain about filesystem access and sequirity risk it’s a clear signal of incompetence imo.

Autonomous weapons: agreed, not ready… yet.

Mass surveillance: Agreed… but, I do wonder how we would all feel about this topic if we were having the discussion on 9/12/2001.

The DoW just needs to wait until the next (manufactured?) crisis occurs, and not let it go to waste.

Mark my words: this will be Patriot Act++

Until this moment, I did the same thing… but right now I realize, this behavior incentivizes a domain owner to intentionally break their site, to trick the visitor to disable their blocker.

Then the browser: refreshes the page, downloadz all the thingz… presents cookie banner.

I’ve been using uBlock (or Brave) for years now, and when “something doesn’t work right” the first thing I often do is lower my shields… :facepalm:

From now on, I’ll just bounce. Keep your cookies, I’m not hungry.

I’ll concede that IPv6 has usefulness on the public Internet, where adoption is actually gaining nicely. No issues there really.

However, my comparison is end-user focused (ie. the Linux desktop experience). I should have been more clear about the scope perhaps.

Both IPv6 and Wayland have increased complexity and surface area for pain (cost) without an obvious benefit for the end-user.

Also: wrt IPv6 specifically, I don’t believe every device on a private network should be publicly addressable/routable. To me that’s a bug, not a feature, and again does not serve the consumer, only the producer.

Wayland smells like IPv6 to me. No need to switch, and it hurts when you try.

It’s all fun and games until your ISP changes your prefix and breaks all your firewall/routing rules. I tried to adopt IP6 with Spectrum internet, but every time the cable modem reboots, my prefix changes and breaks everything. No thanks.

lost me at `npm install …`

The “My Big TOE” trilogy of books by Thomas Campbell is an excellent white rabbit to follow deeper into the magic of this topic imho.

GitHub Copilot nvim plugin[1] has autocomplete with ghost text, but of course it requires you use GitHub Copilot :)

[1]: https://github.com/github/copilot.vim

This doesn’t even come close to CodeCompanion[1], which doesn’t require any new LSP config/dependencies or filetype limitations.

There is no ability to share the current buffer(s) for context, no tool support. This seems like a checkbox release. You’re better off using CodeCompanion with Amazon Bedrock, which includes the added benefit of sovereignty.

[1]: https://github.com/olimorris/codecompanion.nvim

I can think of no reason to be surprised by this, except that Cisco is the one reporting it. That part is surprising.

Interesting timing. I was just reading about a new self-hosted router [1] today. Now I’ll definitely need to check it out.

https://github.com/felixszeto/NiceAPI

I’m a big fan of durdraw[1] for crafting ANSI/ASCII art in the terminal, but this takes it to a whole new level, excited to try this especially if it includes color? From the website examples it doesn’t appear to include a color palette, but if it does then game on!

[1] https://github.com/cmang/durdraw

fwiw: I’ve never run webtop with privileged mode or docker-in-docker enabled, those are both optional.

I’ll just leave this here, thank me later:

https://docs.linuxserver.io/images/docker-webtop/

These images are top-notch, well documented, and have recently been refactored to use Selkies under the hood. Even with gamepad support, I’ve used these for running DOSbox, RetroArch, streaming video, and many other things.

There’s even a mature extensibility layer for using their images as a base layer to add services and apps.

Can’t speak highly enough of the linuxserver.io folks.

I came here to say the same damn thing.