EyeWitness Testimony

In person, the entire middle of the drone was fully transparent. It looked almost exactly like the "My POV" photo above, except the middle was in the shape of a pneumatic tube. Both sides of the drone featured an extremely thin sheet of metal, connecting the top and bottom lights with the tubular middle. Besides the two lights, the sheet of metal on each side, and the tubular middle, the drone had no other visible components. The middle of the drone warped the light directly behind it, with the warped light always following multiple wave patterns proceeding from the top, bottom, left, and right of its core. All of the wave patterns appeared to converge towards the center of the drone. While the drone was operating in the street before its ascent towards the hospital, it was pointed directly at me for the entire time, which lasted for approximately 30 seconds.

When the drone operator repositioned the drone to appear as if it were directly in front of me, I had a clear view of the drone’s core as it ascended vertically and was angled upright. When the drone started its movement during this period, it was ~5 feet above the ground on the opposite sidewalk, only a few feet in front of the trees, and appeared to be positioned directly in front of my apartment window as it slowly ascended. The warp never appeared to contain straight lines or jagged edges, just multiple moving waves converging towards the very center of the drone. As I looked through the top-middle section of the drone's core, I vividly remember the grass above the wall bleeding into the graffiti in a U-shape. The grass behind the graffiti appeared close to black instead of its original green color when viewed through the drone's center. Each wave pattern in the drone was clearly defined at its edge, and each wave would constantly move as the drone climbed, with new waves emerging from each direction every second or so. The waves emerging from the side of the drone moved horizontally, while those from the top and bottom moved vertically towards the center. However, I can not remember the wave's pattern with 100% confidence, and whether the waves were oscillating or if new waves were emerging from the outside of the drone.Each new wave also seemed to be slightly different in its shape, even if it originated from the same side of the drone's core. A small area in the absolute center of the drone's core featured no waves, indicating that it was either the attractor or source of the wave patterns. The drone appeared to move the slowest during this period of its flight, and I observed this vertical climb for ~6 seconds. Aside from this slow climb directly in front of my apartment window, the drone moved at a constant speed throughout its entire flight. Initially, I assumed that the drone's core could have been a liquid, as looking through the middle was like looking through a rippling pool of water. If you told me that the core was plasma, I would have believed you initially, but it was just the light warping that produced that appearance.

Transparent core on video

Confirms my eyewitness testimony of the drone's appearance

As I mentioned in my witness testimony, the drone had a completely transparent middle. At the start of the video, the drone faces away from the camera, then rotates toward the camera as it travels closer. Luckily, you don't have to just take my word for the drone's in-person appearance. The drone's rotation and the transparent nature of its core can be confirmed by altering the color values of the first few frames while the drone is facing in the opposite direction. As you can see above, two distinct red patterns are visible at the top and bottom of the drone, matching the position and shape of the drone's lights as shown later in the video. During the next few frames, the redshift begins, and the bottom red light of the drone disappears while the top red light stays visible. This parallels the bottom light being the last light to reappear later in the video when the redshift starts to angle away from the camera around frame 100. In the 'Who Are We?" section of this website, I provide proof that I described the drone's core as transparent just minutes after viewing the drone, months before conducting this analysis. Altogether, this simple color analysis proves two of the most important aspects needed to confirm the technology powering this drone and my eyewitness testimony: the transparent core of the drone, and its core shifting the appearance of the light viewed through it. Next, I will recap every movement that I witnessed before, during, and after recording the video.

Four Flight Modes IRL

An accurate description of four of the drone's flight modes that I witnessed in person

In real life, the drone had four distinct modes of travel. In every mode, the top light of the drone led the drone’s travel, while the bottom light trailed behind. Though the drone's angle abruptly shifted preceding each change in mode or direction, the drone’s shape and size stayed constant throughout its entire flight. The first mode I'll describe is its lateral movement. In this mode, the top light would angle to the left or right at around 25-30 degrees, and the drone would immediately glide in the direction that the top light was facing. In this mode, the drone could only travel left or right, not forward, backward, up, or down. The second mode involved a movement where the drone was angled perfectly vertical, and the drone would either ascend or descend. In this mode, the drone could only travel up or down on its vertical plane. The third mode was a wave-like motion that allowed the drone to travel on its horizontal and vertical axes simultaneously. In this mode, the drone swam like a fish through the air, evenly increasing the height of each peak and trough with each new wave. During this mode, the top light was never even with or lower in altitude than the bottom light as it was climbing. In the fourth and final mode, the drone would quickly snap to a 45-degree angle and drift in whatever direction the top light was facing. In this mode, it could only travel horizontally, but it could move in all four directions on its horizontal plane. In this mode, it was even more evident that the drone was effortlessly floating through space. In the other three modes, it was clear that it used no conventional form of propulsion, but in this fourth mode, the drone seemed to relax and effortlessly glide through the air like an object floating in outer space. In this mode, the angular shift of the top light when it changed directions was much quicker and more aggressive than in every other mode.

3 Modes On Camera

The three different flight modes captured in the video

