Avatar
Uxellodunum
af27a694e1ed4f6fe41290139a4819b182dc39befd9d855f718285546dba7c8f
🇬🇧🇵🇹 Technomancer @ Proxymana https://info.proxymana.net Building infrastructure, a cyberfort for our community. 🐧Linux daily-driver.🐧 No Windows machines in this household. ₿ Bitcoin ₿ & ⚡ Lightning ⚡ Node & Mining Operator. Not your keys, not your coin ₿ In the process of maximizing Sovereignty. Mining since 825039. On nostr since 789374. Bitcoin Class of 2017.

#Bitcoin is the escape valve.

#nostr is the first port of safehaven.

Fuck the #ECB

I think I'll move my #UTXO s around just for fucking fun.

STOP ME BITCHES.

#Bitcoin fixes this.

https://www.virtue.news/european-union-introduces-ban-on-anonymous-cryptocurrency-transactions-over-eu3-000/

Figured it out!

I was logging in with an extension, so mainly just pub key was used with signing done on a per-need basis.

Once I logged in with private testing key, I was able to test Nip-44 DMing.

Would it make sense for Coracle's messaging to request the private key specifically for this purpose? I thought the "Decrypt messages from peers" permission that nos2x-fox asks for would be included, but seems it's not.

nostr:nprofile1qyvhwumn8ghj76r0v3kxymmy9ehx7um5wgcjucm0d5hszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0qy88wumn8ghj7mn0wvhxcmmv9uq35amnwvaz7tmjv4kxz7fwwpex77red4skucfwdejhgtcqyztuwzjyxe4x2dwpgken87tna2rdlhpd02va5cvvgrrywpddnr3jynnn8vu Hey, question on Coracle.

When sending DMs, a warning shows stating the usage of legacy DMs. Is this simply an FYI warning, is there a way to enable NIP-44 messaging, or is development required to implement this?

Testing relay broadcasting on Coracle.

A war of values and integrity is being waged.

It's unfortunate it shows many hard truths.

Best we can do is attempt to educate and look for save haven - Safe havens will show themselves, sometimes in the places we least expect.

Not saying they are a safe haven per se, but pretty sure no one expected El Salvador would be the first country to embrace Bitcoin, in fact, many people didn't even know it existed. That's how much things are changing.

Have you seen the relay menu on #Lume?

It has a huge list of global relays + relays used by followers.

If the current optimal number of relays to use is 2-5, I think such list make a lot of sense, but could perhaps use extra metrics to guide the user towards their usage.

Example, metrics such as latency (Again, just using Lume as an example, but that seems to be missing), whether it's paid, etc

I think another problem isn't even the centralisation at the user level. But rather, at the ISP level.

Arguably, well-operated relays that are not hosted by a cloud provider are better in every sense (assuming bandwidth needs are met by whichever ISP is used).

I think this is the next best step after self-hosting relays.

Integrating relays into clients can also solve a lot of problems (has its own challenges).

>> I keep wondering if the next step is to incentivize relay-starters somehow.

I've seen some mentions of clients considering integrating relays. This would be a really good step. If these integrated relays could then broadcast themselves as available, it could solve a lot of problems concerning decentralization and censorship, but it has challenges like dialling down network noise.

I like how the #Lume #Nostr #Client does away with Likes. It shifts focus from meaningless, effortless clicks, to a degree of proof-of-work in showing of value and appreciation, be it in the form of comments or #zaps.

What other clients do this?

#asknostr

Coinbase is bashed on because their practices include ponzi scheme endorsements along with setting themselves up for regulatory capture forcing their users to KYC themselves.

Seen what's happening in the EU with the new bill in passing? Likely to happen everywhere else, which affects anyone and everyone with KYC stacks, and any establishments that host such wallets. DEXs existed before coinbase, but users chose forgoing responsability and effort (proof of work), instead of taking full custody of their stack.

If your stack is KYC'd and has not been mixed, you will be limited. Linking one's BTC stack to the legacy finance system was never going to work, they were made holisitically incompatible from the ground up.

Any that a regulated by the EU, I think that's what they mean.

Effectively? Any CEX, any merchant that doesn't transact P2P and announces it for tax purposes.

Finally, it begins.

Everyone knew this was coming.

Your KYC stack will make you a target.

Time to start packing bags, and looking for places whose values align with yours, and Bitcoin's.

I think a big part of the problem is that tech giants centralised TCP/IP to a point that big hosting companies can easily take part in censorship under the guise of regulatory pressure.

Self-hosted relays that are open are what we need - Better yet, nostr-client-intergrated-relays with meek or something of the like. No point in having multiple relays hosted by a singe company - That's still a high degree of centralisation, even if spread around the globe.

Can't remember which one it was, but I recall a desktop Nostr app with a built-in relay service, going over a tor tunnel. I have a feeling that's where Lume announced it was headed in the future - And I think that's the right step to go.

Nostr on websites is great from an accessibility perspective (hail PWAs I guess), but accessibility and censorship-resistance are not the same thing. I'd say anyone using nostr solely via websites is setting themselves up for trouble, at some point, somewhere, for some reason.