Mehow

720 posts

Mehow banner
Mehow

Mehow

@MehowHacks

CEO @Americanfort_io, Life hax0r, multi-patented inventor, husband, EMT, SAR, HAM, pilot, eng, river runner, maker, skier, guitarist, hunter and fitness fanatik

Jackson Hole, WY Katılım Ekim 2009
229 Takip Edilen1.5K Takipçiler
Mehow retweetledi
AmericanFortress
AmericanFortress@Americanfort_io·
Quantum computers will eventually be able to drain any wallet whose public key has been exposed on-chain. That's basically everyone. We just filed the patent to fix it and raised $8M to make sure it gets built. Quantum-resistant transaction signing, embedded directly into our Send-to-Name™ infrastructure, so every transaction is protected before the threat arrives, not after. AmericanFortress™ is the first naming and privacy layer to get here, and we're just getting started. Check out the news on @Investingcom below.
AmericanFortress tweet media
English
926
762
867
7.9K
Mehow retweetledi
AmericanFortress
AmericanFortress@Americanfort_io·
Your wallet address is a liability. Your FortressName is the fix.
AmericanFortress tweet media
English
609
378
472
7.3K
Mehow
Mehow@MehowHacks·
@almasjustine @Americanfort_io You’re right - our tech on the UTXO side can’t know your balances. On EVM side we use Infura and Infura can track your info although we don’t do it. At some point we’ll setup a cfilter version of Infura.
English
0
0
0
14
AmericanFortress
AmericanFortress@Americanfort_io·
The simplest explanation of AmericanFortress? Decentralized PayPal for all of crypto. @MehowHacks on what that actually means 👇
English
2.6K
1.3K
1.5K
15.6K
Nickel Web3
Nickel Web3@Wb3Amb·
@Americanfort_io @MehowHacks Watching @MehowHacks break it down, I'm thinking this is what mass adoption actually looks like. No more copying long strings or stressing about phishing, just smooth transfers that stay private by default.
English
1
0
1
22
Mehow retweetledi
AmericanFortress
AmericanFortress@Americanfort_io·
Sarge found you staring at etherscan at 3am and said "enough."
AmericanFortress tweet media
English
15
21
77
2.7K
Mehow retweetledi
AmericanFortress
AmericanFortress@Americanfort_io·
Those last 42-60 characters of your wallet address? They’re basically your crypto tattoo. Everyone sees it. Tracks it. Profiles it. Swap them for a FortressName.
AmericanFortress tweet media
English
14
24
44
2.9K
Mehow retweetledi
AmericanFortress
AmericanFortress@Americanfort_io·
Phishing does not begin with a fake link. It begins with visibility. If attackers can see your wallet, study your behavior, and map your counterparties, the setup already started. AmericanFortress reduces that exposure.
English
14
27
43
3.9K
Mehow retweetledi
AmericanFortress
AmericanFortress@Americanfort_io·
The trap doesn't look like a trap. It looks like a familiar address. It looks like your transaction history. It looks completely normal. Until it isn't.
AmericanFortress tweet media
English
17
24
49
3.8K
Mehow retweetledi
AmericanFortress
AmericanFortress@Americanfort_io·
Fort Knox for your on-chain life.
AmericanFortress tweet media
English
17
24
53
2K
Mehow retweetledi
AmericanFortress
AmericanFortress@Americanfort_io·
Have you found the missing piece to your on-chain privacy?
AmericanFortress tweet media
English
19
31
100
3.8K
Mehow retweetledi
AmericanFortress
AmericanFortress@Americanfort_io·
The dark side isn't crypto. It's transparency without protection. The light? Stealth addresses, verified senders, private receipts.
AmericanFortress tweet media
English
47
51
109
3.5K
Mehow retweetledi
AmericanFortress
AmericanFortress@Americanfort_io·
Top of the hourglass: exposed balances, tracked transactions, zero privacy. Bottom: one verified, private payment. Clean.
AmericanFortress tweet media
English
10K
5.2K
5K
84.8K
Mehow retweetledi
AmericanFortress
AmericanFortress@Americanfort_io·
The best privacy is the kind you don't notice. Type a name. Hit send. It just happens. @MehowHacks breaks down how we built that 👇
English
1.5K
1.1K
1.3K
14.6K
Mehow
Mehow@MehowHacks·
SOP is to look anyway if you’re cleared to cross a runway. But when truck was cleared the aircraft was on short final still a mile away - so unclear if it was visible and unobstructed from the ground. The pilots didn’t observe the truck clearance and no one saw each other to mitigate the tower mistake.
English
0
0
0
20
hbengineer
hbengineer@HB3ngineer·
@MehowHacks Does the truck driver have eyes that can look right to see a large aircraft approaching?
English
1
0
0
31
Mehow
Mehow@MehowHacks·
You're not listening to enough of the audio—it's a single human ATC error, barring any wild new data. The same controller clears the firetruck straight at JZA646. Get the AI ATC systems in there because they would have caught this. It's like the controller forgot he had another plane coming in after the Southwest that he himself cleared. Here is all the relevant Tower audio that's not omitting the entire error. The tower controller clears JZA646 to land on runway 4 at 21:35:04 (that's 25 seconds into the attached audio). A Southwest plane, SWA3988, lands on 4, and shortly thereafter—at 21:37:02 (nearly 2 minutes later from the initial clearance to land for the Air Canada)—the SAME controller clears the truck onto the same runway that the JZA646 pilots, who are unknowingly in the last 20 seconds of their lives, are landing on. Within seconds he realizes his mistake ("stop, stop"), but it's too late. Horrible loss of life from a single human ATC error. This, however, is not a coordination error, not a problem between Ground and Tower, and not some systemic problem—unless these guys are just overworked—EXCEPT that there's no tech in place to fix this. As a pilot, I hate seeing a situation where ATC kills pilots and passengers. Whether you're a ground vehicle or a plane crossing an active runway, you're always talking to Tower (the aircraft has right of way). In this case, the same controller at Tower. And that controller put the aircraft and the firetruck on the same runway at the exact same time. He sounds pretty relaxed until he realizes his mistake. My only other comment is that it would have been a miracle if the pilots had heard the truck clearance and initiated a go-around themselves. As a pilot, once you get clearance to land, you're so focused on landing that you're not really paying attention to Tower anymore unless they call you directly. The pilots are still listening on Tower frequency and can hear everything Tower is saying, but sadly they didn't notice the controller's mistake—and they lost their lives. More excepted would be the truck crew checking whats coming in on final but that didn't happen either. @elonmusk and @xai Please get the better software in there ASAP. My heart goes out to the crew, the families of the pilots, the passengers, and the controller. I hope everyone in the hospital makes it. Bottom line a chat bot can trivially catch this mistake - let's get the tech in there.
English
4
2
12
3.6K
Mehow
Mehow@MehowHacks·
@chamath yup, single human error ... SAME controller cleared the truck and the plane into the exact same spot. x.com/MehowHacks/sta…
Mehow@MehowHacks

You're not listening to enough of the audio—it's a single human ATC error, barring any wild new data. The same controller clears the firetruck straight at JZA646. Get the AI ATC systems in there because they would have caught this. It's like the controller forgot he had another plane coming in after the Southwest that he himself cleared. Here is all the relevant Tower audio that's not omitting the entire error. The tower controller clears JZA646 to land on runway 4 at 21:35:04 (that's 25 seconds into the attached audio). A Southwest plane, SWA3988, lands on 4, and shortly thereafter—at 21:37:02 (nearly 2 minutes later from the initial clearance to land for the Air Canada)—the SAME controller clears the truck onto the same runway that the JZA646 pilots, who are unknowingly in the last 20 seconds of their lives, are landing on. Within seconds he realizes his mistake ("stop, stop"), but it's too late. Horrible loss of life from a single human ATC error. This, however, is not a coordination error, not a problem between Ground and Tower, and not some systemic problem—unless these guys are just overworked—EXCEPT that there's no tech in place to fix this. As a pilot, I hate seeing a situation where ATC kills pilots and passengers. Whether you're a ground vehicle or a plane crossing an active runway, you're always talking to Tower (the aircraft has right of way). In this case, the same controller at Tower. And that controller put the aircraft and the firetruck on the same runway at the exact same time. He sounds pretty relaxed until he realizes his mistake. My only other comment is that it would have been a miracle if the pilots had heard the truck clearance and initiated a go-around themselves. As a pilot, once you get clearance to land, you're so focused on landing that you're not really paying attention to Tower anymore unless they call you directly. The pilots are still listening on Tower frequency and can hear everything Tower is saying, but sadly they didn't notice the controller's mistake—and they lost their lives. More excepted would be the truck crew checking whats coming in on final but that didn't happen either. @elonmusk and @xai Please get the better software in there ASAP. My heart goes out to the crew, the families of the pilots, the passengers, and the controller. I hope everyone in the hospital makes it. Bottom line a chat bot can trivially catch this mistake - let's get the tech in there.

English
0
0
9
1.8K
Mehow
Mehow@MehowHacks·
@OnDisasters same Tower controller cleared the jet and the firetruck ... :( x.com/MehowHacks/sta…
Mehow@MehowHacks

You're not listening to enough of the audio—it's a single human ATC error, barring any wild new data. The same controller clears the firetruck straight at JZA646. Get the AI ATC systems in there because they would have caught this. It's like the controller forgot he had another plane coming in after the Southwest that he himself cleared. Here is all the relevant Tower audio that's not omitting the entire error. The tower controller clears JZA646 to land on runway 4 at 21:35:04 (that's 25 seconds into the attached audio). A Southwest plane, SWA3988, lands on 4, and shortly thereafter—at 21:37:02 (nearly 2 minutes later from the initial clearance to land for the Air Canada)—the SAME controller clears the truck onto the same runway that the JZA646 pilots, who are unknowingly in the last 20 seconds of their lives, are landing on. Within seconds he realizes his mistake ("stop, stop"), but it's too late. Horrible loss of life from a single human ATC error. This, however, is not a coordination error, not a problem between Ground and Tower, and not some systemic problem—unless these guys are just overworked—EXCEPT that there's no tech in place to fix this. As a pilot, I hate seeing a situation where ATC kills pilots and passengers. Whether you're a ground vehicle or a plane crossing an active runway, you're always talking to Tower (the aircraft has right of way). In this case, the same controller at Tower. And that controller put the aircraft and the firetruck on the same runway at the exact same time. He sounds pretty relaxed until he realizes his mistake. My only other comment is that it would have been a miracle if the pilots had heard the truck clearance and initiated a go-around themselves. As a pilot, once you get clearance to land, you're so focused on landing that you're not really paying attention to Tower anymore unless they call you directly. The pilots are still listening on Tower frequency and can hear everything Tower is saying, but sadly they didn't notice the controller's mistake—and they lost their lives. More excepted would be the truck crew checking whats coming in on final but that didn't happen either. @elonmusk and @xai Please get the better software in there ASAP. My heart goes out to the crew, the families of the pilots, the passengers, and the controller. I hope everyone in the hospital makes it. Bottom line a chat bot can trivially catch this mistake - let's get the tech in there.

English
0
0
0
869
Francisco Cunha
Francisco Cunha@OnDisasters·
Roundup of the collision in La Guardia: Yesterday, a CRJ-900 collided with a fire truck at LaGuardia Airport (NY). Two dead (both crew of the CRJ) – 41 wounded (39 on jet, the two aboard the truck). The aircraft was at 114 knots when it hit the vehicle (according to preliminary data). The fire truck was crossing Runway 04 to reach Taxiway D. The controller at the time – important note, working both ground and tower - cleared the truck to cross runway 04, but then told the truck to “stop” * multiple times as the CRJ was on the runway. [ * This hints he likely realized something was wrong, but for some reason – which I´m sure investigators will look at it soon – the collision could not be avoided. In some of the recordings you can even hear the controller say “I messed up” ] According to AV Herald, after impact - “The aircraft skidded onto high speed turn off F/turn off E, about 430 feet further down the runway, before coming to a stop on turn off E. The fire truck at crossed the runway to attend a Boeing 737 MAX 8 that reported a sickening odor following two aborted takeoffs from runway 13. The CRJ-900 [Registration C-GNJZ] was operating Air Canada Express Flight AC8646, inbound from Monteal. (Even though the jet had Air Canada colors, it was operated by Jazz Aviation LP, as usual in this type of “regional ops”) Latest updates reports, that besides the two fatalities confirmed earlier there are 11 serious injuries (the 2 aboard the truck and 9 on the jet) and 32 pax with minor injuries. There were a total of 76 aboard the aircraft. Airport is closed and NTSB has opened an inquiry Other data – at local time, collision occurred on Sunday, March 22, local time 23h37) Some sources label the truck as ARFF Truck – ARFF stands for Airport Rescue and Fire Fighting Service Info – ASN / AV Herald Video – Flightradar 24
English
2
7
57
45.4K
Mehow retweetledi
Jsquare
Jsquare@JSquare_co·
Catch the highlights from @StanfordSBA’s BASS event during #ETHDenver! 🏔️ Our Partner @DinghanL had the honor of moderating an insightful panel with @MehowHacks (@Americanfort_io), @P3b7_ (@Ledger), and @segall_max (@privy_io). as they navigate: 🔹The evolution of fundamental security fixes & UX pain points. 🔹Architecting wallet infrastructure for the Agentic AI era. 🔹The tension between seamless convenience and crypto-native control. From legacy threat models to the future of autonomous agents—watch how we’re defining the next frontier of Web3. Full video🎥 youtube.com/watch?v=2btTir…
YouTube video
YouTube
English
31
4
6
9.3K