Tha_14

I have been happily using PipePipe for the past few months and have been very satisfied with it. The developer seems to spend the time and attention needed to make it work again whenever youtube likes to change things and I really appreciate that.

Anything that is P2P E2EE is hard to block by utilizing traditional measures. Personally I use and trust Tox. If you also want anonimity you can pair it with tor.

You can always use Melanotan II instead to get a good tan while also increasing libido and sleep quality; )

Well, I don't know if anyone else responds to the mailing lists anymore to be honest. You can still get in touch through IRC though. We are on libera currently(and dogfooding tox groupchats). #tox for user related questions and #toktok for development.

Edit: Also, development is happening on github: https://github.com/TokTok/c-toxcore

I think that you're refering to qTox(which is currebtly not being maintained). Tox, the protocol, continues development as usual.

Unfortunately we don't have any good clients for android that do videocalls properly(not even qtox on PC works that great). aTox is the only android client that was starting to get the proper features but the maintainer is busy with IRL stuff. You're right though, text and file transfers work pretty well and we are writing replacements for the existing code to make everything more reliable(and faster in the case of file transfers).

I also used to use rEFInd while I was running macOS/windows dualboot for a short time. I am going back to it from grub now since booting from my zfs root partition with grub has become a hassle.

> I've previously assumed that the choice there is either:

> a) don't save CC info at all

> b) save CC info in tokenized form (whatever that means)

> And since I never save CC info on websites (only in the phone wallet feature) I've always rejected these "tokenized" prompts. But it seems I need to research this thing more next time.

Tokenization means that the payment processor saves your cc information for "easier" use when you make purchases/pay bills in the future. The seller/service provider can of course use that token to charge you anytime they want. I hope this helps with understanding how it works(and why I am hesitant to allow tokenization of my cards).

> Just the other day I've encountered a cookie modal, where the enabled option was grayed out and when disabled it was colored. Only noticed this because the required cookies toggle was obviously on (though gray in color). For someone in a hurry (like we are all when dismissing those modals), you would expect to gray those out, which would actually make you opt-in to all those advertising cookies. Talk about dark patterns.

I realized the same pattern but in reverse in my phone provider's app. When you're making a payment with your credit/debit card, there is a toggle that you can turn on for them to tokenize your card. By default, the toggle is to the left side and it's colored light blue. When you toggle it to the right it become gray. I believe they have done it on purpose to confuse prople who don't want their card tokenized.

I've been using vscodium for the most part but you cannot avoid the extensions themselves sending their own telemetry.