Readit NewsI would be interested if the Lamor clock also shows a shift in the reflected particles. Because that would mean, also the reflected particles spend some time inside the barrier.
Of course, but it is less than one. Hence the measurement underestimates the proper time interval.
The Larmor clock doesn’t measure a proper time as in spacetime distance between two events. Instead it measures the rotation of a dipole in an electromagnetic field.
The experimenters apply a combination of an electrostatic field (the barrier) and a magnetic field (the timer driving Larmor precession). In the frame of reference of the spinning particle, this is exhibited as a sum of two electrostatic fields. The barrier is a locally uniform repulsive electrostatic field, while the the timer is a radially varying axial electrostatic field. The particle is a dipole, tilted from the timer axis by the precession angle. When the particle tunnels through the barrier, it also tunnels through the timer field, without precessing over the tunneled distance just as the particle is not exhibiting repulsion from the barrier over the same distance.
This is experimentally verifiable as the amount of missed precession has a lower bound proportional to the sine of the angle between the magnetic field and the barrier.
Then you've got to set up your domain, and domain headers on your domain host. Oh, DMARC is also another thing.
Then, most ISPs will outright refuse to accept incoming mail from your IP address, since they've basically changed from blacklisting to whitelisting. So you've also got to relay your outgoing mail via your domain host.
And then spam rules. I took the recommended rules from the Debian/Postfix/something-something-sorbs.net website, and I rarely receive email from e.g. eBay, because they've been marked as sending spam. Often happens with gmail addresses, too.
Despite all this... I still run my own mail server, but hotdamn, you're calling this not hard?
EDIT: Oh, and nowdays you've also got to entangle your TLS certificates into the whole process somehow. I managed it, but don't ask me how, I'd need to read up on that.
* CVE-2019-11500 : Critical Dovecot and Pigeonhole vulnerability (https://www.openwall.com/lists/oss-security/2019/08/28/3)
I still run my own mail server, but I hate having to keep up with these security vulnerabilities which can come up at the most inconvenient time.
Thus, I agree with you, there's value in making digits beyond 9 pronouncable for higher bases (if dealing with them enough to make devising the system worthwhile of course).
The part I disagree with relates to "relying on the optimizer for placement". Even in C++ using the above factory pattern, you are returning the constructed object from a function - and there is no problem if it is ultimately part of some larger object. The C++ standard specifies copy-elision very precisely so you don't have to hope the optimizer does it - it is required to. To demonstrate you can do stuff like this even if you object contains non-moveable members, like std::mutex
class Foo
{
private:
std::mutex mutex_;
SomeComplexSubObject sub_;
Foo(SomeComplexSubObject sub) noexcept
: sub_{std::move(sub)}
{ }
public:
static std::optional<Foo> make(SomeParams params) noexcept
{
try {
return Foo{SomeComplexSubObject{params}};
}
catch (std::exception const& e) {
return std::nullopt;
}
}
};
On a small scale, planar waves can be modeled like flat sheets of paper traveling through space without any angular momentum (no twisting motion). Yet when these sheets hit an object from multiple angles with the right timing, they can actually cause the object to twist.
They certainly have angular momentum, it just depends on the choice of origin. If you pick an origin along the peak ray of the plane wave, there will be no twist around that point. Just like with a particle traveling in free space.