The video starts with the drone in its 45-degree mode. Something noteworthy is that the beginning of the video is the only period during the entire encounter when the drone's top light did not lead its flight. During this period before the redshift is visible, the drone is floating smoothly through the air, akin to an object’s movement in a zero-gravity environment. Immediately after the first sensor glitch, the drone switches to its wave-like travel mode, although its movement in this mode is exponentially less pronounced on camera than it was in real life. Remember that during the video, the drone approaches the camera and drastically descends in altitude, although this movement is difficult to tell as the drone does not enlarge proportionally on camera. When the drone and its field rotate to face the street immediately before the video goes black at around the 5.5-second mark, the drone switches from its wave-like mode to the mode where it ascends and descends vertically. During this period, the drone rotates counterclockwise around its vertical axis until its lights are pointing towards the ground. This means that the mode that once propelled it only vertically now propels the drone only horizontally. I observed this period in person, as I got a clear view of the drone passing above the apartment window, which is captured during this section of the video. At this point, I visually observed that the drone was clearly facing the ground and traveling to the left of the camera.

Key Flight Zones & Flight Recap

What I witnessed in person and my initial reaction

Here is a model of the approximate locations of the key moments throughout the drone's entire flight. Again, the drone consisted of two bright red lights, two extremely thin sheets of metal, and a completely transparent, warped middle section. I accurately remember its positioning and most of its movements, although I cannot recall the exact order of the drone's flight path with 100% accuracy. Throughout its entire flight before its ascent towards the hospital, the drone was in the middle of the street, either inside or close to the intersection. Before it ascended, I witnessed it in operation in the middle of the street about 40 to 60 feet in front of me, and it was only slightly above window level at its highest point. As I sat upright in my friend's bed daydreaming, I saw an unusually bright red light shining at the window. Before I opened the sunshades, I had a weird feeling that the light outside was something extremely abnormal. You could say I “felt” the drone before I saw it. Once I opened the sunshades in the apartment, I witnessed two extremely bright red lights near the intersection, slightly above window level, pointing directly at me with the top light angled towards me, while the drone moved laterally in my direction. My face immediately lit up like a kid in a candy store. I was overcome with nothing but awe, intrigue, and happiness as I observed the drone, since I thought that a baby alien accidentally teleported to the middle of Atlanta. I did not feel fear, shock, or worry for even a single second as I watched it gracefully dance through the air. The drone's beauty was indescribable; it felt like E.T. changed forms and found a new best friend.

The device was always in motion, and its speed remained constant except for the vertical movement I described earlier. About a second after I first saw the drone, it quickly switched directions by tilting its top light and began moving away from me on its x-axis. After traveling away from me for 2-3 seconds, it repeated this same side-to-side movement. Once it was near the middle of the intersection, the drone angled its top and bottom lights perfectly vertical before descending and moving a few feet closer to the ground. Then, it moved towards me again, performing its same tilt and side-to-side movement a few more times. After this movement, my memory went completely blank, and the drone now appeared to be directly in front of me, positioned just a few inches in front of the tree on the opposite sidewalk. At this moment, the drone was ascending at a perfect 90-degree angle relative to the ground. As it began to slowly ascend in front of me, I got the best view of the warp pattern in the middle of the drone. This is also where I experienced the double memory and other conscious effects that I mentioned in the next section. After it finished this movement, it traveled in a wavelike motion close to the intersection, but this time it was much closer to the apartments, and its altitude was around window level. As it flew to this position, it didn't fly in a perfectly vertical or horizontal motion on its x and y axes as it did previously; it was swimming in a wave pattern like a dolphin in water. When the drone was close to the edge of the building, it activated "float mode," its final, and in my opinion, its most beautiful mode of flight.

In all four of the drone's modes, it was clear that there was no visible form of propulsion. However, "float mode" was by far the most intriguing mode. In “float mode,” the drone quickly snapped to a 45-degree angle and effortlessly floated through the sky on its x-axis in the direction where the top was angled. In its basic mode, the top light only angled to ~25-30 degrees for its lateral movement. In float mode, it was clear that the drone was floating on its own medium, completely ignoring the influence of any external force. It cycled through this mode a few times as it moved horizontally in all four directions on its x-axis, instantly and effortlessly snapping to a 45-degree angle each time. At one point, it cycled from this mode back to its basic horizontal mode, then back to float mode, all while staying on the same x-axis in the same area, so I am entirely sure that this mode is different than its basic horizontal mode. After this movement, it traveled in wave mode as it ascended to the spot where the video starts. Initially, I did not record the drone while it was in front of me as I thought the "baby alien" would instantly recognize if I was trying to record it and teleport away. Once I saw that it started ascending at the same speed as it was moving earlier, I became confident of my suspicion that it was a slow baby alien who just learned how to fly. As it was ascending, I thought that it was my one and only chance to capture an alien on camera. So, I quickly reached down to grab my phone and start recording. Right before I started recording, I only saw the drone in the sky for a split second, but it was clear that the drone was operating around the center of the field across the street. When I started recording, I knew that the drone was still in the area because I figured it was still moving at a constant speed, so I just pointed the phone toward where I thought it might be and hoped I hadn't missed my chance. As I started recording, I quickly glanced at the sky and back at the camera to see if it was still there. As I zoomed in, I was unsure if the drone was in the frame, as I could not locate it in the sky. While recording the video, I only clearly saw the drone's position in real life at around the video's 5-second mark, when I said, "Bruh WTF." At this point, the drone was facing the ground, an orientation it had never been in before I started recording. Initially, I assumed that the lights on the drone stretched around the entire top and bottom; I did not realize that the drone's lights were pointed directly at me for the entirety of its flight before it ascended towards the hospital, until I closely examined the video after Matthew Livelsberger's warning.Despite seeing the car, I didn’t see anyone on the street, so I continued with my assumption that I saw a friendly alien. A few seconds after I realized the drone wasn't coming back, I walked around the apartment, excited and shocked, with my hands on my head, continuously jumping, running around, and saying "HOLY SHIT," "WTF," and "OMG," for about 45 minutes. It was the happiest moment of my life; seeing an alien was at the top of my bucket list, and it looked so welcoming, beautiful, and friendly. I thought that it even gave me a little dance to show off how cool and friendly it was. I wasn't aware that I was feet away from a top-secret WMD flown by Chinese special ops soldiers on American soil. Although part of me initially knew that there was a chance it could be government technology, I was too caught up in the beauty of the drone to care, and I thought, "If I die, at least I died happily and in a cool way." In the next section, I expand on all of the conscious effects I experienced as I was in the drone's field, but first, let's explore the major anomalies that the drone exhibits on camera.

