Monday, 11 July 2016

Windows 10 Insider Hub App: Two Years On

Back in August 2015 I wrote an article about the 'Insider Hub' app which was available to Windows Insiders. 


Today, one year on in July 2016, I'm revisiting the same article with another look at the hub app, which is now retitled the 'Feedback Hub'. 


What's changed in a year? Sadly, not a lot. 

The SAME issues I wrote about a year ago as being the most disappointing and annoying aspects of the Insider Hub still reside in the Feedback Hub. Despite words of encouragement from Microsoft for all Insiders to be excited about the actual feedback aspect of the Insider Project, very little has moved on and been developed.

An Introduction to Insider Feedback

I used the definition from The Oxford Dictionary for the word "hub" in last year's article, which defines it as being "The effective centre of an activity, region, or network". 12 months on, and this definition is STILL likely to make many insiders laugh out loud.

Whereas Windows 10 itself has developed from the original v1507 release on to v1511 and to the soon v1607 version which has some rather noticeable visual and background changes, the actual feedback nature of the Insider Programme, from an actual Insider user perspective, has changed very little. 

If the 'Insider Hub' and 'Windows Feedback' apps were version 1.0, then what we have now, with both apps combined into the 'Feedback Hub', could be seen as v1.5. Realistically, almost coming up to 2 years on from the creation of the Insider Programme somewhere around October 2014, we should see any Insider Feedback app as version 3.0 by now in terms of its evolution. Sadly, the feedback aspect has not kept pace with the development of Windows 10 itself.

The UWP platform hasn't taken off as hoped for by Microsoft or its fans, but it has at least seen some noticeable transformation over Windows 10's lifetime, with the main system apps now genuinely useful, quite stable and aptly supported by the much better Windows Store (at least the one in v1607).

The Insider Hub was supposed to be the heart of the Insider Programme. Something we'd use each day, immersing ourselves with it in terms of feedback that goes two-ways with Microsoft & fellow Insiders. All the latest news and information about Windows 10 development would be in the hub, where we'd be given specific quests to perform and providing results that were tangible and rewarding for us performing them. Sadly, that's still not materialised, with the quests almost feeling like a chore at best, or, at worse, completely irrelevant to the device we're on. This is further evidence about how far the actual Insider feedback aspect of Windows 10 is the lagging tremendously behind the OS.

The Feedback Hub is nowhere near the heart of the Insider Programme, but lingering more near the belly button, for it's as much use as the fluff we inner-belly button people find on a daily basis. As each day ends, we find fluff that looks exactly the same as the previous day, is of next to no use to us, and will be back again the next day. Nevertheless, much like the heart still is, the belly button was an integral part of where our body originally was fed but, unlike the heart, the belly button is now a fossil, going nowhere. The Feedback Hub feels similar in terms of treading water.  

The Feedback Hub has improved over time in minor ways, much like the Action Centre has started to become more useful and interactive from v1607 onwards. But, it's STILL not the pinnacle of Insider Information & Interaction. That source continues to come largely from Twitter, via the new Insider Chief Dona Sarkar (replacing the brilliant Gabe Aul) and the large decent number of Microsoft Employees who also reside on that social network. Want to find out about fixes, feedback and future possible changes? Head to twitter or 3rd-party windows news sites, because as sure as sure, you'll get little to no early information on developments or details about your feedback from the Feedback Hub.

The Feedback Hub continues to sum up what I said about it in 2015, which was that most Insiders might feel their feedback relationship with Microsoft is akin to being their poor cousin; they only come to us when they want something, and then we don't see them again for years, and we have no idea what they did with that present we gave them.

Microsoft are taking telemetry data from our Windows 10 PCs by the barrel load, which we are knowingly & willingly providing, but what do we actually know about that data? We know something (click link for my telemetry article) but still very little. To the most part, if you're talking about Feedback and the Feedback Hub, we probably know just as much about the telemetry as we do with our feedback via the hub, in terms of actual submitted feedback items, and, yes, those ruddy quests. That is, we know very little. We hear pint-size portions on feedback responses or have to wait weeks to hear anything via the hub. Microsoft themselves are combing through our telemetry and feedback on a daily basis, making decisions on that data and then producing actions or crossing items off their list. 

What do we hear about Microsoft’s current thought process and decision making based on OUR latest feedback? Nothing.

When do we find out if that feedback request or bug is getting any attention? 

The answer is ... When Microsoft want us to know ... or if we badger a Microsoft employee on twitter.

The ONLY time we get any tangible information about our feedback via the hub is from the "Made By You" articles which are often months behind the times, or when new builds come out and we see things like "We fixed that problem you were telling us about". Yeah, thanks for that Microsoft.

"We're listening to your feedback" is what we're told by Microsoft. Yes, they might be listening, if listening means trawling through feedback items and telemetry data, but this Insider thing was supposed to be a lot more two-way than that wasn’t it? It's extremely hard to believe that Microsoft are listening to anything we say about issues we’re having, or feature changes we all want, when there are so many examples of that not happening, or us not knowing they are listening until they proudly tell us they have, many months after we all starting moaning at their feedback brick wall about something.

Anyhow …

Back to the actual app, the Feedback Hub, and what is STILL annoying about it a year on from my last article about it, and two years on from the birth of the Insider Programme.


1. Announcements


