Suggested business model: Vivaldi as a subscription broker
-
@eggcorn That's the main point. Nimiq (for instance) is not based on such activity.
-
@eggcorn In order to create more Bitcoin, it relies on the trustworthiness of the miners. But it is also a trust less system. To solve this, mining takes a hugely inflated processing power so that no one person can mine all the Bitcoin. As @Ayespy said this results in a huge waste of energy. It is called Proof of Work.
Nimiq (and other many other blockchains) uses a Proof of Stake model where miners are trustworthy because they lay down money. If they are caught cheating the algorithm takes the money away. And unless one person owns all the money the mining will be well divided among people. Nimiq also uses Rust WASM binaries to limit the processing power needed.
If Vivaldi used blockchain to help in a semi decentralized content provider protocol then they should probably use a PoS blockchain.
-
I'm a little sad that this entire discussion was almost exclusively about cryptocurrencies, which was completely beside the point. So long, idea.
-
@wildente Sorry!
-
-
@luetage said in Vivaldi should move on from being just another browser:
Responding to your comment in that other thread, My line of thinking is that the other browsers' business models are such that they have no interest in helping users to solve that whole subscription mess.
Vivaldi on the other hand is a bit special because their business model is to partner with certain sites already. News outlets might like it because it just adds another potential revenue stream, and I'm pretty sure everything is welcome as long as it's hardly any cost to implement and maintain.
The concept works in general as shown e.g. in the form of Readly but that is not really seamlessly integrated. Vivaldi is the point of access for everything on the web anyway. Total value add.
-
@luetage My idea, which I did not explain well, was that it is done in a decentralized fashion where Vivaldi would benefit but would not be the sole vendor.
Essentially, a master list of partner sites could be kept by the vendor, and a token could be distributed by the vendor in such a manner that everyone can read as much as they want, within reason.
Sites can declare required payments with a meta tag or JS, stating:
- Article ID
- Coin or Token Name
- Amount
- Proof of Payment API endpoint (send payment details including cryptographic signature in order to receive a proof of payment such as a cookie)