As if tetraethyl lead in gasoline wasn't bad enough, they also added ethylene dichloride and/or ethylene dibromide, which acted as a lead scavengers, preventing deposits of insoluble lead (II) oxide from forming and clogging up engines/exhaust equipment. Instead, water-soluble-at-high-temperatures lead (II) chloride and lead (II) chloride were blasted out the tailpipes of vehicles using tetraethyl lead. These are mildly soluble at ambient temperatures, allowing the lead to permeate even further than it otherwise would have.
Getting a capture card that supports VGA is another possibility. Or don't and just say you did. Is there realistically any way to know whether a video was screen-recorded or if it was downloaded?
I assume if you download the stream directly it could be shown that your copy and youtubes copy are identical, since encoding a video and compressing it is different every time.
In spite of its issues, it seems like Monero is the only mainstream cryptocurrency that actually still lives up to the ethos of what Satoshi had in mind.
The built-in terminal app seems to be similarly flaky on my Pixel 8. Also, the kernel it boots into is really stripped down, and it lacks a ton of essential features. I was not able to install VirtualHere client to pass through USB devices, and there's no built-in functionality. There's also no way to open it full-screen on the Pixel 8's DP-over-USB-C desktop mode. Hopefully it continues to improve, but it seems like Google is more into extracting value than they are improving their products at this point.
Another example, this one deliriant and not psychedelic, is atropine/scopolamine, found in certain nightshades, such as deadly nightshade, mandrake, plants in the Datura genus, and trees in the Brugmansia genus. The chemical weapon QNB, also called BZ is another example of a long-acting deliriant.
As far as classic psychedelics go, I've read mescaline (3,4,5-trimethoxyphenethylamine) lasts really long.
My experiences with mescaline are that it has mostly wound down by 6-8 hours though I can tell that I am slightly "off" for a few hours after that. Shorter timeframe than LSD, though not by a whole lot.
I tried it during the summer between 8th and 9th grade after discovering a Datura Stramonium plant growing at a beach on Cape Cod. Fortunately the plant was growing in sand, and the alkaloid content of the plant was very low. I boiled an entire pod down in a soda can and gave it a try. In terms of effects, I did not become delirious, but my perception of gravity was greatly enhanced; I felt like I weighed 600lb. My eyes were also completely incapable of focusing on anything close-up for several days. I never tried Datura again, and I never will. I was lucky I didn't wind up dead, in jail, or in the hospital.
I kind of doubt this, as the rapidly changing nature of mobile IP addresses would mean that a periodic outbound connection would still be necessary to keep the attack up-to-date on the compromised devices current IP address. At that point, you may as well have the compromised device periodically poll an attacker-controlled server for instructions rather than jump through a bunch of hoops by getting things to work over inbound connections.
In the case of T-Mobile, unsolicited inbound IPv6 connections are blocked, but direct P2P is still possible. I successfully established a WireGuard tunnel over IPv6 between 2 phones. With IPv6, since the internal addresses and ports and the same end-to-end, all that is needed is a dynamic DNS service; STUN isn't necessary. I did need to set a persistent keepalive of 25 seconds on both sides of the tunnel to keep the firewall holes open.
Interestingly, Verizon Wireless blocks connections to other Verizon Wireless IPv6 addresses. T-Mobile-to-T-Mobile connections work, Verizon-to-T-Mobile connections work, but Verizon-to-Verizon connections do not work. Given the way Verizon's network has stagnated while T-Mobile's network has been rapidly improving, it may be time to move away from Verizon.
Slightly off-topic, but if you have a modern Google Pixel phone, Google includes "free" VPN service (which probably collects/sells your data). This service uses Endpoint-Independent filtering, so if you send an outbound packet with the source port you want to map, regardless of the destination IP/port, you can effectively receive unsolicited inbound connections from any host on the internet that contacts your IP:port, so long as you send a periodic keepalive packet from the source port you are using to anywhere.
This is how researchers were able to remotely hack several Chrysler models. They used a Sprint hotspot to get an IP on the cell network and were able to connect to any other Sprint device. The cellular modems on these cars were on Sprint so they just had to be on the same network. I wonder if Verizon intentionally blocks this.
All the Linux routers I've used utilize Endpoint-Independent mapping with Address- and Port-Dependent _filtering_.
This means you can still establish direct P2P connectivity behind a Linux-based NAT device with users behind other Linux-based NAT devices. The only time it becomes an issue is when attempting to communicate with users behind NAT devices that do Address-Dependent _mapping_ or Address and Port-Dependent _mapping_. Some *BSD-based NAT implementations are this way.
Endpoint-independent _filtering_ is only a good idea for CGNAT implementations. Having an EIM/EIF NAT/firewall setup without additional firewalling makes it possible and easy for devices to run public-facing UDP-based servers without anyone's knowledge. With EIM/EIF, once you create a NAT mapping, so long as you send out periodic keepalives, _any_ IP address with _any_ source port can make unsolicited connections to a server that the NAT mapping points to. The best compromise is Endpoint-independent mapping with Address- (but not port-) dependent filtering.
This is true, but the beauty of UDP is that it's basically just a raw socket with a tiny 8 byte header slapped on top, with 2 bytes for source port, 2 bytes for destination port, 2 bytes for length, and 2 bytes for a checksum.
You could slap a UDP header on top of the TCP header and get the benefits of TCP with the hole-punching capabilities of UDP, provided you implemented some kind of keep-alive functionality and an out-of-band way of telling the "server" to establish an outbound connection with the "client". Or use QUIC, assuming it fits the use case.
reply