![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
That’s fine as long as it can self reference.
That’s fine as long as it can self reference.
You need a phone, tablet, or other device that’s been rooted.
Damit
And to calculate the offset needed to get them all synced up involves calculating time dilation, which involves knowing/assuming the speed of light. These synchronizations work just as well if the two way speed of light is different than the one way speed of light.
To know the speed of light you assume the speed of light is c, but you’re trying to calculate c so all those clocks aren’t verified synced.
Just read through the wiki or Harvard’s books if you’d like, this is an unsolved “problem” in physics for a reason or do you think no one cares about how fast c is?
See also This or, more accessibly “Synchronization conventions”
It is impossible to synchronize the clocks in such a way that you can actually measure the speed of light with it due to time dilation unless you define beforehand how fast the speed of light is to calculate that time dilation.
See also This or, more accessibly “Synchronization conventions”
The very accurate clock needed in this case is physically impossible as far as we know, there’s no way to measure it as far as our current understanding of physics goes.
Though if you can figure out a way you should publish a paper about it.
And further down:
Unfortunately, if the one-way speed of light is anisotropic, the correct time dilation factor becomes
, with the anisotropy parameter κ between -1 and +1.[17] This introduces a new linear term,
(here
), meaning time dilation can no longer be ignored at small velocities, and slow clock-transport will fail to detect this anisotropy. Thus it is equivalent to Einstein synchronization.
This is slighlty different though, we only know the two-way speed of light, not the one way speed of light.
We only know that this trip, to and back, takes x seconds. We cannot prove that the trip to the mirror takes the same length of time as the way back.
The special theory of relativity for example does not depend on the one way speed of light to be the same as the two way speed of light.
Surely it can wait, right? How likely could it possibly be that it breaks when you least expect it?
It doesn’t though? IANAL but as far as I can tell you can fork, modify and redistribute it as long as you provide the source code to your users.
It’s AGPL-3.0 so… https://www.tldrlegal.com/license/gnu-affero-general-public-license-v3-agpl-3-0
For now
That’s not Firefox forcing you to update, you had Firefox open while you (/your package manager) was updating Firefox and after the update was done Firefox needs to be reopened. To prevent this you just have to …not update Firefox while it is running.
But those only have a short life, they don’t get many updates iirc.
your staff play document format police.
Often the email filter will just convert everything not allowed to PDF.
Yes it seems to have infinite energy but the throughput is limited to 2g of acceleration, unless you give it infinite time as well it will not reach c, though it would approach it.
Doing some calculation the final speed of 33kg, falling in 2g, for 70 years, without friction is “only” 99.77% the speed of light.
Edit: Forgot to convert the 0.9977c to percent.
Well, yes. We don’t know if the measurement we take is the result of a wave form collapse (we caused it) or the result of someone else having measured it, which would giving us the oposite value that they measured. We can’t tell if someone “sent” information or if it was the random result and we have no way to chose what value we (or the other end) gets when we collapse it.
This isn’t easy to explain over text so I’d recommend watching this video, specifically chapter “How to exploit?” as the visuals make it easier to understand.
Basically as far as we can tell there there is no information traveling at FTL speed so it just works? All information that is traveling is just as fast as c or slower.
“Certain phenomena in quantum mechanics, such as quantum entanglement, might give the superficial impression of allowing communication of information faster than light. According to the no-communication theorem these phenomena do not allow true communication; they only let two observers in different locations see the same system simultaneously, without any way of controlling what either sees.” link
“In physics, the no-communication theorem or no-signaling principle is a no-go theorem from quantum information theory which states that, during measurement of an entangled quantum state, it is not possible for one observer, by making a measurement of a subsystem of the total state, to communicate information to another observer.” link
According to special relativity, the energy of an object with rest mass m and speed v is given by γmc2, where γ is the Lorentz factor defined above^1. […] The γ factor approaches infinity as v approaches c, and it would take an infinite amount of energy to accelerate an object with mass to the speed of light. The speed of light is the upper limit for the speeds of objects with positive rest mass[…] This is experimentally established in many tests of relativistic energy and momentum.
More generally, it is impossible for signals or energy to travel faster than c. One argument for this follows from the counter-intuitive implication of special relativity known as the relativity of simultaneity. If the spatial distance between two events A and B is greater than the time interval between them multiplied by c then there are frames of reference in which A precedes B, others in which B precedes A, and others in which they are simultaneous. As a result, if something were travelling faster than c relative to an inertial frame of reference, it would be travelling backwards in time relative to another frame, and causality would be violated. In such a frame of reference, an “effect” could be observed before its “cause”. Such a violation of causality has never been recorded, and would lead to paradoxes such as the tachyonic antitelephone.
1 γ = (1 − v2/c2)−1/2
Last time I enabled secure boot it was with a unified kernel image, there was nothing on the EFI partition that was unsigned.
Idk about the default shim setup but using dracut with uki, rolled keys and luks it’d be secure.
After this you’re protected from offline attacks only though, unless you sign the UKI on a different device any program with root could still sign the modified images itself but no one could do an Evil Maid Attack or similar.
Would this even cause a kernel panic? I think this just causes a userland “panic”