Both sides? "Oh yeah, the front looks a lot like the ID I lost, but can you please send me the back side too so that I can confirm?"

Finally. Someone noticed 🥹

Funny thing is that those of who left aren't there anymore to comment that we did leave... So anyone who is still there is probably looking at the others who stayed and saying "See?! The protest didn't work because we are still here!"

Aah, ok! That at least explains what they could have been thinking.

But, of course, this is a terrible idea!!

Ah, do you mean "hate speech"?

My new phone runs GrapheneOS and I love it.

One recommendation that I would give people is that it does not need to be an all-or-nothing jump into the abyss. It can be a bit disheartening when you try to get rid of all the privacy-invasive things in your life and you get cut off from your family and friends.

After some failed attempts, the strategy that I have found more successful is that I have new phone that I installed GrapheneOS into, and I keep the older phone with whatsapp. The older phone is in Airplane mode connected to WiFi at my home. It is effectively a landline. I can still use it once or twice a day to check on my family through WhatsApp without having to broadcast my location all day to Meta. This way I don't need to install any sandboxed Google Play services into my new phone. The old phone is the sandboxed Google Play. I also use the old phone for verifications, 2FA, and any other things that I don't want to contaminate my new phone with.

Over time I am finding that my GrapheneOS is perfectly functional. The main difficulty is the chats services that are used by my family, friends, and work-related "group chats". I have convinced some people to join my XMPP server, including my mom (wuhuu), but it is an uphill battle. That's why the other phone is still essential for me.

If I understand this correctly, signify would allow someone to verify that the executable was built by me. But then they would still have to trust me, because I can also sign the malicious executable.

The creator of the tool is the admin of lemmings.world, and the tool is hosted at schedule.lemmings.world. So, if you have a user at lemmings.world, you can use this tool without having to trust a third-party.

If you don't have a user there, you can create a user in that instance for the purpose of creating scheduled posts. Removing the need to trust two parties rather than one.

And, of course, since the source code is open anyone else can attach this to their own instance! Pretty cool.

1. I purchase Monero through Kraken

2. Not sure

3. It is not exactly the same as KYC, because KYC is about the exchange verifying your identity, keeping a record of who you are, keeping a record of your transactions, and the crypto addressees that they send you funds to.

It depends on what your goal is and who is looking at your finances. If you want to buy hundreds of thousands of dollars worth of Monero to avoid paying taxes, then your bank and potentially the tax authorities will pay attention to a massive transaction leaving your account and disappearing into a non-KYC crypto exchange. So, from that point of view, it is effectively similar to KYC.

But if you are interested in privacy and the per-transaction amounts are not massive, then both the bank and the exchange will still have some record of the transaction tied to your identity. But the bank is unlikely to take notice, and the exchange, being a Non-KYC, will not verify your identity nor is it under the same level of pressure to keep detailed records. Still, some of your information is leaked and it is out there.

Monero is very private, so even with KYC you can pull it off the exchange and your identity is immediately disassociated from it.

Depending on how much you want to buy, and who you know, one way of getting it is to buy it from a friend or an acquaintance.

You have a good reason to be proud. It's awesome!

I think that any step that facilitates verifying the build is great. If trust is required, then I should simply not release any executables if I want to remain anonymous. I would like to be able to release executables without needing to ask people to blindly trust me. I would like to be able to show them reasonably good evidence that the program is built from the source that I say it is.

Actually... let's just get started with [email protected], and we can change things later!

Edit: https://nano.garden/c/jobs

No, I'm not concerned about a lawsuit. It's something that I want to do because I think that it is important. If I want to share tools with non-tech savvy people who are unable to build them from source, I want to be able to share these without anyone needing to "trust" me. The reproducible builds standards are a very nice idea, and I will learn how to implement them.

But I still wonder whether my approach is valid or not - is printing the hash of the output executable during Github's build process, such that it is visible in the workflow logs, very strong evidence that the executable in the release with the same hash was built by github through the transparent build process? Or is there a way a regular user would be able to fake these logs?

Ah, it's always in the small-text (Note [2] at the bottom of https://www.paypal.com/us/digital-wallet/manage-money/crypto/pyusd):

PayPal Balance account required to access cryptocurrency. When you buy or sell cryptocurrency, including when you check out with crypto, we will disclose an exchange rate and any fees you will be charged for that transaction. For currencies other than PYUSD, the exchange rate includes a spread that PayPal earns on each purchase and sale. Learn more about cryptocurrency fees.

So, it is not clear to me whether you would be able to exchange monero for PYUSD in some non-KYC exchange, but from this I gather that the only way to actually pay a vendor using PYUSD would be to have a PayPal account that is tied to your identity.

Furthermore, their smart contract has a built-in "asstProtectionRole" that allows them to uni-laterally freeze the balance in any account.

You can find the read-me in their github project here: https://github.com/paxosglobal/pyusd-contract

Here is an excerpt:

Asset Protection Role

Paxos Trust Company is regulated by the New York Department of Financial Services (NYDFS). As required by the regulator, Paxos must have a role for asset protection to freeze or seize the assets of a criminal party when required to do so by law, including by court order or other legal process.

The assetProtectionRole can freeze and unfreeze the PYUSD balance of any address on chain. It can also wipe the balance of an address after it is frozen to allow the appropriate authorities to seize the backing assets.

Freezing is something that Paxos will not do on its own accord, and as such we expect to happen extremely rarely. The list of frozen addresses is available in isFrozen(address who).

You can see the actual function here.

I don't see this as much of an improvement over using PayPal and a bank. Maybe it can be useful if you want to move crypto into an asset that you can pay with in regular online purchases without going through an exchange. But PayPal will still play the role of the intermediary that knows you. Storing value in an asset that can be frozen by PayPal is absolutely not desirable. So I think that this coin is kind of a gimmick.

But it could have a positive influence in that online vendors might become more accustomed to accepting crypto payments, and it could help adoption in the long run. Let's hope.

TIL. That's an interesting craft!

I have created a new job offer 😁

Noooope

Why not both?

Probably paypal just covering niche without any clear understanding just because stablecoins under the hood is very similar to paypal , just using different rails

Yes, that is what it looks like to me.

The thing is... it would take such a small modification to this system to change the world. If PayPal were to implement this such that the PayPal payment can be made by transferring the crypto into the seller's account directly and anonymously without the buyer having a PayPal Balance account, and then PayPal is willing to exchange the seller's PYUSD for fiat directly on the site, this would be such a significant step in the crypto revolution.

Ah. Cool. I was under the impression that docker images suffered from a similar issue - that one can't verify that the image is built from the source. I'm happy to be mistaken about that.