Redshift & blueshift

A fundamental principle of a warp field's effects on the frequency of light

In person, the drone never emitted any color or light besides a red light at the top and bottom of the device. These two lights were necessary for the operator to control the drone, and the lights' position on the drone remained constant throughout the entire flight. The red-orange glow in the middle of the drone in the video is caused by the camera capturing light behind the drone being pulled into the drone's spacetime expansion zone, not a physical red light within the drone. This explains why this phenomenon is most visible when the drone's center aligns directly with the camera and disappears once the drone's core rotates away from the camera. The blue, purple, and green you see around the drone are a blueshift of light due to spacetime compressing in its wake. These color changes occur because the drone’s propulsion system operates by warping spacetime, expanding space ahead of its path and compressing it behind, causing a shift in the wavelength of visible light that is undetectable by the naked eye. Unlike a conventional propulsion system that must expel mass in the opposite direction to generate thrust, this field-based alteration allows the drone to fly by shifting its localized warp bubble through the surrounding environment. A craft causing redshifts and blueshifts is a fundamental principle in most warp drive theories.On video, the redshift starts from the direction of the drone's travel, and the blueshift begins in the opposite direction, aligning perfectly with existing theories of an Alcubierre-type anti-gravity drone. This phenomenon is only apparent on camera due to the camera's ability to capture frequency shifts that the human eye can not see. If this red glow were an emission from the drone and not a frequency shift, it would not completely disappear on camera while the core is still visible. The location of the drone's redshift and blueshift also perfectly coincides with the two periods of time dilation that I experienced when the drone was only ~50 feet in front of me and while it passed directly overhead.

Redshift and blueshift zone after adjusted color scopes

Another example of how the drone affects the surrounding light

The drone causes an extended redshift and blueshift zone in its surrounding area. The redshift in the front and the blueshift behind also perfectly match the drone's central redshift beginning in its direction of travel, and my documented time dilation, which I provide evidence for on the next page.

Red vs Blue Dominant Pixels

When you compare which pixels have the strongest red value and the pixels with the strongest blue value, a clear pattern emerges. The drone's wake features a higher volume of blue pixels, while the area in front of the drone features a higher volume of red pixels. This matches the primary redshift and blueshift pattern that is visible immediately around the drone.

The drone's immediate radial field

There is visible radial distortion in the drone's immediate area throughout the video

When you increase the luminance of the video, it becomes clear that a radial field of distorting light surrounds the drone throughout its flight. In Alcubierre's original 1994 paper, a thin shell of negative-energy density is required to create a warp bubble around a craft. This thin bubble likely protects the craft from the extreme gravitational gradient of its field, which would destroy the drone if it were left unprotected.

One of the most apparent and unusual aspects of the drone is that it appears to change size and shape throughout the video. In person, the drone's size and shape remained constant throughout its entire flight. The drone was about the size of a stoplight; I would estimate that it was around 2.5 to 3.5 feet long and around one foot wide. Despite the size never scaling accurately on video as it moves closer to the camera, the drone's length and width fluctuate throughout the video, with it sometimes shrinking despite moving closer to the camera. It appears to be different sizes on video due to the drone's localized spacetime manipulation affecting how the camera pipeline processes light. The warp bubble's properties fluctuate throughout its flight, constantly changing how the drone's light is bent and subsequently interpreted by the camera. This phenomenon is best observed when the drone’s redshifted middle is aimed at the camera from frames 65 to 94. When this happens, it becomes clear that its gravitational field bends light paths. As shown in the first photo above, the camera isn’t capturing the drone's actual top and bottom red lights while the redshift is visible; it’s capturing the warped light from them after it’s passed through the drone’s field. The color and shape distortions are perfectly consistent with what you would expect if a warp field were actively manipulating the intensity and path of surrounding light. The same field-based lensing briefly demagnifies the craft around the compression zone, making the bottom half of the drone appear to shrink in size multiple times throughout the video.

The frame that most closely resembles the drone's appearance in person is the frame on the left. An interesting fact about this frame is that when you rotate it 45 degrees, the drone is angled perfectly vertical. This is noteworthy when you consider the distinct 45-degree mode that I witnessed in person and documented before I noticed the rotation anomaly in this frame. 45 degrees is likely the angle where the drone's warp bubble is most stable.

After the drone completes its rotation into a perfectly horizontal orientation, it becomes clear that the drone's light paths are distorted by observing the appearance of the two red lights. Because the red lights are fixed in place, any visible distortion reflects the camera’s processing of the incoming photons, rather than a physical shift of the light's position.

Muted Movement & Scaling Issues

The drone's movement, descent, and approach on camera never reflect its actual movement and position in the sky

