mirror of
https://github.com/kremalicious/blog.git
synced 2024-06-28 16:48:00 +02:00
content changes
This commit is contained in:
parent
3adb682245
commit
053df74b28
GPG Key ID:
606EEEF3C479A91F
|
|
@ -22,7 +22,7 @@ I'm using macOS Catalina (10.15) for the following instructions but it should wo
|
|||
|
||||
## Tor Browser
|
||||
|
||||
|
||||
|
||||
|
||||
The most simple way to surf anonymously with Tor is to just grab [Tor Browser](https://www.torproject.org/projects/torbrowser.html.en). It's a modified version of [Firefox Extended Support Release (ESR)](https://www.mozilla.org/en-US/firefox/organizations/) with Tor and some extensions (Torbutton, TorLauncher, NoScript, and HTTPS-Everywhere) built right in. Upon start, Tor Browser automatically starts the required Tor background processes and routes traffic through the Tor network. That's the way to go if you want the highest level of protection without much further configuration.
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ You can do this under _System Preferences > Network_ by creating a specific Tor
|
|||
- _SOCKS proxy server_: `localhost`
|
||||
- _Port_: `9050`
|
||||
|
||||
|
||||
|
||||
|
||||
After hitting _OK_ & _Apply_ at the initial network screen, you can easily switch to this newly created location from your menu bar under _ > Location_ whenever you start up Tor.
|
||||
|
||||
|
|
@ -121,7 +121,7 @@ tor.sh
|
|||
|
||||
and Tor should run smoothly on your system without additional configuration:
|
||||
|
||||
|
||||
|
||||
|
||||
Verify you're indeed browsing over the Tor network by going to [check.torproject.org](https://check.torproject.org).
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: CSS App Store Badges
|
||||
image: ../media/teaser-appstorebadges.png
|
||||
image: ./teaser-appstorebadges.png
|
||||
|
||||
author: Matthias Kretschmann
|
||||
date: 2015-09-13 18:55:18.418548000 +02:00
|
||||
|
|
@ -28,8 +28,15 @@ So all buttons are just set in Apple’s San Francisco UI font with this funky f
|
|||
|
||||
```css
|
||||
.badge {
|
||||
font-family: system, -apple-system, '.SFNSDisplay-Regular', 'San Francisco', 'Helvetica Neue',
|
||||
'Helvetica', 'Arial', sans-serif;
|
||||
font-family:
|
||||
system,
|
||||
-apple-system,
|
||||
'.SFNSDisplay-Regular',
|
||||
'San Francisco',
|
||||
'Helvetica Neue',
|
||||
'Helvetica',
|
||||
'Arial',
|
||||
sans-serif;
|
||||
}
|
||||
```
|
||||
|
||||
|
Before Width: | Height: | Size: 338 KiB After Width: | Height: | Size: 338 KiB |
|
|
@ -34,13 +34,13 @@ The primary target audience for our [Commons Marketplace](https://commons.oceanp
|
|||
|
||||
All permissions are handled through your wallet account in MetaMask, there’s no login or password or any of that old-school Web 2.0 stuff. You unlock your MetaMask account, and you’re ready to go.
|
||||
|
||||
|
||||
|
||||
|
||||
You can discover the open data sets in Ocean’s Nile network, even if you don’t use a Web3-capable browser.
|
||||
|
||||
While focusing on free data assets only, Commons has the full Ocean Protocol flow implemented for registering and consuming assets. All files attached to an asset have their URLs encrypted and when you want to consume a data asset, URLs are decrypted and the respective files are downloaded.
|
||||
|
||||
|
||||
|
||||
|
||||
In its current state, the Commons marketplace is a minimum useful product to help you get a feel for what a data marketplace could look like in the future. Expect many more iterations in the next weeks and months. If you run into issues, or want to suggest new features, feel free to [report them on GitHub](https://github.com/oceanprotocol/commons/issues/new).
|
||||
|
||||
|
|
@ -88,7 +88,7 @@ To connect to the Nile network:
|
|||
|
||||
3. Hit _Save_, and you’re now connected to Nile:
|
||||
|
||||
|
||||
|
||||
|
||||
The Commons marketplace includes a faucet functionality under [https://commons.oceanprotocol.com/faucet](https://commons.oceanprotocol.com/faucet) from where you can easily request some Ether to be added to your account by clicking the _Request Ether_ button:
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ When an asset is registered into Ocean Protocol, the file URLs are encrypted and
|
|||
|
||||
We tweaked all of the relevant [Ocean Protocol components](https://docs.oceanprotocol.com/concepts/components/) in the background (Aquarius, Brizo, Secret Store, Squid-js) to be able to provide a faster consume flow. We also added more real-time feedback during the whole process in the UI. In combination, these steps introduced a much more stable consume flow and a dramatic decrease in real and perceived time required to download an asset in Pacific.
|
||||
|
||||
|
||||
|
||||
|
||||
It is still not as fast as we would like it to be, and we will continue to make improvements on the speed over time.
|
||||
|
||||
|
|
@ -46,7 +46,7 @@ We found this to be one of the main pain points users had when interacting with
|
|||
|
||||
We’ve started adding some improvements to remedy this, and so that Ocean developers will be able to debug more quickly:
|
||||
|
||||
|
||||
|
||||
|
||||
But telling users to read some version numbers and act on it can’t be the solution.
|
||||
|
||||
|
|
@ -56,7 +56,7 @@ We went back to the drawing board, created some [concepts and prototypes](https:
|
|||
|
||||
A burner wallet is a frictionless but disposable wallet, often used for signing transactions only, or to move small amounts of tokens around. They are usually [hierarchical deterministic wallets (HD wallet)](https://en.bitcoinwiki.org/wiki/Deterministic_wallet), generating a set of public/private keys from a random seed phrase. But the keys are not protected as much as in a “normal” wallet, and in our case the seed phrase is stored in your browser’s cache, hence the low-security aspect.
|
||||
|
||||
|
||||
|
||||
|
||||
Luckily, this doesn’t matter for interactions in the Commons Marketplace, where all assets are free and don’t require any transfer of tokens. All that is required to interact with all Ocean Protocol features in Commons is a wallet for signing during the register & consume requests.
|
||||
|
||||
|
|
@ -66,17 +66,17 @@ Conceptually, a burner wallet’s private keys are supposed to be destroyed (“
|
|||
|
||||
Any visitor to the Commons Marketplace will be switched to a burner wallet by default. In the background, we create a wallet in your browser from a random mnemonic with [Truffle’s HD Wallet](https://github.com/trufflesuite/truffle/tree/develop/packages/hdwallet-provider) and pass that wallet to Web3 as the provider. We then load its first generated account and also send some Pacific ETH (not to be confused with Ethereum Mainnet ETH) from our [Faucet](https://github.com/oceanprotocol/faucet) to that account, in order to cover eventual Gas costs for publishing and consuming.
|
||||
|
||||
|
||||
|
||||
|
||||
We try to give you some persistence across sessions though, by storing that seed phrase in your browser’s _localStorage_, and on next visit we’ll generate your wallet again from this seed phrase, so you’ll get the same account again. This persistence is needed so we can provide you with some basic level of personalization, e.g. the _History_ page will show the assets published by you, meaning by the Web3 account you are using.
|
||||
|
||||
Phew, that’s a lot of tech going on in the background — so let’s get back to the UI! All those tasks are moved aside and are not visible to end users. They essentially transform the previous view where consuming was not possible without a Web3 browser or MetaMask:
|
||||
|
||||
|
||||
|
||||
|
||||
Into this view, unlocking the consume flow even for non-Web3 capable browsers without any user action required:
|
||||
|
||||
|
||||
|
||||
|
||||
> **Disclaimer:**
|
||||
> Being low-security and disposable by design, a burner wallet should not be used if you want to keep track of all your published and downloaded assets, or if you want to hold tokens in it. We strongly suggest not using any burner wallet generated in Commons to move or hold any tokens. The burner wallet only exists in your browser and is geared towards usage in Commons only. We don’t ever store any account information so we are not able to restore a lost burner wallet.
|
||||
|
|
@ -85,25 +85,25 @@ Into this view, unlocking the consume flow even for non-Web3 capable browsers wi
|
|||
|
||||
If you require more security, you can optionally switch to [using MetaMask](https://docs.oceanprotocol.com/tutorials/metamask-setup/) with an account that only you control. If we detect your browser is able to use MetaMask (i.e. is Web3-capable), we show an action for switching the wallet you’re using in Commons:
|
||||
|
||||
|
||||
|
||||
|
||||
In the wallet selector you can switch to MetaMask:
|
||||
|
||||
|
||||
|
||||
|
||||
After selecting MetaMask, the UI switches to your first account in it. If you use MetaMask for the first time with Commons, you will be prompted by MetaMask to approve reading access to your accounts:
|
||||
|
||||
|
||||
|
||||
|
||||
Approving this request results in your first MetaMask account being selected, displayed and ready to use in Commons:
|
||||
|
||||
|
||||
|
||||
|
||||
We also store your selection and, on your next visit, we switch to MetaMask automatically.
|
||||
|
||||
Additionally, we allow you to export your burner wallet by providing the seed phrase you can use to import the wallet into MetaMask:
|
||||
|
||||
|
||||
|
||||
|
||||
This is helpful if you have already made some interactions in Commons, published and consumed some assets, and now want to keep your history and transactions in an account you control.
|
||||
|
||||
|
|
@ -121,7 +121,7 @@ With [Pacific](https://docs.oceanprotocol.com/concepts/pacific-network/) running
|
|||
|
||||
This all provides much more helpful feedback in case of network & account misconfigurations, e.g. if you use MetaMask and are connected to the wrong network:
|
||||
|
||||
|
||||
|
||||
|
||||
For this check we fetch the network from the Brizo endpoint configured in Commons client, then check that against the network you’re connected to in MetaMask. This allows Ocean devs to deploy the front-end into any network, and it will figure out the correct network combination automatically, and show relevant help messages.
|
||||
|
||||
|
|
@ -139,7 +139,7 @@ As a developer, this also means you can use the Nile & Duero installations as a
|
|||
|
||||
The Ocean Versions component in those Commons installations under their _About_ pages allows you to see which endpoints are in use:
|
||||
|
||||
|
||||
|
||||
|
||||
And you can use the [Commons client & server](https://github.com/oceanprotocol/commons) locally on your machine to fully customize it for your Ocean testing purposes, and as a blueprint to build your own marketplace on top of Ocean Protocol.
|
||||
|
||||
|
|
@ -151,7 +151,7 @@ A feature to enhance data discoverability and introduce a first basic curation m
|
|||
|
||||
Our first channel is AI For Good, created as part of the [AI for Good Global Summit 2019](https://aiforgood.itu.int) in Geneva. [AI for Good](https://blog.oceanprotocol.com/ai-for-good-at-scale-7bc65b51d764) is an initiative to promote the use of artificial intelligence for taking action on the [United Nations Sustainable Development Goals (SDGs)](https://www.un.org/sustainabledevelopment/sustainable-development-goals/) such as fighting poverty, climate change, improving healthcare, etc. The AI for Good Commons channel is aimed at helping scale AI for Good by enabling relevant open datasets to be published and shared and connecting AI problem owners with problem solvers. All curated by the Ocean Protocol team.
|
||||
|
||||
|
||||
|
||||
|
||||
- [**Channel: AI For Good →**](https://commons.oceanprotocol.com/channels/ai-for-good)
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user