If I were a cynic
I might suspect that these vulnerabilities are designed to keep people on the upgrade hamster wheel.
84 posts • joined 1 Jul 2009
I liked my Fitbit and I found the service very good. The moment a Google came sniffing, I ditched the device and service.
No service is perfect or can be trusted but when you’ve got Google’s form, you’d better be happy having your bowel movements as public knowledge.
I did get some comments saying I was using the Fitbit incorrectly. Hey ho.
There is no single 'Webex meetings'. Broadly there's Webex Meetings on-prem, Webex Meetings cloud 'Legacy' (multiple versions thereof) and Webex Meetings cloud 'New'. Financial institutions usually have on-prem because they've had it for years (frequently 10+) for compliance and archiving.
They are all rock solid in terms of stability, but if you're on the first 2, then yes, they can be a bit dated for look/feel and user experience. The new cloud version (around for a couple of years now) is a much better experience. Modern even. ;)
I'll bet you were using the 'new' Webex first and then the on-prem for the second. Very different things.
Full disclosure - yes, I work with this stuff as a partner.
Ah yes. Happened to me whilst measuring the 'magnetic screening properties of a high temperature superconductor'. High Temp, in this case, meant liquid nitrogen. Being undergrads, the kit was all a bit Heath Robinson, including the clamp holding the sample in place. As you might suspect, it fell off once or twice. Only once did I put my hand in (with glove). There was a hole in the thumb (Dear Liza) which promptly filled up. Cue spilled liquid nitrogen all over the desk/floor.
This is when I learned that liquid nitrogen is cheap, so the easiest way was was to pour it out, salvage the sample and start again.
My first encounter with liquid nitrogen was during an open weekend at the Physics dept in Exeter. A group of us walked into one lab, where some prof decided it was fun to pour it all over our feet.
Years ago, I was a network admin who had a running battle with the developers when the file I/O moved from local disk to the network. 'But it's so slow' they cried. I tried to convince them that reading one byte at a time wasn't perhaps the best approach.
Eventually one dev relented and wrote a program to test file I/O with variable length requests.
Guess what? A 10 byte request was 10 times faster.....
I remember being told about the flywheel at a school talk.
IIRC we were told it took a couple of days to get up to speed and if it ever came away from it's bearings it would go all the way to Reading, smash through the centre and keep going.
Not all bad then....
It's the documentation.
Which is a bit of an odd mix. 'Here's some open source documentation for our 'open' (closed source) web service'.
More accurately, this is 'Please, please PLEASE use Bing. Someone? Anyone?'
I was initially genuinely excited, only to come crashing down to earth. Ah well.....
That's what happens when you can't observe it any more.
Only a matter of time before someone starts worshipping 'Vger' as a new deity.
Cant see it? - check
Lots of people get excited when referring to it and look skywards with reverence? - check
All the whales dead? - getting there.
Ah, play the man if you cant play the facts Mr AC....
Yes, CO2 is part of the life cycle of the planet. However, that doesnt mean it isn't a pollutant. Any substance that occurs in a concentration or form that adversely effects the environment into which it is introduced is a pollutant. CO2 has even been shown to adversely effect photosynthesis in concentrations that could exist atmostpherically.
So, not pejorative really is it? Bigot? Prejudiced? Give me some facts and I'll consider them.
Do you really think we can just pump out CO2 and everything will be just fine? Why dont you try 1% CO2 in a sealed room for a few days, and see how you feel? Maybe you already have.
Yeah yeah. We get it. No smoking gun. Again.
The science is constantly being refined, but we have to work with what we have. We may also have to accept there may not be a smoking gun moment within a timeframe that allows the science to catch up and for us to not have broken things irrevocably in the mean time.
Do you think that we can endlessly pollute (with whatever the pollutant may be, CO2 for the sake of argument) with no consequence? Is it worth taking the chance?
....only a rucksack is versatile enough for a one bag option. As soon as you put any weight in a man-bag it either slips from your shoulder or garrottes you (depending on how you wear it).
Not forgetting of course, that you cant use a man-bag to barge tourists out of the way on the tube.
If you couldn't guarantee it's provenience + authenticity, then it was a dodgy piece of code. This isn't a PI. A PI has robust development with specific goal - education. This is a cheap, generic board piggy backing off the PI brand.
Put my backups on it. Not a chance. Your mileage may vary of course.
Could be very useful, the problem may come if MS decide that this doesnt work for them any more. Ok, they can't 'un-open source' but they can close off any potential development routes that might conflict for them. That may hurt someone who has gone wholesale into .net because of this.
Another option opens up, which is a good thing.
The 3 of them are as bad as each other (MS, Google, Apple) but I'm just finding all a bit tedious with Apple. Yes, the hardware is better then other mainstream manufacturers. Yes the OS works well and generally stays out of your way. Yes there are native apps that let you be productive. Yes I like the battery life. However If you want to send my data somewhere other than my computer then bloody well have the manners to ask (in a clear, non sneaky way). I might even say yes if I think it benefits in a 'larger' non direct sense.
I thought Little Snitch was trying to tell me something....I guess I should have paid more attention.
While I'm in rant mode. Stop soldering RAM. It's unnecessary, makes more landfill and makes you look cheap. I get that the standard soddim connector takes quite a bit of space, but soldering as solution. How very 1986.
I guess I'll start toying with Linux again to see if there's a setup I can work with, but I really dont want to have to. Any suggestions on comparable hardware to a MBP 13" that can take 16GB of RAM? I'll probably fail and continue as I was.
"You! Yes! You behind the bikesheds! Stand still, laddie!" Get back in line and stop complaining.
Edit - Oh, and dont worry, your fingerprints are safe with us.....
Absolutely. This is the last hurrah of the original licensing and regulation back in the 80's when the networks were split from service provision the end users. This led to a whole raft of independents which did very well while it lasted. When the regulations were changed in the mid 90's all of the independents were essentially doomed. The networks brought the service providers back in house and made it the primary route to market (Vodafone/Vodac for instance). You only have to look at the number of network owned retail outlets vs the independents to realise that the writing is on the wall.
'It really isn't - and it doesn't' - It may or it may not come as part of the subscription. It depends on what you sign up to. Office 365?
'Much better stack' - matter of opinion, and not really the point.
'Better integrated' - Well you'd hope so wouldn't you, but then the differences in user experience are tiny (if you've got it set up right).
'No signs of that whatsoever in the corporate space so far.' - Agreed, but because there isn't a viable alternative single stack, which is what I was trying to get at. The components are all out there in one form or another, someone just needs to bring it together. Cisco, Oracle, HP or whoever. Cisco does seem to be moving that way.
Always thought that Red Hat would be in Ciscos sights for either a significant partnership or acquisition.
1. An alternative vendors SDN on Cisco hardware is never going work for Cisco.
2. RHEL is already the default OS for Cisco apps.
3. Cisco need to counter the MS desktop ownership to keep driving UC.
Not controlling the hypervisor and losing control of the SDN element is a hard enough for Cisco, but it goes further than that. In the Desktop/UC space a significant driver for Lync adoption is 'because it comes with our subscription' (whatever form that subscription that might be) . The only effective way to counter that it with an alternative business application stack, and that starts with the OS and office suite. Ok, there is so much legacy in Windows that it won't be an option for a lot of people, but just look how fast the application space is moving. It's phenomenal. I think significant numbers of people will find themselves able to move away from Windows if one of the top players providing an 'easy' to use cheap alternative.
Most of the alternatives apps are good enough for most people, what's missing is a single office suite with the core MS Office has. Currently the major missing component is the integrated calendar + email in a single package. I know there are alternatives and it's possible to DIY, but most people don't want to have to spend all the time and effort. A single installation and integrated package is what people want.
If Cisco (or anyone else) can bring that 'base business stack' together, I think Microsoft have got problems (bigger problems!).
Sometimes quite a bit, sometimes not a lot.
A NAS is always attached to the network where the storage sits behind a controller that has two halves. The first half looks after the disk array (JBOD/raid or whatever). The second half is the network side that presents the disk array as an NFS/CIF type share. The clients (which might be a server) are never aware of the disk topology that supports the share.
A SAN can be network attached, fibre channel attached or a number of other technologies that connect the disk array to a host. This attachment is usually through some sort of fabric/network that abstract the array from the host. It is this network (FC, FCoE, iSCSI etc) together with the storage and host interconnect that makes up a SAN. Sometimes the host knows directly about the disk array, but usually it doesn't.
Some NAS boxes can also do iSCSI or Fibre channel which is where you get overlap. Sometimes they are configured to do both simultaneously.
I think that makes sense....Hope it helps.
Biting the hand that feeds IT © 1998–2020