Leaderboard
Popular Content
Showing content with the highest reputation on 09/24/2022 in all areas
-
3 points
-
La Voie lactée / The Milky Way Au Lac-de-la-Chaîne. Lac-Bouchette, Saguenay–Lac-Saint-Jean, Quebec, Canada. By Curculion: https://www.flickr.com/photos/curculion/ On Flickr: https://www.flickr.com/photos/curculion/27572901630/2 points
-
https://www.almanac.com/content/first-day-fall-autumnal-equinox Its starting to look this way and I LOVE it so much2 points
-
Thanks, sending a virtual hug your way! It's not something I hear in real life. But then, I'm distrustful of other people in general and keep to myself. Anxiety doesn't help. I see you're back as well, @msfntor . I had an odd feeling you contracted something heavier and fatal back then. This is a particularly messed up year. I'd rather not talk about in detail about that specific event that happened recently and the can of worms it opened. Other than that, I gave away the old car. Actually left it at the dealer where I bought a new one. That one week during summer, the engine in the old car randomly shut down on a motorway. Didn't realize it at first, thought it'll snap back eventually, I retreated to the emergency lane and only several seconds later thought to hit the clutch so could see the tachometer turning to zero and the battery indicator lighting up. It did restart right away, but since I've come to a complete stop in the meantime, I had to wait a while before I could go because so many damn cars passing by. Not pleasant. Then it happened again two days later, the experience from the first time helped that I managed to restart the engine while the car was still on the move. Maybe they would've put it back in working order if I took it to the official service. It served well for 21,5 years, I was its 3rd owner for 5 years and after recent experiences and generally issues popping up in shorter periods in recent times, I thought it might be the time to update myself in that department.1 point
-
Well it's not impossible of course that this is being caused by a POSReady update, but there's no indication of any problems elsewhere. I'm sure I'm not the only one running this version of 360Chrome on a POSReady updated machine, and I'd be interested to hear from anyone else who is, especially in the UK, so see if they're seeing the same issue with the history. It's not a dealbreaker, the main annoyance is not being able to see the history from previously in the current day, but it is puzzling. It will be interesting to see if there is any change in behaviour when the UK goes back onto GMT on October 30th. If there is, that will prove that it's timezone related I think.1 point
-
1 point
-
67° Sunny Day 68° • Night 51° I am outside my porch today and its quiet1 point
-
.............. We're missing love in this world. Kindness is easier than hate. I still have some hope things could change.1 point
-
1 point
-
I love to take virtual trips and ride on roller coasters from around the world. When I was young (18 perhaps) I used to ride on them with my DD Father and fond memories of that. We used to enjoy the ones that we upside-down. Ha!1 point
-
Welcome back ... been a while since I've updated or keeping up and much for the same reason.1 point
-
1 point
-
1 point
-
Gravity: The Story So Far What happens when we try to explain gravity? by George Ellis | Templeton prize-winning cosmologist and co-author of 'The Large Scale Structure of Space-Time' with Stephen Hawking. The basic issue Gravity holds us to the Earth and makes apples drop to the ground when they fall off a tree. It controls how the Moon moves round the Earth and how the Moon causes tides on Earth. It controls how the Earth moves round the Sun and how the Sun moves round the Galaxy. But it’s not a force. That was Einstein’s great discovery. How can we say that? Well because you can, at least for a while, simply make it vanish! How do you do that? Just let go! In other words, jump off a building, and you’ll feel no gravity as you fall down (hitting the Earth does not count as falling down). More gently, join a freely orbiting space station crew, and you’ll find life difficult because there will be no felt gravity to hold you down on your seat or to hold your coffee in a cup. In short, what appears to be a gravitational force actually depends, locally at least, on how you are moving. You can make it go away by allowing yourself to fall freely. The reason why The reason this is true is because the gravitational mass of a body is the same as its inertial mass. This is what Galileo discovered, allegedly, by dropping objects of different weight from the Leaning Tower of Pisa (that experiment has since been done much more accurately by modern physicists - see this video for a feather and a ball falling at the same speed). That means that if you are in lift and the rope breaks, you and everything around you will fall at the same rate as the lift – so you will no longer feel gravity holding you to the floor of the lift. This was Einstein’s “happiest discovery”. What is it then? Gravity is now understood as being an effect of space-time curvature; in a static situation, of spatial curvature. A model is as follows: if you consider two aircraft that start off 1000 miles apart at the same instant from the Earth’s equator and they each fly at the same speed in an unchanging Northerly direction, they will get closer and closer together and will eventually collide at the North Pole. It is as if a force was pulling them together even though there was no attractive force acting between them. It was the curvature of the Earth that was the cause of this apparent force. Spacetime curvature is like that: if, for example, you let a spacecraft fall freely around the Earth at the right speed, with the engine turned off, it will arrive back exactly where it started because of the curvature of space caused by the Earth’s gravitational field. It never fired an engine to change direction but just kept going. ... ___ ... Is General Relativity the right classical theory? We don’t know. It has passed every test we have tried – there is no evidence against it. But to check if a theory is right, you need to compare it with other candidate theories and see which performs better. General Relativity has passed all these tests with flying colours. But some scientists, for example, are claiming you don’t need to have the huge amounts of dark matter in the universe that are suggested by standard studies – because they assume that General Relativity is correct. Maybe a modified gravitational theory, for example one in which the gravitational constant changes with space or time, might remove the need for dark matter. So many alternatives are being proposed and tested. It is difficult to test on Earth because it is a long range force, It is dominant in the Universe on large scales because all gravitational mass is positive, unlike electricity, where there are equal numbers of positive and negatively charged particles. We understand Einstein’s theory pretty well, despite its complexity. But that is not the end of the story. If you want to take part in the search for the ultimate answer, you will have to learn the maths (tensor calculus, maybe spinors) and the physics (variational principles and symmetry groups, for example) and then get going. No one knows what direction may lead to new and unexpected answers. Editor's note - in light of the recent awarding of the Nobel Prize in physics for the detection of gravitational waves, the author has added the below: "Gravitational waves are very difficult to detect because their sources are so far away and, despite appearances, the gravitational force is so weak. The first related Nobel Prize was awarded in 1973 jointly to Russell A. Hulse and Joseph H. Taylor, Jr, for the discovery of the effect of gravitational radiation emission on the orbits of binary pulsars (emission of gravitational waves causes energy loss that changes the orbits of the pulsars). This indirectly proved the existence of gravitational waves as foretold by the theory. Then this year, half the physics award went to Rainer Weiss and the other half jointly to Barry C. Barish and Kip S. Thorne for the extraordinary feat of constructing detectors that could measure gravitational waves directly - an incredible theoretical and observational tour de force. So Einstein proposed they could exist in 1917. We now have two independent ways of proving not only that they can exist , but that the carry energy with them (some of that energy being deposited in the LIGO/VIRGO gravitational wave detectors) as predicted." Here: https://iai.tv/articles/gravity-the-story-so-far-auid-896 Gravity and the Dark Side of Science Anti-gravity does not exist. Or does it? - by Valia Allori | Associate Professor of Philosophy at Northern Illinois University If anti-gravity existed, the book that explains it would be impossible to put down. Unfortunately, anti-gravity does not exist. Or does it? It is not a settled question, and there is a sense in which it will never be. Nonetheless, that does not matter much. How can that be? Keep reading! There are two ingredients at play in this: theory and evidence. And their connection is more complicated than one may initially think. Let me start with theory. Gravity is responsible for stuff falling on the ground, as well as for planets moving in the sky. Scientific theories have been proposed to account for these phenomena: Newton’s theory of gravity first and Einstein’s general relativity later. Newton’s gravity is a force that acts instantaneously to pull bodies closer in virtue of their mass. In other words two massive bodies, no matter how distant, feel each other’s presence instantly and tend to get together. Here now comes evidence. Newton’s theory has been very successful. The theory predicted, for instance, the Halley comet to be seen again in 1758. One may even think that our best scientific theories are definitely proven by experiments - Newton’s theory successfully predicted the return of the Halley comet, therefore Newton’s theory is true. Right? Well, no. It does not logically follow that Newton’s theory is true even if all experiments come out as predicted. It like someone concluding that it is snowing right now by starting with the consideration that if it's snowing then the streets will be covered with snow, and then observing that the streets are now covered with snow. This is unwarranted: it takes snow a very long time to melt, so snow could have fallen earlier in the day. Similarly, the Halley comet return is a good indication of the past success of Newton’s theory, but does not provide any guarantee of its future success. Indeed, it later turned out that Newton’s theory was false and it was substituted by Einstein’s theory of relativity. Einstein argued that gravity is not a force but rather the effect of the modification of the fabric of space-time due to the presence of material bodies. That is, in empty space a body will go straight, but the presence of another body will bend its trajectory as if it were affected by a pulling force. Even if it is an imprecise analogy, a ball thrown on a bed where a cat is sleeping will not go straight but will rather curve towards the cat. Anyway, we cannot prove beyond any doubt a theory to be true, no matter how successful it is. It is better to say that the theory is confirmed, or more cautiously corroborated, by positive experiments: arguably, we have more reasons to believe a theory with lots of confirmatory instances than one with fewer. Can we at least prove a theory to be false? Newton’s theory would be proven false if the predicted acceleration of falling bodies were different from the measured one, say. Indeed, Newton’s theory was falsified by experiments: the theory predicted Mercury’s orbit around the Sun would not shift forward, which instead does. Such shift was predicted by Einstein’s theory of general relativity. So, can falsification be definite? Again, no: sometimes old theories do not get replaced even if they have contrary evidence. In this case, experimental refutation of Newton’s theory was not the reason why relativity took the place of Newton’s theory in the physics books. Even if the predictions were wrong, scientists were not ready to consider Newton’s theory to be false and kept using it. After all, is it worth throwing away all the successes of such a powerful, explanatory theory just for such a small discrepancy? It could well be some experimental error. Nonetheless, eventually Newton’s theory was replaced because of theoretical, rather than empirical, reasons. Einstein proposed his theory of relativity because he found the ‘spooky action-at-a-distance’ of Newton’s theory of gravity extremely unsatisfactory. Therefore, he looked for another explanation and he found it. The bonus was that his theory could also correctly recover the shift in Mercury’s orbit that Newton’s theory could not account for. __ "Even if the predictions were wrong, scientists were not ready to consider Newton's theory to be false and kept using it. After all, is it worth throwing away all the successes of such a powerful, explanatory theory just for such a small discrepancy?" ___ Also, consider this other example. Gravity keeps the universe together and one of the leading early theories of the origin of the universe is the big bang theory: the universe started expanding after a huge explosion at the beginning of time. One should expect sooner or later the universe to slow down, just like the fragments of a more ‘regular’ explosion. However, recent astronomical data suggest that the fragments are getting away at increasing speed. This is a falsification of the big bang theory, which predicted deceleration. Nonetheless, sometimes, like in the case of Newton’s failure to predict Mercury’s orbital shift, rejecting falsified theories seems just too harsh. If I drop an egg on the floor and it does not break as expected, I will not claim I have refuted the current theory of gravity. Rather, I will check for false assumptions that would explain the mistaken result. Another example is that Newton’s theory predicted a different orbit for Uranus than the one observed. So the theory was, again, falsified. However, instead of rejecting Newton’s theory, astronomers questioned the assumption that there were seven planets: the existence of another planet, Neptune, would explain the observed orbit of Uranus, which they indeed later observed. Back to the case of the accelerating universe, many astronomers decided to do the same thing: they did not refute the theory, even with contrary evidence. In a sense, they proposed that gravity has its own dark side: something, now known as dark energy, which overpowers gravity’s attraction. More precisely, they questioned the assumption that space-time has no energy in itself. One may think of this as a repulsive gravity or anti-gravity, but do not read too much into it. Notice that hidden, unquestioned, assumptions are everywhere. For instance, when using a microscope, we assume light propagates in a straight line, even if it does not. There are some situations in which this is irrelevant, but some others in which it may not. Hence, when facing empirical refutation, scientists always have the option to put the theory into question or to challenge some hidden assumption instead. In this case, astronomers could either deny the existence of dark energy and radically modify general relativity, or assume dark energy exists without modifying general relativity too much. If the former is the case, there is a sense in which there is anti-gravity; if the latter, there is not. The philosophical question therefore is: when is it reasonable for a scientist to hold on to her theory, and when is she just stubbornly in love with it? Even if this is not the case here, I am sure you understand the gravity of the situation (pun intended!) if alternative theories are empirically equivalent. That is, in the case in which no experiment can be performed to tell them apart. This happens, for instance, between some different formulations of non-relativistic quantum mechanics. If we cannot choose which theory is correct based on the empirical results, what can help us? It is unclear: some will say super-empirical, or purely theoretical virtues, should be important. Simpler theories, for instance, should be preferred. However, what is simplicity? Why should we believe that the universe is simple? The bottom line is therefore this: one is never able to prove or rule out a scientific theory beyond any doubt with experiments alone. That means that there will certainly be alternatives and it is unclear how theoretical virtues may help in theory selection. Having said that, I believe that scientific theories are powerful tools that can tell us about the nature of reality. Even if we cannot definitively prove they are true or false, they are either one or the other. There is something about the scientific method that allows science, as opposed to the unscientific alternatives like crystal ball gazing or tarot reading, to track truth, even if we do not know exactly what it is. Not knowing it yet does not imply we will never find out more. And not knowing what it is it does not mean that it does not work: my mum’s ignorance about the way in which a nuclear power plant works does not make the plant stop working. So does anti-gravity exist? Either it does or it does not. We do not know yet and we will never be able to know for sure. However, science can still give fallible knowledge of the world: we sometime get things wrong but we are getting somewhere. Therefore, if you want to investigate the mysteries of gravity, as well as any other, keep studying, become a scientist and keep your philosophical eye open: the path is going to be uphill, but there is no fun without a challenge. Here: https://iai.tv/articles/gravity-and-the-dark-side-of-science-auid-9011 point
-
Animal Welfare (Sentience) in the UK legal code Animals to be formally recognised as sentient beings in domestic law Introduction of the Animal Welfare (Sentience) Bill as part of the Government's Action Plan for Animal Welfare From: Department for Environment, Food & Rural Affairs and The Rt Hon Lord Goldsmith Published 13 May 2021 Government introduces Bill to formally recognise animals as sentient beings Animal Sentience Committee will put animal sentience at heart of government policy Bill introduced as part of government’s first of a kind Action Plan for Animal Welfare Vertebrate animals will be recognised as sentient beings for the first time in UK law thanks to the introduction of the Animal Welfare (Sentience) Bill, introduced in Parliament today. The legislation will also ensure that animal sentience is taken into account when developing policy across Government through the creation of a Animal Sentience Committee which will be made up of animal experts from within the field. By enshrining sentience in domestic law in this way, any new legislation will have to take into account the fact that animals can experience feelings such as pain or joy. The Bill will underpin the Government’s Action Plan for Animal Welfare, which launched yesterday and sets out the government’s plans to improve standards and eradicate cruel practices for animals both domestically and internationally. The Bill’s introduction, fulfilling a key Manifesto commitment, will further the UK’s position as a world-leader on animal welfare. Now that we have left the EU we have the opportunity to remake laws and go further to promote animal welfare by making sure that all Government departments properly consider animal sentience when designing policy, covering all vertebrate animals from farm to forest. The Animal Welfare (Sentience) Bill will: formally recognise animals as sentient beings in domestic law establish an Animal Sentience Committee made up of experts to ensure cross departmental government policy considers animal sentience ensure Government Ministers update parliament on recommendations made by the Animal Sentience Committee ... Here: https://www.gov.uk/government/news/animals-to-be-formally-recognised-as-sentient-beings-in-domestic-law1 point
-
Medicine's bad philosophy threatens your health Medicine has a mind-body problem by Diane O'Leary In recent years medicine has increasingly recognized a connection between mind and body and how the interaction between the two can affect our health. But in its effort to avoid a problematic separation between mind and body, medicine has been led astray. Due to misunderstanding what in philosophy is called mind-body dualism, trained medical doctors end up over-diagnosing conditions as psychosomatic, automatically construing medically unexplained symptoms as psychiatric problems. This is a philosophical error that ends up putting the health of patients at risk, argues Diane O’Leary. Medicine and philosophy have an uneasy relationship. Medicine is a practical endeavor, aiming for concrete results. Philosophy, on the other hand, has been construed as a head-in-the-clouds kind of thing since antiquity. Today, outside of medical ethics (which has taken a rightful place within the profession), it’s hard to see how philosophy’s abstractions could make a real difference to the nuts and bolts of diagnosis and treatment. If medicine were just an applied science of the body, all of this would make good sense. But in the late twentieth century, western medicine reconsidered its exclusive focus on the body and emphatically rejected it. Patients, it turns out, are not just bodies, we’re people. And persons have minds, as well as bodies. This shift raised one modern philosophy’s most intractable issues: the mind-body problem: How do our subjective, mental experiences relate to our objective, physical bodies?... More here: https://iai.tv/articles/medicines-bad-philosophy-threatens-your-health-auid-22251 point
-
25/07/2022 The Chinese superhero: caught a two-year-old baby girl who fell from the fifth floor A Chinese man was declared a "national hero" after he miraculously caught a two-year-old girl who fell from a fifth-floor window. Shen Dong, 31, was parking his car in front of an apartment building in Tongxiang, Zhejiang Province, when he heard a loud noise. It was a baby girl who fell from the window from the fifth floor and landed on a metal roof. The two-year-old slipped off the roof and was about to hit the sidewalk, when she was saved at the last moment by a tooth that caught her. The girl was rushed to the hospital with injuries to her legs and lungs, and her condition is stable, the "South China Morning Post" reported. A video of the incident was shared by the local police on Weibo - China's equivalent of Twitter - and went viral. On social networks, Shen was nicknamed "superhero". Shen, who works at the bank opposite, saw what was happening and was in the middle of a phone call to the emergency services, but then he noticed that the girl was about to fall from the roof, threw his phone and managed to catch her before she hit the concrete. According to him, at first he did not know it was a baby. "The truth is, I don't remember all the details," he told the "Chiangyang Evening News." "I don't remember if my arms hurt. It was an instinct to grab her. I was lucky I was able to grab her in time. Otherwise I would have felt terrible." Here: https://newsrnd.com/news/2022-07-25-the-chinese-superhero--caught-a-two-year-old-baby-girl-who-fell-from-the-fifth-floor---voila!-news.S1WXyuln2c.html1 point
-
that's horrible, awful! But you wrote in this same time: - voilà, exactly...so keep in touch with the others, please! cool, hold it like this. I'm Ok., generally speaking.1 point
-
Enough about me, I'm getting better. How is everyone doing?1 point
-
New regular/weekly KM-Goanna release: https://o.rthost.win/kmeleon/KM76.4.6-Goanna-20220924.7z Changelog: Out-of-tree changes: * update Goanna3 to git d7ee65a30f..7f6fda62d8: - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1205941 - Make TimerFirings logging output post-processible with fix_linux_stack.py. r=glandium. (042e3968a2) - Bug 1203427 (part 6) - Add link to MDN docs about TimerFirings logging. r=me. (19967a22e7) - missing bit of Bug 1178890 (b421ab56a1) - Bug 1207497 - Part 1: Remove use of expression closure from toolkit/, exept tests. r=Gijs (4cf4abbf3d) - Bug 1207497 - Part 2: Remove use of expression closure from tests in toolkit/. r=Gijs (6c4517c20e) - Bug 1207497 - Part 3: Fix wrong replacement in debug print in toolkit/mozapps/downloads/tests/unit/test_lowMinutes.js. r=me DONTBUILD (5311950d45) - bug 1171649 - Implement arm/iOS support in JS JITs. r=jandem (0eb06f1d3d) - Bug 1205708: Check if validation failed before reporting helper thread failure in Odin; r=luke (0bd8b70919) - missing bit of Bug 1112627: Remove redundant inline specifier in SIMD (76cea80b8c) - Bug 1189059: Replace setObjectMetadataCallback with enableObjectMetadataCallback, fix callers. r=fitzgen (053ae86af2) - Bug 1125412 - Draw a graph of memory usage, r=terrence (4ac21380a4) - Bug 1147985 - Avoid blank space when heap size graph is unavailable, r=terrence (9b48d4d435) - Bug 1170372 - Skip js1_5/Regress/regress-312588.js on SM(cgc) builds due to timeouts. (5298485837) - Bug 1160149 - Skip basic/testManyVars.js on SM(cgc) builds for frequent timeouts. (562cfc2713) - Bug 1198549 - Switch from | to $ as the preferred separator token (due to operator|), r=me\ (cc6fdb0697) - Bug 963738 - Handle Arrays in the analysis, r=terrence (589b285306) - Bug 1209696 - Check the return value of fopen, r=terrence (8c2378f3f9) - Bug 1197941 - Allow getline() to malloc its own buffer to avoid intermittent crashes, r=shu (e37b934fcc) - Bug 1180985 - Implement a JS GDB pretty-printer for JS::GCCellPtr. r=sfink (8848723b3a) - Bug 1180984 - JS GDB pretty-printers: Support Python 3. r=sfink (ae4c76014d) - Bug 1198628 - IonMonkey: ARM: Redefine FloatRegisters::Code and use it in the right way. r=nbp (d0d608b1cc) - Bug 1198145 - guard calls to getInst(). r=me (bb8c4e2e4b) (24dc63cddd) - d3d9: further lowered MaxTexture limit to 1024 to give chance for Radeon 9550 and GMA 965 to use hardware acceleration (db3284c954) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1186982 - propagate OOM failures (no test case). r=h4writer (ddb0e5e6c6) - Bug 1205621 - arm64: Handle OOMs in a safer manner. r=lth (82d08e6935) - Bug 984018 - Fixed build on Arm64. r=nbp (7b7614f965) - Bug 1191531 - Fill in AtomicOperations-arm64.h. r=lth (38d0d330a7) - Bug 1202367 - reinitialize expected value inside CAS loop. r=sstangl (e219a3b6d2) - missing of 1084248 (ad8109cb8e) - Bug 1183842 - Use InvertCondition to expand the range of conditional branches. r=h4writer (fa790d9ae2) - Bug 1203287 - Fix build errors in ARM64 JIT. r=hv1989 (da2b2ea212) - Bug 1189117 - IonMonkey: treat ObjectState instructions as effect free for the purposes of AliasAnalysis. r=nbp (5b9b17a27f) - Bug 1209132 - Check for SSE3 in MacroAssemblerX86::convertUInt64ToDouble. r=sstangl (87879864ba) - Bug 1209132 - Part 2: Fix SSE assertion in Assembler::vhaddpd. r=jandem (a632975d60) - Bug 1205639 - MacroAssembler*::toggledCall: Prevent assertions in oom cases. r=jandem (b76696545a) - Bug 1209026 - Use infallible new for some Label allocations. r=jonco (a61994c680) - code style (dfef676fca) - fix patch order (dfcb632d8a) - code style (aecddaebbd) - Bug 1208259 - Disable ARM64 Ion, fail testPreserveJitCode. r=jandem (3c2fc9721c) - missing bits of Bug 1143679 - Make TryNoteIterIon behave more like Baseline/interpreter iterators. r=shu (dcf33819df) - adapted Bug 1199952 - Mark formal arguments when we have a LazyLink frame. r=nbp (96a741b93d) - Bug 1132265 - Handle dummy frames when initializing ProfilingFrameIterator. r=shu (f669bbd8cf) - Bug 1205937. r=jandem, with various input from efaust as well (bc9f3802c9) - pointer style (b9049bdc6b) - Bug 1199898 - Tolerate constants appearing before interrupt checks during instruction reordering, r=sunfish. (2bb41a7194) - Bug 1151267 - app update telemetry for UPDATE_CANNOT_APPLY_* is reversed. r=spohl (abd7f60f0e) - adapted of Bug 1204675: IonMonkey - Replace input with constant in a tableswitch, r=jandem (ac5139dd1a) - missing bit of 994016 (a3f5666f4b) - Bug 1177318 - Add Ion support for JSOP_TOSTRING, to make template strings faster. r=jandem. (9cad760048) - Bug 1204675: IonMonkey - Don't specialize using baseline stubs for strict equality, r=jandem (a5a6578e51) - Bug 1207572 - Make sure idempotent caches are invalidated when getting the non-int32 length of an array, r=jandem. (c7b5635add) - Bug 1201850 - Don't elide stack check when getelem/setelem caches are used. r=bhackett (e0749ae114) - Bug 1199217 - Implement JS::ubi::Node::size for js::jit::JitCode referents; r=sfink (81b65699a9) - Pointer style (b25713d3c9) - Bug 984018 - Added signatures in simulators (arm, arm64 and mips). r=nbp (3f45986cc5) - pointer style (740b82bff6) - Bug 1141032: Fix a string comparison when checking for env overriding JIT defaults; r=h4writer (e9e548e262) - pointer style and reshuffle (ad693dcf06) - Bug 1207413: Check callers of TypeSets::unionSets for OOM; r=h4writer (080b5fcb47) - Bug 1201469: IonMonkey: Don't specialize to float32 when binary arith instruction is a vm call, r=bbouvier (aff7dc5cd9) - No Bug - Followup fix for build failure on a CLOSED TREE; r=bustage, a=RyanVM (8808df4ba7) - pointer style (ae467507c5) - Bug 1054047 - Determine the correct range from MArgumentLength. r=sunfish (ec9387d5b7) - Bug 1205842: Don't add range asserts to recovered on bailouts instructions; r=nbp (7778cc2946) - pointer style (da3efc548f) - Bug 1140336: Remove init() method in VMFunction (and dubious assert); r=h4writer (7f25460883) - bug 1174701 - Don't use NEON assembly for ARM iOS in gfx/ycbcr. r=jrmuizel (7db573d30a) - add back some SPS stuff (d55e260359) - Bug 1164480 - Make sure MacIOSurfaceLib is initialized before we use it. r=jya (2f1ce4a035) - Bug 1158321. Normalize OS X vsync timestamp if CVDisplayLinkCallback executes early. r=mstange (9f51c2e6eb) - Bug 1171156. Add logging to OS X vsync timestamps. r=mstange (4c0e097a97) - Bug 1171156. More logging to test vsync timestamps. r=me (70f6679115) - Bug 1171156. Normalize vsync timestamps when given bad values on OS X. r=mstange (4fac136d2e) - Bug 1139824 - Track construction/destruction of the font table wrappers attached to hb_blob objects, to enable leak detection. r=jdaggett (9801625a4a) - adapt code to TFF (ca938d4d5f) - Bug 1195188 - add fontlist init problem telemetry for DirectWrite. r=m_kato (b54014a179) - Bug 1190590 - Fix MinGW cross-compile for --enable-bundled-fonts. r=jfkthame (134a7f0fa5) - Bug 1168527 - Add support to gfxContext for clip exporting. r=jrmuizel (3114271491) (5c4f111a47) - update NSS builtin certstore to Sep 2022 version from mozilla upstream. (d812eaca76) - partly import changes from tenfourfox: - 102ESR: rev EV roots, TLS roots, TLDs, tzdata, HSTS, pins (c47bef11f) (f5491c9bdb) - sync external protocol handlers pref with UXP (e0de03b045) - partly import changes from tenfourfox: - #651: M1497246 M1776658 M1773717 (bc6daa0ae) (22f768afa7) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1152509. Use Mask with alpha to avoid allocating a surface. r=bas (ddab7594e3) - Bug 1155881 follow-up: Make gfxAndroidPlatform::SupportsApzTouchInput const (a31194495e) - Bug 1193481 - Prefer "Firefox Emoji" font for emoji characters in GetCommonFallbackFonts on B2G. r=jdaggett (e94e0eb718) - Bug 1139253. Reuse the same thread for the software vsync thread. r=kats (fe7f6849bf) - Bug 1147390. Enable / disable vsync on the vsync thread only. r=kats (fd485f8ec4) - Bug 1146691 - Create tests to check that the RefreshDriverVsyncObservers get vsync notifications. r=kats (7a8527b378) - Bug 1197201. Delete hardware vsync and vsync compositor prefs. r=kats (e8f0ef3258) - Bug 1175530 - Log using gfxDebugOnce when enabling vsync compositor. r=mchang (81a48aebae) - Bug 1196308 - Delete Software Compositor Scheduler. r=sotaro (d0e9620ddb) - Don't run the compositor:created notification from within unsafer callers. (bug 1201684, r=mattwoodrow) (83d585749a) - Bug 1160216 - Add a preference to force software vsync and set software vsync rate. r=kats (850d3ce7ab) - Bug 1132966 - use relaxed Atomic integers for tracking graphics surface memory usage; r=njn (aca764781f) - bug 1180012 remove unused GetPrefFonts() r=jdaggett (80a5a99f7f) - Bug 1139726 - Assert gfxPlatform::Init is called on the main thread. r=kats (dd1ad58304) - Bug 1208945 - Rename Color::{To,From}ARGB() so they aren't easily confused with {To,From}ABGR(). r=Bas. (8e83d44741) - Bug 1199885 - Part 1: Add MouseInput InputData. r=kats (67764c13a6) (0484be0c56) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1199885 - Part 2: Add AsyncDragMetrics. r=kats (220a4f445e) - Bug 1149482 - Localize the 'none' string for APZ in about:support. r=dvander (3e0128f62e) - Bug 1199885 - Part 3: Add 'apz.drag.enabled' preference for async scrollbars. r=kats (5133061d3f) - Bug 1199885 - Part 4: Let the hit testing tree know about the scroll thumb. r=kats (26a9a69443) - Bug 1199885 - Part 5: Make mRootLayerTreeID const to prove that there's no data races. r=kats (88e2eb80f1) - Bug 1199885 - Part 8: Add FindScrollNode to locate the scrollbar thumb. r=kats (a545ec9569) - Bug 1199885 - Part 9: Let APZC handle the drag events. r=kats (4cc0f88153) - Bug 1199885 - Part 9.5: Make the mouse events APZC aware. r=kats (69bd4caf94) - Bug 1199885 - Part 10: Add APZTeeManager API to start an async scroll. r=kats (e212ee2750) - Bug 1199885 - Part 12: Add StartScrollbarDrag IPC message. r=kats (705af3b233) - Bug 1199885 - Part 13: Let nsSliderFrame trigger async scrolling via StartScrollbarDrag. r=kats (d31b5a790d) - put in gstreamer as of 2015-10-05 Bug 1146482 (7cca45858c) - pointer style (f8041af438) - Bug 1197097 - Don't use a context-wide cycle-detection mechanism for detecting cycles during JSON.stringify. This prevents nested (yet separate) JSON.stringify, and it causes that algorithm to be affected by specification-unrelated operations like toSource. r=jonco (09652471c1) - align to ugly grammaer of 1114782 (c760693693) - remove space (7158a0c2bf) - align to FF/TFF (27138a55bb) - Bug 1205887 - Verify that MOZILLA_VERSION was set correctly, r=glandium (2269e8f31b) - Bug 1205012 - Allow rust source code in SpiderMonkey; r=mshal (9ebca9ed28) - Bug 1197281 - Use MOZ_FIND_WINSDK_VERSION for MOZ_WINSDK_MAXVER on mingw. r=glandium (2910b2160e) - Bug 1207893 - Refactor how build backend execution is summarized. r=gps (56d8fecbc2) - Bug 1207893 - Allow to create multiple build backends at once. r=gps (d8cba87d2b) - Bug 1207897 - Add a configure option to build multiple build backends. r=gps (f9c7851d02) - Bug 1188555 - part 1 - remove write-only configure.in variable NO_LD_ARCHIVE_FLAGS; r=mshal (461958b100) - Bug 1188555 - part 2 - remove write-only configure.in variables MKSHLIB_{UN,}FORCE_ALL; r=mshal (1813210dda) - Bug 1207882 - Ensure chrome manifests are created in a directory that exists when processing jar manifests. r=gps (59165a64cb) - Bug 1204712 - Handle wildcards properly for localized content in jar manifests. r=gps (54dfb632c7) - Bug 1188551: treat assertion failures as bad mozconfig; r=mshal (e307769de7) - Bug 1181040 - Set ${var}_IS_SET variables for mk_add_options-defined variables. r=gps (19f169556b) - Bug 1193015 - Require MOZ_GLX_USE_SURFACE_SHARING to enable WebGL surface sharing on GLX. r=jgilbert (9aa4fa8f41) - Bug 1211324 (part 1) - Remove BILINEAR and GAUSSIAN filter constants. (3d9290ef02) - Bug 1211324 (part 2) - Make gfx::FILTER::GOOD convert to GraphicsFilter::FILTER_GOOD. r=mattwoodrow. (16e7607c70) - Bug 1208365 (part 1) - Remove unused EXTEND_PAD_EDGE. r=Bas. (10920e2bb6) - Bug 1208365 (part 2) - Remove gfxPattern::Extend(). r=bas. (3703b9748a) - Bug 1208365 (part 3) - Change gfxPattern::mExtend from a GraphicsExtend to a gfx::ExtendMode. r=bas. (b105d06e91) - Bug 1208365 (part 4) - Remove gfxPattern::GraphicsExtend. r=bas. (7a16d48995) - Bug 1211324 (part 3) - Remove GraphicsFilter::FILTER_FAST and replace it with FILTER_BEST. r=mattwoodrow. (b5101e049f) - Bug 1211324 (part 4) - Replace GraphicsFilter constants with gfx::Filter equivalents. r=mattwoodrow. (c19b6b030e) - Bug 1190117 - Track mLastProducerID and mLastFrameID explicitly in ImageLayerProperties. r=roc (ed9a5c777f) - Bug 1211324 (part 5) - Remove GraphicsFilter and gfxGraphicsFilter. r=mattwoodrow. (0bd4ce7160) - Bug 1194954 - Fix -Wunreachable-code warnings in gfx/layers and gfx/thebes. r=BenWa (1a3d68c490) - Bug 1180509 - Fix judder of icons in Australis doorhanger menu at the end of its scale-in animation. r=roc (9b4df470fa) - Bug 1206915 - Make paint dumping to a file e10s-friendly. r=mattwoodrow (87d2e12c2b) - Bug 1206915 - Handle nested PaintFrame() calls correctly during paint dumping. r=mattwoodrow,BenWa (d30f77fbdd) - Fix max texture size handling in displayport clamping. (bug 1135907 follow-up, r=kats) (a791894332) - Fix bogus assertion in nsLayoutUtils::SetDisplayPortMargins. (bug 1156409, r=botond, a=philor) (b635b21c34) - Bug 1169879 - Use only the critical displayport when computing image visibility. r=tn (9ec91c9527) - Bug 1169881 - Recompute image visibility when display port margins change. r=tn (35a5bd3a51) - Bug 1197765 - Compare text content inside frame instead of the content node for ruby autohiding. r=dbaron (00cf5b7674) - Bug 1173580 - Record content descriptions in APZ test data. r=kats (7a72d1ac0a) - Bug 1178971 - Changed line snapping behaviour depending on even/odd-ness of stroke width. r=mstange (495b32dc23) - Bug 1208953: [mp3] Don't parse data we've already parsed. r=cpearce (72eed4309f) - Bug 1137151: Marked destructor of |android::MediaCodecReader| as protected, r=sotaro (0632b34bc5) - Bug 1205351 - Replace nsBaseHashtable::Enumerate() calls in dom/media/ with iterators r=cpearce (45976c24c0) - Bug 1133624 - Add lang-specific ruby rules to ua.css. r=dbaron (46788cc220) - Bug 1133624 - followup add fuzzy maxdiff on CLOSED TREE (1b6b62aded) - Bug 1180443 - Consider whitespace collapse when calculating intrinsic isize of ruby. r=dbaron (3862184acd) - Bug 1153764 - Avoid explicitly doing break before when there is ruby span. r=roc (71b4ec7749) - add gstreamer parts (7e562556be) - some preferences aligned to FF (b26d0b389c) - Bug 1166301 - If APZ is enabled, clip fixed background images at the layer level rather than the display item level. r=mattwoodrow (5644e22090) - Bug 1144990 - Dump display items with class id and name, r=roc (aa2e227e35) - Bug 1205087 - Remove LayerManager parameter for ShouldFixToViewport. r=roc (00a1f2e36f) - Bug 1205087 - Make nsSVGIntegrationUtils paint frame continuations manually since combining them meant that our reference frame wasn't an ancestor of all painted frames. r=roc (e40f6b7b81) - Bug 1195400 - Check ancestor geometry roots when determining scrollability of a layer. r=mattwoodrow (4699b7e935) - Bug 1205087 - Cache the AnimatedGeometryRoot on DisplayItem. r=roc (06bba311c3) - Back out the bits of bug 1205087 that cache the AnimatedGeometryRoot on DisplayItem. r=backout (254057a6b6) - Bug 1203190 - Don't intersect with the visible rect for fixed background images. r=mattwoodrow (1c5a432459) - Bug 1208438 - Don't allow layers with scrolling clips to occlusion-cull layers behind them. r=mattwoodrow (c3d77a9846) - Bug 1205630 - Translate a fixed background display item's clip rect correctly when setting it on the layer. r=mstange (49039f0e2d) - Bug 1205630 - Reftest. r=mstange (a8db59eaee) - Bug 1105832 - Also dump inactive layer managers when display list dumping is enabled. r=mattwoodrow (564fe5fcbc) - Bug 1208661 - Move Dump() up from ContentClient to CompositableClient. r=BenWa (37915312b3) (e1776c67f8) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1208661 - Make ContentClient dumping play nicely with HTML dumping. r=BenWa (18b2c4a11b) - Bug 1204895 - Add fence handling to AutoRemoveTexture on gonk r=nical (d1f21e0210) - Bug 1208661 - Support dumping client-side layer textures without compression. r=BenWa (22ee0a45b5) - Bug 1206915 - Avoid reordering of different parts of paint dump output. r=mattwoodrow (0c7d46bca1) - Bug 1208661 - Do not assume that PaintRoot()'s contributions to the HTML paint dump will all be inside a <script> tag. r=BenWa (5917d13001) - Bug 1203992 - Distinguish between SingleTiledContentClient and MultiTiledContentClient in the layer tree dump. r=nical (70955c53cc) - Bug 1207590 - Don't use SingleTiledContentClient for layers that are larger than the maximum texture size. r=mattwoodrow (dd2a094297) - Bug 1201541 - Use SingleTiledContentClient for non-scrollable layers on Android r=mattwoodrow (6010b5080d) - missing of Bug 1161662 - Exclude post scale from layer.GetTransform(). r=roc (a3c92f89ae) - Bug 1172537 - Make the warning: "Tiled PaintedLayer with no scrollable container ancestor" occur only on actual b2g phones. r=nical (d604c9e9da) - Bug 1204597 - Use Move constructor for opaque region in FrameLayerBuilder instead of copying. r=jrmuizel (26bf99c0fb) - Bug 1201541 - Add a pref for disabling single tile layers r=mattwoodrow (e3170f8f4c) - Bug 1172719 - Fix SharedSurface fence handling on gonk r=jgilbert,nical (9fdf5fef4f) - Support all blend modes in the basic compositor. (bug 1203829 part 1, r=mattwoodrow) (ac9eeca118) - Compile shaders with newer fxc. (bug 1203829 part 2, r=mattwoodrow) (3fd4acc1ec) - Refactor shader initialization in CompositorD3D11. (bug 1203829 part 3, r=mattwoodrow) (a5e79828ad) - Handle screen and multiply blend modes in the D3D11 compositor. (bug 1203829 part 4, r=mattwoodrow) (b20c4af7fc) - Bug 1173107: Add hexa() around various hr logging. r=jrmuizel a=KWierso (76d6d27ff9) - Get the sync texture's sync handle during compositor initialization, where it can be made to fail gracefully. (bug 1207665 part 3, r=bas) (98d15069a0) - Log initialization failures in CompositorD3D11.cpp. (bug 1211109 part 1, r=mattwoodrow) (211725e4ce) - Don't use Direct2D if CompositorD3D11::Initialize fails. (bug 1208638, r=jrmuizel) (17a119bc1a) - Bug 1143653 - Typo fix in a variable name. r=me (469e89d0b6) - Remove the static compositor backend variable. (bug 1211109 part 2, r=mattwoodrow) (3b7dcb9a7c) - Allow top-level window changes to the remembered compositor type. (bug 1211109 part 3, r=mattwoodrow) (9309cdfd0f) - Remove ISurfaceAllocator::GetCompositorBackend. (bug 1211109 part 4, r=mattwoodrow) (2928f757c8) - Bug 1143653 - Backout part of the initial patch because of crashes. (33637851d4) - missing bit of 687388 (19770529ef) - Bug 1208071 - Ensure that only valid texture actors are added to ImageBridge tarnsactions. r=sotaro (23bef4f601) - Bug 1197534 - Send RecycleTexture messages from the ImageBridge thread. r=sotaro (7249beb404) (7f6fda62d8) * Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses. A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon761 point
-
Spiritually speaking, of course, meaning we are not just skin an bones.1 point
-
New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220924-3219d2d-uxp-f84bc6d60-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20220924-3219d2d-uxp-f84bc6d60-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220924-3219d2d-uxp-f84bc6d60-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220924-d849524bd-uxp-f84bc6d60-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220924-d849524bd-uxp-f84bc6d60-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20220924-d849524bd-uxp-f84bc6d60-xpmod.7z Official UXP changes picked since my last build: - No issue - Stop pre-processing some files that don't have preprocessor statements in them. (800090d0c) - Issue #2008 - Implement missing s parameter parsing and align case with spec. (05389eb41) - [DOM security] Be more explicit about CSP checks and reports. (95120acbb) - [network] Reject cookies with no name and a __Secure- or __Host- prefix (91b51a650) - Issue #1992 - Part 1: Un-prefix -moz-{min|max}-content keywords. (fa8bc1e81) - Issue #1992 - Part 2: Regenerate devtools CSS database. (5abfd892a) - Issue #1977 - Follow-up: Correct pref check to be selective on wave formats only. (d2276a48d) Official Pale-Moon changes picked since my last build: - [Pale-Moon] Issue #21 - Remove leftover telemetry code for the app menu's opening time (0f67602bf) Official Basilisk changes picked since my last build: - [Basilisk] Issue #29 - Remove telemetry from pdfjs completely (f5e49fb5a) - [Basilisk] No Issue - Remove stray semicolon (ef3685dc5) My changes picked since my last build: - update NSS builtin certstore to Sep 2022 version from mozilla upstream. (29846d1e4) - partly import changes from tenfourfox: - 102ESR: rev EV roots, TLDs, tzdata (c47bef11f) (a9c379217) - partly import changes from tenfourfox: - #651: M1767365+backbugs M1757604 M1771774 M1776658 (bc6daa0ae) (591552c5b) - d3d9: further lowered MaxTexture limit to 1024 to give chance for Radeon 9550 and GMA 965 to use hardware acceleration (67a84940e) - backout bug1757604 part from rev 591552c5 as it cause display issues (5d774d070) Update Notice: - You may delete file named icudt58l.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.1 point
-
Same here. Now I use your modified version, in which I also replaced './assets/assets.json' with the current one from uBO 1.44.5b0. There have been some significant changes over time. The last one being in regard to the very slow download of EasyList and EasyPrivacy. uBlock0_1.16.4.30.firefox-legacy-mod-by-@AstroSkipper&nicolaasjan.zip1 point
-
Since you have a Windows 10 available, use the fsutil to check the sector size that the disk exposes. If it exposes 512 bytes/sector, you won't be able to access more than 2.2 TB (a special formatting is possible to access up to around 4.4 TB, but it won't work in XP only in 7 and possibly later) If it exposes 4096 bytes sector (aka 4K native), then it should be possible to access the whole 5 TB from XP (but the disk won't be bootable, for other reasons). The fact that all tools you tried set a limit to 2-2.2 TB should mean that the disk exposes a 512 bytes/sector, and as such you cannot go past the 2^32-1 sector llimit. The 1 MB in front of the partition you created is rather "normal", it is the "new" alignment to 1MB (2048 512 bytes/sector) introduced since Vista as opposed to the traditional 63 sector (cylinder/head alignment) used up to XP (but XP has no issues with 1 MB alignment UNLESS you use logical volumes inside extended). The thread you referenced is about a very peculiar external case with two connection interfaces, eSATA and USB) that provided a "pass through" on one interface and a "translated" one on the other, your disk has only one interface (USB) so it is unrelated, it can only be useful if you need to (tangentially) learn more about the implications of 512/512AF vs. 4K disks. Check the disk with gdisk: https://www.rodsbooks.com/gdisk/ not the most friendly tool around, but the only one that will provide you with the exact data in either the MBR partition table or GPT. jaclaz1 point
-
@UCyborg Great to see you back after approximately 3 months of your inactivity! How's life going? Many people in this forum miss you. Mainly, me, @XPerceniol, @msfntor and @AstroSkipper miss you here. I hope you're fine.1 point