Omni*Web

BitDurian: Omni*Web module for Durian farming, training and investment

BitDurian consists of several modules:

1. Fruit tracking

Decentralised investment is one of the most significant innovations in Omni*Web and BitDurian.

In conventional software projects, funding is usually managed centrally by a company, disbursing payments to individual programmes who are programmers or subcontractors. Blockchain programmers attempted to introduce decentralised finance methodologies to software development but their adoption has been problematic due to various technical and practical issues.

In BitDurian fruit tracking system, where big and small farmers may take photos of Durian fruits on site to generate Omnihash and DJSON codes, which can then be scanned by customers to retrieve the on site photos and relevant information, each party involved in the software development, from programmers to farm owners, may pay in cash or record their transactions using Omnihash or DJSON, to be used as a credit note to claim payments in the future.

This implementation is greatly simplified compared to Blockchain based methodologies, and can be incrementally tested and expanded in live environments, as Omnihash and DJSON decentralised features enable complete isolation of types of transactions, allowing customers to participate in simulation and testing and perform actual payments separately.


2. Multilevel Advertising & Supplier Subsidies

Small farmers are usually extremely cost conscious and may be reluctant to adopt new technologies if it involves additional costs that they cannot afford.

As such, suppliers of farming materials such as fertilisers and pesticides may offer small farmers subsidies to encourage them to adopt Omnihash fruit tracking system, as the suppliers usually have more capital and resources, and may use the subsidy scheme as an advertising campaign.

Needless to say, the supplier’s subsidy scheme can be implemented using Omnihash and DJSON.

In general, Omnihash and DJSON can be used for general purpose multilevel advertising, despite the notoriety associated with unscrupulous scammers, and we wish to highlight that proper use of cryptographic algorithms is crucial for eliminating corrupt actors and practices in business transactions.

3. Training & Investment

Besides fruit tracking, subsidies and advertising, Omnihash and DJSON can be used for training and investment purposes. In short, BitDurian and Omni*Web cover all aspects of the ecosystem of Durian agribusiness, and can be extended to other industries as well.

Cash and capital rich, diversified to other sectors.

Durian is a unique agribusiness sector that possesses many features that are non existent in other types of fruits or businesses. BitDurian introduces decentralised investment tools that carry many innovative benefits.

To illustrate, according to unofficial statistics, there are around 30,000 acres of Durian plantations in West Malaysia, of which 20,000 acres are concentrated in Rauh, Pahang. The operating costs per acre per annum is around MYR 100k, and fruit output is around MYR 150k per acre per annum, making it one of the very few investment target with annual returns higher than 20%, as well as investment quantum as little as MYR 2500 per tree per annum.

These factors make Durian an investment vehicle that has the following exceptional features:

The demand for operational funding at MYR 100k per acre per annum is no mean fest. Many plantation owners, large or small, would rather outsource the farms to subcontractors in exchange for payments before a new season than take the risks for a full year. Such transactions have been carried out amongst farm owners and subcontractors with little documentation as the Durian farmers are mostly Chinese descendants speaking various Cantonese dialects that few outsiders comprehend.

The increasing demands for Malaysian Durian, the crème de la crème, have pushed Durian prices towards MYR 80 per kg for branded variants such as Black Thorn and Musang King, and as high as MYR 120 per kg for Tupai King.

With new investors from China and elsewhere, coupled with Employees Provident Fund withdrawals at 50 and 55 years old, digitalisation of Durian contract funding using BitDurian and Omni*Web becomes a superior solution to modernise the Durian farming industry to comply with international investment practices and absorb these sources of funds.

Training

Having addressed funding issues for Durian farming, experienced Durian farm managers would become the most sought after experts, as they play THE key role in ensuring everything runs smoothly in the farm every minute, every day for a whole year until the next harvest. As such, a modern and efficient training scheme is required to manage the 30,000 acres and more newly cultivated farms in West Malaysia.

