Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

One of our complaints from traders: the UI optimised orders for speed, not correctness. Some flows updated positions before the exchange responded, then corrected them later if the order was partially filled or failed, but this caused late updates, incorrect states, and failed sells. Now that our indexing and...

15,715 Aufrufe • vor 8 Tagen •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Al‑Qaeda Isn’t Finished. They’re Intent on Turning Past Failures into Success. One of the most important things people miss about al‑Qaeda is this: They don’t abandon failed plots. They recycle them. Their current U.S. homeland strategy is built on bringing old failures back, and this time, making them succeed. Look at the pattern: They hit the World Trade Center in 1993 and failed to bring it down. Eight years later, they came back and finished the job. The same mindset applies to everything else al‑Qaeda tried and couldn’t pull off: Project Bojinka was the original blueprint for using commercial aviation as a weapon. Parts of it failed in the 1990s. They brought the idea back and used it to build 9/11. They still believe Bojinka must be completed. That is why the aviation plot is back. None of these ideas are over. The group’s current U.S. homeland plot is not new, it is simply being fulfilled by the next generation of al-Qaeda. It is a direct extension of what they attempted before, only now they intend to turn every past failure into a success. Yes, you read that right. Every. Single. One. Abu Bakr Naji, al‑Qaeda strategist and doctrinal advisor, author of The Management of Savagery, believed failure was part of a longer-term strategy, not a terminal endpoint. In his framework, setbacks aren’t the end of jihad, just a step in escalation, refinement, and eventual success. He wrote: “If we fail—we seek refuge with God from that—it does not mean an end of the matter. Rather, this failure will lead to an increase in savagery.” Understanding this is key: the next attack will hit harder. Our intelligence community knows how each plot failed before. So why can’t they thwart them now?

Sarah Adams

94,999 Aufrufe • vor 10 Monaten

🚨 BREAKING: President Trump announces he will be appointing a HIGH IQ "AI CZAR" and launches the "AI FORCE" Trump says we will UNLEASH AI and that the propaganda will fail All of this will be geared towards not only BUSTING anti-AI hoaxes but keeping America number one. LET'S GO! 🔥 "I am forming the AI Force, much like I did Space Force, which has been a tremendous SUCCESS, in my First Term. To that end, I will be announcing, in the near future, the AI “Czar” — Only High I.Q. individuals need apply! AI is the next Industrial Revolution, or Internet, but will be even larger and more impactful, possibly as much as 25% of our Country’s GDP. We are leading China, and the rest of the World, and I intend to keep it that way!" "Over the years, there have been many Hoaxes, all generated by the Radical Left Dumocrats, for purposes of destroying our Country. RUSSIA, RUSSIA, RUSSIA, UKRAINE, UKRAINE, UKRAINE, Global Warming, Impeachment Hoax 1, Impeachment Hoax 2..." "Now, the decimation, or destruction, of AI, commonly known as Artificial Intelligence — And I, as President of the United States, will not stand by and let this happen." "It all began with an attack on our Data Centers, until people realized how wealthy and prestigious they were for the Communities in which they were built." "Higher Salaries, Lower Taxes, and Safer Streets, was the result, and the crazed Data Center attack has largely failed, so now, in much the same way as they changed the term “Global Warming” to “Climate Change,” in that it covers a much larger “territory” of doubt, they are going straight at AI. We will not in any way hinder or stifle the Growth of this incredible Industry." "Rather, we will cherish it, help it, and watch over it, as it grows! However, we will also be looking for BAD, and we can do that, very easily, with our already existing Criminal and Civil Justice System."

Eric Daugherty

190,669 Aufrufe • vor 5 Tagen

As a graphics engine coder I think when you look at a flickering bug like this one in the video below it’s not immediately obvious what is going on. The key here is observation - to study this flickering/bugged render carefully - what do we see? Firstly for me it was very obvious that nearly all of the scene shadows were flashing on and off - but (but!) there was a secondary issue where some buildings and parts of the sky were also flashing purple. Hmmmm. Interesting. I initially thought then this might be two separate bugs - but because the sky purple element could only based on full screen post fx and not 3D rendering I looked at this first with a few GPU captures to step through all our post processing to find the rendering stage which made these pixels turn purple: When I did this I found the colour 3D texture LUT grading that makes our different biomes have unique colour palettes was going very wrong - colours near 0 or 1 were wrapping and making the purple elements that we see in the said sky and base parts. The only way this could happen was if the texture was corrupt (which it was not) or if the 3D texture sampling was wrapping and not clamped as intended. That was the Eureka moment - because if the post fx had the wrong texture sampler then the disappearing shadows which also require an exact texture sampler for comparing depth might be also wrong because of the same kind of texture sampling issue! So with this idea that the engine was using the wrong texture samplers, but only in very high draw call scenes like the big base here I the looked at some engine limits and found the bug very quickly - a circular dx12 descriptor buffer for samplers running out over multiple frames, reusing the wrong data for new scenes inflight. Hence the flickering, as the GPU randomly got wrong samplers for some post textures or shadow depth. Easy to fix with triple limits for future expansion and also adding an assert/debug spam in case this limit is ever reached again - QA testers would see this message and report if they ever saw a flicker with this style of bug. My bug and my bad from 2017 porting NMS to DX12 without foreseeing how massively complex bases and our game would grow.

Martin Griffiths

72,855 Aufrufe • vor 1 Jahr