From 51a689ee080d81639cc9581bd4cbc45f3a7883ab Mon Sep 17 00:00:00 2001 From: lostMia Date: Fri, 11 Oct 2024 19:18:25 +0200 Subject: [PATCH] Rewrote hard-to-read parts, fixed typos --- README.md | 49 ++++++++++++++++++++++++------------------------- 1 file changed, 24 insertions(+), 25 deletions(-) diff --git a/README.md b/README.md index 0f53e5f..ae83cae 100644 --- a/README.md +++ b/README.md @@ -1,38 +1,37 @@ # MiZe - An implementation of how I think data should be handled. -- Slogan: Elevate the unix file Philosophy into the age of connectivity. +- Slogan: _Elevate the Unix file philosophy into the age of connectivity._ -## Why I'm doing this. -- What annoyes me about Software these days is things are done in so many different ways. - - e.g: Different Cloud Apps for syncing data (Google-Cloud, Onedrive, Dropbox) - - e.g: Every App stores the Data it deals with in it's own way (the way that the developer thought is best for this particular app) +## Why am I doing this? +- What annoys me about software these days is, that things are done in so many different ways. + - e.g: Different cloud applications for syncing data (Google Cloud, OneDrive, Dropbox) + - e.g: Every app stores the data it deals with in it's own way (the way that the developer thought is best for this particular app) -- Back when Unix came out EVERYTHING was stored in one place: the file system of the computer. +- Back when Unix came out **everything** was stored in one place: the file system of the computer. - (just as simple bytestreams/files, organized by a folder-structure) - and NO program stored and synced any data around in unpredictable ways. -- This Philosophy is still used in every Unix/Linux machine, on a local level, but completely abstracted away (especially on mobile phones) from the user (by every App). +- This philosophy is still used in every Unix/Linux machine, on a local level, but completely abstracted away (especially on mobile phones) from the user (by every app). -- I would say: The Unix File system just hasn't evolved into the age of connectivity. It is still completely the same. And I think it shouldn't be. +- I would say: The Unix file system just hasn't evolved into the age of connectivity. It is still completely the same. And I think it shouldn't be. -- miZe aims to bring that idea of storing all data +- MiZe aims to bring that idea of storing all data - in one place - in one predictable and simple way - - and programms only taking data from there and not storing it everywhere in messy ways -- back ... into the age of connectivity. + - and programs only taking data from there and not storing it everywhere in messy ways -- That's why the slogan is going to be: Elevate the unix file Philosophy into the age of connectivity. +- That's why the slogan is going to be: _Elevate the unix file philosophy into the age of connectivity._ -## How I'm going to do this. -- Is not yet completely clear, but what I know so far: - - Using what I call "Items" instead of Files - - With "Items" being a key-value store of strings/bytestreams - - Those "Items" have types, that give meaning to the key-value pairs. - - A Server Written in Rust that stores those "Items". - - A way to mount "Items"(or parts of them) into a regular filesystem. - - Webcomponents to show/render the contents of Items in a Browser (or electron style apps). - - Server middleware to connect external apis (emails, youtube, google account) to this ecosystem. - - The Server is one binary without any external requirements (that should run on any POSIX system) - - to make it simpler to deploy - - I've previously experimented with using MongoDB to store items, but then there has to be a MongoDB instance running that the server can connect to. And the connection can fail ... and lots of other things can go wrong. - - I want a binary that you just start and it's a working server. +## How am I going to do this? +Is not yet completely clear, but here's what I know so far: +- Using what I call "Items" instead of files + - With "Items" being a key-value store of strings/bytestreams + - Those "Items" have types, that give meaning to the key-value pairs. +- A server written in Rust that stores those "Items". +- A way to mount "Items" (or parts of them) into a regular filesystem. +- Web Components to show/render the contents of items in a browser (or Electron-style apps). +- Server middleware to connect external APIs (e.g. emails, YouTube, Google accounts) to this ecosystem. +- The server is one binary without any external requirements (that should run on any POSIX system) + - This makes it very simple to deploy + - I've previously experimented with using MongoDB to store items, but that requires a MongoDB instance to always be running that the server can connect to. And the connection can fail ... and lots of other things can go wrong. + - I want a binary that you can simply start, which then provides a working server.