I didn't think Lenovo could get much worse than the 6-row abomination that that they foisted on the T-series fans. At least on the T-series you still have the whole caps-lock key that can be remapped to Control. Scattering keys like they've been doing for the past few years is inexcusable. I've enjoyed Thinkpads up to the T420, but no further. This is why my next laptop will not be a Thinkpad or Lenovo of any kind.
Here's something nice: http://starringthecomputer.com/. Various sightings of various computers in movies along with ratings of importance, realism, and visibility.
How'd you get the idea that a tobacco virus was involved here? The article says "M13". If you check with Google and Wikipedia, you'll find that it's a filimentous bacteriophage (it infects bacteria). And about committing sabotage on tobacco farmers, most tobacco diseases affect many other members of the nightshade family. Two important ones are potatoes and tomatoes.
I haven't yet seen mention of someone setting up microphones sensitive to ultrasonic frequencies to check to see what, if any, odd sounds are being made by the computers. A lot of extraordinary claims are being made and I just don't see the requisite extraordinary evidence.
Thanks. This is the most direct answer I've gotten so far. A followup: How much work has been done on that part of the supporting ecosystem to support remoting?
Here's a very simple question with hopefully no wiggle room: Suppose I have two Linux boxes, each running Wayland. They do not run X11 in any form or fashion. I am on the console of one of them and in Wayland. Can I start a terminal emulator, ssh over to the other box, issue a command that starts some graphical program (which uses only Wayland coding, no X11), and expect that program's window to show up on the first box? Assume that ssh has already been modified to allow for this sort of thing. If this cannot be done, what prevents it from being done? I have yet received no complete answer for this.
It looks like people are already putting garbage into his database so as to render it useless. At the top of the page is "know something about the project before you comment". In the FAQ and Guidelines, it seems that the author might know what he's talking about. I'm still not clear if he's a hoplophobic crank or playing a joke on hoplophobes. If he's the former, then he made a tremendous blunder by not realizing that lots of people would put garbage into the database.
Somehow I accidentally moderated you down. I hope this post fixes that.
This is the point I've been making above and I've been getting non-answers like "it'll do X backwards compatibility" or "you can do remote desktops". I've never received an answer to this basic question of if a single application can be displayed on another machine.
That's for X apps. I'm talking about Wayland apps. Can native Wayland apps be remoted? I don't want to have a situation where I'm given a native Wayland app to control something and that something is on a remote machine. I don't want to have a situation of "Well, it's native Wayland. You have to be on the system's console to see that." Further, I don't want to have to fire up an entire desktop session to watch a window that takes up a tiny fraction of the screen.
Okay, I see now. Some other observations: 1) It sounds like Wayland doesn't do remoting yet. 2) The way they're talking about it suggests it's desktop-only -- no starting an application on some other machine and displaying it on the local machine.
#1 isn't too bad -- they're working on it. #2 has me more concerned. Are they planning on having it be able to export individual applications rather than just the entire deskstop?
Not supporting remoting is a misconception about Wayland? I certainly didn't see any discussion about that in the article. Would someone please point out a web page that discusses Wayland's remote capabilities?
A lot of these hot supermassive gas giants seem to be extremely young. I wonder what that says about planetary development. Do they lose mass after a billion or two years?
Slightly related, here are a few threads about radio-based baby monitors causing trouble in the ham bands:
The first and second one are about hams tracking down the problems. The second goes into great detail on how the user of the monitor was busted by the FCC. The third is from a user of a baby monitor going full-retard.
I spent some time as a poll official. As part of that job, I had to help people vote paper ballots with fill-bubbles who couldn't figure it out for themselves. Of course, I was forbidden from telling people who or what to vote for, or from offering any comments. The marks also had to be made by the voter's hand. Most of the people with trouble constantly made illegible squiggly marks all over the ballot instead of bubbling in neatly. People who did manage to vote by themselves also had problems. I was able to see their voted ballots because they ignored the instructions to keep the ballot concealed in the provided folder. Instead they waved the ballots over their heads for everyone to see. These too were often marked illegibly. The poll-watchers could only shrug sympathetically to me when this sort of thing happened. Voters have three tries to do it right and after that, too bad. A few people managed to get past the official guarding the ballot box and dumped their illegible ballot in before the official could react. There's another source of bad ballots.
I think New York might be trying to solve problems like these.
Other problems we had were cases of the adult child, who could barely speak or read English, was helping an elderly parent who couldn't speak or read English at all, and so I had to help. I very clearly caught many of these sons pointing to particular candidates or measures saying "Mark here". They were warned several times about this, but ultimately I couldn't do anything besides accept the ballot. Again the poll watchers just shrugged.