Web2Web Bootstrap
elendirx.github.io
elendirx.github.io
> Websites get seized by losing control over a webserver or a domain. If we
> replace both the webserver and the domain with torrents and blockchain then
> there's nothing left to seize.
>
> When you open index.html in the browser, here's what happens:
> - Bitcoin address 1DhDyqB4xgDWjZzfbYGeutqdqBhSF7tGt4 is searched for the
> latest outgoing transaction containing OP_RETURN script. Inside the
> script there is a torrent infohash of webpage.html.
> - webpage.html is downloaded from torrent via webtorrent and displayed.
Edit:
Now that I think about it more, I'm a little confused about how this "decentralizes" anything, because the page is still required to get the bitcoin address in the first place? What prevents someone from seizing a domain or webserver and modifying this particular bitcoin address, other than the work involved? Can anyone familiar with IPFS speak to similarities or differences?
I'm currently working in the peer to peer application/protocol space and the biggest thing that stands out to me is the impact these technologies could have in developing countries. The challenge is making things light enough to run well on the weak hardware most people have to work with. Browser apps don't make the cut.
When you say "language" here, are you referring to the web languages (HTML, JS)?
Is this possible? If so, is there any guidance on how to achieve this?
Thanks
On the frontend side, when you install a module, it loads the .js file (using a regular <script> tag) which contains a single function. The Odoo core passes its main JS object (the base of the core API) to that function, which then initializes the whole module and uses the Odoo API to configure stuff, setup hooks, etc.
There's no security, though: by design, a module is trusted and can do anything on the platform. I'm not sure if and how one could contain them.
(Disclaimer: I'm a developer working for an Odoo partner, we write modules and host it as a SaaS.)
These concepts may hurt or cripple early developers since html/css is obvious and easy while the concept that globals, scope and the database is in an entirely seperate location seems odd. What makes it worse is that xmlhttp requests arent very kind.
The concept of the single page app and "serverless" architecture seems to be a fools errand to build (or influence big names to build) complex html applications without the need to spend money or wrappers to bridge the gap. Meteor, northwest.js and electron are celebrated for attempting to accomplish these goals.
It depends. A desktop application may have a backend, like a central web service to connect to. Even if it doesn't, there is still likely to be a logical separation of layers which may or may not be in different languages (think c++ backend with a c#/xaml front end).
As the potential capabilities in front-end web development increase, the differences between web development and "desktop" software development are reduced, because web developers find themselves facing more and more of the same questions software developers have always faced when dealing with distributed software architectures at scale.
Also IMH developer perspective HTML+JS+CSS is surprisingly a not so bad UI toolkit, and React makes the development experience even better.
I will always bet on standards and, at least for now, modern web is the standard that I can trust.
We can do better.
because that's where people's attention is.
where people's attention is, is where apps are going to be built, with whatever is there to build them.
if you think javascript is bad, get ready for SnapchatScript (that's not an actual project, but it all too easily could be, and something like it will be an actual project, some day)
I just don't get this at all. The fact that chromium books and in the past netbooks do so well is for this reason. I can't understand why you wouldn't want browser applications at this point. Outside of write once run anywhere, security and accessibility is another benefit of the browser. We still have a huge issue with the walled garden in the app space. I'm assuming you mean primarily in the mobile space ? I think this is largely due to a failure on Apple and Google's lack of wanting to innovate because they control the app stores.
1. You need to make .torrent of your content AND bitcoin transaction = EVERY even smallest change to your site which need to be seeded as new torrent.
2. If there is not enough people to seed your torrent in DHT network then you need to seed it yourself with your IP/server IP which means it can be taken off like any other website.
3. If you want to get an "account" you need to send him money? If you want this project developed you need to "throw money at him". Aha...
4. Project is connecting to blockchain instead of bitcoin nodes, which means if blockchain is down every site hosted in this system will be down.
5. The most important thing, if you will wait for 3 transaction confirmations then every update to your site will need to wait ~30 minutes or anyone will be able to impersonate as you. This is project killer.
Ok so what is an alternative? There is a new BIP pending in BitTorrent protocol that will enable to update .torrent files in DHT network which means you don't need bitcoin at all in this equation.
[1] https://en.wikipedia.org/wiki/Sybil_attack [2] http://ieeexplore.ieee.org/document/6503215/ [3] https://news.ycombinator.com/item?id=10029851
Using mutable torrents you are attaching public key to .torrent file and then just signing any changes with your private key. It's even better than bitcoin and without flaws of bitcoin which i mentioned.
You need to get information about content/website that you want to access somewhere, don't you ? So with this information you can get also sha256 of the public key that is attached to.torrent.
You might be surprised how much of a political issue this is.
Although from the source, it looks like this is really dependent on "https://blockexplorer.com/api/txs/?address=' + CONFIG.btcAddress", so still has an obvious PoF until the browser can speak BTC.
GitTorrent: https://github.com/cjb/GitTorrent
Tahoe-LAFS: https://tahoe-lafs.org/trac/tahoe-lafs
Freenet: https://freenetproject.org/documentation.html#understand
https://github.com/juanpabloaj/markdowntorrent
the content is fetched from torrents, currently the pages are down because their torrents seed are down.
when I made the project, I can't resolve to the question, how you can get the url of the content of your interest?