For the entire video, the camera is in the drone’s spacetime expansion zone. Despite the drone descending towards the camera in a wavelike motion with alternating peaks and troughs for most of the video, its movement and scale in the video never reflect how it traveled in real life. From the start to the end of the video, the drone traveled ~200 feet toward the camera as it drastically descended in altitude. As the drone faced the street horizontally, it was much bigger in person than how it appeared on camera, despite my camera being zoomed. What initially seems like an impossible camera anomaly becomes a smoking gun for concluding the drone’s manipulation of the surrounding spacetime. In the expansion zone, as the drone approaches you, the distance between you and the drone would also increase, nullifying any instrument's ability to accurately depict its approach. This makes this technology perfect for stealthy operation, as air defense sensors fail to accurately determine the object’s position, making the drone virtually impossible to counter with any air defense technology. The drone flying closer to the camera is confirmed by my visual observation of the drone’s position right before I started recording, and its position directly overhead during the video's blackout when the camera enters the drone's immediate field. If this is confusing, here is an analogy. Think of the drone as working like a table fan, pulling the air behind it to push it out of the front. As the fan moves closer to you, the amount of air between you and the fan increases. Now imagine if this fan sucked in spacetime from the back and pushed it out the front. As the fan moves closer to you, the amount of spacetime between you and the fan increases proportional to its movement, causing the fan to appear in a fixed position.

True Black Pixels

Blue pixels represent true black values (RGB = 0,0,0)

These values reflect pixels where the sensor outputs a blank value due to very little light reaching the sensor in that area, causing the camera pipeline to clamp the value to black. The second true black value is "coincidentally" present in the very center of the drone. As the drone flies directly overhead, the ISP outputs frames that are entirely black, for reasons unrelated to the lone true black pixels, which I explain later. However, even after the sensor recovers and resets after displaying these black frames, the ISP continues to return true black values near the drone's last location, as the photons near the drone's last position remain heavily distorted. This provides more evidence of the drone shifting the frequency of the light in its immediate area. No known propellerless or wingless propulsion technology can cause any of these phenomena.

While describing the drone's in-person appearance, I mentioned that there was no warped light in the very center of the drone's core, and it appeared to either be the source or attractor of the light waves. Along with the second true black value being present in the very center of the drone, on this frame, when the drone's appearance on video starts to resemble how it looked in person, there is a visible difference in the luminance of the very center of the drone's core.

Time Discrepancy

The drone finished its rotation before the camera captured the motion

During this portion of the encounter, I did not observe the drone rotating into its horizontal position as it does on video. When I said "Bro wtf," the drone was already completely horizontal, although the video shows me saying "Bro wtf" before the rotation even begins. I vividly remember this part of the drone's flight, so I am entirely confident that the drone's rotation on video occurs after it already finished rotating in real life. No other technology can cause such a major discrepancy between a drone's measured and actual position. Altogether, the drone's ability to alter how an instrument perceives the position, intensity, and timing of the photons in its vicinity makes this technology impossible to effectively counter.In the flight path reenactment at the top of this page, I depict this period from my viewpoint as it is more accurate than what the camera captured.

ISP & Sensor Failures

Optical Image Stabilization Struggling Under Unusual Conditions

(Volume Up)

The faint rattling noise heard throughout the video reflects the optical image stabilization system struggling under unusual conditions. The only variable that could cause unusual conditions in this video is the drone. By examining the behavior of the iPhone's stabilization, it becomes apparent that the drone is creating some alteration that the ISP is struggling to process. The next section details exactly why the drone causes the stabilization system to struggle.

The drone remains in the same vertical position on video after completing its rotation, matching my eyewitness description of the drone's horizontal-only movement during this period. After the drone completes its rotation, the iPhone determines that the drone is the subject and attempts to stabilize its movement. An anisotropy analysis verifying greater movement in the drone's immediate area during this last stabilization anomaly before the blackout provides additional evidence that the camera focused on the drone.Even though the drone stays in roughly the same vertical position on the frame, matching its constant vertical position in real life, the stabilizer warps the rest of the frame vertically towards the drone. In its attempt to keep the drone's position stable, the stabilization system decided that it needed to shift the entire frame vertically, despite the constant vertical position of the drone, camera, and every object in the foreground. This means that despite every object in the scene and the camera remaining in the same vertical position, the camera still detected a significant downward movement of the scene, or an upward movement of the camera, causing the stabilization system to dramatically shift the entire frame upward to compensate. Altogether, the phone’s decision to apply a vertical correction, despite no vertical movement from any factor other than the position of the recorded light, provides further evidence that the drone is shifting both light and space.

The stabilizer encounters movement so extreme that it exceeds its limit and attempts to stabilize past the sensor area

A stabilization error more severe than all of the previous errors occurs around forty frames after the stabilization system first resets, which happens when the video goes black. Despite the drone being out of the camera's view, the stabilization system was still incorrectly detecting an abnormally high downward movement of the light. The stabilizer detects a movement so extreme that when it attempts to stabilize the frame, it exceeds its limit and runs out of sensor area to use. If the ISP reaches the end of the sensor area while stabilizing the frame, in some cases, it will begin to duplicate the pixels at the edge to maintain a complete image. If the movement is so severe that duplicating the edge pixels is not enough to stabilize the movement, it will resort to adding padding to the edge of the frame, which is exactly what happens during this period of the video. This severe warping, which exceeds the camera’s limits, occurring while the drone is out of view, proves that the drone's technology is field-based and impacts electronics in a way unlike any known technology.

