Pgp is based

Their cop-out is saying, “TailsOS only includes packages from debian repos.” So, I am guessing, before feather gets into TailsOS, it would need to be in debian stable. Can we get a debian maintainer for Feather?

Is there something we can do about getting Feather Wallet by default into TailsOS?

See this: https://monero.observer/monero-v0.18.3.4-fluorine-fermi-tagged/

Feather’s the best desktop wallet.

Do you not understand allegory? Are you a literalist who cannot grasp nuance in internet banter?

force

Nah. I said nudge.

crypto scam

Nah.

specify the network to connect to from the official build

That would very useful.

people have success

Which people? Probably technically-minded, and over-determined people, yes. But do we want only such people have access to Haveno? Absolutely not. People who are only able to burn TailsOS onto a USB should also be able to hop-onto using Haveno and contribute to Monero"s distributed liquidity.

you literally can

No I literally cannot! (maybe). AppImage model of running a program is exactly the same as running an exe file. Download, allow executable, and run. Most newcomers easily get disheartened when they read that they need to unzip a deb file or something.

AppImage is absolutely necessary for users of TailsOS and Qubes-Whonix.

I think the rift between haveno devs and the haveno-reto devs is causing some project management issues. One such example that I get direct exposure is around adding a flatpak and AppImage packaging for Haveno(-Reto) and another is around how (or should?) should the users be able to switch between mainnet providers.

For the example of the first one read down from this message: https://github.com/haveno-dex/haveno/issues/270#issuecomment-2294807880

And for the example of the second one, read down this issue: https://github.com/haveno-dex/haveno/issues/931

There is a friction in trying to coordinate and contribute to the developers working on different (albeit quite similar) repos (in the case of the original Haveno repo and the -Reto repo). This friction in comms and contribution is causing delays in introducing software distribution packages such as AppImage and Flatpaks, which hinders (especially for TailsOS and Qubes-Whonix users) the onboarding of the new users, and decentralizing Monero’s liquidity.

1. Monero
2. Tor Browser
3. WhonixOS/QubesOS
4. GrapheneOS
5. Signal/SimpleX
6. I2P+Qbittorrent
7. Balaclava masks for 2 weeks to stop the spread