Again BitDurian employing Omnihash and DJSON provides an integrated platform for independent trainers made up of experienced farm managers to collaborate and train new farm managers at various farm locations owned by participating farm owners.

Linked with other types of training, programming, business etc.

Omni*Web is a multidisciplinary platform for experts from other fields to collaborate and train new trainees. As such BitDurian trainers may collaborate with experts from other sectors such as software, business, marketing, hospitality and so on on Omni*Web.

Hence need training

Pressure for seasonal funding

Fruit tracking statistics

We have demonstrated Omni*Web and BitDurian provide a wide range of services from fruit tracking to subsidies, advertising, investment and training, across multiple disciplines. Fruit tracking statistics provide accurate data which can be used to analyse the prospects of investments. Performance of trainers and trainees, tracked using Omnihash and DJSON can also be used to predict profitability of farms. Advertising and subsidies further promote the growth of BitDurian and Omni*Web to prospective users, programmers and investors.

development

Decentralised investment

Omni*Web: A Truly Decentralised Web Ecosystem

Omni*Web is a free software or open source project, aimed at creating a truly decentralised web ecosystem, owned and operated by free individual users and free software programmers, employing the following breakthrough technologies:

The main keywords above are “truly decentralised web ecosystem, owned and operated”, and the essence lies in the word “owned”, a very common and important English word that is used daily, but poorly defined in the digital realm and yet very few people are aware of the consequences of lacking awareness on ownerships of digital assets, which is one of the educational goals Omni*Web aims to overcome.

  1. BitDurian
  2. BitKotong
  3. BitComics
  4. Omni*Training

For DJAX demonstration, you may just press the LIKE button for this article, which generates a DJSON, which in turn is simply a JSON string consisting one or more Omnihash code,

The DJSON string is compressed using GZIP and encoded as URL safe base64 string, and sent to one of the 3 following options for storage:

  1. Omni*Web I2P (Invisible Internet Project) server
  2. NGROK
  3. GitHub Issues

How does simply adding Omnihash or compatible hash codes to JSON strings make DJAX the biggest breakthrough since AJAX?

This is due to the many powerful cybersecurity properties associated with hash codes that are usually overshadowed by other fanciers algorithms.

We will illustrate the properties of Omnihash or hash codes with examples. The first example shown here is simply a like on this very article. The DJSON will record the following:

nobody

In the JSON string shown above,

As you can see, user_hash and timestamp will be unique and thus the hash code or Omnihash generated from this JSON string, FCrM-oxkcg==, will be “cryptographically unique” as the look-up address.

Omnihash shown above FCrM-oxkcg== can be used to retrieve DJSON from various storage (back-end) platforms, including but not limited to:

  1. I2P (Invisible Internet Project)
  2. NGROK
  3. GitHub Issues

20 years have elapsed between AJAX and DJAX, a Decentralised version of the former, one of the most fundamental operations for sending data between front end browser or application and back end server.

One may conjecture in hindsight what delayed the transition from AJAX to DJAX, given all the essential technologies existed way back in 2005. The Occam’s razor answer might be MMAGA obstructions, given that if DJAX eventually command 0.1% of MMAGA revenues by 2030 which would exceed USD 1 billion annually.

The above conjecture can be verified using DJAX as it spreads to include more server nodes contributed by free individual users and free software programmers. , with a theoretical upper limit engulfing all devices owned by individual users and free software programmers, practically exceeding those owned by non biological corporations.

So perhaps the simplicity of DJAX and the lack of explanation of its delay may be equally interesting to the potential of DJAX to create a truly Decentralised web ecosystem owned and operated by free individual users and free software programmers.

DJSON or Decesntralised JSON is a critical breakthrough by Omni*Web where base 64 hash codes representing any kind of digital assets and entities, from user identifiers to social media actions such as like, comment and share, are embedded in the unassuming ubiquitous JSON strings.

Underlying decentralised JSON is an extension of the Bitcoin address, which is derived from the hash of a public key, to be used as a user identifier. The generalisation of the hash of public key as user identifier is a breakthrough in decentralised computing, as previous frameworks based on blockchains or cryptocurrencies are heavily monopolised by miners.