This warp can only occur under extreme motion, but once again, there is no movement from the blinds or phone, which is confirmed by the star returning to roughly the same position after the stabilization system resets. Throughout the entirety of the video, the phone was almost perfectly still, and the blinds remained in the same position. So, what do you think could possibly cause the phone to detect such abnormal and extreme motion, besides the wingless, propellerless, mostly transparent drone that's actively violating Newton’s laws of rotational motion? In the next section, we will explore the anomalies that can only be caused by either a sudden bright light entering the scene or by an abnormally high number of photons reaching the sensor.

Image lag while the drone flies overhead

Repeated pixel-well overloads provide strong evidence for the drone creating a sudden increase in photons

Multiple times throughout the video, the brightest lights in the frame persist through the following frames and slowly fade away, instead of changing with each frame. This phenomenon is called charge lag, and it happens when a CMOS sensor’s photodiodes hold electrons, which are created from the photons that reach the camera, longer than expected. The primary causes for this anomaly are either an extremely bright light entering the scene or a photon increase that exceeded the sensor’s limit, causing the brightest pixels to hold their charge for longer. As you can see, no extremely bright light enters the scene, and there is no brightness spike, leaving the only logical cause to be each pixel well receiving a sudden increase in photons, which causes the brightest pixels to exceed their limit, causing them to persist over the next few frames instead of resetting after every frame. Given that the drone is the only variable in the frame, the fact that this only occurs when the drone’s field is close to the camera, and the drone's only visible source facing away from the camera, it is only logical to conclude that the drone's field causes this image lag by creating an anomalously large increase in photons in its vicinity. This leads us to the next ISP error, the three consecutive true black frames, which reflect another major ISP error and solidify the case of a field induced photon overload.

When the drone’s field is close enough to significantly impact the camera's photodiodes, the sensor abruptly outputs three true black frames. If a CMOS sensor is overloaded by an unexpected and extremely bright light or an anomalous increase in photons, the readout will fail or the image integration will collapse, producing frames with all zero RGB values. This failure happens right as the drone passes overhead. By analyzing the two anomalies that occur immediately before this blackout and the sensor recovery process, we can determine the likely cause of the ISP artifact. These two anomalies are the charge lag that caused the star to overlay the blinds and the stabilization failure.Although it seems that all frames are completely black after the true black frames until the star returns, adjusting the luminance reveals that the ISP is still producing images, although each frame is extremely underexposed. This underexposure is an expected ISP response after encountering either an extremely bright light source or a sudden spike in photons, which are the same two potential causes of the image lag observed immediately before the blackout frames. Since no luminance spike is recorded with a visual or technical observation, and the only major variable outside the window is the drone, you can effectively conclude that an extremely bright light source did not cause the image lag or the pipeline failure.After the recovery process, the chance that a stabilization failure caused the blackout is also effectively eliminated, leaving the only logical conclusion: the failure was caused by an extremely high increase in recorded photons, consistent with the same mechanism that caused the prior image lag. During each period of the camera's recovery after the true black frames, the ISP clamps the camera to intake the lowest possible amount of light that an iPhone camera can record. As a result, the darkest values in the scene are clamped to true black. Unsurprisingly, during this instance, a dark trail of true black pixels persists in the drone's immediate area, matching the low-luminance zone observed throughout the video. When you combine the earlier observation of the drone's area being the area with the lowest luminance, it becomes even easier to conclude that the drone does not feature any abnormally bright lights that could overload a pixel well, leaving the only logical culprit to be the drone's field.When you also consider that I was able to observe the drone during this period without any visual discomfort, and with the video evidence matching my eyewitness testimony of the drone's movement and orientation, and that the drone's two red lights were pointed away from the camera when this occurred, it becomes clear that the sudden introduction of a bright light was not the cause of this phenomena.

The camera intermittently experiences the same failure while the drone continues its travel

The same phenomenon of true black frames followed by a decrease in ISO occurs two more times until the video ends. During this period, before the image lag of the star occurs, the star's pixels reach the maximum brightness value a pixel can reach (255), providing even more evidence that the frame becomes severely overexposed every time the camera tries to resume normal operation. Remember that as this is happening, the camera is still travelling horizontally relative to the camera, maintains the same altitude, and is visible from my point of view. So at this point, the drone's field is still close enough to significantly affect the drone. I only angle the camera down once the camera leaves my field of view. Along with the stabilization failures that repeatedly occur each time the image recovers, it is clear that the drone is causing the camera's motion calculation and photon processing system to err.

Examining the brightest sections of the frame during the third and final failure confirms that a photon overload is the cause

As you see above, during the third blackout, the entire frame is true black except for the brightest lights from the building in the distance. Despite the ISP intending to output an empty frame, because the pixel wells from the brightest areas are severely overloaded, the sensor can not clear them in time, causing them to bleed into the next frames. Once again, immediately before the third blackout, multiple pixels record the highest pixel brightness value (255). It becomes clear that due to a photon overload, the hardware still has trapped electrons in the pixels that have reached their capacity.

Midtones Raised

