I hereby claim:
- I am riverar on github.
- I am rafael (https://keybase.io/rafael) on keybase.
- I have a public key whose fingerprint is 3E18 3879 1DB0 7B7C A2B5 F94F 050B 5707 E2BF 6D6A
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
var g_openVerbString = Memory.allocUtf16String("open"); | |
var fn = Module.findExportByName("shell32.dll", "ShellExecuteExW"); | |
Interceptor.attach(fn, { | |
onEnter: function(args) { | |
// Right now, SHELLEXECUTEINFO presumably looks like: | |
// ... | |
// lpVerb = nullptr | |
// lpFile = RUNDLL32.EXE |
<h1>Inside WDG - Branches and Rings</h1> | |
<p>Today, we’re kicking off a new series of articles we’ll publish regularly to Insider Hub called Inside WDG. WDG is short for the Windows and Devices Group which is the group at Microsoft responsible for Windows as well as Microsoft’s devices such as Surface, Xbox, Lumia, and Band. And with Inside WDG, we want to give Insiders a behind-the-scenes look at how we’re building Windows. It will also give us the opportunity go into greater detail on specific topics that we know are of interest to Insiders. For our first Inside WDG article, we’re going to talk about our Windows branches and rings.</p> | |
<p>Throughout Windows 10 development and over the past year of the Windows Insider Program, we have evolved how we develop and release Windows. We have learned a lot from our Windows Insiders and customers and have made significant improvements to our product and the tools we use to develop them. Therefore, we would like to take the time to give Windows Insiders some backgrou |
<p>Hello Windows Insiders!</p> | |
<p>My name is Miki Albertson and I’m a Program Manager from Windows Localization team. Today I would like to give you a behind-the-scenes look at how WDG products are made available to Windows Insiders in their language. By the way, we call this process “Localization”.</p> | |
<p>If you have ever wondered about how our products are made available in your markets and in your language, please read on!"</p> | |
<p>This is a simplified view, but it will give you an overview into main aspects of Localization process.</p> | |
<p>Each process is explained in detail below. </p> |
<h3>Introduction </h3> | |
<p>Cortana is really smart, but she isn’t perfect. Cortana does automatically get better, so just using Cortana is a great way to help. In fact, the more you use Cortana the better she gets for everybody. But your feedback is absolutely critical. Feedback helps us identify issues and focus attention to the most urgent needs.</p> | |
<p>In this article, we’ll show you how to give feedback about Cortana, what we do every day with that critical feedback, and provide real examples where feedback has impacted changes to Cortana.</p> | |
<h3>Cortana Feedback (How it works and what we do with it) </h3> | |
<p>One of the key sources of feedback comes from within the Cortana experience. You can provide ideas, likes and dislikes to our team. Each report is recorded by our system, including a screenshot (if you allow), as well as few key details such as the Windows language used. </p> |
<p>Hello, Windows Insiders!</p> | |
<p>We are the Photos and Camera team and we are very excited to share with you some of the changes that our team has worked on—all because of your feedback!</p> | |
<p><strong>How we read your feedback</strong></p> | |
<p>We’re constantly discussing your feedback and making changes to our apps based on this. We read the feedback you send to us in the Feedback Hub as well as Store reviews. Our process of reading the feedback includes meeting weekly in our living room and thinking about how we could best act on it. Our goal is to get you to love our apps as much as we do. To help us get there, all of our engineers are required to spend time reading and understanding your feedback, and to dedicate their time working to find ways to prioritize and address your concerns.</p> | |
<p><img src="http://compass.microsoft.com/assets/dc/d6/dcd6a7a6-b2d9-4379-8211-9a54b7af175e.jpg?n=photoandcamerateam.jpg" width="467" height="312" /></p> |
import _ from 'lodash'; | |
import {fs} from '../promisify'; | |
import BuildDiscoverBase from '../build-discover-base'; | |
export default class OverrideBuildDiscoverer extends BuildDiscoverBase { | |
constructor(rootDir) { | |
super(rootDir); | |
} | |
async getAffinityForRootDir() { |
#!/usr/bin/env node | |
'use strict' | |
const co = require('co') | |
const frida = require('frida') | |
const fs = require('fs-promise') | |
const path = require('path') | |
const sleep = require('co-sleep'); | |
const pkg = require('./package.json') |
{ | |
"version": "0.2.0", | |
"configurations": [ | |
{ | |
"type": "node", | |
"request": "attach", | |
"name": "Attach to Process", | |
"port": 6666 | |
} | |
] |
#include "stdafx.h" | |
#include "nvapi.h" | |
#include "NvApiDriverSettings.h" | |
#define FAST_FAIL(x) { __debugbreak; NvAPI_Status __status = x; if (__status != NVAPI_OK) { return __status; } } | |
int wmain() | |
{ | |
auto NvStringOrEmpty = [](NvAPI_UnicodeString nvstring) -> LPWSTR |