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.
Replying to ₿itcoin

https://forums.whonix.org/t/bisq-the-p2p-exchange-network/4953/78

"bisq signing key recently changed. I couldn’t find any explanation for the change.

An anonymous wiki edit was suggested to update the signing key." - whonix dev

#bisq #bitcoin beware and stay vigilant.

Am I right in that this change was/would be specific to the build on by Whonix's pkgmgr?

It's true.

The SEC, the Fed, the ECB, they all know it.

And they're scared shitless.

#Bitcoin #Fiat #Grownostr #Debasement

No convenience outweighs the risk in these cases.

To anyone considering this: Just take a couple hours, make it a weekend project if you have to, it's fun anyway - Follow the GrapheneOS tutorial, verify your GrapheneOS ROM's hash, and install it the proper way. You'll feel accomplished, it'll be yours, and you'll know no one messed with it. No trusting, just verifying.

Does auto-correct actually work though?

Either way thanks for confirming, I'll need to check on auto-correct a bit more then.

Replying to Avatar Vitor Pamplona

#Amethyst v0.84.1: ncryptsec support (NIP-49)

Now you can export and login with a password-protected version of your private key.

This new format starts with **ncryptsec** and requires inputting a password to decrypt the key before loading it into a client. Keep in mind that the new format is not designed to replace your **nsec**, but to work side-by-side with it. Keep your nsec in the safest place you can and use the **ncryptsec** to move your key between devices, deleting it as soon as you are done with the transfer.

New Additions:

- Adds support for NIP49 to login and back up key screens

- Adds cryptographic support for NIP-49 to Quartz

- Enables citation on chats via @

- Adds "₿itcoin" to the set of custom hashtags

Updated translations:

- Portuguese by nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

- Hungarian by nostr:npub1ww8kjxz2akn82qptdpl7glywnchhkx3x04hez3d3rye397turrhssenvtp

- Dutch by nostr:npub1w4la29u3zv09r6crx5u8yxax0ffxgekzdm2egzjkjckef7xc83fs0ftxcd

- Chinese by nostr:npub1raspu6ag9kfcw9jz0rz4z693qwmqe5sx6jdhhuvkwz5zy8rygztqnwfhd7

Performance Improvements:

- Avoids the memory use of the flatten operation on Notification counters

- Adds a check for the main thread when pulling opengraph tags.

- No need to crossfade when clicking on Show More

Code Quality Improvements:

- Updates Compose dependencies

Download:

- [Play Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.84.1/amethyst-googleplay-universal-v0.84.1.apk )

- [FOSS Edition - No translations](https://github.com/vitorpamplona/amethyst/releases/download/v0.84.1/amethyst-fdroid-universal-v0.84.1.apk )

Just wondering, does Amethyst need a translator for European Portuguese? Assuming fiatjaf's is brazilian portuguese.

Little late but FYI, I've confirmed this is related to word/correction suggestions. If disabled, mentions will work regardless of keyboard.

Should've been clearer, all suggestions and autocorrect.

However Openboard seems to have a dependency between next word suggestions and corrections. Auto-corrections also don't seem to work with suggestions turned off from my testing.

Okay, I'm now using Openboard and got both working - I believe the issue is related to word suggestions. I've disabled those and it's working now.

We are the few.

While some stay at the base layer, looking at pricing, we are here, proving it works, proving decentralisation is the future, generating a circular economy.

Building, testing, decentralising and putting in the effort, the POW.

They'll eventually make their way up the layers to experience a new internet. If the now is an indication of anything, it'll be an absolute game-changer.

Native money on the internet with a social network protocol that's more relatable to the internet than something solely glued together by a few thousand SQL DBs.

Connecting our own corners of cyberspace to a permisionless network.

#bitcoin #nostr

The mention or the backspace issue? Mentions are a keyboard issue. Backspace issue still unsure.

Switched to Openboard and still happening.

Also, do you see any issue with backspacing, where words get merged as you backspace after you've completed a word?

Depends. I can see the interpretation that it could be swap to self-custody sats (cash out option), but could also be interpreted as swapping the token to a mint the friend fully trusts (perhaps runs even) - But yes, effectively the friend is claiming before Callenis able to do a claim-back on that token.

Personally I think this is one of the most interesting things due to the PoC for offline transacting.

nostr:nevent1qqsqqqqzgt9qyjez0g2u8u2txpsk7mn90j7ppqm4vv4cun0qdfnpl2spzfmhxue69uhkummnw3ezumr49e4k2tczyz9w4dcqx39mw2f9l6n8u5wuds04gplcvx8w6qjlaw6pyw8826gwgqcyqqqqqqgz0ttea

As an example, the EU has guidelines that apply to ecash-based CBDC applicants that completely break a lot of the expected ecash benefits - They'd fuck everyone over from the start.

You could argue that then it's not ecash, much less chaumian, but truth is it's being looked at, there are applicants and it *could* come to pass.

It could also depend on competition. Say an exchange does introduce ecash, which presents no downsides compared to what's done now and multiple upsides for the end-user (but also for the exchange potentially).

All it takes is one and the question then becomes which one is, in fact, offering the better service for the end-user? I think time will make it clear.