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.
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_
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.
There's a dialog within the program to enter your key though I haven't checked if it connects to the internet at that point. I use an account so I can easily use it on several computers.
Stay away from Groovy. It's a horrible language. It's quick to write but slow and difficult to read. It's conventions make it a very error prone.
Link to the things you mention e.g. you say to get familiar with Loom. When searching for that all I get is some screen recording software (probably not what you meant).
It can't be removed. That info comes straight from the hardware itself (UEFI and individual devices).