|ryan rix 06a62f4cc3 Integrate foundation. This was difficult||1 week ago|
|assets||1 week ago|
|config||1 week ago|
|lib||1 week ago|
|priv||1 week ago|
|test||1 week ago|
|.formatter.exs||1 week ago|
|.gitignore||1 week ago|
|README.org||1 week ago|
|mix.exs||1 week ago|
|mix.lock||1 week ago|
Arcology is an attempt to build a personal information management system. It grows out of a love of Emacs Org-mode and the principles behind it.
Arcology grows out of years of honing a computer down to a shape that fits naturally in my hand and head.
The road here has been slow and steady, and the road ahead stretches years, perhaps my career.
Let us begin.
This software is ideological in nature, it will be designed simply to meet the needs of Ryan Rix.
A set of ideas to keep in mind when reading this code:
These initial considerations are built around an MVP of providing an alternate implementation of GNUS Adaptive Scoring algorithm, paired with an RSS news fetching infrastructure for keeping up with subjects I care about across a broad range of topics.
But it's locked in to GNUS, it's locked in to Emacs, and it locks me to a platform that is essentially a Rube Goldberg machine around Emacs. I'm ready to build my own Rube Goldberg machine.
Features, in rough order of priority after news client completion and polish:
To enable these things:
Given a closed ecosystem, and a set of basic components like this, I can imagine a world where a set of devices sync their state and provide services to my self and my tribe and enables the lifestyle and values which I want to cultivate.
These things do not need to be in the same location, and they do not need to be homogeneous.
For the most part, we can assume things are freely internetworked using WireGuard.
I've been thinking about Capstone1 again.
I think it would be incredible to have a device like the Pixelbook or the Yoga Book which I could fit in a carry-on bag and take anywhere in the world. It syncs in the morning when I'm on WiFi in the hotel. I do whatever I want through out the day, reading ebooks, writing, creating, and then sync back when I get home. My travails are published to my website and emailed to my family. My server gets a sync of a bunch of metadata and then runs some reports.
What if this thing could program itself?
Store the code of each module in Arcology, with description and metadata like everything else. generate a deployment image from a metadata heirarchy, deploy that render the code on the web with privileged editing.
A fun first pass on this would be rendering ClojureScript to the web frontend in this respect.
Once this happens, what if we built a client delivered in this way, in a framework which can attain near-native performance?
A tablet and a mobile phone running Arcology, as a full-screen application framework, downloading the application code at startup from a local server
It's gonna take a while. I hope I can do it.
What follows for now is the Phoenix README converted to Org.
To start your Phoenix server:
cd assets && npm install
iex -S mix phx.server
Now you can visit
http://localhost:4000 from your browser.
Ready to run in production? Please check our deployment guides.