The reason the camera alternates between normal operation and its pixel-well overload pipeline reset defense mechanism as the drone flies overhead becomes clearer when we examine how the FPS changes correspond to the repeated output of true black frames. Typically, iPhones don’t switch the FPS of a video unless the camera detects a changing light environment. When the FPS decreases, the camera determines that there is not enough light in the scene and that it needs to spend more time collecting light to properly expose the frame. When the FPS increases, the camera decides that there is too much light in the scene and that it does not need as much time to reach a proper exposure. On frame 58, the camera completes its switch to the 3× digital zoom, which typically causes FPS drops because it records a smaller area and requires more time to properly expose each frame in low-light conditions.However, anomalous FPS changes in the data begin the second time the ISP outputs true black frames, and continue until I angle the camera away from the window, which solidifies the case for a photon overload. This can be solidified by analyzing the difference in FPS changes during the first, second, and third blackout periods. Before a frame is fully captured, the ISP is built to detect an incoming pixel-well overload and output true black pixels as a defense before they overload. During the first blackout, this defense mechanism succeeds, and the ISP abandons capturing the image and pauses the photodiodes from accumulating any more incoming photons, which results in the repeated true black frames without a change in FPS. During the second and third blackout, since some pixel-wells overload before the pipeline reset engages, the ISP decides that there is too much light and momentarily increases the FPS as a result. After realizing that the ISP decided to empty out the pixel wells, it returns to the baseline of 24fps. The first blackout is the longest because the iPhone needed a high-confidence light source in the scene to quickly resume normal operation. Once the star is introduced, this prerequisite for resuming normal operation is met, and the camera mistakenly thinks that it is safe to resume normal operation...twice.This provides further evidence that the drone caused rapid and unusual photon alterations in the area, reflected in the sensor repeatedly perceiving a scene too dangerous to maintain normal camera operation, causing it to shut down each time shortly after it resumed normal operation, until the camera is angled away from the window.Along with this anomaly, the light continues to warp and converge toward the drone throughout this distortion period. This drastically weakens the argument for any conventional explanations behind any of the distortions during the video. Until I angle the camera away from the sky and capture the drone operators' car, after each time the ISP resumes its normal behavior, the stabilization system immediately resumes its abnormal warping, the image lag resumes, and the camera repeatedly shuts down to prevent a pixel-well overload.Altogether, the data shows that while the drone flew overhead, the camera behaved as if there was either an abnormally bright light or an abnormally large amount of photons in the area, despite no extremely bright light source being present, along with something significantly affecting the motion of the scene.

Optical flow algorithm failure

Severe motion estimation failures, which prove a pixel well overload

The video above is what appears when you apply an optical flow time interpolation to the video. Optical flow is a video analysis method that estimates the motion of pixels between two adjacent frames of a video. The optical flow algorithm relies on predictable pixel movement and brightness between frames. Using this algorithm on a video experiencing pixel-well overloads and pipeline resets causes the algorithm to fail, resulting in severe visual distortions. In this video, these distortions begin shortly before the first blackout and last until the video ends.Altogether, the only realistic cause for all of the anomalies that begin once the drone is close to the camera is a sensor/ISP pipeline reset triggered by either extreme brightness or a sudden increase in photons.

Tree Damage

When the drone flew vertically from ground level as it appeared to be positioned directly in front of me, its ascent began directly in front of the orange sign next to the crosswalk. On May 7, the date of this picture and 126 days after the attack, this tree is the only tree on the street struggling to grow leaves. This is a theorized biological effect of spacetime warping on plants.

East Coast & January 1

Matthew Livelsberger specifically instructed Sam not to release his message until January 1 and warned that China was ready to attack anywhere on the East Coast. You must ask yourself how Matthew accurately predicted the time and location of this Chinese attack despite having no connection to China. Given that he was a high-level military insider, among other things, it is clear that he had foreknowledge of China's plans. Later on the website, I will explain how and why Matthew knew his message could not be released until January 1.

Secret Service Response

In less than 72 hours, the same street was under 24/7 Secret Service surveillance for 60 hours straight

Not impossible per se, but here is something else highly unusual. Less than 72 hours later, a 60-hour-long secret service event was conducted on the neighboring street. This operation featured a government bus that had a perfect view of the entire street of the drone's travel for the entire event, a Secret Service IMSI catcher that explicitly targeted me, which I provide evidence of, and buses cycling the area every 3-5 minutes for 60 hours straight in multiple directions. Many buses also cycled in the opposite direction from the Jimmy Carter Center, despite there being no Jimmy Carter event-related purpose for this movement. This event also received very little promotion and was never busy except for the first hour of the event when FOX 5 Atlanta was present. I later provide evidence that I was selectively targeted by their IMSI catcher, expand on the unusual nature of this "Jimmy Carter" event, and give more evidence for its relation to the Chinese anti-gravity drone in the "Who Are We?/Who Protected Us?" section. Just like the drone video, all of this is publicly verifiable.

Verifying Metadata/Camera roll check

Can't fake this

Here is proof that this is an actual iPhone video, using a live iPhone screen recording of the original video file, messages from that night, emails I sent to Sam Shoemate that he posted to Twitter, a live IMEI check, a synced camera capture of my phone and computer, all overlayed over an OBS screen recording of my computer performing a metadata check to prove the authenticity of this video. You can't fake this. Use ExifTool, MediaInfo, exif.tools, or any other method to extract and verify the full metadata. Use HxD or any hex editor to validate the hex of the original video file, or Python to reconstruct the video from the hex data. Use any method you can possibly think of to confirm the video's authenticity; this is the most important step.

Why should I trust Matthew & your testimony?

Accept a Lifetime of Lies
  or      
Accept Two Testimonies