If you’ve got an app as a hub for a specific purpose, you’d expect it to be where you’ll find out not only everything about the subject matter to which the hub belongs, but also the place to find all the latest news. When it comes to the feedback hub, you’d be wrong in thinking that. Perhaps it’s no wonder that it has been renamed from ‘Insider Hub’ to ‘Feedback Hub’ because it doesn’t really feel like a hub for insiders but somewhere us minions go to continually submit further information to Microsoft without hearing anything back.

Being a hub, you'd expect the announcements section of the app to be pouring daily-ish with the latest news in terms of how everything is progressing and the latest on our feedback, yet aside from being updated with information on build releases, and occasional team member profiles or “Made By You” articles, there's no other news to report that's of any interest. 

It’s also debatable how interesting the information that appears there is anyways. All the build information also appears on the Insider Blog and then naturally on numerous Windows Technology blogs, so it’s hardly unique to the app. May as well just whack a url link to the blog for all the special love to Insider’s that the build news provides us in the announcements section.

In fact, if the announcement feed came straight from the Windows 10 blog, it'll be much more interesting, but instead we get a drip feed of build news, random updates about apps when they feel like telling us, and the news that all insiders would never ask for if we were tortured; Microsoft Employee Bios ...





Yes, it’s interesting to know who works in the Windows 10 teams, and they are all of course lovely people in varying ways, but the actual information reads more like a dating site advert than anything relevant to Windows 10. We want to know EXCACTLY what they do with Windows 10, not what their fav food and hobbies are.

The Hub Announcements section should be crammed full of the latest Windows 10 development information, yet it barely scratches the surface of what an invigorating relevant news feed should contain.



And what about the ‘Known Issues’ filter available in this section? A year ago it was largely empty and useless. Now at least it’s not empty, because every time a build is released the known issues with that build are tagged with the ‘Known Issue’ category. However, this isn’t what any of us Insiders were expecting from this. At the bare minimum we’d expect what we currently have, but this should be the busiest part of the app when it comes to announcements because there are always bugs and issues that are ongoing with any build which Insiders may or may not be experiencing. We want this filter to be banging out the latest information on any issues on a daily basis, not waiting for builds and then having this section remain static until the next build comes around. You'd expect to know about all known issues at the touch of a button as an Insider, given we are providing the most feedback, but no. 

As said a year ago, the hub should be the first place for information on Windows 10 and insider news, but we all know that the juicy stuff is anywhere but in the hub. Thus this part of the hub has quickly become irrelevant and one that no serious insider, of which most are, would bother to click on.


2. Quests


Don’t get me wrong here. I love the concept of quests. They get us insiders to interact, learn about Windows 10 features, and provide direct feedback.

However, something has gone seriously wrong with Quests since the inception of this app. They are literally all over the place in terms of relevance, skill level, readability and … well … why are we bothering to do them?

Far too often, clicking on the quests section of this app has become something of a chore. As said a year ago by myself, out of everything I heard about the Insider Programme when I signed up, Quests for the most part have been up there as the most unsatisfactory side of being an insider.

A year ago I’d completed about 49 quests since the insider programme started up. Currently, 12 months on, I’m at 107. Within this period nothing has changed with the issues that these quests induce upon us insiders. It’s a real shame that the feedback hub is full of the same complaints time and time again about Quests but nothing is changing. 

The problem is that the vast majority of quests are STILL either childish, pointless, or behind the times. They also range wildly in terms of complexity from the simple, like opening an app, to the complex, like the equivalent of writing a C++ program to interact with NASA. Yes, they still can be that complex, especially during Bug Bashing periods. Sure, those bug squashing quests are supposed to be to iron out issues but I’m surprised by some of them that such information isn’t already being transmitted via telemetry data. 

The ONLY noticeable change to quests in the last 12 months is that there tends to be more of them and that the complex ones can have a little extra header to warn the user that they are for advanced users. The readability of the instructions within advanced quests though is often impossible to follow. Who wrote these? Did they test them with someone else first?

The main problem with quests for me, two years since they began, is that there is STILL no personalization in them. We can’t tell Microsoft what subject matters we’re interested in, or levels of complexity we’re willing to perform. We just get a dump of all quests to trawl through. Worse still, and I REALLY CAN’T BELIEVE THIS HAS NOT IMPROVED is that the quests we’re getting have NO idea of the device we’re running the hub app on! They ask us to do things we can’t do because we don’t have a touchscreen or the right flavour of Windows 10. Seriously Microsoft, how difficult is it for you to filter quests based on the device we’re on? Don’t tell me it’s difficult because you don’t know what device we’re running. You have our telemetry data and can use the app to look up basic system information on the fly. Why do we get irrelevant quests still? This is basic configuration stuff, surely?

Then there’s the problem with some of the subject matters of quests outside of Bug Bashing. They can feel like something that was discussed in the AOB section of a Windows 10 Insider meeting, with someone saying "Yeah, guess we better do something" and then someone being forced to make something up. Go check out this part of a Microsoft website or app. That’s not my idea of a quest! 

Another major problem with quests is all about reward. Jason and the Argonauts went on a quest for a reward. That’s mostly what quests are for, right? I suppose there’s the learning experience? Don’t tell me we get a badge in the achievements section or I’ll scream. Besides, we don’t get a badge for every quest. I’m somewhat thankful for that.

What is the reward for the insider for doing a quest?

