Could you use claude via aws bedrock?

Sure, but that'd be charged at API pricing. I'm talking about subscription mode above.

I thought Wayland was different from X11, and didn't allow this. But I'm far from an expert on this topic so I'd like to learn more.

https://github.com/neonkore/waypipe proxies Wayland over a network. It’s straightforward enough in theory: Wayland core is just a communications protocol plus shared memory; so you just need to forward the messages, and detect and send changes in the shared memory. Not the cheapest thing, but perfectly tractable. Of course, there are also more difficult extensions, like GPU integration, but that sort of thing was a problem for X as well.

This is how modern x11 worked too since nobody uses software rendering with x primitives anyway.

Wayland natively isn’t built for forwarding the way X11 is. Waypipe fixes this, providing an X11 protocol equivalent for Wayland. This project is a waypipe client for macOS.

here is Wayland vs X11 visualised.. it might help - https://vectree.io/c/compositing-window-management-architect...

According to that page Wayland's architecture is simpler than X11.

If you put everything into a monolith, it looks simpler than if you have components that have to speak protocols to each other.

Rio and its predecesor in Unix v8/v10 did it better than X. In some cases we got the worst:

- POSIX bloat vs Plan9's simple C and even simpler API

- ioctl's vs everything it's a file

- Complex socket spawning vs open() and dial() under Plan9/Go

- ALSA vs tuned up OSSv4, or plaing audio/mixerfs under 9front

- find -which syntax is huge- vs walk -f (or -d for dirs) | grep

- RDP/VNC/SSH/NFS/SMB vs just rcpu+auth (9p) and run rio(4) and for files... 9fs which does a simple bind()

- Symlinks and hard links vs bind and namespaces.

- GDB and SSH vs importing a remote /proc in a rio window and remote-debugging your damn remote machine as if it were your own. How cool is that? Ditto with devices. Import sound cards, network cards with the whole IP stack. NAT you say? No more.

- FFSv2 (hello OpenBSD) vs current GeFS under 9front which is like a miracle over what OBSD it's trying, the bad ZFS license or BTRFS not being ready on GNU yet. Probably the Hurd people will port GeFS to Hurd/Mach first, before BTRFS gets even ready...

- Dynamic vs static linking. 9front, a suite of multiarch compilers. Set $objtype, compile, link, deploy a standalone binary. Ready, as if it were a Go binary under Unix, but without glibc oddities. ARM binaries from 386? Done. You need a crazy long i686-gnu-foo-bar and the rest of crazyness? Not anymore. These come in src form, compile and install them, no internet required. Literal two damn commands to do so, from any to any arch.

- SH/KSH/Bash. Complexity ridden shells. Here's rc. No aliases there, just functions. No complex escaping, just () for strings, ^ to concat, ' ' for quoting. Problem solved. Even the conditonal words' syntax it's like throwing down all the complexity giving you a weirdly simple shell.

- PCRE and ex commands under vi/nvi/vim (bloat) vs Sam and structural regexes. Sam it's like a graphical vi, period, there's nothing alien of it. Imagine a modeless vi with a small frame to input commands with an easier syntax:

     x/lookup/c/replace 

These can be chained with ease.

> permitted a single ECS task role "read access to every secret in the account, including the production Redshift master credential."

...

> noting that the stolen information was old and consisted mostly of non-critical details

So I guess 'mostly' is doing a lot of heavy lifting, and they hadn't rotated the credentials in a long time

Like the headline said, you had to be there...

Of course, nostalgia slop can exist for any period. But it can be interesting to stop and think about how the little details of everyday life have changed over the years.

Yes. And I'm sure the next administration will as well. These things only ratchet in one direction.

You would still be able to use the telnet client to connect to an SMTP server on TCP port 25, just not port 23, right? I don't think that part changed here.

It's... not super clear from the article whether this is a port block or a stateful protocol thing. But yes, you're probably right and SMTP spoofing is probably safe for now.

I read it as a clear port 23 block.

Or Simple Sabotage[1]?

[1]: https://www.gutenberg.org/ebooks/26184

A good insider threat program already would pick up on that.

If I started implementing the organizational sabotage section at Google people would think I'm going for promo.

Maybe this doesn't beep at you if you take your hands off the wheel?

And people think that is a good thing?

It beeps at you if you stop paying attention, which is superior. Hands on wheel is an arbitrary design decision more likely to placate what a layman would think is necessary to ensure safe AI steering.

It’s an option in open pilot, but not one that defaults to on

My car judges it if I have put in any manual inputs over the past 10 or so seconds then it starts complaining. Which is seemingly reasonable however there's plenty of nearly perfect straight aways where there's nothing to do for it or me.

It would be nice if it had a system where if it isn't doing anything, it doesn't think I'm not doing anything either.

Except those straight, boring roads that require no input are also exactly where and when I most want to use autopilot. This means I have to manually adjust to keep the car happy, instead of letting the well-aligned car just carry on. Autopilot ends up being more work, and more annoying, than just driving myself

Okay, but "fad-use-of-GPU bros" doesn't roll off the tongue as well.