Qubes is the gold standard
Network namespaces also work
Portmaster is a good gui for this approach
More rarely: some poorly configured USB controllers can actually provide enough backwash power to the motherboard that some LEDs still blink, like the Ethernet indicators.
I ran into this myself, I notice the lights being on, and they stayed on when I unplugged the computer. Took me a good 5m of debugging to figure it out.
this 100% factually incorrect.
cohost is a social media microblogging platform
If you can’t find groups to join, you can start your own group. The key is to be a GM looking for players, then people will magically appear…
Then you can move onto the next phase: scheduling hell, and why I hate people
fdroid does not require you to sign in
https://www.privacyguides.org/en/basics/hardware/?h=networking#secure-your-network
Really you need to first define your threat model, the EFF has a good guide on that.
Maximum paranoia would be Wi-Fi only connects to a restricted VLAN that can only talk to a VPN server. You must use a VPN to access your network over wireless. That’s probably too much work for most people. But it would be the most compartmentalized, not trusting Wi-Fi encryption, which really isn’t that strong
Super basic data hygiene means you only use WPA2 and above security for your Wi-Fi network.
Depending on your actual threat model, what you choose to do will probably be between those two points.
having a stalker, makes privacy very important
Having identity theft, makes privacy even more important
Being pigeonholed, makes privacy important
Sounds like want a pbc with extensions, like astrix. You could program it twilio too
But… sms verification systems won’t honor extensions
https://www.privacyguides.org/en/os/android-overview/#choosing-an-android-distribution
https://www.privacyguides.org/en/android/distributions/
https://share.privacyguides.org/tools/grapheneos/
There you go. Everything you wanted to know and more about Android security and trade-offs
https://hackertalks.com/comment/4806772
They have demonstrated history of asking third party clients to not use the signal name, and not use the signal network. The client that currently exists that do this do it against the wishes of the signal foundation
you keep moving the goal posts, Ive justified my position in the original comment.
By all means, use signal, I do. But let’s not deny the realities. I think we’ve covered all that we need to cover in this discussion thread. We don’t have to agree and that’s okay, and I wish you a good day, but I’m not going to respond anymore
I respectfully disagree. They could be waiting until it becomes a big issue. Right now that would just cost them good PR, but if somebody was using the signal network and their client became very popular they absolutely have expressed the desire, intent, and as you indicated the capability to do so.
Moxie made it incredibly clear, he does not want third party is talking to the signal servers.
Libra signal took him at his word and turn themselves off
The other developers, like Molly, take a stronger road.
Is signal currently banning third party clients? No. But they’ve made it clear they don’t like them. They didn’t actually ban Libra signal, they just asked them to stop. Could they ban the clients in the future? Yes
In the Libra signal issue that you linked to, they made it clear they don’t want third-party clients talking to signal servers
You’re free to use our source code for whatever you would like under the terms of the license, but you’re not entitled to use our name or the service that we run.
If you think running servers is difficult and expensive (you’re right), ask yourself why you feel entitled for us to run them for your product.
A really excellent writeup!
yes. mail
or crypto like monero
or prepaid credit cards
or voucher resellers, etc