Filen is good. Works like a charm. Back in the days I got their pay once for 100GB of storage package and am very happy about it. Looks like they have the starter 100GB lifetime available still i.e. pay only once.
Filen is good. Works like a charm. Back in the days I got their pay once for 100GB of storage package and am very happy about it. Looks like they have the starter 100GB lifetime available still i.e. pay only once.
I use that myself though haven’t sent a sms/mms in like > 10 years. Anyhow FOSS > stock spyware any day. The fossify project has many other useful tools as well.
Whatsapp uses the same protocol as signal so MITM is unlikely however there’s no way to know what happens before or after the messages are encrypted/decrypted and sent. They can do that scanning at that stage.
That is different than Signal which (unless they changed something with the profiles thing) was always P2P E2EE. You’re sending encrypted messages directly to the other persons phone, not to a server.
Sender cannot know where the recipient is and using P2P would be resource consuming on all client devices (i.e. everyone who uses Signal) so I guess the messages are routed thru Signal’s servers though messages are encrypted on device with keys that only the messaging parties know (couldn’t find an official diagram for this to confirm).
In a country with good consumer rights, this would be a valid reason to return it and get a replacement or refund: It’s no longer offering functionality that was advertised and that you paid for as part of the purchase price.
In the EU this would probably be a no-brainer.
Wonder how they’d manage that as they both are E2EE.
You won’t get rid of google tracking you on Youtube or Gmail,
For gmail that’s true (one should use something else anyhow). For youtube you can use an alternative frontend like NewPipe to avoid tracking.
If you care about privacy you should use a trustworthy paid email. They even aren’t that expensive. You can get them as low as 1 € / month.
You can basically disable most Google tracking though a good DNS that blocks that traffic.
So only most but not all. Therefore it’s not private if there’s any tracking. Thus a de-googled version is the only option.
Have you checked the source code that they actually respect private dns setting for their tracking? Or otherwise verified that no traffic goes to google tracking servers?
If there’s tracking it’s not private.
It can’t be removed. That info comes straight from the hardware itself (UEFI and individual devices).
This didn’t seem to occur in Windows, but I’m pretty sure the copy process was also slower so guessing it’s some sort of buffer or heat quirk that 'nix didn’t account for in the more generic driver
If the device says it’s a generic storage device (to the system that is) but actually isn’t (based on your description) then it’s 100% devices fault and not a Linux fault.
Just use some other search engine. No tricks needed to get non ai bs results.
Have an idea which might solve this.
When the host routing table is like this:
$route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.102.1 0.0.0.0 UG 600 0 0 wlp19s0f4u1u1
default RT-AC86U-6D60 0.0.0.0 UG 20100 0 0 enp15s0
the VM has internet connection. If the defaults are the other way around it doesn’t.
This sounds reasonable. Curiously now that I tried again with both host lan & wlan active there was no problem. I have a hunch the routing depends on which interface networkmanger starts first.
$route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.102.1 0.0.0.0 UG 600 0 0 wlp19s0f4u1u1
default RT-AC86U-6D60 0.0.0.0 UG 20100 0 0 enp15s0
192.168.2.0 0.0.0.0 255.255.255.0 U 100 0 0 enp15s0
192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr1
192.168.102.0 0.0.0.0 255.255.255.0 U 600 0 0 wlp19s0f4u1u1
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0_
Here’s the final peer reviewed version https://peerj.com/articles/cs-111/.
They didn’t use very comprehensive research methods. Also they only used Github.
First, from the GHTorrent data set, we extract the email addresses of GitHub users. Second, for each email address, we use the search engine in the Google+ social network to search for users with that email address. Third, we parse the returned users’ ‘About’ page to scrape their gender.
a bias against men exists, that is, a form of reverse discrimination.
How is it reverse discrimination. It’s still plain old discrimination. I’m starting to smell a biased research here. Or at least the researchers have a bias.
I’m in the EU and that section in the settings isn’t even there. I guess they aren’t doing it here, for now at least. Probably due to GDPR.