… and keep a particularly close eye on the logs of those who selected this option?

Android now working

Today I tested NoShore on Android (in Termux) and fixed some errors that prevented a smooth setup process.

Clone branch v0.1.1 to get the lastet version:

git clone --branch v0.1.1 https://gitlab.com/fullmetalScience/noshore.git ~/xmr.zone/noshore

This sure clarifies the circumstances. I appreciate the explanation and went on to verify the claims.

Here are the corresponding Etherscan-links to spare others the hassle:

1. [0x2274] MONEROCHAN creation
2. [0x2274] Uniswap funding / locking
3. [0xB9A1] Buying 789,420,933 (at time of writing)
4. [0xB9A1] Burning of 383,913,580 (at time of writing)

So far I couldn’t detect any discrepancies. Note that, on Blockchair, whale.monerochan.eth appears to resolve to 0x0000000000000000000000000000000000000000, while airdrops come from 0x4642, after being funded by 0xB9A1.

Thank you for the onboarding!

The text has some … “orange” flags.

For example, burning 25% doesn’t make sense when you decided on the supply to begin with and “100 % fair distribution” isn’t possible in the given scenario.

But then again, meme coins are all about not making sense, and some play may actually lead to the desired exposure. Let’s get Monero some marketing:

0xe746433469235aB0D5cc404b592C9634eF2ECB1D

It does make sense that the tables are for Monero-exclusive applications. Loaded GUI’s lead to user confusion and thus errors.

Think absolute beginner: “I installed that secure app you recommended and bought <thatothercoin> and happily transacted and now you say that wasn’t secure?!”

This is bad news for those of us who were not only looking to give old mobile hardware a longer lifespan, but simultaneously obtain privacy and security while doing so.

The arguments provided in the blog post are rather faint and give a vibe of “holding on to last straws”, as other distributions and even BSD’s have managed to run both GNOME and KDE fine, even before pmOS.

For readers unfamiliar with systemd’s drawbacks, these resources can serve as good starting points:

without-systemd.org // nosystemd.org

Out of curiosity: Can you point to a log of the communication with the Alpine team?

Great. Maybe you can give a little heads-up after the weekend.

I just went to donate, but OpenCollective turned out to be cloudflared and therefore doesn’t let me pass (for originating from Tor).

Though I could steer around this and as much as I would like to financially support the project, I cannot, in good-conscience, support the use and propagation of the worlds biggest MitM attacker.