A database for the complex, the changing, and the indeterminate. https://upend.dev
 
 
 
 
 
 
Go to file
Tomáš Mládek 7540b31ab8
add play button to video thumbnails
2022-02-03 18:13:09 +01:00
docs first database draft 2020-09-06 12:02:55 +02:00
media dark mode upend.svg, use as favicon, create /media 2021-12-06 15:13:30 +01:00
migrations add Meta queries, check db version on start 2022-01-31 15:57:35 +01:00
src add play button to video thumbnails 2022-02-03 18:13:09 +01:00
tools [ui] add version display 2022-02-02 22:36:45 +01:00
webui [ui] spinner for video while waiting for poster to load 2022-02-03 17:04:50 +01:00
.env initial commit 2020-08-27 00:11:50 +02:00
.gitattributes add play button to video thumbnails 2022-02-03 18:13:09 +01:00
.gitignore rudimentary makefile, first "self-serving" version, enable NO_BROWSER flag 2020-08-30 23:13:09 +02:00
.gitlab-ci.yml add lib lint to CI 2022-01-30 16:52:23 +01:00
Cargo.lock (cargo-release) version 0.0.27 2022-02-03 00:12:03 +01:00
Cargo.toml (cargo-release) version 0.0.27 2022-02-03 00:12:03 +01:00
LICENSE Add LICENSE 2021-05-28 18:24:48 +00:00
Makefile add play button to video thumbnails 2022-02-03 18:13:09 +01:00
README.md add a basic README 2021-04-27 20:49:22 +02:00
build.rs add "built" crate 2022-01-31 15:19:48 +01:00
diesel.toml fix update_schema make target, diesel.toml 2022-01-21 17:58:41 +01:00
upend.desktop prepare Makefile for AppDir deploy 2021-06-11 15:07:16 +02:00

README.md

UpEnd

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