- Grab a computer (at least the iOS app doesn't seem to expose these settings)
- Log on to betterment.com
- Go to the Portfolio → Betterment Portfolios page:
- For each of your portfolios, walk them through these steps to change your allocation to the Socially Responsible Investing strategy:
- Click the Edit Portfolio link:
- Click the Betterment SRI → "Review Strategy" button, which will walk you through next steps to eventually change to that investment strategy. (If there isn't a blue button next to it, but is for each of the other strategies available, you're already done – good work!)
- Scroll through the page and click "Review and refine" at the bottom:
- Same thing, and click "Continue":
- Clicking "Finish Setup" changes this portfolio's allocation:
- This confirms the money in your portfolio no longer helps killing people – keep going until you run out of portfolios:
Webby thoughts, most about around interesting applications of ecmascript in relation to other open web standards. I live in Mountain View, California, and spend some of my spare time co-maintaining Greasemonkey together with Anthony Lieuallen.
2018-03-26
Betterment betterment
2018-01-17
Is DevTools open?
If you follow the web world, you have hopefully read this recent post on how we need to protect people against attacks on user data. On a mostly unrelated note, I wrote some assertions that I wanted to throw errors when I'm not debugging things, but console.log
them when I am, and then trip a debugger
statement. It's not really api detectable what mode I am in, but the openness of browser DevTools is a fair proxy, for me, at least, and the examples it linked to gave me a shim for crafting myself the window.isDevToolsOpen
setter bookmarklet I wanted:
javascript:((i) => {
Object.defineProperty(i, 'id', {
get: () => { window.isDevToolsOpen = true; }
});
setInterval(() => {
window.isDevToolsOpen = false;
console.debug(i);
}, 1000);
})(new Image)
Maybe it'll come in handy for someone else. These things rarely work forever; this post was written in the days of Chrome 63.0.3239.84 and Safari 11.0.2 (13604.4.7.1.3), when it did, whereas it already doesn't in Chrome Canary 65.0.3322.0, for instance. It gave me a useful time window of really convenient debugging a piece of complex code, which might require a full-blown browser extension at a later time. (Feel encouraged to comment if you made one.)