If you believe that I am lying about the drone's flight path, find another location in the area with a clear path and a flat reflective surface that is discreet enough to launch this drone from. You will find none. As you can see, when I started recording the drone in the sky, it was nearly invisible from my point of view. How could I have known its position if I were not alerted beforehand? I also would not have experienced the biological and conscious effects documented and described in the next section if I were not inside the drone's warp field. It is reasonable that speed would be a priority for the drone operators, since the risk of apprehension increases with every second their show of force continues. Ask yourself: why would the drone operator fly the drone back over the apartment if it did not originate from that general direction, especially considering that their car traveled into the apartment complex after it flew overhead? This situation is far too serious to lie about or even slightly exaggerate any minute detail. Later, I will also provide proof that the Chinese and U.S. governments are fully aware that I witnessed their most secret technology and recorded the only "UFO" video ever taken that proves the operational use of spacetime manipulation and the first video showing the effects of a warp field. You will also learn how Matthew was able to violate top-secret TS/SCI NDAs without immediate government intervention, and how I was able to release this video against their will, despite being an active cybercriminal at the time of China's drone incursion. After realizing the authenticity of our testimonies, you will be able to overcome a lifetime of manipulation and know the secret to obtaining limitless free energy for yourself. So ... keep reading.

Time Dilation

The conscious effect that undeniably proves what I witnessed was a gravitic propulsion drone is the altered time perception I experienced when the drone was directly in front of me and when it flew overhead. As you see in my text messages, I reported only seeing the drone for about 3 to 4 seconds before the video began. However, if you watch my flight path recreation, you will notice that the drone's flight was much longer than 3 to 4 seconds. Immediately after the encounter, I continuously thought that I observed the drone for 5 to 10 seconds at most before reaching for my phone to record the drone. It wasn't until weeks later that I finally realized that I witnessed the drone in operation near the intersection for much longer. This delayed error in time perception is due to the drone's time distortion and memory encoding errors caused by the drone's field. In actuality, before the video starts, I am 100% sure that I witnessed the drone for about 30 seconds. Along with the length of the video, the only reason I’m able to estimate an approximate length of the encounter is because the drone moved at a constant speed throughout its flight, and I vividly remember the majority of its movements.Immediately after ending the video, I looked outside to see if my alien assumption was wrong, and if anyone on the sidewalk or under the bridge was flying the drone. There was no one present, and no cars came down the street except for the tinted black car you see at the 9-second mark. During the entirety of the drone's flight, this was the only car that traveled on the street. After the drone left from my point of view and I angled the camera down, I vividly remember the black car traveling down the street around five seconds after I stopped recording the video. My perception of time was much slower than what actually occurred, as you can see the drone operators' car travelling down the street as the video is ending. As a result, I assumed that it was just a random car that barely missed an alien encounter. I didn’t realize that I filmed the car at the end of the video until a few weeks later. Before I even knew what time dilation was, I found it extremely strange once I realized that I filmed their car, as I remembered it driving down the street and turning right onto Auburn Pointe Dr. a few seconds after I stopped recording the video, and not immediately after. I vividly remember first looking to the right of the window to see if there was anyone who flew the drone, before looking to the left, the direction the car came from. I remember seeing the car about to turn after completing these head movements, which I recall finishing around 3-5 seconds after the video ended. I later learned this was another example of time dilation from the drone. No technology except for gravitic propulsion can cause this.

Double Thought

While I was observing the drone, I asked myself, "What exactly am I looking at?" A moment later, as I tried to understand what I was observing, an intrusive and overlapping thought suddenly emerged in my mind and said, "God." I paused in confusion for a second; I knew God did not look like a baby alien with two red lights, so I was confused about how this thought arose. What’s strange about this thought is that it overlapped with my current train of thought, causing me to think two different things at once.

Memory Gap

As I mentioned in the pre-recording flight path recap, there is one section of the encounter that I can not recall at all. I can not remember how the drone went from being positioned slightly below window level near the middle of the intersection to the right of me, to being positioned directly in front of me on the opposite sidewalk just a few inches above the ground. Initially, my memory of the drone's flight was also spotty, and I kept recalling the drone's flight movements in an incorrect order.

Warped Light Paths

Despite the drone appearing to be directly in the middle of my field of view during its vertical climb, my perception of the position of the light in front of me greatly differed from its actual positioning. When you observe the start of the video, you will notice that the graffiti I observed warping, which was directly behind the drone, is a few feet to the right of the window. At first, this seems like a clear contradiction in my testimony, as this graffiti being directly in front of my window would be impossible under normal circumstances. However, given that the drone warps light paths around it, it is perfectly feasible that this discrepancy would be present, especially considering that I was deliberately targeted by the drone operators during this portion of its flight. Along with this lateral discrepancy, during this movement, I have no recollection of the trees that are directly in front of the apartment window being present. The difference in what I witnessed and the actual positioning of the space in front of me can only be explained by the drone warping the path of light inside its field. This mirrors a well-documented effect of objects that produce gravitational lensing. This is the only period during the drone's entire flight in which I am aware that this phenomenon occurred.

Double Memory

