Mmm... your quote (IDK where it's from) mentions them having consent from device owners, but your FBI link cautions on how to avoid getting infected by malware.
If they have consent, they're not really botnets. Botnets involve infecting devices without the owners knowing.
With consent, it wouldn't be much different from e.g. open WiFis at restaurants and hotels, companies using a single ISP and single public IPv4 address for all their employees, and most VPN services.
`ssh -X` has awful performance for some reason. You can see each line render individually when invoking the Info manual on Emacs even while within LAN.
It's better if you enable TCP connections on your X11 server, setup a Wireguard VPN between your Emacs host and your X11 server host, and a firewall to only permit X11 connections over that. Throughput and latency then should be so good the remote Emacs window/frame will be indistinguishable from local ones (at least within LAN, haven't really tried over the internet).
> Do beware though that if you use the non-PGTK GTK build, closing this new frame will crash the remote Emacs.
Guess I've used the good one. Haven't had this problem. What I do have is that if you open a frame in a host that you then put to sleep long enough for the X11 connection to timeout on the Emacs host, then `emacs --daemon` will crash. When I've used it, I've just made sure to save buffers often. systemd would start `emacs --daemon` again on its own.
`emacs --daemon` has no problem using multiple simultaneous X11 connections to different hosts, but it just doesn't handle the connections closing on their own. It also doesn't itself close X11 connections when all frames to an X11 server have been closed. So even if you close all of a machine's Emacs frames prior to putting it to sleep, it still causes `emacs --daemon` to crash.
"Discriminating" is one of those words with multiple similar but distinct definitions. You're using it to mean "distinguishing", but I'm using it to mean "applying prejudice". They're not distinguishing "between blood containing disease vs blood that doesn't". They're distinguishing between travelers coming from certain countries and non-travelers and using that as a very error-prone proxy. That's prejudice, as in "before proper judgment". The fact that you came from a given country does not automatically mean you're carrying a disease.
Could be a normal parasocial thing. They treat the camera (their viewers as a collective) as a relationship they've known for years. You might meet them expecting them to treat you like their camera, like you've got a relationship of years, but you're individually a complete stranger to them. You might treat strangers better, but not everyone does. People can confuse the politeness of being treated nice with wanting the relationship to go further.
Could be a normal parasocial thing. They treat the camera as a relationship they've known for years. You might meet them expecting them to treat you like their camera, like you've got a relationship of years, but you're actually stranger to them. You might treat strangers better, but not everyone does.
Generally, because they're discriminatory. It's like how racial profiling in law enforcement can be a heuristic that can work. Though, in the case of blood donations, it seems that tests aren't accurate enough to be able to rely solely on them. Also, being discriminated against on being able to donate blood is not as big of a deal. Though in some places with public health systems, stuff like getting a surgery may somewhat depend on you and family/friends donating a certain amount of blood.
"Linux, the open-source language of the internet" comes from the linked akamai.com press release, not the blog post author. Their putting that as a section title to the quote may be their poking light fun at it.
> I keep trying to explain to people that private companies harvesting your data, while not good, is done solely for the purpose of trying to get you to voluntarily buy more toilet bowl cleaner.
A reminder that governments can buy from private companies. A company like Palantir can buy data from private companies then incorporate it into the software it sells to governments.
> Well, the brackets thing and the necessity to repeat name of every element twice,
As a document format, it's supposed to be hand-written by humans. If you have paragraphs between the opening tag and closing tag, it makes sense to let the reader know what they're seeing the closing of.
After deciding you do want to repeat the element name, the angle brackets make more sense. Otherwise, you can have a syntax like LaTeX's.
> The worst part about it is the tags vs attributes fights. They both do the same thing and the only difference is preference.
They're not the same thing. If you look at it as the extensible markup language for documents that it is, "tags" (i.e. inner content) would be visible and "attributes" would not. If your XML document was processed by an application to convert to another type of document (PDF, etc.), and it didn't recognize a particular tag, it would be sensible for attributes to disappear, but inner content ("tags") to remain.
It's only seems like a preference thing if you look at XML as a structured data format like JSON is.
> developers must become domain experts [my emphasis] in a rich and complex space that is essentially unrelated to the application itself.
XML is a markup language, but most people that used it just needed a standard structured data format. In comes JSON which is more easily compatible with the object systems of various languages and in particular is compatible with Javascript syntax, and XML loses most of the people that used it.
As a markup language though, it seems pretty good. It's just that the amount of people that actually need an extensible markup language is much smaller.
I do hate the strictness of it. The header
<?xml version="1.0" encoding="UTF-8"?>
should be unnecessary. For a markup language, an already-made plain-text document should already count as XML. The tags should be something you can just sprinkle as you'd like to add contextual metadata.
> Most men who call themselves feminists got there by agreeing with ideas. Agreement is the easy part. The hard part is the gap between a man's stated principles and his Tuesday afternoon
Given the title, I thought this was about work on one's personal or professional lives. Never expected it to be some kind of call to action to male feminists.
If they have consent, they're not really botnets. Botnets involve infecting devices without the owners knowing.
With consent, it wouldn't be much different from e.g. open WiFis at restaurants and hotels, companies using a single ISP and single public IPv4 address for all their employees, and most VPN services.