There’s none really. We go through the instructions, click submit, get to rate something between 1-5 and then provide a free text feedback comment. Click submit and off that goes into the internet and into Microsoft’s DB where we hear absolutely nothing back. 

How many people did that quest? What rating did they give? What was the most popular comment? What conclusions did Microsoft make from that quest?

These are all the basic rewarding information us Insiders would expect from a quest but we hear absolutely nothing back about our efforts. 

The idea of quests is good, but the payoff seems to be heavily weighted against insiders, not least with some of the ridiculous quests we've been given and that there is no real incentive to perform them because we hear absolutely no feedback on our efforts. 

I really wonder what the point of even bothering with quests is anymore, and that’s a sad stage to have reached.


3. Rewards


Those who read my article last year will know that issue 3 was originally about the ‘alerts’ section of the Insider App. Thankfully that has been changed in the course of the year. Yes, it’s gone! Alerts are history. Thank goodness for that. So, issue number 4 from last year becomes issue number 3 this year.

Related to the lack of rewards that I was talking about from quests, we get to the section of the app that is all about making Insiders feel special and worthwhile to Microsoft. 

First up, we all know the biggest reward Microsoft gives us is the opportunity to be an Insider and get those new builds. That’s what we’re all here for, so thank you very much Microsoft. That aspect of the Insider Programme has been a tremendous success and we appreciate it.

However, let’s look at the achievements section of the Feedback Hub once again. I said it a year ago, and I’ll say it again. I grew out of wearing badges when I left the scouts many years ago. But at least those badges I earned had some relevance, like knowing I could tie a knot or make a tent. Insider achievements are so basic and worthless, that I’m surprised there's not a badge for logging into Windows or being able to turn off the computer ...



Last year I had 11 badges. This year I’m up to 14 and I feel most of them I’ve actually not really earned.

We got a badge because Microsoft released Windows 10 and then v1511. Soon there will be one for v1607. Now, I’m happy that Microsoft have released these updates, but as an insider what did I actually do towards it? I don’t know, do I, because there’s no feedback on my suggestion/problems submitted or from the quests I’ve performed. If there was, then I might feel like I had a small part to play in matters although I didn’t actually do any serious work towards manufacturing the Windows 10 OS.

Out of the 14 badges I’ve got, maybe only a handful feel relevant even two years on. I still can’t get over the ridiculousness of some of the badges that I moaned about last year. I'm a trendsetter because someone has upvoted a piece of my feedback by at least 10 votes? Great, so a few people agree with me, and what? I've started a revolution? I'm a feedback phenom because I've submitted over 50 items of feedback, yet isn't that what we're supposed to be doing? I know Microsoft is getting telemetry data from us all the time, but wasn't part of being an Insider so that we feedback information? 50 items should be a drop in the ocean compared to how much we should be letting Microsoft know about an OS that is big money for them.

Let’s look at the two of the three new ones from the last 12 months. They are about the Bug Bash which I did some quests from, for my sins. I can sort of agree with having those badges. The bug bash was specific and special for Microsoft and I did set aside time just to participate in it. The only other new one is about the shipping of v1511, which as I said before, doesn’t feel like I had much of a part to play in due to any real responses to feedback or quests.

After earning 10 badges in the first year for just turning up and doing my job as an Insider, only 3 in the second year? It feels like I’ve done absolutely nothing doesn’t it! Have Microsoft forgetting about earning badges? They were giving them away like sweets originally.

Aside from rewards, what about incentives? Still the same problems from last year … 

