16
invisibull
16b1dcd2d87fa08c0fc5b1a431dd16fdece4c293ab8b31703a566550bfd25f2a

I LOVE it.

Do you have some tickets open for grabs or need any help with it?

Nothing if you (1) can and (2) want to use it. I merely suggested an alternative path.

The reply from grimoire took some effort, btw. Typing this from Amethyst now.

But I think, once I get used to it, it might be my secret pleasure client. Love how nerdy it is.

There is no second best.

Also 🖕to Saylor :D

nostr:nprofile1qqs0agvxc2jx0rdugdmsfmkjzcyyd698s8jlk9c9d6dmxvuyp4daauspz9mhxue69uhkummnw3ezumrpdejz7qgmwaehxw309a6xsetxdaex2um59ehx7um5wgcjucm0d5hsxx5cc2 I don't see an issue with it because they clearly display SHA256.

Let's take Bitwarden latest release for example. This is a sha for the apk from their GitHub repo (copy/paste)

sha256:fc8c8124650665270925648e0ec35bf7336f26058e3bd72eabf41d859727d220

You will see this same sha displayed in zapstore. Makes no huge difference who signs the release if keys match.

Replying to Avatar Ava

RIP #Obtanium on "certified Android devices."

"Non-certified OSes, like GrapheneOS, should be unaffected by this for as long as they are allowed to continue to exist."

Freedom tech exists on iOS—after developers KYC themselves, even where Apple now allows sideloading under its rules. Android matters because it's open source and allows sideloading without Google's permission. That's why Nostr apps, FOSS tools, and freedom tech took root here.

#GrapheneOS works because it preserves that ecosystem without breaking continuity. But now Google's forcing developer KYC for the Play Store on certified devices. The choice becomes: KYC to Google or start over.

This is what breaks mobile in a way desktop never broke. On Linux, you can run open-source and closed-source software on the same primary system. On mobile, once the app ecosystem is gated, custom AOSP ROMs don’t get that role.

The result is a split by design. As I predicted—for the foreseeable future—stock Android becomes the primary device for most. Privacy ROMs get relegated to secondary use, not because of capability—but because of access.

For those whose threat model demands it, privacy ROMs remain the primary device. For everyone else, they become secondary—appealing to those willing to sacrifice convenience for privacy and security, but not the masses.

Obtainium dying on stock Android is the warning. After this, the rest is just enforcement.

The catch now, however, is that with custom ROMs you’re rebuilding the entire app ecosystem from scratch.

On Linux, you can still install closed-source software. On mobile, once you step outside the Google/Apple ecosystem, you’re not just losing a store—you’re losing the distribution, licensing, and services stack a lot of the apps people actually use are built around.

That’s Linux on mobile, but without an easy way to carry over the apps people already paid for, depend on for productivity, and use every day.

That’s the challenge in front of us right now.

https://keepandroidopen.org/

#IKITAO

"There is no spoon"

I was able to set up a new GrapheneOS for a family member without ever touching droidify or obtanium.

First step, download nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgpz9mhxue69uhkummnw3ezuamfdejj7rn7acz APK directly from their github repo (use Vanadium for this).

Once zapstore is installed you literally never ever have the need for Obtanium again.

As I understand, you have to bebin Poland. Most likely you need to already be a user of that BLIK system, etc.

I think this is why nostr:nprofile1qqst0mtgkp3du662ztj3l4fgts0purksu5fgek5n4vgmg9gt2hkn9lqppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qythwumn8ghj7un9d3shjtnp0faxzmt09ehx2ap06fen87 was asking if anyone's building a global solution.

Use what exactly? I haven't used either BLIK or satispay.

I was referring to the idea of applying this principle to the local p2p solutions cathing on.

Replying to Avatar TKay

nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg

How can create a feed of the pubkeys I follow?

There are "Follow Lists" on Amethyst that achieve exactly this.

I was surprised to learn about BLIK in Poland. So I was chatting with our robot friends to learn if there are similar p2p systems in outher EU countries. If we could replicate what Poles did, this would be HUGE. Here's a full list:

| Country | Payment system |

|---|---|

| Austria | Express-Transfer (bank instant services), MeinElba (bank apps) |

| Belgium | Bancontact Mobile, Payconiq by Bancontact |

| Bulgaria | Local bank mobile apps (instant), ePay (card services) |

| Croatia | m-Transfer (bank apps) |

| Cyprus | Local bank mobile apps (instant transfers) |

| Czech Republic | Instant bank transfers via bank apps |

| Denmark | MobilePay |

| Estonia | Bank apps / Mobile-ID instant transfers |

| Finland | Siirto (now integrated into bank apps) |

| France | Paylib, Lydia (fintech P2P), bank app instant transfers |

