A database for the complex, the changing, and the indeterminate. https://upend.dev
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Tomáš Mládek a741bad5ee chore: stuff for mozilla webext packaging 3 hours ago
assets media: add more buttony upend icon 1 week ago
cli chore: send a header with version 4 hours ago
docs docs: add conceptual tutorial 4 weeks ago
example_vault chore: add 2 levels of directories to example 2 months ago
migrations feat!: add provenance & timestamp to Entry 2 months ago
src fix: don't needlessly insert hashy filename 11 hours ago
tools chore: rename uploadFile to putBlob, enable remote url 11 hours ago
webext chore: stuff for mozilla webext packaging 3 hours ago
webui chore: safeguard in webext against running in upend 3 hours ago
.env initial commit 3 years ago
.gitattributes add play button to video thumbnails 1 year ago
.gitignore ci, wip!: replace Makefile with Taskfile 1 month ago
.gitlab-ci.yml chore: don't package by default 7 months ago
CHANGELOG.md update CHANGELOG 3 months ago
Cargo.lock fix: panics due to async black magic 4 days ago
Cargo.toml chore: use url instead of string in address 1 week ago
LICENSE Add LICENSE 2 years ago
README.md add a basic README 2 years ago
Taskfile.yml chore: stuff for mozilla webext packaging 3 hours ago
build.rs chore: switch from `built` to `shadow_rs` 7 months ago
diesel.toml fix update_schema make target, diesel.toml 1 year ago
upend.desktop prepare Makefile for AppDir deploy 2 years ago



UpEnd is a project born out of frustration with several long-standing limitations in personal computing, as well as the recently reinvigorated interest in personal information management, hypertext and augmented knowledge work.

The core issues / concepts it intends to address are:

  1. limitations of the hierarchical structure as present in nearly all of software
  2. the neglect of (unrealized potential of) of development of base OS abstractions and features

In short, UpEnd is an attempt to build a new ubiquitous storage layer for the personal computer - kind of like "the filesystem" is now, but with more advanced semantics that better reflect the inherent interconnectedness of the data, as well as its inner "meaning", which is nowadays mostly locked within so-called application silos. Namely, it should allow for more than trivial hierarchies, building on the work done on tag-based systems and transhierarchical systems, in that all data objects (which can be files but also arbitrary structures) can be meaningfully interrelated (e.g. multiple audio tracks being renditions of the same symphony; books as well as paintings being related to the same author/genre...), arbitrarily annotated (à la ID3 tags) and traversed according to their connections - not locations; while not doing away with the benefits of hierarchies altogether.

More elaboration on this project can be found in my notes: https://t.mldk.cz/notes/883493cb-d722-45e6-bb1c-391ab523ac8b.html