v0.8.0-alpha48 rolled out to alpha testers.

This build features:

- LND v0.17.0-beta.rc6

Numerous fixes including some P2P networking and Taproot related patches

- LND: ability to add custom preimages to invoices

Initial support for Zaplocker

I wonder if alby & wos are really one in the same?

That's why I always withdraw to self custody whenever I can. Phoenix wallet good

can we have a day each month, where everybody only focuses on promoting nostr on other platforms and getting people on here and helping them get onboarded?

#joinathon

So I have 3K to put into Bitcoin but I'm wondering if I should just DCA into it or lump sum into it ?

Seen people saying it already.

That’s why I said it.

I wouldn’t exactly consider #nostr a #bitcoin L3.

It’s not built on #lightning & it doesn’t use the blockchain.

It uses lightning.

Saves nothing on chain.

ANDROID 14 SITUATIONAL UPDATE:

Stable release of Android 14 is expected to be released in early October. We've spent months preparing for it and we've completed a lot of porting in advance. This has been much more difficult than it should be since we have to rely on unofficial access to pre-launch sources.

Stable releases of Android are open source. Pixel stock OS source tree matches the AOSP source tree with additional private repositories added for the Google/Pixel components/overlays. Beta releases and the development branches are mostly internal. Most isn't done in AOSP main.

The Android security team wanted to collaborate with us and gave us security partner access. We hoped this would lead to us getting full partner access so that we could port to new major releases much earlier with the ability to build and test nearly all of the port in advance.

The engineering side appreciates our work and multiple prominent people have tried to get full partner access for the GrapheneOS Foundation. Android's business side had our security partner access revoked and blocked progress. We've decided to stop making upstream contributions.

Many of the privacy and security features we're built could be included in Android. It was always difficult to contribute without partner access, but we put in significant effort and achieved some positive results. We also reported a lot of firmware and software vulnerabilities.

Not having partner access makes quickly porting to major releases into an ordeal, but we still have to do it for security reasons. We only managed to have it done within around a week of launch of Android 13 and past releases via superhuman amounts of work hours and productivity.

Our policy for upstream Android vulnerabilities we discover has become fixing them downstream ASAP with a clear explanation in our release notes for the release including them. Filing a report upstream hasn't been part of our process for a while due to their related decisions.

We've deferred shipping most of our newly developed features until after Android 14 including duress PIN/password and several new per-app toggles for enabling additional security features we already had implemented but couldn't enable globally due to some apps being incompatible.

What does that even mean "toxic"? Such a idiotic buzz-word; Anybody who doesn't like something, may call it "toxic". Isn't that just normal conversations? Exchange of opinions?

🚨 BREAKING: The US government has less than two days to prevent a shutdown.

Addiction is clearly possible without algorithms, but this one feels nice because it’s things you want to read about - Like reading a good book is addictive.

Twitter became addictive in the same way candy is addictive. It’s not healthy, but you keep grabbing more.

nostr clients are way stickier than I expected