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?
Do you follow the -dev and no-wallet-left-behind irc/matrix room discussions? Kayabanerve posts some good updates on the work being done. Last time I checked was that they were getting math proofs for the FCMP.
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.
Full membership proofs will solve the issues, 1, 2, 3, 4 and 5. It can't arrive soon enough (provided that the maths and the code implementation are sound and secure, of course).
tails to keep electrum pre installed only by default.
I still can't comprehend the TailsOS developers for this decision. They are going all the way about hiding the trails of internet packages that are sent/received to the Tails operating system. But they are literally operating on the "clearnet" when it comes to the trails of internet money bits.
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.
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.
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.
Done 👍
Yessir
Yes I indeed ignored everything that came after when you referred to Monero as a scam.
Do you even know what XMR is, or are you a drive-by commenter?
Do you not understand allegory? Are you a literalist who cannot grasp nuance in internet banter?
Nah. I said nudge.
Nah.
Bounty increased to 2 XMR.
Do you follow the -dev and no-wallet-left-behind irc/matrix room discussions? Kayabanerve posts some good updates on the work being done. Last time I checked was that they were getting math proofs for the FCMP.
That would very useful.
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.
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 do hoard it tho.
Full membership proofs will solve the issues, 1, 2, 3, 4 and 5. It can't arrive soon enough (provided that the maths and the code implementation are sound and secure, of course).
I still can't comprehend the TailsOS developers for this decision. They are going all the way about hiding the trails of internet packages that are sent/received to the Tails operating system. But they are literally operating on the "clearnet" when it comes to the trails of internet money bits.
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.
What's your point?