I definitely prefer NIP94, which is available since March on Amethyst. But here we are...

NIP 44 and subsequent work on encrypted messages represent a major improvement over NIP 04, but are not anywhere near on par with simplex, signal, or MLS. If you want real privacy (foward/future secrecy), use those instead.

I am trying to see if this is a bug or an issue in the server. Is it always nostr.build?

USB Debugging isn't necessary for installation. Follow the instructions on grapheneos.org/install/web ONLY do not use other guides independently.

Only developer option toggle required to be on is OEM Unlock.

Also keep in mind that the 4XL is End of Life:

More importantly, it had shareholders and advertisers.

Shout out to nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

I have been client hopping between #Snort #Primal and #noStrudel for so long - but the one client that hasn't failed me once has been #Amethyst. Rock solid, always working and just being so consistent. Small phone, foldable screen or tablet - it just keeps on working.

So good. ^^

unpopular opinion: a majority of feminists are not crazy misandrists that people make them out be.

feminism isn’t inherently misandrist or hateful at all, and is usually is a good thing.

I always laugh when people make fun of my English!

Try speaking Portuguese hahaha

Recieved a zap without a message or notification here.

Thankyou to whoever it was.

So the company I Fight for has just been bought by another company…anyone with merger experience have some suggestions?

What's a documentary you've enjoyed recently?

Sanctions against Russian people continue to ramp up, but I don't see the same treatment happening in the most recent invasion of a certain strip.

Seems... hypocritical.

MEMORY TAGGING (MTE) OUTLINE FOR GRAPHENEOS

GrapheneOS now has hardware memory tagging support in our Stable channel. Memory tagging greatly improves protection against targeted attacks. Thanks to hardware support on the Pixel 8 and Pixel 8 Pro, it's extremely low overhead despite the massive benefits it's able to provide.

GrapheneOS users on the Pixel 8 and Pixel 8 Pro can enable memory tagging via Settings ➔ Security ➔ More security settings ➔ Advanced memory protection beta on supported devices. We'll be enabling it by default soon since we have a solid approach to preserve app compatibility.

We integrated it into hardened_malloc where it's able to provide stronger security properties than the experimental stock OS implementation.

Our current toggle enables it for everything other than Vanadium, vendor executables and user installed apps bundling native libraries.

We'll be enabling memory tagging support for Vanadium by default via the standard Chromium implementation.

For the near future, we'll be leaving memory tagging disabled by default for user installed apps bundling native libraries to avoid introducing a new compatibility issues.

It will be possible to enable memory tagging for all user installed apps with the ability to opt-out for specific apps where it causes issues. We want to eventually have it globally enabled by default, but we expect it to uncover a lot of issues hardened_malloc hasn't before.

It's also possible to use MTE for protecting from stack buffer overflows and use-after-scope by aligning and tagging variables with an escaping pointer. LLVM has an implementation of this and we've confirmed it works but it may not be optimized enough to enable it quite yet.

When fully integrated into the compiler and each heap allocator, MTE enforces a form of memory safety. It detects memory corruption as it happens. 4 bit tags limit it to probabilistic detection for the general case, but deterministic guarantees are possible via reserving tags.

In hardened_malloc, we deterministically prevent sequential overflows by excluding adjacent tags. We exclude a tag reserved for free tag and the previous tag used for the previous allocation in the slot to help with use-after-free detection alongside FIFO and random quarantines.

MTE support for protecting the Linux kernel isn't enabled yet, but we can likely enable that by default too. However, it's currently part of kasan and is more oriented towards debugging than hardening. It's not entirely clear that enabling it in the current state is a good idea.

I like Bitcoin podcasts and I listen to a couple of them. But since I'm notoriously short on time between business and family life, what I can't do is listening to 10 minutes of intro, a lengthy introduction of everyone on and off camera, friendly farting around for another 10 minutes, then a situation analysis beginning in October 2008, a message from our sponsors, and only half an hour after I started listening I get to hear about THE THING. Nothing from about friendly farting but sometimes I only have 5 minutes and I really want to know about this cycling attack or what have you.

So here it is, merry Christmas:

A Bitcoin Podcast but each episode is maximum 5 minutes long including introduction and outro. Focused on one specific issue only, segmented in explanation, opinion, way forward, closing thoughts:

'Hello this is the 5m BTCNPDCST with [dude], it's about the thing that just happened, [dude], what's it about? Take it away' Sprinkle in some 'but why?', 'how?', and 'that's crazy', and voilá, we got ourselves a short and dense piece of infotainment. Aimed at half-wits like myself who know all the concepts and ideas but don't fully understand the technical issue in question just yet.

If this note receives more than 1 attention I go look for a good deal on a microphone and webcam and I do it 🤙