| Germany | giropay, Kwitt (Sparkassen), SEPA Instant via banks |

| Greece | Bank mobile apps (instant), Viva Wallet P2P |

| Hungary | Bank app instant transfers, fintech apps |

| Iceland | Bank app instant transfers |

| Ireland | Bank app instant transfers, Revolut and fintechs |

| Italy | Bancomat Pay, Satispay, MyBank, bank app instant transfers |

| Latvia | Bank app instant transfers |

| Lithuania | Paysera, bank app instant transfers |

| Luxembourg | Bank app instant transfers |

| Malta | Bank app instant transfers, fintech apps |

| Netherlands | iDEAL (e‑commerce), Tikkie (ABN AMRO P2P) |

| Norway | Vipps |

| Poland | BLIK |

| Portugal | MB WAY |

| Romania | Bank app instant transfers, fintechs (e.g., Revolut) |

| Slovenia | FLIK |

| Slovakia | Bank app instant transfers (e.g., Tatra banka) |

| Spain | Bizum |

| Sweden | Swish |

| Switzerland | TWINT |

| United Kingdom | Faster Payments (bank-backed), bank app P2P (Monzo, Revolut) |

"Notes: This list emphasizes nationally used P2P/payment schemes or widely adopted bank-backed instant transfer services in European countries; coverage and features vary (QR, phone-number transfers, one-time codes, ATM withdrawal)."

Thank you for the service you're providing to lovely people of Thailand. The idea is so clever. It should be replicated wherever possible.

Just want to share my observation around the UX when setting up ecash/LN wallets for a Nostr profile.

Unless I was doing something wrong, nostr:nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0wfjkccte9ekkjmnfvf5hguewvdshx6p0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0wsvavr wins when it comes to ease of setup compared to nostr:nprofile1qqs0y3tvskgs9gpgxxu5ahgz3fmms3rzmxt504qceqtz4a6pdgfwlkgppemhxue69uhkummn9ekx7mp0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uq3qamnwvaz7tmwdaehgu3wd4hk6tcm38aw4

The main differentiator was the ability to create a wallet that gets assigned some random "minibits.cash" address that you can immediately use as your nostr LN address.

On the other hand, cashu.me generates npub/nsec together with the wallet (basically ties them together) when you "enable LN address". There is an option to bring your own nsec with a clear warning that it's not recommended and it's dangerous.

Another thing is that minibits has a proper app while cashu is PWA.

Cashu provides a plethora of advanced options, though. I am sure both are great options but minibits seems a bit more user friendly.

Did I miss anything during the setup? Trying to move past the noob phase.

Isn't it crazy that they are not on Nostr?

Honestly, not even sure what the UX would be like but initiatives like this one should feel at home here.

Can someone help a boomer make sense of the follow lists at Amethyst?

There are some profiles that I'd like to keep around primarily as bookmarks but do not really care seeing their posts in my feed. A good example is nostr:nprofile1qqs0nm9kjzthrt64j2vy6n4ll9yr374raf3jm0akqpfktg7szftwvygpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctcukcy7t that I just learned about from nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgkwaehxw309a5xjum59ehx7um5wghxcctwvshszrnhwden5te0dehhxtnvdakz7qrxnfk

Is this what those lists are for?

#asknostr

Replying to Avatar calle

You simply don't know how good PlebQR is. I've been basically living on Bitcoin for the past couple of weeks and purchasing food, drinks, clothes, tickets with the sats I earn by shitposting on Nostr.

PlebQR is an unstoppable peer-to-peer Bitcoin to fiat on and off-ramp. Every Bitcoiner deserves to have this. Read on and maybe it'll inspire you to create something similar for your region too.

In Thailand, like in many other places in the world, especially in Asia, the most common digital payment methods aren't credit cards, they're QR codes. All sorts of QR codes from many different fiat payment providers. Shitty ones, good ones, it doesn't matter. As long as it's a QR code, it'll work for us.

Here's where PlebQR comes in. PlebQR is what I would call a Let-me-pay-for-you app. It matches you, the person who wants to pay for a drink with Bitcoin, with a random stranger on the internet who wants your Bitcoin and pay your fiat QR bill in return!

The UX is straightforward: You scan the QR code at the store, pay a Lightning invoice, and wait for the payment. No sign up needed and with incredible privacy.

It works best when you're not in a hurry and when there isn't a line of people waiting behind you. Those cases are surprisingly common, think restaurant bill, or at the flea market. Right now, it usually takes a minute or two for the payment to clear but it'll get faster as more people use it.

The best part though isn't that it just enables Bitcoin payments for basically everything and everywhere. It's that it represents a different, more natural form of decentralized trading that can't be stopped, and that isn't about buying and selling Bitcoin, but about spending it.

I wish you could try it out some time.

Pure magic Internet money ✨