Except that the conclusion is wrong because you need tolerance. A bridge is designed to tolerate a certain weight, then you factor in some large tolerance for special circumstances, the same is true of effort.
You put more effort into your team presentation just in case there are guests. You cannot suddenly have a better presentation instantaneously when you arrive and see the CTO. In sports, such as bouldering, you will grip a hold slightly harder than strictly required in case you suddenly slip or just to easily accommodate the dynamics necessary as you shift your weight without requiring ultra precision which is a different form of effort.
The additional effort you expend is based on your estimation of the risk. As you master whatever skill it is, then you are better able to estimate the risks and the need or lack thereof for additional effort. Novices expend more effort than masters because they cannot gauge the need, but they will also make more mistakes by correctly guessing the correct effort but not accommodating for the risk.
The appropriate (over)effort is never 0 because there is always some context dependent risk.
This is an incomplete list of protocols that aren't part of core Wayland. Compositors implement additional protocols that aren't even part of this process (e.g. wlr-screencopy-unstable). See the wlroota protocols here: https://gitlab.freedesktop.org/wlroots/wlroots/-/tree/master...
Right but there's the xdg-portal for screen capture which runs through Pipewire and supports sand-boxing (because its negotiated over dbus), which all the main compositors support.
Just because a protocol isn't part of Wayland, doesn't mean a standard protocol does not exists.
They run these clients themselves and the redis instance isn't publically exposed.
It would indeed be very strange to hope your random users coordinate with your client side load balancer. You wouldn't even have to send real traffic. You could just manipulate redis directly to force all the real traffic to go to a single node. DoSing redis itself is also pretty easy.
I don't think the article implied that the client was for some sort of internal server-to-server communication, or that the Redis instance was directly exposed to the internet.
So no, I don't think they run these clients themselves. If the code runs out there, it's open to inspection.
Either way, you are right to point out that it important to only a try a pattern like this if your clients are highly trusted (or/and have additional compensating controls against DDOS threats). It would be beneficial if the OP made more explicit what their client/server relationships and also flagged the risk you mentioned for general audiences not to go implementing such a solution in the wrong places.
BTW the page mentions Alternate Styles, which is an obscure feature in firefox (View -> Page Styles). If you try it out, you will probably run into [0] and not be able to reset the style. The workaround is to open the page in a different tab, which will go back to the default style.
Having driven in the US and UK, this is a significant difference between the two. In the UK, you might sometimes drive 30 under on a road that is nominally 60 mph. In the US, that road would have a specific posted speed limit that is safe to drive. US roads are also more consistently designed for constant speed or have additional advisory speed limits for curves. You can nearly always drive as fast as the number on the sign unless there is some additional hazard.
I'm not the author, but I think you could by using UNION ALL instead of temp tables. You could also make a view that just calls this function. I'm not sure why it would matter though.
I think the sports analogy would be passing the ball back and forth in front of the goal instead of shooting. Nearly every time, an athlete with the ball in front of an open goal will take the shot themselves instead of passing. Even in a 2v1 situation, passing is a huge risk and taking the shot has a high likelihood of scoring, so you only want to pass if the defender is leaving your teammate open (usually they split the difference, so it's complicated). Too many passes in a 2v1 guarantees that more defenders will show up and you lose your advantage.
The paper is based on an estimate of productivity increases per industry due to AI. The highest increases are around 0.2% and most industries are <0.1%. In that world, AI isn't transformative and doesn't accelerate.
In some ways I think this is probably realistic, but it's not compatible with outcomes touted by boosters. They estimate 28 PJ/year, which is only about 0.9 GW. Stargate was planned to build 10 GW of capacity alone, so they can't both be true
"lawful" seems like an enormous loophole that makes this seem vacuous. If the government makes what you are doing unlawful, then it can be restricted. How would the government restrict you from doing something lawful in the first place? A bill of attainder? That's already illegal.
It gives a legal foothold to those who would challenge later laws, akin to the bill of rights. Believe it or not, courts will honor that kind of thing, and many legislators act in good faith (at least at the state level).
The difference is that while they can restrict the what, they can't restrict the how. Yeah they could make training LLMs illegal, but they can't for example put a quota on how much training you can do. Passing a law to ban something completely is a lot harder than passing a law that puts a "minor restriction" in place.
Ultimately any law can be repealed, so the loophole of changing the law in the future always exists. The point is that any future change to the law will take time and effort, so people can be confident in the near term that they won't be subject to the whims of a regulator or judge making decisions in a legal grayzone which may come down to which side of the bed they woke up on.
Yes, rights are real in the way ideas are real, for what that’s worth. They’re not guarantees, as many tend to view them.
They only become tangibly real when those in power allow it. More of a temporary gift, quickly taken away when those in power are supplanted by a tyrant.
The interesting angle to me is that the same ideas seem to be sort of “inevitably re-emergent”. They return, even after generations of tyranny, where no one alive in society has been handed these ideas we call rights.
So it’s more of a temporary gift that we should appreciate while we have it, which is forever at risk of being taken away, but which will always re-emerge as long as there are conscious beings capable of suffering.
That's as strong a rule as you can put in a normal law. If you want it to restrict what laws the government can pass, you need to put it in the constitution.
reply