If you don't name the ideology that led to this (without qualifiers), you are dishonouring every single individual who died on that day. Be courageous. Fight those who wish to enslave us.

To understand a Marine you must know: We left home as teenagers or in our early twenties for an unknown adventure. We loved our country enough to defend it and protect it with our own lives. We said goodbye to friends and family and everything we knew. We learned the basics and then we scattered in the wind to the far corners of the Earth. We found new friends and a new family. We became brothers and sisters regardless of color, race, or creed. We had plenty of good times, and plenty of bad times. We didn’t get enough sleep. We smoked and drank too much. We picked up both good and bad habits. We worked hard and played harder. We didn’t earn a great wage. We experienced the happiness of mail call and the sadness of missing important events. We didn’t know when, or even if, we were ever going to see home again. We grew up fast, and yet somehow, we never grew up at all. We fought for our freedom, as well as the freedom of others. Some of us saw actual combat, and some of us didn’t. Some of us saw the world, and some of us didn’t. Some of us dealt with physical warfare, most of us dealt with psychological warfare. We have seen and experienced and dealt with things that we can’t fully describe or explain, as not all of our sacrifices were physical. We participated in time-honored ceremonies and rituals with each other, strengthening our bonds and camaraderie. We counted on each other to get our job done and sometimes to survive it at all. We have dealt with victory and tragedy. We have celebrated and mourned. We lost a few along the way. When our adventure was over, some of us went back home, some of us started somewhere new and some of us never came home at all. We have told amazing and hilarious stories of our exploits and adventures. We share an unspoken bond with each other, that most people don’t experience, and few will understand. We speak highly of our own branch of service and poke fun at the other branches. We know, however, that, if needed, we will be there for our brothers and sisters and stand together as one, in a heartbeat. Being a Marine is something that had to be earned, and it can never be taken away. It has no monetary value, but at the same time, it is a priceless gift. People see a Marine and they thank them for their service. When we see each other, we give that little upwards head nod, or a slight smile, knowing that we have shared and experienced things that most people have not. So, from myself to the rest of the Marines out there, I commend and thank you for all that you have done and sacrificed for your country. Try to remember the good times and make peace with the bad times. Share your stories. But most importantly, stand tall and proud, for you have earned the right to be called a Marine. I’m a Marine - Damn Proud!

I'm a good friend of @4nt1p4tt3rn . Very close. Help me find frens? @Brushbeater et al.

Good evening gentlemen! [🚨 GIVEAWAY} Say hello to our DVLP Sweepstakes #5, a premium, custom-built EDC/Lapel Pin tray from our DVLP brother over at @HeritageUSAWood ! (You can follow the story of it's creation from scratch on his profile!) This piece (valued at close to $300) is a tropical hardwood, sourced from Florida known as Monkey Pod. Finished with food safe beeswax and mineral oil, it measures 17 1/4" x 11 3/4" x 2 1/4", with two stackable lapel pin EVA foam boards 9" x 9", perfect for storing and displaying your favorite based gems from DVLP. Entry this week is simple: 1) Like this post 2) Quote/share this post and tag @TheAimAndAuthor & @HeritageUSAWood 3) Follow @HeritageUSAWood We'll take entries up until 11:59pm CST this Saturday and announce the winner on Monday morning! (Pew pew not included...this time). 🫡 LET'S GO! #DeusVult

IQ of 146 I'm far from retarded trust me. I know more about weapons safety than you your mama your daddy and all the other retards in your family. Trust me when I say I am way hella smarter than you are.

All the lictor fans tonight trying to get that bank bag.

That has to be the funniest s*** I read all day as if military intelligence wasn't an oxymoron you may want to look that word up. And when it comes to balls b**** I work in neighborhoods you would never set foot in alone and I don't fear little jarheads like you you're too f****** stupid to ever win a fight I'm stronger tougher and smarter than you dumb f**** and I have more integrity because I won't kill innocent people for pedophiles keep reaching. Also not gay and I don't eat hot pockets

This proposal wouldn't hide that a wipe occurred and would help adversaries exploit and recover data from the device. It isn't a new idea and people have proposed variations of this hundreds of time for years. These proposals wouldn't hold up against widely available forensic software. Giving an attacker access to a decoy profile would make it far easier for them to exploit the device. Without a shut down or reboot, a device was previously in After First Unlock state would be very vulnerable to having data extracted. GrapheneOS has strong protection against data extraction without depending on a duress PIN/password. The default enabled protections combined with a strong passphrase and 2nd factor fingerprint PIN would have provided fantastic protection for the data on the device. Reducing the device auto-reboot timer would be even better. The secure element would have protected the data with only a random 6 digit PIN instead of a passphrase in practice too. All of our features are designed to work against adversaries aware of GrapheneOS. Our duress PIN/password is no different. Adversaries aware of GrapheneOS face a dilemma about whether a PIN/password provided by the user is going to unlock the device or wipe it. It wasn't designed around being a secret resulting in an unpleasant surprise for an adversary. We also plan to provide it as part of secure element rate limiting on future devices built to run GrapheneOS to prevent bypassing it with an OS exploit. Triggering our duress PIN/password feature wipes both hardware keystores, the secure element as a whole and disk encryption metadata. Each of these 3 steps is enough on their own to reliably wipe material needed to obtain the key encryption keys for disk encryption. It happens nearly instantly and it wouldn't be secure if it took a bunch of time or depended on actually erasing any of the encrypted data. Shutting down the device triggers clearing sensitive data from RAM and registers to complete the process. It's necessary to clear a lot of sensitive data from memory and registers including decrypted encryption keys in TEE memory. Giving an adversary access to a profile on the device instead of shutting down or rebooting would be very problematic. It would give them an immense amount of attack surface for exploiting the device to recover sensitive user data. If the Owner user is in After First Unlock state, the adversary has given massive attack surface for exploiting the device to obtain all of the data from the main user. It would be the extreme opposite of the attack surface reduction and exploit protections provided by GrapheneOS. GrapheneOS and apps running on it could continue to function indefinitely after the key derivation material is wiped. It already has disk encryption keys loaded into Trusted Execution Environment memory and is using those for inline disk encryption via wrapped keys. Only functionality depending on hardware keys would be broken. If there were profiles in After First Unlock state those would still be available. An attacker exploiting the device would recover the same data as before wiping the key encryption keys. Forensic data extraction companies have access to GrapheneOS and we don't have access to their software. We cannot rely on security through obscurity or knowing how their software works including which vulnerabilities they exploit. Fooling widely available forensic software into believing a decoy profile is the Owner user isn't feasible. It would need to provide a fully functional Android Debug Bridge (ADB) environment which is completely impractical. People should consider the fact that they likely haven't thought about this nearly as much as us. There are good reasons for why we designed this feature the way we did and it's working as intended in the real world. The feature becoming widely known about is a requirement for it to work as intended by creating a dilemma for adversaries. The main thing we need now is secure element support for it which we can get implemented for future devices as part of our Motorola Mobility partnership and future OEM partnerships.