cpuguy83

I'm pretty sure he said Rex will remain free.

7.0 added task level filtering using regular bpf filters.

https://lwn.net/Articles/1054225

Initial Position Offload

It's also the FTC's responsibility to challenge mergers that would substantially reduce competition.

No one is saying the merger is illegal, just that it probably shouldn't be allowed.

I'm curious what you mean about vendoring.

In go, vendoring dependencies just copies the deps out of the module system into the local tree and it's managed the same as not vendoring. It won't even build of the go.mod has changed without also updating the vendor tree.

The reality is Apple has been working on rewriting bits and pieces in Swift.

https://bsky.app/profile/anthonymoser.com/post/3myf5fwpl7s2t is a good explainer I think without getting into the nitty gritty details.

  for the non technical folks:  imagine there was a password that if you guess   it, you can impersonate *any website on the internet*
  
  now imagine the password is literally the number 4

Well that's just pure insanity. I have to know this now. I didn't need this :D

A cli asking for a password is a pretty normal thing, I think?

With curl|bash you are literally getting anything that happens to be in that script. These are frequently poorly constructed, so not check hashes or pin dependencies they install. Even security companies (see trivy supply chain attack) get these badly wrong.

I'm not replying here to say one is better than than the other (npm has obviously had its share of problems) but rather to combat claims that curl|bash is somehow safer, it absolutely is not, in fact it's all the bad stuff about npm without the pretense of being potentially safe.

Training AI on the stories we created about AI taking over causing AI to have that idea. Ouroboros.

It doesn't do messages or notifications. "Just" things like file copy and clipboard.

kdeconnect has an iOS client.

"Easy" is subjective, but tether seems like it would do this? There is also kdeconnect (don't let the "KDE" fool you).

Also created memcached, livejournal... Brad has a long list of impressive work.

Interesting. I thought about doing this immediately after reading their old blog[1] post on punching through NAT some time ago.

Just a combo of never getting around to it and friends talking me out of it b/c of existing alternatives such as wormhole[2].

[1] https://tailscale.com/blog/how-nat-traversal-works

[2] https://github.com/magic-wormhole/magic-wormhole

Larger model -> more memory

It depends on what model(s) you want to run.

Sure, but I don't expect build to execute arbitrary code. That's a big difference.

It's like if `git clone` ran random stuff from the cloned repo.

The problem isn't the language here, it's cargo executing build.rs from dependencies which necessarily allows arbitrary code execution.

The US is not much different. We don't have a wealth of specialists available to see people right away.

I've flat out been rejected from a specialist because they had no availability at all. I actually tried again and got to be seen, but an appointment is months out, always.

I'm fairly certain that docker sandbox is based on https://github.com/containerd/nerdbox which you can run on Linux.

USB-C is literally just the name of the connector. USB-A can also have varying speeds across it... and B. These are all connectors, not speed ratings.

There is usb 1, 2, 3, and 4 that are more of a statement on the performance capability.

I'm pretty sure the issue is not "higher order abstractions". It is using multiple single letter references with no real grounding or relationship that the reader has to track.

For example, looping over a map with "k" and "v" vars is not that bad because the reader understands k=key and v=value, and that makes since for a map. If you do this same thing with different single letter vars, e.g. "a" and "b", it instantly becomes more difficult to read.

When writing a generic function and using these single character type references it can make sense, especially because the function/method doesn't care what those references are, however to someone trying to understand what's going on it can be extremely difficult simply because of the names.

Sure, if all you are going to do is call that method or function those type references go away and the call site may be relatively clean, but you still have to read the thing to understand what it is and how to use it.

Enjoyed the read, thanks!

Beyond the content, the font, style, etc made it a pleasant experience for me.

Bug is uncovered. Where was it first introduced? Why was the code changed? What did it do before the bug was introduced?

This is focused on builds, so running either buildkitd or dockerd in an Apple containerization container. No port forwarding or host volume stuff (really its focused on running buildkit on mac) BUT complete integration with docker CLI and buildx.

https://github.com/cpuguy83/crucible

Thanks for this. Just started another rewatch and were of course in awe of the house.

Plenty of people offended by closing a PR or issue unresolved.

In an ideal universe yes. But we live in a world where vulnerability scanners reign supreme.

It's not (just) more of them, it's the same ones reported by multiple people.

I think the point is those issues are now easily discoverable and are nearly public because of it.