“The incentives for being an insider are low, and these badges really summarize it in graphic form. To celebrate Windows 10's release, Insiders were offered a discount at the Microsoft store, but only if you lived anywhere near one, of which most Insiders probably haven't even seen a Microsoft store, except for that icon in Windows 10 (and the discount wasn't for the app kind of store).” 

Microsoft, if you’re going to give us incentives and discounts, please make sure that the majority can actually benefit from them, or just don’t bother.


4. Feedback is still one-way


Two years on, and after some serious talk about changes coming to the Hub, we’ve only seen two major changes from an Insider’s perspective in terms of the visual aspect of the app. 

The separate feedback app got integrated into the Insider App, which makes a lot of sense for the Insider Programme. That was a positive change. 

Then they introduced the first aspect of trying to provide more interaction between Insiders and Microsoft. We’ve now got comments for feedback items. Woop Woop. Finally. We can converse with other Insiders. Fantastic! Well, it would be if it was considerably more useful. It’s so fiddly to use that it’s disappointing. If you comment on an item, you can’t specifically reply to someone else’s comment, but just add to the conversation. Worse still, after commenting you’ve no way of finding that comment again at a later date unless you take a screenshot of the item and search for it. Comments are like throwaway words. I’ve no idea what items I’ve commented on, or if someone agreed or disagreed with what I said because there’s no way to open up the feedback section of the app and filter just for your comments. I’m sure it’s coming but why introduce something that makes it so hard to find what you just did? It’s like writing a Word document without the ability to name the file and put it where you want on your computer. 

Then there’s the long awaited Microsoft response aspect of feedback items. Yes, Microsoft themselves can now actually mark items as being looked at or resolved, or give a few carefully construed robotic sentences of response. The latter feels worthless as it’s often just the same old thing. “Thanks for that suggestion. We love hearing from you. We’ll think about it”  … Yeah, right. 

Just like the issue with finding your comments on items, you try finding items where Microsoft have marked it as anything other than “We’ve received this”. They are hard to find in the first place, and impossible to find quickly. It really shouldn’t be this difficult to find out what Microsoft’s response is to feedback items. Because it’s so tedious we’re left feeling as most have for the last two years, which is that feedback is really only one-way. i.e. heading into Microsoft’s laps where they keep it to themselves until they decide they want us to know what they think. If they have a negative view on some feedback, they’ll probably not tell us. If they have a positive view they’ll tell us eventually months later, and probably paint it up as they are listening to us. Sigh.


5. Hub isn't a community STILL


Two years on and the hub is still not the focal point that it should be for insider information. I said it a year ago about what should change, and at least the feedback app has been integrated as I suggested but the hub needs a lot more to make it feel like an Insider community. There’s should be RSS feeds from all Windows 10 blogs, the insider forum also should be integrated into the app to make it feel more like a community. The hub feels more like the welcoming sign to somewhere, which you only take any notice of the first time you visit.

The hub continues to provide data to us on things we do, which is interesting, but this information has almost become meaningless to any insider who has been on the programme for two years as it’s the same information updated with no real conviction behind the numbers.

 

I’m still the best with feedback a year on? Hah, beat that fellow insiders! 

What’s that you say? The app also tells you that you are the best? I thought I was Microsoft’s favourite?

See what I mean? Why provide us with numbers that go nowhere? How do I compare to all the other insiders? I know I’m not the best. I’m not that brilliant. Make these numbers mean something by telling us how we rate in relationship to fellow insiders. Make the numbers even more relevant by telling us how much of our feedback was useful. How much of it was related to known issues? How much of it did you actually use and make changes from? Where is the feedback on our feedback?

We know we've given lots of feedback, but what any of it meant to Microsoft is unknown. Perhaps it meant very little. That's what it feels like, as we don't get an indication of its usefulness all that often, that aside from that odd mention in a build's release notes, it's the only time it's actually mentioned by Microsoft. Even then it apparently seems that Microsoft only value the top 3 or so things that we feedback about, because that's about as much as they ever let on about using our feedback.

Finally, there's ‘Devices and Activity’ in the Feedback App. LOL. What has happened to this? A year ago I wondered what the point of this was. "Activity", what did that mean? Was it referring to having the computer turned on, or what we've actually done with the build, which could be just to run a screensaver all day? And what devices does it refer to?

Oh dear. Oh dear. This part of the app has gotten even worse. Many builds ago, it stopped working reliably, and now instead of telling us hours of use, it just displays the version of the feedback app:



So many items of feedback about this not working and nothing from Microsoft. You’d expect something in the announcements section of the hub app wouldn’t you? Well, you would. But don’t be daft. That would mean Microsoft would have to be reactive and responsive with our feedback. That just doesn’t happen.



So, the final word ...


One year on from my last hub article. Two years on since the start of the insider programme. 

The first part of my summary remains largely unchanged from last year so I’ll simply be regurgitating it … albeit with some minor updates before we get to the juicy section at the end.

“In summary, the whole Insider experience had excitement oozing out of my mouth two years ago, and the enjoyment of using new builds has been largely just that ... enjoyable. For most insiders that might be enough, but it's not for those of us who place value on the time we take to use something and provide feedback. We need to know that what we're doing is worthwhile. We need to feel like we're included, and not just thrown some treats every so often in the form of new builds to lap up without any thought or reason behind our time spent using them.

Any insider who is in the IT industry with both feet, will know that whatever they do, they need to know its delivering results. The checkout counter assistant knows they are doing their job well, because people are coming by their till throughout the day, they see their expressions, and they hear their words ... and their boss isn't moaning at them. We insiders are simply checking out builds in the same way, but it's like we have blindfolds on, because we have no idea how our customers (Microsoft) feel about our performance.”

So, two years on, I still feel exactly the same, as the last year has seen extremely little attempt to change my views on being an Insider and providing feedback. I’ll continue to provide feedback but it’s getting harder to enjoy as every build arrives. What’s the point, it feels.

Development of the Windows 10 OS progresses at a reasonable pace and is of course the main part of the whole Windows Programme. But, why have Insiders and then keep them at arm’s length? The Insider aspect of Windows 10 has seriously lagged behind the pace of the OS development. It’s so far behind now that I feel that it’s still stuck on v1507 of Windows 10, rather than about to enter v1607. 

Two years on and Microsoft has continuously failed to step up to the plate with the Insider Programme. Thus far one feels more like an outsider than an insider.

Something needs to change and quickly. Extensively more focus on the hub app is needed to make it what it should have been by now. Perhaps "ranks" of insiders need to be created by Microsoft, where the most "basic" of insiders simply just play with builds and don't care what happens with their time, with an "expert" rank of insiders encouraged to use the forum, spend time on quests, talk to Microsoft and have interactions with Microsoft employees to understand and know that their feedback and issues are being listened to and being used to improve aspects of the OS.

With millions of people in the Insider Programme it should feel like one big family that's in constant contact with each other, and feeling the love. Sadly, it all too often feels nothing like a family, but that we've all been squashed into individual rooms in the same hotel with no idea of what's going on in the bigger picture.

We submit feedback items but don’t know what happens to that information. Was it useful? Did it help? Did you do anything with that information? 

We submit feedback surveys but we don’t get the results to know how well everyone else on the insider programme thinks things are going. What did everyone want to change? What did they like or dislike? Microsoft keeps all this information to themselves. It would have been a great opportunity for Insiders to interact more with other insiders in terms of knowing what each other is thinking. 

We complete quests but to what end? We don’t know how many insiders do the quests, how they rated them or what Microsoft deduced from the results of that quest. Tell us! We want to know. We want the quests to mean something to us.

“We’re listening to your feedback” says Microsoft a lot. It’s time to prove it in a real tangible way by letting us know the results of feedback quicker and with qualitative information

Why can’t we have an Insider Feedback Blog integrated into the app, where every month the main sections from our feedback in the hub are written about by Microsoft. I want to know what’s happening to the top items in each section, the items trending in the last month. What are Microsoft doing about them? Anything? We don’t know. It’s like we’re submitting feedback against a brick wall. Perhaps we’re merely writing graffiti on Microsoft’s wall and only get feedback when they come to clean it up? I’m fed up of waiting for “Made By You” articles that are months behind the times to tell us what they do with our feedback.

I said it last year, and I say it again …

Microsoft, are we insiders, or outsiders?

Does our feedback mean anything to you?

If the answer to both is yes, and one assumes and hopes so, you’re seriously overdue on making the insider programme mean something much more than it is, and for feedback to work both ways. Do something about it, and soon!

Thursday, 19 May 2016

If Microsoft gave the UWP treatment to the car ...

Coming Soon! 

Microsoft will announce a surprise addition to their ambitious plans to turn everything into a Universal Windows App. Because nothing is sacred and because, quite frankly, they can, Microsoft have released a insider preview of their UWP version of the humble automobile. 

Yes, they’ve given the vehicle we all know and love, which gets us from A to B, the universal treatment, apparently for no good reason at all. Still, what we get to look forward to is a car that will bring a consistent and responsive approach no matter what Windows 10 device it’s used with, be that mobile, PC, HoloLens or Xbox.

Head of Product Development for this new ground-breaking app, Dave R Watson posted on the official Microsoft Windows 10 blog about the excitement the new app generated inside Microsoft. They say it’s incomplete at this early stage but that it’s more than good enough for insiders. They hope to gain initial feedback on what insiders think, if they find any bugs, and if they have any features they’d like to see.

As you can see below, it’s already available in the Store for insiders to download, and yes, if you can spot the obvious elephant in the room issue, we’ve got the reply for Microsoft’s Head of Product Development for you.




“Yes, we know it’s missing all its wheels ..., “explained Dave slyly. “… We hope to literally roll out its tyres in a future update. However, we didn’t think that would get in the way of insiders getting an early look and an opportunity to wander around what is a responsive and feature-rich interior.”

If you want to get hold of this app it’s up now in the store although the initial release is listed to have only the following features:
  • Edit the interior of your car.
  • Easily share your car’s engine, seats and other internal luxuries with friends and family.
  • Upload your car to Sway or Photos app.
  • Live Tile (see live values from your car's air-con!)
  • A universal app that’s responsive across all your Windows 10 devices.
Of course, it didn’t take very long for insiders to try out this new universal app and start up voting via the feedback hub what they want to see.

The following is a selection of the latest and most popular comments:



















Tuesday, 17 May 2016

Eggheads: How to improve the show

I love the show. It passes half hour whilst munching away on my dinner. Plus, unlike mastermind, i stand a good chance of answering or at least guessing the answers to the questions. However, the show is quite dry and simple. The latter helps everyone follow it along nicely and it'll likely never ever be significantly altered in format as it runs for the next 20 years. But, if I could have my way for five minutes and make some changes that I reckon will improve the show, this is what I'd do.

Bring back the Egghead's introduction


"Hello, my name is Chris Hughes. Now, back in 1980 ..."

I loved hearing the Eggheads introduce themselves. It never took up much time and gave us all a decent nudge to remember how they got to be on the show and their credentials.

Then, for some reason, this was ditched.

Suddenly it's not important that we hear their CV and get to empathise and relate to the legendary Eggheads. Yet, we have to sit through listening to the opposition for almost a minute, whom we've never met before.

The Eggheads are the show. We should hear more from them and not just little chit-chats every so often when Jeremy Vine doesn't understand an answer to a question. It doesn't have to be long, just a quick "Hello, my name is x. I got all these x quiz awards etc. Away from quizzing I like to x."

We don't get to nearly enough interact with the Eggheads, which is a big shame in my book.

Tension


It's so quiet in the studio that you could hear a pin drop.

It's so dry that you are surprised a camel doesn't walk along every so often, followed by some tumbleweed.

I'm not asking for much. I don't want the Who Wants to be a Millionaire light-show or drums beating away like everyone is about to be eaten by cannibals.

All I'd like to see is a little chirpy sound to indicate an answer was right or wrong, some gentle background tension music when we go to sudden death, and maybe a little shifting in lighting to make the final general knowledge section seem just that little bit like it really matters.

This would all combine to make it all feel like this is something more than a family quiz over the dinner table and that it's a contest between minds. Plus, there is money on the line, our UK license taxpayer's money, and it should mean something to those playing and us watching.

So, lets use a little technology to make it seem like there's money up for grabs here, and that getting a question wrong is more than a little inconvenience.



Eggheads: TOP Jeremy Vine Annoyances

1. The Question is, can they be beaten?



It's not really much of a question that needs answering to anyone who has watched the Eggheads for at least a few weeks. They do get beaten, and have been beaten on numerous occasions. Sure, they don't lose that often but it's not like they are undefeated for years on end.

The question should be, when will they be beaten next?

2. Would you like to try?



No Jeremy, we wouldn't. We came on to this show purely to introduce ourselves, get a few seconds of TV fame and then bugger off home!

What exactly does Jeremy think they will say to answer, other than yes?

A better question would be, are you ready to have a go?

3. The Eggheads look worried



Jeremy is clearly not a psychologist because the Eggheads never look worried, scared or anything negative during this show. They might possibly look like they are having fun, or sometimes positively bored stiff, but worried or scared is certainly never something they look.

4. I wonder who will beat you



He may well wonder, and so do we all, but let's not bill them up as being impregnable because all sorts of people have already beaten them. Probably a better end question would be, When will you lose next?

Monday, 9 May 2016

Windows 10 Telemetry: What we do and don't know


Since Windows 10 rolled out many people have been shouting at the top of their voices about how Windows 10 is somehow stealing not only our data but probably our soul at the same time. The Privacy settings in Windows 10 tell Microsoft information about you specifically, so that your Windows 10 experience improves as it learns about you and can make things even more intuitive and magical for you as time ticks on. For example, they let you control what access apps get to your data and can help Cortana learn more about you. Telemetry, on the other hand, isn’t so dynamic in terms of it leaving your computer and later magically changing your Windows 10 personality overnight. It’s largely a one-way stream of information departing your computer and heading to Microsoft HQ for them to analyse. They use it to discover issues people are having with Windows 10 that they can then either fix or enhance in future updates.

It’s worth remembering that there is other software on your computer other than the actual OS collecting telemetry of varying sorts all the time. Microsoft Office has its own telemetry settings, so does Windows Update and Defender. Most 3rd party apps will send various statistics and diagnostics back to their respective HQ, although usually these apps have a setting to turn telemetry on or off.

Disclaimer: I'm only human and also dyslexic. I try my best to read and write accurately but I make mistakes and my enthusiasm can sometimes cloud fact. This is also a hobby, not a job. Please do check official documentation yourself to be sure I've got things right.

What do we know about telemetry?


  • In its documentation, Microsoft refers to a “Connected User Experience & Telemetry Component” (hereafter referred to as just the telemetry client) as the mechanism that’s used in Windows 10 to supply them with information about your device. This suggests, as one might expect, that there is a kind of client running in Windows 10 that controls all aspects of telemetry.
  • This telemetry client updates it’s settings from Microsoft. This suggests that what the client is set to do can be dynamically changed by Microsoft.
  • Reassuringly, all Telemetry data is encrypted during transfer to Microsoft.
  • There are 3 telemetry levels you can set your device to; Full, Enhanced and Basic. If you are running Windows 10 Enterprise, Education or IoT OS versions there’s also a security level, but for us consumers it’s just the three. If you’re using an insider build you are automatically locked in to the full level.
  • The telemetry client service name is called DiagTrack (Display Name = Connected User Experiences and Telemetry), so assumingly one could just turn this service off to stop telemetry?
  • The telemetry client process name is utcsvc. So if you want to monitor what goes on, this is the process to follow.
  • The telemetry client stores its data in folders under C:\ProgramData\Microsoft\Diagnosis
  • Data sent by the telemetry client is claimed by Microsoft to be about 1.2k in size.
  • On a PC running at the basic telemetry level, tests by Ed Bott suggest that data transmissions occurred 32 times in an eight hour period.
  • There’s no official off switch for the telemetry client (aside from disabling the service) but you can control the level of telemetry sent back to Microsoft by toning down the level. The telemetry level at its lowest level is “Basic”.
  • At the lowest level of “Basic” you’re still sending a lot of information about your device to Microsoft. The word “Basic” has a considerably higher baseline than it might appear. The documentation says “device info” is sent to Microsoft at this level, listing Internet Explorer/battery/networking/processor/storage attributes as examples. On top of that, info about all the applications (apps and win32 software) installed, performance and reliability data, hardware attached to your computer and information about your network and connection is sent to Microsoft. It’s highly likely that, at the very least, the sort of information you find in “System Information” (msinfo) Reliability Monitor, Resource Monitor and Performance Monitor is heading to Microsoft at this “Basic” level. 
  • In its documentation about the telemetry client Microsoft frequently makes use of the words “including”, “such as” and “some examples”, which all implies that the specific information they’ve listed as being collected by the telemetry client isn’t comprehensive or complete. There’s highly likely to be considerably more information being sent to Microsoft than what they’ve outlined.
  • At the “Enhanced” level, everything in “Basic” is sent to Microsoft as well as extra information about how you interact with the OS and apps. The wording in the documentation suggests that only specific events related to problems regarding apps, the OS and certain devices are sent to Microsoft. However, they aren’t clear on what “events” really means. They could be the frequency or the length of time you use a certain feature or app but it’s all somewhat ambiguous.
  • If the telemetry client detects a problem with an app or OS feature on your device it’s possible that the information sent to Microsoft might happen just the once at the time of the specific event, or for up to 2 weeks.
  • It’s possible that at any of the three telemetry levels, although specifically enhanced and full, that personal information might be sent to Microsoft. I.e. if the app or OS crashed whilst you had a file open or was surfing a webpage, then the telemetry client would send some of that information to Microsoft. However, any personal information will not be used to identify or contact you.
  • At the Enhanced level, insider devices will send back specific information about pre-release binary and features so Microsoft know how well those new build features are performing.
  • At the Enhanced Level, Microsoft Engineers can ask the telemetry client to run further diagnostics on your device, including gathering personal content and registry keys related to the specific problem your device reported, so they can investigate the issue.
  • All information gathered by the telemetry client has to comply with their security and privacy policies as well as laws and regulations. Only a limited number of employees at Microsoft are allowed access to telemetry info.
  • If you have set your Wi-Fi connection as a metered network then not all telemetry data will be sent to Microsoft. Diagnostic Data, Crash data and “Normal” events are specifically stated as not being sent on metered networks.
  • The telemetry client (on non-metered networks) will send real-time event information immediately but other information is normally uploaded to Microsoft every 15 minutes if you’re connected to A/C power or every 4 hours if on battery.
  • Some telemetry information is only kept by Microsoft for 30 days but there is other data that is kept longer if it’s needed to provide a service and future analysis.
  • It’s possible that telemetry data will be shared with Microsoft vendors & agents but they must abide by privacy and security policies and are not allowed to use personal data for any purposes.



What don’t we know about telemetry?

  •  How often does the telemetry client update its settings from Microsoft?
  • What information is in the settings data that the telemetry client obtains from Microsoft?
  • When and why are the settings the telemetry client is updated with changed by Microsoft?
  • How do we know when our device is sending telemetry data back to Microsoft?
  • When the telemetry client detects a problem with the OS or an app, what are the metrics used to determine how frequently the client will continue to send data to Microsoft related to that issue?
  • What’s the full list of information sent to Microsoft at each of the telemetry levels via the telemetry client?
  • What kind of the data does Microsoft retain from the telemetry client beyond 30 days?
  • What exactly does the data look like that Microsoft passes on to vendors and agents?
  • How do we know when a Microsoft Engineer is accessing our devices via the telemetry client and what they did?
  • How many employees at Microsoft can view our telemetry data? How many is a ‘limited number’?
  • Why can’t we turn off the telemetry client when most third-party applications allow you to do so? Sure, we could disable the service but there should be an official option to turn off the telemetry, plus, it's unclear what effect turning off telemetry might have on a system.

Saturday, 7 May 2016

Windows 10 Telemetry Documentation Latest

All information here is from Microsoft's Technet Documentation about Windows 10 telemetry, under this section https://technet.microsoft.com/en-us/itpro/windows/manage/index

This document lists the main changes I've noticed in the latest version of Microsoft's telemetry documentation, which is dated 6th May 2016. 

Disclaimer: I'm only human and also dyslexic. I try my best to read and write accurately but I make mistakes and my enthusiasm can sometimes cloud fact. This is also a hobby, not a job. Please do check documentation yourself to be sure I've got things right.

My Summary


There's new insight into how the telemetry client works in latest update. We know not only is HTTPS involved, but SSL and certificate pinning when data is transferred from us to Microsoft. More interestingly to me, it's stated that the client uses Event Tracing which will mean it's likely writing a log file somewhere. This is the same technology that they introduced for Windows Update in Windows 10 which requires a blooming powershell command to convert the log files into readable text!

There's a fair few nuggets for enterprise customers to chew over; unlike with Windows 10, Windows Server metered connections will continue to send telemetry as normal unless you've set telemetry level to lowest, which is the security level. It's stated that non-internet servers should be set to that level so they don't amass data that's going nowhere. At the same time they say that if you rely on Windows Update Services (and who doesn't?) you shouldn't use the security level as that level doesn't send telemetry on update success etc, meaning Microsoft can't improve quality of updates as they learn nothing. Regarding System Center telemetry, it says that at basic and security level, no system center telemetry is sent but makes it clear that the control for System Center telemetry is from within the product itself. Also worth noting is that the text suggests that the default telemetry level for Server OS is Enhanced. I'm not sure if that's new or if that's what consumer Windows is set to as well. I thought it was basic?

Consumer wise, the Retention section now suggests that a fair amount of data is retained longer than 30 days. Which makes sense in some respects as they do say they supply anonymised data to third parties and vendors. Would be hard to do that without keeping data longer than a month, right? Of course, they don't say what they do keep specifically.

Equally interesting to me, and somewhat expected I guess, is that if you run any virtual machines, they too will be sending telemetry back, including all the apps they have installed. They also make it clear about something I already suspected, which is that pretty much every aspect to the use of an app is recorded too. i.e. how long it's used, does it have focus and when was it started. You can bet they'll be more than those 3 aspects that they described here that they record.

Not a biggie, and somewhat also unsurprising, the text now says that they can take crash dump files too from your computer via telemetry client. This is done at Enhanced Telemetry Level.

The ability at enhanced telemetry level to take content that might include user sensitive information is now not in the documentation at all, but I'd be surprised if that means they don't do that anymore. Remember, this is only if the user files were involved in the issue they are investigating and they won't do anything with what they find. i.e. your info in a document are safe.

There's also mention that telemetry data is taken at a "fractional sampling rate" which can be as low as 1%. I don't really know what that means. Suggests that telemetry likely targets only specific devices perhaps? Also, doesn't say what the average sampling rate is, only what the minimum could be.

Actual list of changes:


Configure windows telemetry in your organisation


Overview Section

  • Makes it clear that the article doesn’t apply to System Center products as they use different telemetry service than Windows and Windows Server.
  • Overview section explains the forms of telemetry Microsoft used to take in previous versions of windows and windows server; Defender Signature, Windows Update, Reliability Analysis Service and using CEIP.
  • Overview section says Microsoft partnering with enterprises to provide added value from the telemetry information shared from their devices; i.e. app capability and driver reliability issues.

Data Collection section:
  • Completely reworded section, now with additional information.
  • NEW = Connected User Experience & Telemetry component in Windows 10 and Windows Server 2016 uses Event Tracing for Windows trace logging to gather and store telemetry events and data.
  • NEW = The Connected User Experience and Telemetry Components transmits over HTTPS and uses certificate pinning.
  • NEW = Enhanced & Full levels of telemetry is gathered at a fractional sampling rate, which can be as low as 1% of such devices reporting data.

Data Transfer section
  • Section has been renamed to ‘Data Transmission’.
  • CHANGE = Now implicitly says telemetry data is encrypted using SSL and uses certificate pinning during transfer. Before it just said data was encrypted.
  • CHANGE = The example it gives for real-time events that are sent immediately is altered from ‘gaming achievements’ to ‘Windows Defender Advanced Threat Protection’.
  • CHANGE = After saying that normal events are not uploaded on metered networks it now says that doesn’t apply if you are on a metered server connection.

Microsoft Data Management Service Section
  • Section title renamed to ‘Endpoints’
  • CHANGE = Opening two sentences changed substantially:
    • Used to say = “The Microsoft Data Management Service routes information to internal cloud storage, where it's compiled into business reports for analysis and research. Sensitive info is stored in a separate data store that's locked down to a small subset of Microsoft employees in the Windows Devices Group. The privacy governance team permits access only to people with a valid business justification.”
    • Now says = “The Microsoft Data Management Service routes data back to our secure cloud storage. Only Microsoft personnel with a valid business justification are permitted access.
  • NEW = Two new endpoints now mentioned:
    • Windows Error Reporting connects to Watson.telemetry.microsoft.com
    • Online Crash Analysis connects to oca.telemetry.microsoft.com

Usage section
  • Renamed to ‘Data use and access’.
  • Minor wording changes to all sentences but essentially saying exactly the same thing as before.

Retention
  • Mostly minor wording changes except last two sentences.
  • CHANGE = “Other info may be retained longer, particularly if there is a regulatory requirement to do so.” Changed to “Much of the info about how Windows and apps are functioning is deleted within 30 days. Other info may be retained longer, such as error reporting data or Store purchase history.”
  • NOT NEW (as I've subsequently realised but I'll keep it here anyway) = Added sentence here which was previously elsewhere “Info is typically gathered at a fractional sampling rate, which for some client services, can be as low as 1%.”

Telemetry Levels

Overview

·         CHANGE = Windows Server 2016 and System Center added to list of Oss that this section applies to.
·         CHANGE = Windows Server 2016 added to list OS that have additional Security telemetry level.

Security Level 
·         CHANGE = In first ‘Note’ where it says organisation that rely on Windows Update shouldn’t use the Security level, it now says that because Windows Update Information isn’t being sent at this level, Microsoft can’t use that information to fix causes of any failures and improve quality of updates.
·         NEW = Says that servers with default telemetry settings and no 
·         NEW = Says telemetry data about Windows Server features or System Center are not gathered at this level.internet connectivity should be set the telemetry level to Security to stop data gathering for events that will  never be uploaded due to no internet connectivity.

Basic Level 
·         NEW = Says “The Connected User Experience and Telemetry component does not gather telemetry data about System Center, but it can transmit telemetry for other non-Windows applications if they have user consent.”
·         NEW = Added following to list of data that basic level gathers “Virtualization attribute, such as Second Level Address Translation (SLAT) support and guest operating system.”
·         CHANGE = App compatibility section now says that apps that are installed on a device or virtual machine will be gathered at this telemetry level.
·         NEW = Added following to list of data that basic level gathers “App usage Data. Includes how an app is used, including how long it is used for, when the app has focus and when the app is started.”

Enhanced Level
·         NEW = “Says this is the default level and the minimum level needed to quickly identify and address quality issues with Windows, Windows Server and System Center”.
·         NEW = Added following to list of data that enhanced level gathers “Some crash dump types. All crash dumps, except for heap dumps and full dumps.”
·         REMOVED = Sentence that says what happens if more details are required no longer says anything about how long it will gather info for that issue (was 2 weeks).

Full Level
·         Where section says what capabilities Microsoft Engineers have to use the telemetry client to gather more information ...
·         REMOVED = “Ability to gather user content, such as documents, if they might have been the trigger for the issue.”
·         ADDED = “All crash dump types, including heap dumps and full dumps.”

Manage your telemetry settings section
·         NEW = “Says you can turn on and off system center telemetry gathering. The default is on. Says setting telemetry level to Basic will turn off system center telemetry even if system center telemetry switch is on”.
·         NEW – Section on how to configure system center 2016 telemetry settings.

Examples of how Microsoft uses the telemetry data section
·         This is a new section.
·         Has three paragraphs explaining how telemetry data is used, which have the headings “Driver higher application and driver quality in the ecosystem”, “Reduce your TCO and downtime”, “Build features that address our customers’ needs”