What makes DJSON so special and powerful is what we call “type preservation property” of hash numbers and integers, which is derived from Ring theory properties of integers, where the operations of additon and multiplication on integers invariably result in integers as output.

The previous paragraph may sound like your typical high school mathematics nightmare, but it is the biggest secret underlying Bitcoin and other cryptocurrencies as well as novel decentralised social media platforms as we shall see in the following example:

We will reveal the answer first and explain later as we assume there are readers who are impatient:

In the DJSON above, the fields are:

doc_hash means hash of URL of document.

The following are the steps for generating the “like” DJSON of this article, accompanied by a video:

  1. Save a copy of this web page as a local file on Omni*Web server.
  2. Generate doc_hash for this document.
  3. Make a subdirectory for this document with doc_hash.
  4. Copy neccessary files and soft links.
  5. Open the local copy on Omni*Web server using I2P (Invisible Internet Project) and doc_hash.
  6. Start Omni*Shell from browser console.
  7. Refresh authentication token with user’s public key.
  8. Send “like” DJSON from browser console using Omni*Shell Phoscript commands.

If the steps above look daunting to you then you will be pleased to know that those are exactly what happen millions of times per seconds around the world when “like” buttons are clicked on social media platforms – except that YOU, the users and free software programmers, do not OWN and OPERATE any part of that, and therefore CANNOT make any money out of it.

… which brings us to Omni*Web aim – to create a truly decentralised web ecosystem, OWNED and OPERATED by free individual users and free software programmers, capable of providing free alternatives to ALL existing services provided by the biggest trillion dollar corporations such as MMAGA – a funny abbreviation for Microsoft, Meta, Amazon, Google and Apple.

Omni*Web will attempt to improve Jekyll’s documentation, as we shall do for other free software projects too,

This article itself will demonstrate several features of Omni*Web aiming at improving Jekyll documentation and promoting it, as well as introduce metaprogramming features that can be used to extend Jekyll’s functionalities.

One of Omni*Web most important innovation is Decentralised Full Stack Programming (DFSP).

Decentralised Full Stack Programming using Hash

Full stack programming has evolved out of the need to coordinate web browser front end and server back end functionalities. Over many years, many frameworks have been developed and front end modules have now included mobile device environments. Their complexities have grown exponentially and we now proposed a decentralised programming paradigm based on hashes, greatly simplifying overall full stack operations.

To summarise the whole idea before delving into details, we present an example where a user responds to a post with a comment on a GitHub page, where the URL of the original post and the user’s comment, as well as the user’s identifier are represented by hashes, and these hashes can be hashed using a hash function to produce a root hash, representing the overall transaction.

The user may submit the transaction JSON and its hash to a server independently operating unrelated to the GitHub page server, as long as it understands and complies with the protocols determined by the hashes.

A user may claim the same identity with different hash identifiers as long as they can prove the chain of identities by verifying ciphers using the private key for each of the identities.

Jekyll

Jekyll in a nutshell is like a pure front end MVC framework, so that mega websites like GitHub will feel safe to provide pseudo MVC features to its users, in this case, primarily programmers.

Jekyll is the default markdown document parser on GitHub, which is very powerful, but unfortunately has some rather confusing documentation and not so easy to debug.

Decentralised Monetised Collaboration

Demon Collab

Demon’s Con

Omni*DOC

It is interesting how word tricks in English and Latin play out.

The Latin root of “collaborate” is “con” + “laboro”, where “con” is a variation of “cum” meaning “with”.

As such, Decentralised Monetised Collaboration is shortened as “Demon’s Con”.

We will tentatively use Demon’s Con as the nickname for Decentralised Monetised Collaboration, as we have received feedback that the cryptocurrency industry now has such a bad reputation that we might as well use a Latin word trick to engage users.

