<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bobby Dresser on Medium]]></title>
        <description><![CDATA[Stories by Bobby Dresser on Medium]]></description>
        <link>https://medium.com/@b0bby?source=rss-614818abc13c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*J9xNAWpj80_2HkVqjMf9DA.png</url>
            <title>Stories by Bobby Dresser on Medium</title>
            <link>https://medium.com/@b0bby?source=rss-614818abc13c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 13:56:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@b0bby/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What I Learned as an Open-Source Product Manager]]></title>
            <link>https://medium.com/agileinsider/what-i-learned-as-an-open-source-product-manager-1ba9d2ed5039?source=rss-614818abc13c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ba9d2ed5039</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Bobby Dresser]]></dc:creator>
            <pubDate>Mon, 10 Feb 2020 14:52:13 GMT</pubDate>
            <atom:updated>2020-04-07T19:22:44.776Z</atom:updated>
            <content:encoded><![CDATA[<h4>Working as a PM alongside an open-source community is full of new lessons and exciting challenges</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_LOB6XcT2TEX8KXU0TSZpQ.jpeg" /><figcaption>image: Visual Tag via Pexels</figcaption></figure><p>For the past two years, I’ve worked as a product manager on an open-source project called MetaMask.</p><p>Our team builds a browser extension that lets people use Ethereum applications. It exposes an API for websites to interact with the blockchain, and it provides a UI for people to manage funds and approve transactions.</p><p>Our core team has 20 members, but our project has nearly 200 contributors from around the world. In past product roles, I’d been energized by collaborating with dozens of teammates in different functions and departments. But how could we collaborate with 10 times as many people, many of whom weren’t even part of our official team?</p><p>In my time at MetaMask, I’ve learned that PMing with a hands-on OS community can be vastly more complex and exciting. Here are a couple takeaways that will stick with me:</p><h3>Community is a growth strategy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XUzy9IlJays50TiFbHLFaw.jpeg" /></figure><p>Community is powerful. I remember having my first “wow” moment when I realized how many people were answering questions on StackExchange and Reddit, responding to technical questions in our Github, and generally evangelizing MetaMask across the web. It was all work our team would have stretched to do ourselves, but there were people around the world helping us succeed. Why?</p><p>As I spoke with more contributors, I heard some similar things:</p><p>“MetaMask is useful for me, so I want it to be useful for others.”</p><p>“It feels like it’s my product and my team.”</p><p>“I want to help where I can, so you can keep building the product I love.”</p><p>When we quickly fix a problematic bug, or accept PRs from folks who need a certain feature, or even when we share the minutiae of our decision-making process, we’re giving community members a sense of trust and ownership. They trust we care about their needs, and they realize their contributions actually matter to the product (both true!).</p><p>This positive sentiment pays back a hundredfold. When developers used MetaMask to build their application, they’d recommend it to their users. As users had positive experiences with the product, they began helping others with <a href="https://www.youtube.com/results?search_query=metamask">how-to content and tutorials</a>.</p><p>Community members were our best marketers, our brand ambassadors and a source of substantial product growth.</p><h3>Feedback loops are good, but it’s important to avoid information overload</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z1r_tREzEB9HBbykC5Yj9g.jpeg" /></figure><p>All our work at MetaMask takes place in the open. Anyone with an internet connection can see our backlog of issues, our current sprint, our design process and our work-in-progress prototypes.</p><p>This openness shapes our product process. There is no “feedback stage,” because we hear from users at every step. People open issues on Github, where we maintain our backlog. They advocate for certain bug fixes or feature requests to be included in the next sprint. They weigh in on our requirements docs and give feedback on in-progress designs, often sharing use cases we hadn’t considered. They QA, help us diagnose bugs, demand progress — it’s simultaneously overwhelming and helpful.</p><p>On the plus side, we’re able to source dramatically more feedback on our feature proposals, designs and test builds than we otherwise would. Good product management always includes this kind of feedback, but by conducting the process in public, it’s higher in volume and frequency than anything I’ve experienced.</p><p>On the other hand, this amount of feedback has a cost. It’s akin to inviting a small crowd to every meeting. Every team member must learn to balance the value of community input with the focus necessary to achieve their core goals.</p><p>I spend a substantial amount of time acting as an editor — distilling the noise to salient feedback that helps our developers and designers succeed without being overwhelmed.</p><h3>Transparent decision-making keeps collaborators engaged</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uPexiSN17HVGvPB4yUzEMg.jpeg" /></figure><p>Product management is often about keeping focus. Keeping focus sometimes requires saying, “No.”</p><p>Inside my team, I always explain the reasoning behind a “no.” Perhaps another project is more likely to help us reach our company’s goals, or maybe we don’t have the resources to execute a project appropriately. That context can make it clear that prioritization decisions are made to maximize outcomes, not to play favorites.</p><p>With external contributors, those justifications can be harder to communicate. An outsider doesn’t have the same familiarity with our company’s business goals, strategic direction or resource constraints — which makes saying “no” harder to explain.</p><p>This has reinforced my need to have specific, evidence-driven reasons for making product decisions. If I say “no” to a community member’s feature request, the “why?” is quick to follow. To continue building an engaged community that trusts us, explaining rationale is crucial.</p><p>That sounds something like this: “No, we won’t remove that screen from onboarding. I know it’s redundant, but we saw a 25% reduction in password-related support requests after we added it.”</p><p>Or this: “No, we won’t add more network data to the home screen. Only 10% of users actually switch to test networks, so we don’t think that information is important enough to include by default.”</p><h3>Plan for the unpredictable</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UR9SEBrTMMQue9FXjdhKBA.jpeg" /></figure><p>Community members don’t follow the sprint plan. A rule follower might pluck an issue from the backlog we’ve declared needs help. A frustrated developer might fix a bug that’s been affecting her application. But it’s usually a chaotic do-gooder who drives by to introduce a new UI to our home screen or build out a feature we hadn’t yet had time to design properly.</p><p>As discussed, sometimes a “no, because …” is necessary. In all cases, we encourage contributors to pre-flight their new idea by opening an issue before they invest time in the code. But in the cases where a community member builds or fixes something with substantial value and little warning, our team must be flexible enough to accept a contribution while still making progress on our own priorities.</p><p>We’ve learned to budget this effort into our planning. If our development team has 100 fictional “points” of effort, anywhere between 10 and 40 of those points might be spent on community management each sprint (which includes code review, feedback on implementation, debugging, helping with build issues, etc). Each cycle, we review the in-progress community PRs and point the community management work accordingly, which lets me understand how much bandwidth we have left for other priorities.</p><p>On the design side, this planning is a bit harder. It’s very tough to “sprinkle some UI” on an issue that hasn’t had enough design thinking applied from the start. In some cases, we’ll add a community feature to our design backlog and implement the designs ourselves to complement the under-the-hood work done by an external contributor — a nice collaboration that respects their work without demanding more.</p><p>More than once, our team has let community PRs linger without code review or blocked new features on our design process. Contributors lose interest quickly when their work is ignored. Over time, I’ve learned to maximize outcomes by budgeting for the unpredictable contributions of our community.</p><h3><strong>Invest in productivity multipliers</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XCLEGR2dc_qc7gkKSPU_DA.jpeg" /></figure><p>How many people can you fit in one codebase? How quickly can you get a new contributor up to speed? The answer depends on how the team builds, documents, tests, and collaborates.</p><p>The good news is these are all variables the team can influence. Investing in infrastructure that can help a new contributor go from 0 to 1 will pay compounding returns over time.</p><p>If I have to answer a development question twice, it should be written down in our documentation. If contributors repeatedly have trouble with the test suite, we consider prioritizing a fix. Our design system lets folks build out suitable UI features without requiring design resources. By doubling down on these productivity multipliers, we’ve reduced the number of issues categorized as dev help by ~50% and freed up more of our core team’s time.</p><h3>Inclusion requires intention</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*exgJRwUsZJNCT6O1F8lhMg.jpeg" /></figure><p>Inbound feedback is a gift, but it doesn’t reflect all users’ needs. It usually comes from the technical part of our user base — folks who are comfortable using Github and can express their needs in the specific language of a bug report or feature request.</p><p>This asymmetry might be OK for a proposed change to an API method. But for an update to our onboarding flow, or when considering broader product strategy and prioritization, it’s crucial to gather feedback from other user personas.</p><p>In conversations with community members, I’ve learned that online forums or Github issues are not welcoming to all individuals. Women and people of color in these spaces are disproportionately subject to harassment. We also have a large international user base, but most of our documentation and support is still only in English.</p><p>I’ve learned a lot from folks such as Coraline Ada Ehmke, an open-source developer and advocate who authored the <a href="https://www.contributor-covenant.org/version/1/4/code-of-conduct.html">Contributor Covenant</a>, which sets guidelines for good community conduct.</p><p>Whether that means course-correcting a conversation that’s heating up or removing a repeat offender from our community, proactively building an inclusive space is both moral and productive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0jXbo8D4eVrmyG9GSj8swg.png" /><figcaption>Tongue-in-cheek, but still important!</figcaption></figure><p>That’s all folks! Thanks for reading. Get in touch: bobby.dresser@gmail.com.</p><p>Also, this post notably excludes discussion of business models and a product manager’s responsibility to build (and license) software that helps meet business goals. That is another article for another time!</p><p><em>Note: The internet was built on open-source software and runs on it still today. Many of the most crucial projects are woefully underfunded. Consider supporting an OS team via </em><a href="https://github.com/sponsors"><em>Github Sponsors</em></a><em> or </em><a href="https://opencollective.com/"><em>Open Collective</em></a><em>!</em></p><figure><a href="https://productmanagementinsider.com/?utm_source=pmi&amp;utm_medium=article"><img alt="" src="https://cdn-images-1.medium.com/max/530/1*-r9Yo1EkdF7zGQtUvwtCuw.png" /></a></figure><figure><a href="https://alphahq.com/pmi-demo/"><img alt="" src="https://cdn-images-1.medium.com/max/530/1*nGHoPrcS_pmY7i_UPU53Ug.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ba9d2ed5039" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/what-i-learned-as-an-open-source-product-manager-1ba9d2ed5039">What I Learned as an Open-Source Product Manager</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Figma & the future of work]]></title>
            <link>https://medium.com/swlh/figma-the-future-of-work-670a8ac7c645?source=rss-614818abc13c------2</link>
            <guid isPermaLink="false">https://medium.com/p/670a8ac7c645</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[figma]]></category>
            <dc:creator><![CDATA[Bobby Dresser]]></dc:creator>
            <pubDate>Fri, 31 Jan 2020 21:14:04 GMT</pubDate>
            <atom:updated>2020-04-05T22:52:47.092Z</atom:updated>
            <content:encoded><![CDATA[<h4>How everyone’s favorite design tool can re-shape the way modern product teams collaborate.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vvSqci75RYhfv5EbP-qivQ.png" /></figure><p>I spent the last 2+ years working with a remote team distributed across five time zones. We used a jumble of different tools to collaborate and organize — the usuals, like Slack and Zoom and Google Docs and Airtable. But we also leaned heavily on others — Mural for brainstorming, Loomio for structured decision making, Kialo for complex and sprawling discussions.</p><p>On modern product teams, there’s so much work that does not fit in a spreadsheet or 8 x 11.5 sheet of digital paper. Some discussions are messy &amp; divergent. In a co-located office, they’re the sorts of discussions where the whiteboard markers change hands repeatedly, or where the PM is glad she brought more than one color of sticky note.</p><p>I <em>love</em> this type of collaboration. One of the best parts of working with a brilliant team is the realization that fantastic ideas can come from anyone. As a product manager, part of my job is to fuel these conversations by asking the right questions and encouraging thinking from other perspectives.</p><p>But on my remote team, this style of collaboration was hard to cultivate. The bandwidth of our conversation was so much lower than if we were grouped around a whiteboard — both because of our video software (topic for another time) and because we lacked the right tool for expressing our ideas.</p><p>This is not to say I didn’t <em>try</em> — I spent hours of pre-work time structuring a Mural board for optimal group discussion, planning out 10–15 minute activities, dragging virtual stickies, setting up voting rounds to converge on a plan of action. But it never quite came out perfect. The inertia required to express an idea, the learning curve of the tool, the frequency of an idea imperfectly expressed — it cumulatively kept us from the flow state of a good brainstorm.</p><p>That’s where Figma comes in. The design tool launched in 2011 and has since taken product teams by storm, raised 72 million dollars, and is evolving into a platform for design collaboration. I would love to see the product go further: there’s an opportunity for Figma to become the home for all types of team collaboration by creating a flexible tool modern product teams need to succeed.</p><h3>One design app to rule them all</h3><p>Figma first differentiated itself by taking to the cloud.</p><ul><li>It’s based in the browser (although it offers an Electron app) and allows realtime collaboration.</li><li>It does version control for design files (no more mobile-designs_final_FINAL_v3.png)</li><li>With a simple &quot;Present&quot; feature, it puts WIP designs into display mode, acting as a tool for sharing prototypes.</li></ul><p>This replaces the painful <em>Sketch &lt;&gt; Abstract &lt;&gt; InVision</em> cycle, much to everyone’s relief. I have actually never spoken with a Figma user who did not sing its praises.</p><p><strong>But Figma’s real differentiator is its community.</strong> In 2019, Figma launched a robust plugin system, opening the doors for users to update and remix the product itself. Later in 2019, the team launched a Beta community feature that supports sharing templates from individuals’ profiles.</p><p>This is a savvy growth strategy. <a href="https://medium.com/pminsider/what-i-learned-as-an-open-source-product-manager-1ba9d2ed5039"><strong>As I’ve written elsewhere</strong></a>, community is often a powerful and sustainable source of organic growth. When users build templates or plugins, the product itself becomes more valuable, attracting more folks to the platform who might contribute more assets themselves.</p><p>This community play also brings Figma into competition with other design platforms — sites like Behance and Dribble, which have succeeded as must-have portfolio displays but have always stayed curiously isolated from the spaces where design actually happens.</p><h3>Beyond product design</h3><p>But what about the world beyond designers? Figma shares templates for presentation decks, Google Cloud diagrams, team retrospectives… etc. — projects that require “design,” to be sure, but also acknowledge a variety of other user personas: product managers, technical architects, people giving presentations. These folks want to use Figma’s tools on projects that will not be ultimately translated in to picture-perfect digital products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KI1AxqYGzU6D3eXdHxKXvQ.png" /></figure><p>At the end of 2019, Figma’s marketing team published a delightful <a href="https://www.figma.com/blog/made-in-figma-2019/">article</a> about the habits they gleaned from over 50k design files. The author notes that 33% of Figma files start by using one of the standard screen-sized frames. That means the vast majority of users start off on their own! Certainly, some folks are still designing screen-bound products in custom frames, but this stat made me wonder how we could quantify the non-product design usecase I’m interested in. Some questions I’d love to ask include:</p><ul><li>what percentage of files are never exported or viewed as CSS?</li><li>what percentage files have no dominant “author” (where many users generate roughly-equal amounts of content)?</li><li>what percentage of templates are directed towards non- product design usecases?</li><li>what percentage of plugins are related to non- product design usecases?</li></ul><p>I’ve seen (and made) Figma files as decks, as analytics reviews, as strategy brainstorms, and so on. None are aesthetically acceptable enough to share, but all make use of Figma’s blank slate and flexibility.</p><h3>Tooling for multiple usecases</h3><p>Assuming our quantitative research shows there’s a lot of Figma activity that doesn’t lead to design artifacts, what does this suggest for Figma’s product strategy? As they’ve stated, 2020 is all about community, and it’s likely that community members will help support these a variety of usecases with plugins and templates. Grassroots energy will continue to help the product grow its audience. <strong>But that broader audience might also benefit from some native changes to the product.</strong></p><p>In my quest for a tool that would let my remote team express our ideas fully, I shied away from Figma. It could do everything we needed, and then some, and that added complexity made it wrong for us. In a brainstorm or realtime conversation inside a Figma file, adding a idea or upvote or bit of feedback requires a non-trivial amount of expertise and finesse, and the learning curve is steep.</p><p>Other products like Balsamiq have found their niche by settling at the right zoom level, giving the user blunt instruments that encourage low-fi, high-output thinking. Notably, that type of divergent thinking is a crucial part of every design process I’ve participated in.</p><p>Perhaps Figma does not want to be a felt-tip marker tool. But I can’t help notice that</p><p>(a) the controls required for low-fi brainstorming are a strict sub-set of what Figma has built already, and</p><p>(b) there’s a natural logic to helping designers with every step of their process — from jumbled &amp; divergent discovery through the precision of a final solution.</p><p>A naive proposal might include a “light mode” or “wireframe mode” that simplifies controls to help users contribute fast and loose. But given the success of Figma’s plugin system, I could also see success in an expanded plugin API that lets developers modify the tool, not just the file: a plugin for design reviews could ask viewers to vote, or prompt a visitor to answer a certain set of questions. A brainstorm plugin might give each user in the file a custom toolbox that helps them drag &amp; drop immutable stickies that only allow text. And so on. Building this sort of plugin API is massively complex from a security standpoint, but it could also make Figma into the ultimate remix-able collaboration tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Onhsfu2o2ydV8Xb-0fc5g.png" /></figure><p>Building for teams’ usecases beyond detailed design &amp; prototyping expands Figma’s audience. With better templates, it could replace Keynote, Google Slides, and Powerpoint. With a flexible enough API or the right newb-friendly tooling, it could become the default home for remote collaboration, winning out over Mural and StormBoard in a new-ish category full of unattractive offerings.</p><p>In doing so, Figma becomes an easier sell — not just as a design tool, but a collaboration tool more broadly, one used by product and sales and the C-suite, one required for effective work in the digital age.</p><p>Remote teams will continue to be popular, particularly for people outside the bubble of major technology hubs like San Francisco or Berlin. My experience makes me think these teams will have a harder time collaborating until our tools catch up.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=670a8ac7c645" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/figma-the-future-of-work-670a8ac7c645">Figma &amp; the future of work</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No Longer Injecting web3.js]]></title>
            <link>https://medium.com/metamask/no-longer-injecting-web3-js-4a899ad6e59e?source=rss-614818abc13c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a899ad6e59e</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Bobby Dresser]]></dc:creator>
            <pubDate>Thu, 31 Oct 2019 22:11:16 GMT</pubDate>
            <atom:updated>2021-01-13T01:53:17.645Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/metamask/breaking-changes-to-the-metamask-provider-its-happening-eebc91fff1a7"><em>Click here to learn more about related breaking changes to MetaMask.</em></a><em> These changes were originally planned to take place in 2020.</em></p><p>In <strong>early 2021</strong>, MetaMask will no longer inject the web3.js API. <em>You can still bring your own </em><strong><em>web3.js</em></strong><em> or similar library and use it with MetaMask. </em>We will simply stop injecting a particular version of <strong>web3.js</strong> for you.</p><p>We’ve primarily included <strong>web3.js</strong> as a convenience alongside MetaMask’s core Ethereum provider API, which wraps the JSON-RPC API and is documented <a href="https://metamask.github.io/metamask-docs/API_Reference/Ethereum_Provider">here</a>.</p><p>Removing <strong>web3.js</strong> is part of an effort to simplify MetaMask’s API and provide the safest, most stable experience possible.</p><h4>Why are we doing this? What does this mean for you?</h4><p>MetaMask currently injects web3@0.20.x, which is <a href="https://github.com/ethereum/web3.js/issues/3065">no longer receiving fixes or updates</a>. The 0.20.x version also lacks some safety validations that have caused trouble for our users.</p><p>While upgrading <strong>web3.js</strong> to 1.0.x is an option, the upgrade would require breaking changes.</p><p>Furthermore, web3@2.0.0 is already a scheduled breaking change, so rather than subject our users to a series of breaking changes, we are finally putting version choice firmly in the hands of developers so we can minimize the number of breaking changes in the future.</p><p>You can still bring your own convenience library and use it with the MetaMask inpage provider, whether <a href="https://github.com/ethers-io/ethers.js/"><strong>ethers.js</strong></a>, <strong>web3.js</strong>, or something else.</p><h4>Conclusion</h4><p>Removing our injected version of <strong>web3.js</strong> will help us continue to provide a safe, performant experience for developers while managing our maintenance costs. In <strong>early 2021</strong>, dapps will have to bring their own convenience library if they want to use one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a899ad6e59e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/metamask/no-longer-injecting-web3-js-4a899ad6e59e">No Longer Injecting web3.js</a> was originally published in <a href="https://medium.com/metamask">MetaMask</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Privacy Mode is now enabled by default]]></title>
            <link>https://medium.com/metamask/privacy-mode-is-now-enabled-by-default-1c1c957f4d57?source=rss-614818abc13c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c1c957f4d57</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[metamask]]></category>
            <dc:creator><![CDATA[Bobby Dresser]]></dc:creator>
            <pubDate>Thu, 01 Aug 2019 00:42:31 GMT</pubDate>
            <atom:updated>2019-08-01T20:26:58.755Z</atom:updated>
            <content:encoded><![CDATA[<p>Last year, MetaMask introduced <a href="https://medium.com/metamask/introducing-privacy-mode-42549d4870fa">Privacy Mode</a>, an ecosystem-wide standard to improve user privacy on Ethereum. Rather than exposing users’ Ethereum addresses to all sites, Privacy Mode (detailed in <a href="https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1102.md">EIP 1102</a>) requires that websites ask for user consent before wallets reveal an address.</p><p>Privacy Mode has been enabled by default for new users for the past several months, and available as an opt-in setting for existing users. <strong>In MetaMask v7.0, we’re making Privacy Mode the default for every MetaMask user. </strong>We believe this is an important step for the usability and privacy of users in the Ethereum ecosystem. This update will be rolling out gradually over the next week.</p><h3>What this means for users</h3><p>Many MetaMask users are familiar with the “Connect” screen, where sites ask for your address. Users will continue to see this confirmation screen when interacting with a new application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hLGeP7kdxsTC27PkvIELpA.png" /></figure><p>Thousands of dapps have updated to support EIP 1102. However, there are some projects out there that aren’t currently maintained or haven’t adopted the new standard.</p><p>If you’re having trouble connecting to a dapp, pop open MetaMask from your toolbar and you’ll see an option to manually share your address with the current site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*niUx6GNBfIzEhOiW-77ATw.png" /></figure><p>As always, Privacy Mode can be turned on and off via your settings. If you have questions, please reach out to support@metamask.io.</p><h3>What this means for developer users</h3><p>If your dapp doesn’t support EIP 1102, you’re long overdue to update and stay in step with the ecosystem. Your UX and your users’ privacy is at stake! Follow <a href="https://medium.com/metamask/eip-1102-preparing-your-dapp-5027b2c9ed76">this guide</a> and feel free to reach out on Github or Twitter with questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J1CHjTapiovBT7-RDOKg3g.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c1c957f4d57" width="1" height="1" alt=""><hr><p><a href="https://medium.com/metamask/privacy-mode-is-now-enabled-by-default-1c1c957f4d57">Privacy Mode is now enabled by default</a> was originally published in <a href="https://medium.com/metamask">MetaMask</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MetaMask Metrics]]></title>
            <link>https://medium.com/metamask/metamask-metrics-fbec0e2ceaa7?source=rss-614818abc13c------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbec0e2ceaa7</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[data]]></category>
            <dc:creator><![CDATA[Bobby Dresser]]></dc:creator>
            <pubDate>Thu, 23 May 2019 20:40:53 GMT</pubDate>
            <atom:updated>2019-05-23T21:02:27.570Z</atom:updated>
            <content:encoded><![CDATA[<h3>MetaMask Metrics: a first look</h3><p>MetaMask attracts users from all over the blockchain space — developers, token traders, first-time dapp users who don’t even know what Ethereum is, and everything in between.</p><p>It’s a wide range for a single product, and we’re amazed at the many use cases and insights that come from these different user personas.</p><p>We’ve long relied on qualitative feedback from support, Github and around the community to inform product development. But in early March, we rolled out an opt-in metrics system to provide some quantitative insight on how people are really using MetaMask.</p><p>Two months later, we can see trends and high-level volume that highlight the incredible amount of dapp activity and development happening across the ecosystem. We’re excited to share.</p><h3>Overview</h3><p>At the beginning of March, we asked all users if they were willing to allow their extension to report basic UI metrics. New users saw an additional screen during their onboarding flow, and existing users saw the same screen the next time they opened the extension.</p><p>From the time this metrics system launched in March, we’ve had 275k users opt-in and 104k users decide to opt-out. <strong>That means that the data shown here only reflect 72.6% of our user base.</strong></p><p>The data reported below are either shown “As measured” or “Estimated actual.”</p><ul><li>“<strong>As measured</strong>” is the raw number we recorded for the users who opted in.</li><li>“<strong>Estimated actual</strong>” is the projected total if all behavior were consistent across those users who opted out.</li></ul><p><em>As a reminder, we’ll never collect keys, addresses, transaction details, account balances, full IP addresses, account nicknames, or any data from outside the extension. Users are free to opt-out from metrics with the click of a button (Settings –&gt; Security &amp; Privacy). And we’ll </em><strong><em>never</em></strong><em> sell your data for profit!</em></p><h3>MAU, Growth, and Onboarding</h3><p>In the past two months, we’ve seen <strong>89k new wallets </strong>and <strong>53k imported wallets.</strong></p><p>Week-over-week new user growth for this time period is 1.1%, but doesn’t track a straight line: we’ve found that new user growth is often tied to ecosystem-wide events like the price of ETH, a good press cycle, or a trending game. Still, the overall trend continues to bend upwards.</p><p>Users complete the new wallet onboarding flow 79% of the time, which reflects what we know about the challenges of putting new users in control of their own keys. We’ll continue to iterate on onboarding UX without compromising the core tenets of security &amp; privacy that we hold paramount.</p><p>April measured 192k MAU and 65k WAU, which we can adjust proportionally for the chunk of our userbase who did not opt-in to metrics:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KOsyMUbmPFZfGkioaKHIKg.png" /></figure><p>We’re defining an “active” user as someone who interacts with MetaMask in any way — by opening the extension to check their balance, by sharing their address with a dapp, by switching their active account, etc.</p><p>We find that active users are often *quite* active: we’re measuring roughly 320k visits per week, which means <strong>the average weekly active user visits MetaMask 4.9 times per week.</strong></p><p>That said, not every active user is interacting directly with the blockchain. On any given day, about 30% of active users confirm an on-chain transaction. This suggests there’s still a portion of users who see MetaMask as a wallet, or who are interacting with dapps (via the “Connect” screen, or by signing data) but stop short of confirming a transaction.</p><h3>Transactions</h3><p>MetaMask recorded 1.1 million transactions in the month of April, which projects out to a whopping <strong>1.51 million transactions last month across the entire user base.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eC-pVAjmDGFjKzlw3mD_xg.png" /></figure><p>There’s a sizeable chunk of activity spread across the Ethereum testnets, and development traffic on users’ local Ganache network is represented notably, but <strong>the bulk of this activity (63%) is happening on the Ethereum Mainnet.</strong></p><p>We also recorded 71k transactions on “other” networks, which goes to show MetaMask’s reach beyond just Ethereum chains. There were 25 unique networks with more than 1k transactions in the month of April.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jvM3U6kisxbVlhIPHv1X1w.png" /></figure><h3>Transactions on Mainnet</h3><p>Let’s take a closer look at activity on Mainnet. The previous graph shows the transactions we measured across all networks. Since this only represents about 3/4 of our users, we project that the total transaction volume on Mainnet in April was closer to 1 million transactions overall:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L8ts1T3ONrscKLrr98NF9w.png" /></figure><p>What immediately jumps out from the transaction metrics we measured is that the majority of all transactions are prompted from outside of MetaMask.</p><p>The graph below shows the breakdown between transactions that are initiated by users (by opening MetaMask, clicking the “Send” button, choosing to send ETH or tokens, then completing the transaction) compared to transactions initiated by dapps or exchanges (transactions prompted to the user via the free-standing popup window).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vL1lczAYfEAFs_X9J8IlwQ.png" /></figure><p>We intend for MetaMask to be so much more than a wallet, and our usage data show this is already the case: it’s not just for storing, sending and managing assets on Ethereum — it’s connecting users to functional applications in the emerging decentralized web.</p><p>When we look at Mainnet transactions by function, the data are even clearer:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I9XlaS0JeHerPBxkckwEtA.png" /></figure><p>ETH Sends, token transfers, and approve calls are quite common, but the vast majority of transactions are interactions with non-ERC20 smart contracts.</p><p>We do our best to look up function names for these contract interactions, but most still go unmatched and show simply as “Contract Interaction.” (For dapp developers reading this: we recommend you <a href="https://metamask.github.io/metamask-docs/Best_Practices/Registering_Function_Names">add your functions to this on-chain registry</a>!)</p><p>In the coming months, we’ll be investing in making Confirm screens clearer and more informative, especially for function calls.</p><h3>Dapp Usage</h3><p>There are thousands of individual applications that contribute to the transaction volume above. The top five on mainnet and top five overall are:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oQuSa1k_CndL-YKDt67hiQ.png" /></figure><p>This represents a good mix of collectibles, games, exchanges &amp; developer tools. Remix’s place as the most-used application reflects our substantial developer user base, especially on testnets.</p><p>These applications are only the tip of the iceberg: on Mainnet alone, there are over 25 different dapps with over 5k transactions in April, and we see new applications appear in our weekly charts all the time.</p><h3>Takeaways</h3><ul><li>The goal of this system is to help us improve the product where users need it most. We’ll continue to be transparent about what we learn and how it shapes our roadmap.</li><li>We’re excited to watch our metrics system mature so we can track growth over time, and see how feature development affects key numbers.</li><li>On the product side, we’re taking some time to invest design effort into refreshing the Confirm screens to make them more functional. At the same time, we’re exploring a framework that will help the user extend permissions to different applications and reduce the need to confirm individual actions.</li><li>We’re stoked to see such widespread dapp usage, and we’ll continue to build features that make devs’ &amp; users’ lives easier!</li></ul><p>If you have data you’d like to see, or have questions about how MetaMetrics works, comment below or drop me a line! bobby@metamask.io</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbec0e2ceaa7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/metamask/metamask-metrics-fbec0e2ceaa7">MetaMask Metrics</a> was originally published in <a href="https://medium.com/metamask">MetaMask</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MetaMask Monthly: April]]></title>
            <link>https://medium.com/metamask/metamask-monthly-april-a0ca715ea4d2?source=rss-614818abc13c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0ca715ea4d2</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[token]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Bobby Dresser]]></dc:creator>
            <pubDate>Wed, 01 May 2019 21:14:50 GMT</pubDate>
            <atom:updated>2019-05-01T21:14:50.892Z</atom:updated>
            <content:encoded><![CDATA[<p>Product updates from the MetaMask core team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r7k9Mdbb5YvWgKjgLlzmPg.png" /></figure><h3>Simpler Token Transfers ✨</h3><p>One of MetaMask’s many goals is to make managing ERC20 tokens a breeze. Since rolling out our privacy-first metrics system last month, we’ve learned that token transfers account for 45% of transactions initiated from within the extension (as opposed to those initiated by a dapp). Right now, this requires selecting a token from the left-side hamburger menu, then going through a “Send” flow specific to that asset. “Token” is also one of our most common keywords in support requests.</p><p>To make this flow smoother and more discoverable, we now allow users to select the asset they’d like to send right from the general-purpose “Edit Transaction” screen (#<a href="https://github.com/MetaMask/metamask-extension/pull/6445">6445</a>). Next time you want to transfer tokens, you can start just by clicking the “Send” button on the home screen. (And for the eager: support for sending &amp; managing ERC 721 tokens is coming soon!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X272K0s1-ZLsbvgzvX_oKQ.png" /><figcaption>The new “Asset” field on Send screens</figcaption></figure><h3>MetaMask Supports Goerli 🕸</h3><p>MetaMask now includes a network option for the new (ish) <a href="https://github.com/goerli/testnet">Goerli testnet</a>. Goerli is a proof-of-authority network that aims to be a reliable piece of infrastructure for building and testing dapps on Ethereum (#<a href="https://github.com/MetaMask/metamask-extension/pull/6459">6459</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/712/1*3HFTKFwZ8_RCccelTLpNPg.png" /></figure><h3>Incident Report ⚠️</h3><p>Last week we began a slow roll-out of v6.4.0, which included many of the features &amp; fixes detailed in the release notes below. In an effort to improve the legibility of our confirmation screens, 6.4.0 introduced a feature that would ping an external API (4byte.directory) to look up human-readable function names using a transaction’s method signature. (We primarily rely on a Parity on-chain method registry, but nearly half of all transactions are contract interactions not found in the Parity registry. <strong>To any dapp devs reading: </strong><a href="https://metamask.github.io/metamask-docs/Best_Practices/Registering_Function_Names"><strong>register your app’s function names to help your users!</strong></a><strong>)</strong></p><p>When we increased our rollout percentage to 100% on Thursday night, we brought down 4byte’s API due to ineffective caching in the extension. Due to an overly long timeout period, this caused many users to encounter a minute-long spinner in place of the transaction confirmation they should have seen.</p><p>For more detail on the issue, our response, and our learnings, you can read the incident post-mortem <a href="https://medium.com/metamask/incident-postmortem-slow-confirmation-popups-23108bc954bc">here</a>.</p><h3>Foxes in the Community 👯‍♀️</h3><p>MetaMask dev <a href="https://twitter.com/jenny_pollack?lang=en">Jenny Pollack</a> spoke about open source development this weekend at Recolor, a conference organized by <a href="https://www.she256.io/">she256</a> out of UC Berkeley. Check out <a href="https://consensys.slack.com/archives/DAZ46PN2H/p1556650809001100">this thread</a> for a pull-quote overview of the day’s panels. We are particularly proud of our former intern (and she256 co-founder) <a href="https://medium.com/u/23084b244732">Sara Reynolds</a> for her incredible work promoting diversity and representation in the blockchain space!</p><p>Community manager Jason Lee also went on the record last week to describe some of the key decisions and principles behind MetaMask’s growth over the past three years. You can read the full interview with Decrypt Media <a href="https://decryptmedia.com/6651/jason-lee-metamask">here</a>.</p><h3>MetaMorph Design System 🎨</h3><p>As we work on our mobile application and continue iterating on the extension, we’re approaching a future where MetaMask is represented on a variety of screen types &amp; platforms. Our design team has been hard at work crafting a design system (codename “MetaMorph) to keep our products visually consistent and improve the efficiency of our frontend teams. While it’s still a work-in-progress, you can take a sneak peek on Figma <a href="https://www.figma.com/file/aWgwMrzdAuv9VuPdtst64uuw/Style-Guide?node-id=211%3A0)">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-wRj_WvxcF1FRnS_qSJVog.png" /><figcaption>WIP MetaMask Design System</figcaption></figure><h3>Development — What’s New?</h3><p>v6.4.1 is live on browsers near you!</p><ul><li>Updated publishing guide for transparency on how we build &amp; ship code (#<a href="https://github.com/MetaMask/metamask-extension/pull/6470">6470</a>).</li><li>Updated firmware for fixes to signing methods on Ledger and Trezor (#<a href="https://github.com/MetaMask/metamask-extension/pull/6395">6395</a>).</li><li>Improved parsing of function names on Confirm screen (#<a href="https://github.com/MetaMask/metamask-extension/pull/6403">6403</a>).</li><li>Fixed height display of Custom RPC URLs (#<a href="https://github.com/MetaMask/metamask-extension/pull/6468">6468</a>).</li><li>Fixed inconsistent behavior joining Ganache’s localhost (#<a href="https://github.com/MetaMask/metamask-extension/pull/6444">6444</a>).</li><li>Switched our token price API to CoinGecko (#<a href="https://github.com/MetaMask/metamask-extension/pull/6424">6424</a>). RIP Balanc3 🙏</li><li>Updated in-app metrics for accuracy and consistency (#<a href="https://github.com/MetaMask/metamask-extension/pull/6417">6417</a>).</li><li>Fixed handling of provider errors (#<a href="https://github.com/MetaMask/metamask-extension/pull/6401">6401</a>).</li><li>Fixed broken display on “Advanced” gas chart (#<a href="https://github.com/MetaMask/metamask-extension/pull/6389">6389</a>).</li><li>Various code cleanups (#<a href="https://github.com/MetaMask/metamask-extension/pull/6428">6056</a>, #<a href="https://github.com/MetaMask/metamask-extension/pull/6428">6428</a>, #<a href="https://github.com/MetaMask/metamask-extension/pull/6448">6448</a>, #<a href="https://github.com/MetaMask/metamask-extension/pull/6382">6382</a>)</li></ul><h4>April by the Numbers</h4><blockquote>✅ 50 PRs merged</blockquote><blockquote><em>🛠</em> 154 commits</blockquote><blockquote>💫 63 Github issues closed, 62 opened 😅</blockquote><blockquote>🔧 910 support tickets solved</blockquote><blockquote>💥 2,436 lines of code added and 3,239 deleted.</blockquote><p>~</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0ca715ea4d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/metamask/metamask-monthly-april-a0ca715ea4d2">MetaMask Monthly: April</a> was originally published in <a href="https://medium.com/metamask">MetaMask</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MetaMask Monthly: February]]></title>
            <link>https://medium.com/metamask/metamask-monthly-february-115474740d9f?source=rss-614818abc13c------2</link>
            <guid isPermaLink="false">https://medium.com/p/115474740d9f</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[metamask]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Bobby Dresser]]></dc:creator>
            <pubDate>Thu, 28 Feb 2019 23:37:30 GMT</pubDate>
            <atom:updated>2019-02-28T23:40:03.486Z</atom:updated>
            <content:encoded><![CDATA[<p>Product updates from the MetaMask core team</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P9Z1w5He5EH-3mrcgqbuFg.png" /></figure><h3><strong>The faster fox 💨</strong></h3><p>Last month, we announced some updates to MetaMask’s network efficiency. This month, we’ve shipped even more improvements to reduce our traffic to Infura and eliminate unnecessary requests. v6.1.0 includes a set of changes that bring MetaMask very close to going network silent while not in use, and early reports suggest we’ve reduced our overall number of requests by 50%. Laptop batteries around the world rejoice.</p><h3><strong>MetaMetrics: help us help you 📈</strong></h3><p>MetaMask is a crucial tool for blockchain newcomers, traders, developers, and beyond. The qualitative feedback we get from these different user groups can vary widely. In pursuit of making more data-driven decisions in our UI, MetaMask will begin rolling out an opt-in metrics system starting next week. If you consent, we’ll record anonymized events to better understand the features users gravitate towards, which features go unused, how funnels leak, and so on.</p><p>Our metrics collection takes a strong stance on user privacy: it will never collect public addresses, private keys, transaction IDs, or transaction hashes. We’ll also obfuscate the last nine digits of any IP addresses. Users can opt-out of metrics collection at any time. Last, MetaMask will never profit from sharing or selling your data, ever.</p><p>We’ll use this anonymized data to inform our development and create a better MetaMask for all. We also look forward to sharing high-level data with the community! To read more, check out last week’s <a href="https://medium.com/metamask/metametrics-an-introduction-to-metamasks-new-analytics-system-e9749e74a275">announcement</a>.</p><h3>R.I.P. Old UI ⚰️</h3><p>At long last, we’ve removed the old legacy interface from the MetaMask codebase. For a full list of all the things the current UI can do that the old one couldn’t, check out this <a href="https://metamask.zendesk.com/hc/en-us/articles/360022857872-Removing-the-Old-UI">support article</a>. In addition to providing a better experience for users, this will simplify our testing suite and reduces our bundle size substantially.</p><p>We received some great feedback from the community after announcing our plans to migrate users over to the new interface. In response, we’ve shipped the ability to turn on “advanced” gas editing, which adds plain text inputs to the Send and Confirm screens. While our simpler gas options work well for newer users, some veterans missed the no-click accessibility of granular gas control right on the confirmation page. If that sounds like something you’d like, you can find the toggle in your Settings menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KAGmDODInhZRePkk2OrpLA.png" /><figcaption>Toggle between these display options from your Settings menu.</figcaption></figure><h3><strong>Least Authority &amp; MetaMask Mobile 🔐</strong></h3><p>We’re still hard at work on MetaMask Mobile. As we get closer to launch, the team wants to make sure we’re delivering the best-in-class security you’ve come to expect. We’ve partnered with <a href="https://leastauthority.com/">Least Authority</a> to do a security audit on MetaMask Mobile and make sure we continue to provide a safe experience on the decentralized web. Results of the audit will be published in mid-March!</p><h3>An update from Mustekala 🦑</h3><p>Our light client team (codenamed <a href="https://medium.com/metamask/metamask-labs-presents-mustekala-the-light-client-that-seeds-data-full-nodes-vs-light-clients-3bc785307ef5">Mustekala</a>) is nearing completion of an MVP implementation of the KSN protocol. KSN is an open source protocol on top of libp2p that enables all kind of devices to share slices of the Ethereum Database, taking synchronization and reading to the next level. At the same time, the team is preparing for what comes next — maybe including a simple incentivization protocol on top of KSN. Stay tuned!</p><h3>Release notes</h3><p>MetaMask v6.1.0 is out and auto-updating in browsers near you. Next time you pop it open, check out some of the improvements listed below.</p><ul><li>The “Send” screen now lets users toggle the “amount” input between fiat and crypto using a small arrows button. (<a href="https://github.com/MetaMask/metamask-extension/pull/6091">#6091</a>)</li><li>As we removed the old UI (R.I.P.) we heard from several users that they missed having text inputs to change gas price &amp; gas limit right on the confirm screen. It’s now possible to enable these fields in your extension via the Settings page. (<a href="https://github.com/MetaMask/metamask-extension/pull/6114">#6114</a>)</li><li>In your Activity Log on the homepage, there’s now an option to “Copy Transaction ID” in case you need to send it to a friend or jot it down. (<a href="https://github.com/MetaMask/metamask-extension/pull/6146">#6146</a>)</li><li>We’ve fixed a memory leak caused by repeated calls to isUnlocked or isApproved. Thanks to Graham Kaemmer for this one! (<a href="https://github.com/MetaMask/metamask-extension/pull/6177">#6177</a>)</li><li>Fixed several instances of address presentation across the extension that’s not EIP-55 compliant. (<a href="https://github.com/MetaMask/metamask-extension/pull/6133">#6133</a>)</li><li>There are some wild ERC 20s out there. Not all of them have a user-friendly token “abbreviation.” We now allow editing the default token symbol when adding custom token. (<a href="https://github.com/MetaMask/metamask-extension/pull/6147">#6147</a>)</li><li>The onboarding flow will trim whitespace from seed phrase during import. (<a href="https://github.com/MetaMask/metamask-extension/pull/6134">#6134</a>)</li><li>Adding custom tokens can be confusing for new users. The address label on the import form has changed from “Token Address” to “Token Contract Address” to keep things clear. (<a href="https://github.com/MetaMask/metamask-extension/pull/6182">#6182</a>)</li><li>We’ve improved some Italian &amp; Chinese translations <a href="https://github.com/MetaMask/metamask-extension/pull/6119">#6119</a>, <a href="https://github.com/MetaMask/metamask-extension/pull/6125">#6125</a></li></ul><h3>MetaMask by the numbers</h3><p>In the past month…</p><blockquote>✅ 54 PRs merged</blockquote><blockquote>🛠 220 commits</blockquote><blockquote>💫 119 Github issues closed, 50 opened</blockquote><blockquote>💥 5k lines of code added and 21k deleted (RIP old UI).</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=115474740d9f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/metamask/metamask-monthly-february-115474740d9f">MetaMask Monthly: February</a> was originally published in <a href="https://medium.com/metamask">MetaMask</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MetaMask Monthly: January]]></title>
            <link>https://medium.com/metamask/metamask-monthly-january-cd969e6e20f9?source=rss-614818abc13c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd969e6e20f9</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Bobby Dresser]]></dc:creator>
            <pubDate>Thu, 31 Jan 2019 23:37:06 GMT</pubDate>
            <atom:updated>2019-02-01T00:56:10.386Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sYaI4UNgXtqU-UZAHeR4kQ.png" /></figure><p><em>Documentation, performance improvements, security with SESify and more.</em></p><h3>Docs for the Buidlers</h3><p>We’re happy to announce the launch of our new <a href="https://metamask.github.io/metamask-docs/">developer documentation site</a>. It includes everything you need to get your dapp up and running, including sample code for some basic interactions, best practices to help your users get the most of MetaMask, and technical details on supported signing methods, APIs, and more. We’ll continue to add over time, and if there’s something you think is missing, <a href="https://github.com/metamask/metamask-docs/issues/new">we’d love to hear from you</a>!</p><h3>Protecting our dependency tree with Secure EcmaScript</h3><p>Back in November, news broke about several wallets being <a href="https://www.ccn.com/breaking-numerous-bitcoin-wallets-may-have-been-compromised-by-rogue-developer/">compromised</a> by malicious code in the wallets’ dependency graph. MetaMask has never been compromised, and we plan to keep it that way.</p><p>Since we do rely on a number of dependencies, we’re working on a <a href="https://github.com/MetaMask/sesify">project</a> to reduce supplychain attacks by using Agoric’s <a href="https://github.com/Agoric/SES">Secure ECMAScript</a> (SES) to isolate each module in its own SES container. We’ll be sharing more details about the SESify project soon as we improve its usability.</p><h3>Devs: we want to hear from you</h3><p>If you’re a developer using MetaMask to build your business, dapp, side project, main project, or anything in between — we’d love to chat. We’re always grateful for your suggestions via Github, but the MetaMask user experience research team has a number of broader questions &amp; hypotheses they’d like to test. If you’re willing to help MetaMask improve, please <a href="https://docs.google.com/forms/d/e/1FAIpQLSfdes3d9vlAsLGYz6lpxstNZSK5NNZIWumTyjqK5tsgZj0TwA/viewform">fill out this form</a>!</p><h3><strong>MetaMask, Infura, &amp; performance</strong></h3><p>Today, MetaMask relies on a service called <a href="http://infura.io/">Infura</a> to read Ethereum data and submit transactions to the blockchain. While we have <a href="https://medium.com/metamask/metamask-labs-presents-mustekala-the-light-client-that-seeds-data-full-nodes-vs-light-clients-3bc785307ef5">ambitious long-term plans to decentralize this access layer</a>, Infura makes dapp development simple in the meantime. The data show it: as of <a href="https://blog.infura.io/introducing-the-infura-dashboard-8969b7ab94e7">July 2018</a> Infura’s Mainnet endpoint serviced about 100,000 requests <em>per second</em>.</p><p>A substantial portion of this traffic comes from MetaMask users. In the past couple weeks, we’ve worked to make MetaMask’s requests to Infura more efficient by consolidating requests that fetch token balances (<a href="https://github.com/MetaMask/metamask-extension/pull/6049">#6049</a>), and by caching known method signatures (<a href="https://github.com/MetaMask/metamask-extension/pull/6052">#6052</a>). We’ll continue to trim down where possible over the coming weeks. This work will improve the performance of our application and ease our load on Infura’s infrastructure.</p><h3>MetaMask Mobile — coming soon</h3><p>We’ve been hard at work building MetaMask for iOS and Android. Mobile dapps are the future, and we want to take you there!</p><p>MetaMask Mobile will be available in app stores this spring, but we’ll be launching a Public Beta version for anyone who wants to get a sneak peek and provide feedback. Stay tuned for news on how to sign up!</p><h3>Release notes</h3><p>MetaMask 5.3.4 just hit browser stores near you — it includes features and fixes to improve the experience for devs, end-users, and everyone in between.</p><p><strong>Fixes for some common usability issues 🤓</strong></p><ul><li>We now provide a timeout and clear error message when the extension can’t connect to a user-provided custom RPC network. (#<a href="https://github.com/MetaMask/metamask-extension/pull/5893">5893</a>)</li><li>Since transactions must specify the address they’re sending from, we disabled the editable “From” address on Send screen. (#<a href="https://github.com/MetaMask/metamask-extension/pull/5922">5922</a>)</li><li>Users repeatedly thought they couldn’t access accounts once they overflowed the account menu, so we’ve added a scroll button to the accounts list. (#<a href="https://github.com/MetaMask/metamask-extension/pull/5992">5992</a>)</li><li>Several users reported confusion at seeing multiple transaction entries for attempts to speed up or cancel a single transaction. The activity log will now show one entry per nonce, grouping cancellations and speed up attempts under the transaction they modify. (#<a href="https://github.com/MetaMask/metamask-extension/pull/5886">5886</a>)</li></ul><p><strong>Bugs and patches 🐛</strong></p><ul><li>Prevent invalid Chain IDs when adding custom networks (<a href="https://github.com/MetaMask/metamask-extension/pull/6026">#6026</a>)</li><li>Fixed incorrect token conversion rates from Balanc3 (#<a href="https://github.com/MetaMask/metamask-extension/pull/6005">6005</a>)</li><li>Fixed date and time displays in the Activity Log (#<a href="https://github.com/MetaMask/metamask-extension/pull/5932">5932</a>)</li><li>Disabled account dropdown on signing screens to prevent signing from the wrong account (<a href="https://github.com/MetaMask/metamask-extension/pull/6024">#6024</a>)</li><li>Order Shapeshift transactions by time within the transactions list (#<a href="https://github.com/MetaMask/metamask-extension/pull/6021">6021</a>)</li><li>Prevent an infinite spinner bug caused by missing Network ID (#<a href="https://github.com/MetaMask/metamask-extension/pull/5924">5924</a>)</li><li>Confirm screen now shows proper function name when sending Ether transactions with hex data (<a href="https://github.com/MetaMask/metamask-extension/pull/6008">#6008</a>)</li><li>Updated Slovenian &amp; French translations (<a href="https://github.com/MetaMask/metamask-extension/pull/5966">#5966</a>, <a href="https://github.com/MetaMask/metamask-extension/pull/5970">#5970</a>)</li><li>Fixed UI errors when calling non-standard ERC20 methods (<a href="https://github.com/MetaMask/metamask-extension/pull/5995">#5995</a>)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd969e6e20f9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/metamask/metamask-monthly-january-cd969e6e20f9">MetaMask Monthly: January</a> was originally published in <a href="https://medium.com/metamask">MetaMask</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MetaMask Monthly: November]]></title>
            <link>https://medium.com/metamask/metamask-monthly-november-fc2ef185548c?source=rss-614818abc13c------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc2ef185548c</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[metamask]]></category>
            <dc:creator><![CDATA[Bobby Dresser]]></dc:creator>
            <pubDate>Tue, 04 Dec 2018 22:18:13 GMT</pubDate>
            <atom:updated>2018-12-04T22:18:13.248Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E7LWkfXEu81nnl-EJy9ImA.png" /></figure><p>Since last month at DevCon, the team has been making steady progress on our ambitious goals for the coming year. This newsletter has some updates on projects past and future, as well as several exciting shoutouts across the MetaMask family!</p><h4>An update on 1102 &amp; Privacy Mode</h4><p>Last month we launched a feature called Privacy Mode in MetaMask v5.0.0, which requires that dapps ask users’ permission to view their public Ethereum address. Over the past couple weeks, we’ve seen hundreds of applications across the ecosystem update to support this crucial privacy layer. We’re proud of the ecosystem for stepping up to protect user privacy and excited to keep working to improve the decentralized web.</p><h4>Dependency Security</h4><p>Last week a popular Bitcoin wallet was hacked, which has concerning ramifications for all cryptocurrency wallet developers and users. For a full description of the hack, you can read <a href="https://schneid.io/blog/event-stream-vulnerability-explained/">this blog post</a>.</p><p>Like all software projects, MetaMask has many dependencies in the open source world that help us bring you the ever-evolving experience you’ve grown to expect.</p><p>In addition to continuing along our roadmap, MetaMask is spending some time improving security around our key management. We’ll first lock down the dependencies related to your keys. We’re also exploring the possibility of sandboxing sensitive portions of code to add the absolute highest certainty that keys are only accessed in the intended ways.</p><p>Of course, if you’re taking advantage of our <a href="https://shop.trezor.io/?a=metamask">Trezor</a> and <a href="https://www.ledger.com/products/ledger-nano-s?r=17c4991a03fa&amp;tracker=MY_TRACKER">Ledger</a> hardware wallet support, you’d be immune to this kind of attack, provided you carefully review proposed transactions on the screen of your hardware device.</p><h4>Growing the Design Team</h4><p>MetaMask is stoked to announce our design team has grown by two! We’re welcoming <a href="https://www.linkedin.com/in/omnat/">Omna Toshniwal</a> and <a href="https://www.linkedin.com/in/juwonbahn/">Juwon Bahn</a> to the team. Omna will focus on UX Research and Juwon joins as our second product designer. Design and usability are core to MetaMask’s mission, and our product serves a variety of audiences, so we’re thrilled to have more talented hands on board.</p><p>MetaMask is still hiring for a variety of other positions – <a href="https://consensys.net/open-roles/?discipline=32543">check out our open roles</a> and get in touch!</p><h4>’Tis the Season of Giving</h4><p>This holiday season we’re reminding ourselves to give back to those less fortunate.</p><p>We’re particularly proud of <a href="https://twitter.com/randybrito">Randy Brito</a>, a member of the MetaMask support team. He and his family <a href="https://www.cnbc.com/2017/08/30/venezuela-is-one-of-the-worlds-most-dangerous-places-to-mine-bitcoin.html">fled Venezuela when he was 14</a>, and since then he’s been running an online forum called <a href="https://twitter.com/btcven/">Bitcoin Venezuela</a>. The forum teaches people how to mine bitcoin, and donations to the organization <a href="https://twitter.com/btcven/status/1057396581626978304">help fund soup kitchens</a>, <a href="https://twitter.com/btcven/status/1065774601228230657">schools</a>, farms, and continuous education. They’ve also partnered with <a href="https://medium.com/givecrypto/givecryptos-october-monthly-report-5c191bc03b56">GiveCrypto</a> to identify ways crypto can help people in need. Visit <a href="https://www.bitcoinvenezuela.com/">Bitcoin Venezuela</a> ⚡️ to learn more.</p><h3>Bitcoin Venezuela ⚡️ on Twitter</h3><p>@GiulioWolfe @elenita_tweets @ljxie @givecrypto @CriptoConserje @theairtm @eatBCH_VE @DemocracyEarth @omipediax Hi @GiulioWolfe. We (@btcven) receive donations in #Bitcoin &amp;amp; other cryptocurrencies that we then use to buy food &amp;amp; medicines which are served in soup kitchens &amp;amp; given away in the streets of #Venezuela. We&#39;re currently helping feed ~1600 ppl daily, &amp;amp; helping improve some places!</p><p>He operates this all remotely, part time, in addition to his daily work here at MetaMask. We are very proud to have Randy on our team, and deeply hope Ethereum and other decentralized technology will improve the lives of many in need.</p><h4><strong>You can help too!</strong></h4><p>Some of you may remember last year we encouraged donations to Merry Merkle, a collaboration across the blockchain community to raise money for a youth shelter in Toronto.</p><p>This year, they’re partnering with <a href="https://merrymerkle.africa/learn_more_about_the_angels.pdf">African Angels</a>, an organization that helps fund primary school education for poor and disadvantaged children in South Africa.</p><p>You can donate at <a href="https://merrymerkle.africa/">https://merrymerkle.africa/</a> or `0xf7050c2908b6c1ccdfb2a44b87853bcc3345e3b3`</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/202/0*YSYuWUCoyZQweWZc" /></figure><h3>What’s new in MetaMask</h3><p>In the past couple weeks, a few new things from around the extension:</p><ul><li>Trezor hardware wallets now work with Firefox and Brave browsers.(<a href="https://github.com/MetaMask/metamask-extension/pull/5797">#5797</a>)</li><li>The send screen now includes byte count. (<a href="https://github.com/MetaMask/metamask-extension/pull/5798">#5798</a>)</li><li>The home screen previously marked any transaction that was mined as Confirmed, but this didn’t account for transactions that failed on-chain. The distinction confused users, so we now show on-chain failures as Failed in the extension. (<a href="https://github.com/MetaMask/metamask-extension/pull/5581">#5581</a>)</li><li>The extension will now normalize contract addresses when fetching exchange rates, which fixes an issue that caused some users to see missing token conversion rates. (<a href="https://github.com/MetaMask/metamask-extension/pull/5863">#5863</a>)</li><li>To make onboarding shorter and simpler, users will now see the extension as a full-page tab after initial install. (#5835)</li><li>We’ve fixed an issue that caused some users to see an infinite spinner. (<a href="https://github.com/MetaMask/metamask-extension/pull/5860">#5860</a>)</li><li>The home screen now shows four decimal places, and when sending your “max” balance, the extension will no longer round ETH or token values. (<a href="https://github.com/MetaMask/metamask-extension/pull/5710">#5710</a>, <a href="https://github.com/MetaMask/metamask-extension/pull/5695">#5695</a>)</li><li>We’ve updated the “Connect” screen to use sites’ meta title, and pending Connect requests will now show a count on the extension badge. (#5832)</li><li>We now trim whitespace from seed phrases during import. (<a href="https://github.com/MetaMask/metamask-extension/pull/5827">#5827</a><a href="https://github.com/MetaMask/metamask-extension/pull/5861/commits/33b85cf2e482251ac266468adc2845cd8efa7f10">)</a></li></ul><h4>By the numbers</h4><p>In the past month, we saw:</p><blockquote>✅ 78 PRs merged</blockquote><blockquote>🛠 314 commits</blockquote><blockquote>💫 106 Github issues closed, 85 opened</blockquote><blockquote>💥 14k lines of code added and 5k deleted</blockquote><blockquote>📬 918 support tickets resolved</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc2ef185548c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/metamask/metamask-monthly-november-fc2ef185548c">MetaMask Monthly: November</a> was originally published in <a href="https://medium.com/metamask">MetaMask</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing: Privacy Mode]]></title>
            <link>https://medium.com/metamask/introducing-privacy-mode-42549d4870fa?source=rss-614818abc13c------2</link>
            <guid isPermaLink="false">https://medium.com/p/42549d4870fa</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[metamask]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Bobby Dresser]]></dc:creator>
            <pubDate>Mon, 05 Nov 2018 18:41:50 GMT</pubDate>
            <atom:updated>2018-11-06T18:52:51.377Z</atom:updated>
            <content:encoded><![CDATA[<h4>MetaMask 5.0 includes an optional setting that requires dapps to ask permission to view your account address.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hRqOeHpedsLdQrInNW_OUA.png" /></figure><p>If you have MetaMask installed, you know the extension makes it possible to interact with a whole world of websites built on the Ethereum blockchain.</p><p>On any site you visit, MetaMask automatically adds in a small JavaScript object we call an “Ethereum provider.” This allows websites to do things they otherwise couldn’t: propose Ethereum transactions, ask for your signature, query the blockchain, and so on. It’s how dapps get your account balance, or what lets exchanges ask for your tokens.</p><p>But when it comes to user privacy, this behavior is less than perfect. Dapp browsers like MetaMask show the Ethereum provider object to any site you visit, which means your Ethereum address is indiscriminately exposed. Since the blockchain is public, your account balance and entire transaction history are retrievable by anyone with your address. Malicious sites can use this data to fingerprint, phish, or track unsuspecting users.</p><h4>Putting you in control</h4><p>Over the past couple months, MetaMask has led an effort to improve this privacy flaw across the entire Ethereum ecosystem (documented in <a href="https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1102.md">EIP 1102</a>). We’re excited to introduce “Privacy Mode” as the user-facing piece of this new privacy layer.</p><p>As of version 4.18, MetaMask users will see a new option in their settings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*kVIVDM3VqKm3DEUq46MrvA.png" /><figcaption>Click the top-right icon, then click “Settings,” and find this option near the bottom</figcaption></figure><p>Enabling Privacy Mode means websites have to ask to see your Ethereum accounts. When a dapp asks for permission to see your accounts, you’ll see a MetaMask popup like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/456/1*2g-B7mz9SxGYSoA3CLUnLQ.png" /></figure><p>By default, we’ll remember which sites you’ve allowed to access your addresses. A future version of this feature will let users un-check an option to “Keep me connected to this site,” requiring that site to request access each time you visit.</p><p>Privacy Mode is simple for users, but it’s a significant paradigm shift for how dapps are built. (If you’re a dapp developer, read <a href="https://medium.com/metamask/eip-1102-preparing-your-dapp-5027b2c9ed76">this overview</a> for how to stay compatible.)</p><p>At first, Privacy Mode will be opt-in (and turned “off” by default). Even if you haven’t turned Privacy Mode “on” yet, we want to make it clear what’s happening under the hood, so you may start seeing the “Connect to this site” dialog as you use your favorite dapps.</p><p>If you’ve enabled Privacy Mode and are visiting a dapp that isn’t yet EIP 1102-compliant, the site may not work as expected. In this case, head to your settings, turn Privacy Mode “off,” and try again.</p><p>The MetaMask team firmly believes EIP 1102 is a crucial step towards a safe, user-friendly decentralized web. <strong>Privacy Mode will eventually be the default experience for all MetaMask users.</strong></p><p><em>For developers looking for information on how to build applications compatible with EIP 1102, see </em><a href="https://medium.com/metamask/eip-1102-preparing-your-dapp-5027b2c9ed76"><em>this post</em></a><em>.</em></p><p><em>Thanks to the dozens of developers and community members who have contributed to this standardization effort!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42549d4870fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/metamask/introducing-privacy-mode-42549d4870fa">Introducing: Privacy Mode</a> was originally published in <a href="https://medium.com/metamask">MetaMask</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>