You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A very, very crazy idea that I had is to componentize, modularize and give greater functionality to jnode, to the point that jnode itself is now an os cdn
why jnode in cdn?
You can share your jnode settings, programs, etc.
This automates the process of configuring jnode for multiple computers and multiple people.
better performance
increased reliability
cost savings
It avoids wasting time configuring things from scratch, as I can share my settings publicly on different machines that will use jnode.
resilience against cyber attacks.
another reason is that a cdn network facilitates software development, just see that most css frameworks are on a cdn network
how can we have jnode in cdn?
As mentioned in the initial concept topic, it is necessary to transform the jnode more and more into modules, functions and components
So... this is a way for you to make the jnode operating system even more "malleable, robust, distributed, decentralized and lightweight" - just like you see in a cdn network
usually in a cdn network there is a central server that shares data with other clients, but there may be central cdn servers communicating with each other along with other clients, this network is known as cdn-p2p, which is the idea of p2p protocol applied to the network cdn, works in cases of streaming where you want to see a movie faster without losing data along the way
A cdn operating system that I write here is something futuristic, components, modules, graphical interface and functions are distributed and decentralized in the network - something that operating systems do not have this feature
how could you implement this?
First we have to have a server that will be used to store and share configurations, modules, programs, functions, jnode components.
After that, you share data from the server through http calls or any call on any available network protocol.
how would that work in a practical sense?
Imagine that you install an application on your cell phone through a site such as playstore, apple store, fdroid, etc. I would say that in this case the playstore site is a cdn network, which connects different apps for people. This would be the same case for jnode, imagine a site where you configure your jnode and share settings with another jnode or not.
code-description: As we can see in this html file, we have a cdn server which is responsible for distributing a js file called jnode-os. Anyone can read this file or change this file and share on a cdn network, with that someone else can read this file or change this file and share on a cdn network etc
but... why jnode in cdn?
as I said at the beginning there are advantages such as security, performance, automation
but a real advantage of using a cdn network in an operating system is that most operating systems were not created that way, this would be a commercial advantage as an open project over proprietary or open operating systems today
I like technology and studying technology, one of the subjects that interests me is web 3.0 or web 3, there are people I've met who get upset with the term web 3.0, because only web 3 would be better to pronounce or talk about, something like 3.0 is something excessive to talk about
But... back to the point I want to talk about here, web 3 is not just blockchain, there are several web 3 protocols such as IPFS, Hypercore etc.
It is important to talk about other types of protocols, because many people think that it is just blockchain as a web 3 protocol, but there are several protocols as well, in this sense, as there is a concern about how web 3 will be, some people imagine, conceptualize and research how operating systems will be from now on, things like windows, mac-os and linux have evolved a lot and are offering features very close to the web 3, there are for example linux distributions that come with the IPFS protocol(already installed and configured or with a series of installed applications compatible with ipfs)
jnode in that sense could support things like IPFS, Hypercore etc which as I said are web 3 protocols, not necessarily are blockchain, are alternative protocols in blockchain network
why is it important?
it is an innovative resource, as I said, in commercial terms it is something that operating systems do not have (of course this does not indicate success, but it outlines a commercial plan or focus on a certain target audience thinking about the idea of offering some product or service to the greatest number of person in terms of sofrware)
as I said earlier, today there is a lot of research on web 3, some say that we are on web 2.5 (I can leave a link that talks about this subject specifically in case there is interest), in this sense, focus attention on supporting IPFS, Hypercore, etc. in jnode is something interesting to further increase people's interest that jnode is an innovative operating system
I didn't talk much about IPFS, but IPFS is very promising, you have a cdn network as I said in this topic, where you can store sites, general files etc. I think about using the IPFS protocol to have jnode on a cdn network
what are the disadvantages?
I don't know if support for things like IPFS, Hypercore is something the jnode community likes or wants to have in the jnode operating system
Another problem is that protocols like IPFS, Hypercore are recent protocols and there may be many technical changes in the future or now, and this can delay or compromise the development of jnode
You need things like package manager, dependency manager, module api, functions, components etc. That is, there is a lot of technical part to be developed before any official release
this feature does not guarantee success, but it is something interesting. Each open project makes some commercial decision or not to have certain resources or have a certain scope of development or management, as I said here this resource does not guarantee success, but it is something interesting from the point of view of implementation, despite being complex to do
there is scientific research on the development of distributed operating systems, but much of this is still not something 100% common for finial users - this can be an argument against the cdn network for jnode
spending money on hosting should be something planned and thought out with the community
a general problem I see is that the more modules, functions, components there are, the level of dependence on certain software increases, as well as the difficulty in analyzing certain scenarios and bugs if the jnode is too big, monolithic in terms of the project of software
what is possible to do now?
we can create a jnode package manager or dependencies, so we can configure certain behaviors or components that are part of jnode
we can create a website where jnode packages are stored
both above solutions need to be looked into by all people in the jnode community
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi.
concept
A very, very crazy idea that I had is to componentize, modularize and give greater functionality to jnode, to the point that jnode itself is now an os cdn
why jnode in cdn?
how can we have jnode in cdn?
how could you implement this?
how would that work in a practical sense?
Imagine that you install an application on your cell phone through a site such as playstore, apple store, fdroid, etc. I would say that in this case the playstore site is a cdn network, which connects different apps for people. This would be the same case for jnode, imagine a site where you configure your jnode and share settings with another jnode or not.
do you have any real proof of this idea?
code-description: As we can see in this html file, we have a cdn server which is responsible for distributing a js file called jnode-os. Anyone can read this file or change this file and share on a cdn network, with that someone else can read this file or change this file and share on a cdn network etc
but... why jnode in cdn?
why is it important?
what are the disadvantages?
what is possible to do now?
question/feedback
what do you all think of this idea?
Beta Was this translation helpful? Give feedback.
All reactions