We know some self proclaimed Christians have long associated cryptography with the works of Demons, in folklores like 666. We are interested in engaging in conversation with Christians or any self proclaimed believers in monotheistic religions as we are aware that there are many countries which still practise laws that may prosecute anyone unilaterally as conducting blasphemy, some punishable by death, in 2025 Anno Domino.

However, bringing up Christian demons and 666 also appeals to a large number of fans who are critical of Christian traditions as well as those affected by bad publicity about cryptocurrency and decentralised technologies, bearing in mind that the Washington Wall Street elites prefer to brainwash the American population so that they continue to maintain their monopoly of power in politics and finance.

Decentralised Monetised Collaboration

Demon Collab

Demon’s Con

As the name suggests, Decentralised Monetised Collaboration consists of 3 components: Decentralised infrastructure, Monetisation Legal Framework and Collaborative Transactions.

Collaborative transactions are the most common as they include everything from Google documents to TikTok posts.

Decentralised infrastructure includes everything from I2P invisible internet project which enables everyone to set up server hosts connected to Internet without the Domain Name System, to Omnihash which is a novel hash algorithm for representing ownership of any kind of digital assets.

Monetised Legal Framework means employing decentralised hash algorithms to establish digital legal contracts, including loans, payments and investments.

What can we achieve by combining all 3 components of Decentralisation, Monetisation and Collaboration?

Adding Decentralisation to Collaboration will produce a UNIFIED interface to collaborative transactions. In plain English, it will enable you to combine posts and comments from ALL social media platforms into one integrated platform.

For example, one of the biggest bottlenecks of chatting with artificial intelligence systems is that the conversation results cannot be automatically published, shared and put into collaboration with other users or AI systems.

With Omni*DOC, where D stands for Decentralisation, O for Oro or gold in Spanish, C for collaboration, a user’s conversation with any AI systems can be republished, shared, commented and so on just like any existing social media posts.

Omni*DOC will behave very differently from conventional social media platforms where the operator of the platform will appoint or employ moderators to filter inappropriate speeches. On Omni*DOC however, users themselves may make the decision to choose custom filters to filter out posts or comments that they themselves deem inappropriate.

Omni*DOC works by first converting any URL into a hash code, which can be anything from 53 bits to 512 bits or longer.

Secondly, the hash of URL of HURL will be shared amongst servers running Omni*Web modules.

Thirdly, any of Omni*Web servers may decide to create cache copies of a given URL for further processing.

Up to this stage, Omni*Web behaves like a Decentralised cache and search network, i.e. instead of a huge centralised search engine operated by one company such as Google or Microsoft, the power of Omni*Web depends on the number server nodes participating. It basically works like Waybackmachine but its functionalities can be extended by any user or programmers, as long as they conform to Omni*Contract conditions and protocols.

Social media functionalities exist from step 4 onwards. Although there exist differences amongst social media platforms, different user interface elements are essentially functions which can be represented as paths in graph theory. Further, different paths are represented as hashes, as the ring properties of integers ensure hashes can be concatenated as input to produce an output hash which is also another integer. We may call this property type preservation, namely, the types of inputs and output are preserved. The type preservation property of hashes makes it convenient to manage various types of functions on social media applications.

First 3 stages, multiply servers. Applying hash in server address.

Stage 4, multiply functionalities. Applying hash in data address.

In conventional MVC programming, function calls and data types are tightly coupled to types of data and how they are processed. In hash metaprogramming, everything is hash and hashes are compatible with each other due to type preservation property.

Hash applicable in server and data addresses due to type preservation property.

Omni*DOC Example

This document itself is an example of Omni*DOC anyone may comment, share and follow up etc or add functions they wish.

Move this up as it is easiest to understand.

For example, chat results with AI, repost, comments, follow up.

Demon Collab

Demon’s Con

demonscon

links to backend, backend use I2P addresses

site.data.people[page.author]

[Hello World!][1] [1]:javascript:alert(‘Hello World’)

[Omni*Web][1] [1]:javascript:m_oxmobile()

Hello World

Omni*Web

This site is open source. Improve this page.