Most of the time I pause, it's to talk to someone in the other room or even to take a "phone call". (My Android actually has a function to connect voice-to-voice, amazing!).
Link rot is all to familiar to me. Local newspapers, such as nola.com in New Orleans, are impossible to search because of site updates that wiped out the entire history.
I had not realized there were nine million such links on Wikipedia, as they tend to mind such matters more closely than the commercial media companies. (An exception are the NYT and Washington Post, who in my experience do pretty well in keeping old links working or at least redirected to the same content).
I donate to archive.org partly because they're they only folks who seem to understand that web content with no archive is as ephemeral as a sand drawing on a beach. FIfteen years ago I put up some photos on angelfire that I forgot about but later wanted to see. Voila, here it is on the Wayback machine.
In 10,000 years, our current era may be less well documented than the Bronze Age.
How are these 9 million links broken in the first place?
Wikipedia has a useful and seemingly complete archive of every version and edit for every article. I'm curious how these broken links originate, and how they differ from those that are available in the WIkipedia Revision History.
The problems faced by the farmers with closed access proprietary technology remind me of the brick wall I ran into trying to find a smart outlet to control a simple 115V hot water recirculation pump.
Every smart device seems to need to talk to to a central plant somewhere to gain authorization. I don't want to speak to Alexa or Google Assistant to control the pump. (I cannot bear the idea of Experian selling logs of my hot-water-recirculation habits to the highest bidder.) All I want is an internal web interface on my internal network similar to what my 15 year old Brother printer gives me, with SSH keys that I manage.
There are some limited open source options that require physically modding some existing smart plugs, but nothing that I could find off the shelf allowed me to be in total control of the smart plug in my environment as I manage it. I don't mind soldering up a fine mess on 5V logic circuits, but I draw the line at hand-soldering boards that carry line voltage. A failed connection could burn down the house. I gave up on the project.
That's not an option for a farmer who relies on a tractor to cash in a crop. In just trying to get a stupid smart plug to work within my infrastructure, I got a taste of what farmers must go through with tractors that go on strike unless they can call home or receive the services of a tech just to restart. What a nightmare.
Part of the huge white-space and big button modern trend comes from the advent of touch screens. Remember Windows 8 and how it practically forced users into touch with gestures and "charm zones"?
I appreciate some of these new features. For example, in Siebel's database Open UI, buttons and selection targets are now easier to hit. The downside is less information in the same screen space. (Also, the new interface does not require IE and ActiveX, a positive but not related to the UI's functionality).
I suspect that the concept that touch would completely replace dedicated controls went a little far. Honda's bringing back the volume knob. I expect some of these design elements to be, ahem, "dialed back" as time passes.
" will also get rid of several top publications, including the New York Times and CNN"
Great. The two organizations, flawed as they may be, that actually have reporters who work on location are the ones getting the boot? Who's left, Drudge, Red State, Michael Moore, Greenpeace?
Thanks, Facebook, but I'll personally be trending toward birthday parties and friends' gigs. Oh, and the cats, the never-ending supply of cats.
I watched live on NASA's internal tv network, surrounded by co-workers, all of us part of the Shuttle Program.
We built the tanks and shipped them by barge to the Cape for launch. I was recently graduated mechanical engineer working on robotic welding processes for the Shuttle External Tank. I watched as our pride and joy blew the Shuttle and its crew to pieces. (The External Tank is the piece that actually blew up. The starboard SRB caused the anomaly, and the two boosters continued off on their own rogue paths until the range safety officer destroyed them by command).
NASA had live TV monitors in the office corridors and on the plant floor at the Michoud Assembly Facility, where the tanks (and before that, the Saturn V) were manufactured. At launch time, employees were encouraged to watch their handiwork make the nine minute ascent before it was tossed away for destructive reentry over the Indian Ocean. We were on an ambitious plan to reach 60 tanks per year, corresponding to more than one Shuttle flight per week. After over twenty missions, launches were becoming routine and we were less compelled to see every one. I had already missed a few, but on this particular morning the skies that day over Michoud were crisp, cold, and crystal clear. I knew same air mass was over the Cape. That meant the television optics would be clearer than usual. With this unusual weather in mind, I planned to watch the launch.
General NASA and company policy encouraged employees to take a break and watch launches, but I unfortunately had a new boss who had come from some other non-NASA Martin division and he saw no point in the watching launch video. He kept us sitting around his office in a meeting as the launch started. When I asked if we could be excused to watch, he huffed and griped, but finally relented and agreed to pause our meeting.
I walked down the hall and could see that the launch vehicle had already lifted off and was well into its ascent. I came up upon the cluster fellow employees watching the monitor just as the vehicle trajectory was somewhere near or just after Max Q (maximum aerodynamic pressure, always a moment of concern for the External Tank team).
As I had expected, we had an unusually clear view of the vehicle. A flare of vapor emerged briefly--interesting, as I'd never seen that. Suddenly the image was all smoke and fire. I said "wow, what a spectacular SRB sep, it's not usually that clear." One of my co-workers said quietly "I think we're a little early on that". As he was speaking, the NASA camera pulled back. The SRBs were spiraling off on their own. Debris was raining down over the Atlantic. The audio was momentarily silent and then the announcer said "obviously a major malfunction". I can still hear that in my head as though it happened yesterday.
We stood there in shock for about ten minutes, watching the smoke trails with the cameras zooming in and out as the camera operator tried in vain to find the orbiter. Some employees began crying. A few minutes more and the screen cut to black abruptly, without comment. I walked back to my work area. My new boss said snarkily, "Once you're finished grieving, we can get back to work." To this day, that remains the coldest thing anyone ever said to me at a job. Many employees left at mid-day. In the afternoon, our division president appeared on the monitors looking forlorn. He cautioned about speculating or talking to the press. At day's end I passed out of the gate where local news crews were jockeying with microphones, hoping one of us would chat. I went home to flip between CNN and the big news channels, the 1986 equivalent of Google News and Twitter.
A "tiger team" was immediately convened and two train car loads of manufacturing records were brought in for forensics. A tank failure was the suspected culprit, so every weld x-ray and component flight certification would need to be reexamined. It seemed obvious the tank had exploded, and indeed the failure of the hydrogen tank and the collapse of
Reaching space and staying there without falling back requires more than just height, but also a velocity of about 18,000 mph tangential to the Earth's surface.
When I traveled through the Middle East, Eastern Arabic numerals struck me as much more logical than the Western set I grew up with and use today.
Zero is the simplest possible symbol, a dot. The "five digit is the only symbol that is both closed and without open lines (in other words, like the Western zero), which is an appropriate distinction for the half value of the base. Each of the first four digits has as many strokes as the digit represents (single stroke for one, two for two, etc.). I imagine this makes numbers up to five easier for children to learn.
I use a proprietary Microsoft mouse, but have friends who are happy with Bluetooths.
One cautionary note: My Nokia phone syncs via Bluetooth, but for a long time I had problems with authentication failures. I downloaded updated vendor (Anycom) drivers for my device, and the problem disappeared.
If you add a Bluetooth dongle, be sure to use the vendor's drivers rather than the default Microsoft stack.
Slashdot Mirror
"Non-disruptive."
LOL.
Most of the time I pause, it's to talk to someone in the other room or even to take a "phone call". (My Android actually has a function to connect voice-to-voice, amazing!).
Link rot is all to familiar to me. Local newspapers, such as nola.com in New Orleans, are impossible to search because of site updates that wiped out the entire history.
I had not realized there were nine million such links on Wikipedia, as they tend to mind such matters more closely than the commercial media companies. (An exception are the NYT and Washington Post, who in my experience do pretty well in keeping old links working or at least redirected to the same content).
I donate to archive.org partly because they're they only folks who seem to understand that web content with no archive is as ephemeral as a sand drawing on a beach. FIfteen years ago I put up some photos on angelfire that I forgot about but later wanted to see. Voila, here it is on the Wayback machine.
In 10,000 years, our current era may be less well documented than the Bronze Age.
How are these 9 million links broken in the first place?
Wikipedia has a useful and seemingly complete archive of every version and edit for every article. I'm curious how these broken links originate, and how they differ from those that are available in the WIkipedia Revision History.
The problems faced by the farmers with closed access proprietary technology remind me of the brick wall I ran into trying to find a smart outlet to control a simple 115V hot water recirculation pump.
Every smart device seems to need to talk to to a central plant somewhere to gain authorization. I don't want to speak to Alexa or Google Assistant to control the pump. (I cannot bear the idea of Experian selling logs of my hot-water-recirculation habits to the highest bidder.) All I want is an internal web interface on my internal network similar to what my 15 year old Brother printer gives me, with SSH keys that I manage.
There are some limited open source options that require physically modding some existing smart plugs, but nothing that I could find off the shelf allowed me to be in total control of the smart plug in my environment as I manage it. I don't mind soldering up a fine mess on 5V logic circuits, but I draw the line at hand-soldering boards that carry line voltage. A failed connection could burn down the house. I gave up on the project.
That's not an option for a farmer who relies on a tractor to cash in a crop. In just trying to get a stupid smart plug to work within my infrastructure, I got a taste of what farmers must go through with tractors that go on strike unless they can call home or receive the services of a tech just to restart. What a nightmare.
LBJ during his political ascent in Texas has long been suspected of violating the integrity of the 1948 Senate election.
http://3.bp.blogspot.com/-57xl...
Robert Caro writes about this extensively.
Part of the huge white-space and big button modern trend comes from the advent of touch screens. Remember Windows 8 and how it practically forced users into touch with gestures and "charm zones"?
I appreciate some of these new features. For example, in Siebel's database Open UI, buttons and selection targets are now easier to hit. The downside is less information in the same screen space. (Also, the new interface does not require IE and ActiveX, a positive but not related to the UI's functionality).
I suspect that the concept that touch would completely replace dedicated controls went a little far. Honda's bringing back the volume knob. I expect some of these design elements to be, ahem, "dialed back" as time passes.
I, um, actually do catch up on current events with The Daily Show (and the Nightly Show, too).
I am under no illusion that these show are free of bias. They don't pretend to be, which is part of the appeal.
" will also get rid of several top publications, including the New York Times and CNN"
Great. The two organizations, flawed as they may be, that actually have reporters who work on location are the ones getting the boot? Who's left, Drudge, Red State, Michael Moore, Greenpeace?
Thanks, Facebook, but I'll personally be trending toward birthday parties and friends' gigs. Oh, and the cats, the never-ending supply of cats.
I watched live on NASA's internal tv network, surrounded by co-workers, all of us part of the Shuttle Program.
We built the tanks and shipped them by barge to the Cape for launch. I was recently graduated mechanical engineer working on robotic welding processes for the Shuttle External Tank. I watched as our pride and joy blew the Shuttle and its crew to pieces. (The External Tank is the piece that actually blew up. The starboard SRB caused the anomaly, and the two boosters continued off on their own rogue paths until the range safety officer destroyed them by command).
NASA had live TV monitors in the office corridors and on the plant floor at the Michoud Assembly Facility, where the tanks (and before that, the Saturn V) were manufactured. At launch time, employees were encouraged to watch their handiwork make the nine minute ascent before it was tossed away for destructive reentry over the Indian Ocean. We were on an ambitious plan to reach 60 tanks per year, corresponding to more than one Shuttle flight per week. After over twenty missions, launches were becoming routine and we were less compelled to see every one. I had already missed a few, but on this particular morning the skies that day over Michoud were crisp, cold, and crystal clear. I knew same air mass was over the Cape. That meant the television optics would be clearer than usual. With this unusual weather in mind, I planned to watch the launch.
General NASA and company policy encouraged employees to take a break and watch launches, but I unfortunately had a new boss who had come from some other non-NASA Martin division and he saw no point in the watching launch video. He kept us sitting around his office in a meeting as the launch started. When I asked if we could be excused to watch, he huffed and griped, but finally relented and agreed to pause our meeting.
I walked down the hall and could see that the launch vehicle had already lifted off and was well into its ascent. I came up upon the cluster fellow employees watching the monitor just as the vehicle trajectory was somewhere near or just after Max Q (maximum aerodynamic pressure, always a moment of concern for the External Tank team).
As I had expected, we had an unusually clear view of the vehicle. A flare of vapor emerged briefly--interesting, as I'd never seen that. Suddenly the image was all smoke and fire. I said "wow, what a spectacular SRB sep, it's not usually that clear." One of my co-workers said quietly "I think we're a little early on that". As he was speaking, the NASA camera pulled back. The SRBs were spiraling off on their own. Debris was raining down over the Atlantic. The audio was momentarily silent and then the announcer said "obviously a major malfunction". I can still hear that in my head as though it happened yesterday.
We stood there in shock for about ten minutes, watching the smoke trails with the cameras zooming in and out as the camera operator tried in vain to find the orbiter. Some employees began crying. A few minutes more and the screen cut to black abruptly, without comment. I walked back to my work area. My new boss said snarkily, "Once you're finished grieving, we can get back to work." To this day, that remains the coldest thing anyone ever said to me at a job. Many employees left at mid-day. In the afternoon, our division president appeared on the monitors looking forlorn. He cautioned about speculating or talking to the press. At day's end I passed out of the gate where local news crews were jockeying with microphones, hoping one of us would chat. I went home to flip between CNN and the big news channels, the 1986 equivalent of Google News and Twitter.
A "tiger team" was immediately convened and two train car loads of manufacturing records were brought in for forensics. A tank failure was the suspected culprit, so every weld x-ray and component flight certification would need to be reexamined. It seemed obvious the tank had exploded, and indeed the failure of the hydrogen tank and the collapse of
Reaching space and staying there without falling back requires more than just height, but also a velocity of about 18,000 mph tangential to the Earth's surface.
Wow, your description of Chatty is even funnier than that scene from "Office Space."
And that's really saying something. Well done!
When I traveled through the Middle East, Eastern Arabic numerals struck me as much more logical than the Western set I grew up with and use today. Zero is the simplest possible symbol, a dot. The "five digit is the only symbol that is both closed and without open lines (in other words, like the Western zero), which is an appropriate distinction for the half value of the base. Each of the first four digits has as many strokes as the digit represents (single stroke for one, two for two, etc.). I imagine this makes numbers up to five easier for children to learn.
I use a proprietary Microsoft mouse, but have friends who are happy with Bluetooths.
One cautionary note: My Nokia phone syncs via Bluetooth, but for a long time I had problems with authentication failures. I downloaded updated vendor (Anycom) drivers for my device, and the problem disappeared.
If you add a Bluetooth dongle, be sure to use the vendor's drivers rather than the default Microsoft stack.