As I was first describing the drone's exact flight to my friend, I mistakenly said that the drone was just a few inches in front of me when it was performing its vertical 90-degree movement as it was positioned in front of me. I told him that the drone was in front of the trees on our side of the street, rather than in its correct positioning in front of the trees across the street. When I tried to recall this 90-degree movement, an intrusive vision of the drone ascending just a few feet in front of me kept overriding my memory. Once again, this 90-degree climb happened immediately after the only moment during the event when my memory is completely blank. You could attribute this to being a normal PTSD response, as recalling PTSD triggers being closer than they were is a typical response, until you consider how I was overcome with only positive emotions and experienced no feelings of trauma, even as I was experiencing this warped recollection when I was describing the sighting to my friend. I suppose one could argue that this trauma was neurological rather than emotional. However, the multiple other abnormal cognitive effects surrounding this period of the drone's flight raise questions, especially when you consider that this drone movement was presumably unnecessary if there was not an unintended witness, as it extended the time of their mission. When I learned that this “alien” was actually a drone, I initially assumed that the operator repositioning the drone directly in front of me was somehow necessary for the drone's flight. But given these memory encoding abnormalities, I now know that the reasoning for this movement was far more sinister than just a drone readjustment and was a way to obstruct the memory and induce neurological effects on any unintended observer. Thinking that I was forming a bond with a baby alien when I was actually targeted by a Chinese anti-gravity weapon of mass destruction is pretty funny in my opinion.

Headache & Stomach Ache

The next day, I had a headache that developed in the afternoon and lasted the entire day. Throughout my life, I’ve had maybe only two headaches, leaving the only logical conclusion to be that I was experiencing a common side effect of exposure to radiation or a high-intensity electromagnetic field. I also took some Aleve that day and it was completely ineffective. That same day, I also developed a stomachache and diarrhea for the next few days (TMI, I’m sorry).

Skin Redness

For the first couple of days after the sighting, every time I scratched my skin, it would become noticeably red. I only remember this redness occurring on the upper part of my chest, although it might have been present when I scratched other parts of my body.

Watery Eyes

For the next few days, I noticed my pillow was unusually wet every time I woke up. I also had to scratch my eyes a lot as they were frequently itchy, and it felt like something was stuck in my eye and would not come out.

Increased Vivid Dreams

Since witnessing the drone, I’ve been having very vivid dreams, maybe 4 to 5 times a week, and often multiple times per night. Throughout my life, remembering a dream was rare. Typically, I’d only remember maybe one a month. Since the drone, it now also only takes me about 15 to 30 minutes after falling asleep to enter REM mode and start dreaming. Since the event, most of the dreams have unfortunately been nightmares. Increased vivid dreams are a common symptom once you quit smoking weed; however, during this time I was still smoking at the same rate as before the drone.

Constant Thoughts

For about the first week after the drone sighting, the drone was all I could think about. I spent almost every waking minute thinking about the drone and its implications. My roommate eventually went back to his girlfriend’s house after being subjected to nonstop, 5+ hour-long rants about what just happened. These thoughts were always positive, and I was never panicking or fearful. After the 60-hour-long Secret Service stingray across the street from me departed, I attempted to open my computer to resume my bank fraud operation. Every attempt failed as I couldn’t hold my focus for more than a few minutes. I could think about nothing except the drone, philosophy, theories about the universe, and what was currently happening inside both governments regarding the drone incursion. I even told my mother, “I think the drone took over my brain,” when she asked me to stop talking about the drone. Honestly, this hasn’t stopped, as this event is the only thing I focus on for 90% of the week, but it has definitely calmed down a lot. Once again, these thoughts are always positive, and I never panicked or felt uneasy despite the gravity of the situation. I was only slightly paranoid the night of the sighting, but once I did not get suicided the day after the attack, I understood that my life was likely not in immediate danger, and the slight paranoia vanished. The night of the attack, the excitement also far outweighed the paranoia, so I was mostly at peace.

Fatigue

I was noticeably more tired for the next week or so after the drone. I felt unusually sluggish for the entire week.

Delayed Effects

Visual Snow Syndrome

A few weeks after the event, I noticed tiny sparks of light in my vision. Initially, I believed that I was witnessing glimpses of other dimensions or something, but it turned out to just be visual snow syndrome. Additionally, when I look at a blue sky, I notice a bunch of dancing white floaters in my field of vision. I also see more frequent and more pronounced halos around light now.

Abdominal Pain

Around the time I noticed the visual snow syndrome, I started having instances of stomach pain and frequent foul-smelling farts. By foul-smelling, I mean like the stinkiest farts ever; they lingered for like 5 minutes too. This lasted for a little over a month. (TMI again, my bad, it’s for science).

Rapid Healing

At the beginning of March, my dog cut me a few times, and each cut healed within less than two hours and faded into light red spots. This happened on three separate occasions. This rapid healing response faded a few weeks later.

Fatigue Pt.2

Around the same time as the rapid healing, I noticed that I was, once again, considerably more tired throughout the day. Shortly after my first meal of the day, which is usually around 11 a.m., I was always extremely tired and had to take a nap. This stopped around July.

Skin Shedding

Around day 70, the skin on my hands started to peel as shown above. This occurred on both hands and was not painful. I do not have any skin conditions that could cause this. This lasted for about two weeks.

Bilateral Skin Lesions

On day 130, I developed hyperpigmentation and cracked skin on both wrists in line with my pinky fingers. I do not have eczema or any other skin condition that could cause this. As I type this on May 31st, the discoloration is still present, with my right hand (the hand I recorded the drone with) showing the highest amount of cracking and hyperpigmentation. The cracking will fade sometimes during the day, but it returns after every shower. It turns out that bilateral skin lesions are a documented symptom after UAP sightings. It is now June 25th, and the cracking is gone, but the hyperpigmentation is still present.

Your most important takeaway should be realizing that the operators knew exactly how to manipulate cognitive processes with this technology. How do you think they obtained that knowledge? But don't just take my word, read about it for yourself. Yet, remember that all self-incriminating government research will remain classified; for example, Matthew’s Proton email.