📚 node [[memex]]

Table of Contents

Memex is a system that keeps all your data and acts as an ultimate interface to it.
It gives you fast (ideally instant access), convenient interfaces and ultimately makes you better at thinking and analysing, acting as an auxiliary brain.
Arguably so far none have been built :)

I write more on why would you want it in The sad state of personal data and infrastructure.

related

memex is the ultiplate knowledge management solution [[pkm]]

memex makes lifelogging data alive useful [[lifelogging]]

memex can give you quantified self insights [[qs]]

* my current progress

My Memex so far isn't a single unified system, but has multiple facets and interfaces.

Human Programming Interface [[hpi]]

The backbone of my memex, providing data for other components.

promnesia [[promnesia]]

Promnesia connects the web browser to the rest of your personal data.

dashboard [[dashboard]]

My quantified self component to Memex.

orger [[orger]]

Reflects my data for easier search, providing a plaintext interface.

timeline [[timeline]]

* prior art & inspiration

[2020-03-07] Memex by Andrew Louis + RubyConf 2018 talk

whoa, this is awesome
he mentions the same problems I struggled with literally in the same words!

[2020-05-25] Memri: a very promising project with the focus on user data ownership and privacy

[2021-01-31] NickSto/life-browser: View a timeline of your own history through your personal data. [[timeline]] [[memex]]

This is a project I began to try to collate all the digital breadcrumbs of my life and show them in an easily viewable timeline.

[2021-04-27] ok, interesting, but looks fairly basic, no UI yet and only contacts/location/hangouts/voice

[2020-05-11] Thanks, I'll check it out! Yep, agree about the common codebase, that's why I'm… | Hacker News

Hmm it's interesting how diverse the data sources people are actually using, but there's definitely overlap.

[2021-03-15] Heapy/Komodo-CRM: Life and collaboration assistant. [[memex]]

ran into it from
https://github.com/Heapy/Komodo-CRM/issues/72

[2021-01-21] steve-1820/memex: A brief POC of what a Memex could potentially be. [[memex]]

ok, so it's more of a prototype at this point? and they are reinventing editor/annotation… not sure

* remembrance agents

Remembrance Agents are a set of applications that watch over a user’s shoulder and suggest information relevant to the current situation

[2020-01-06] Remembrance Agent: A continuously running automated information retrieval system (1997)

This looks cool, but doesn't seem to work anymore?

[2020-04-28] A Desktop Remembrance Agent

As you type, every five seconds the prior 60 characters of your keyboard buffer are sent to the RA. Suggestions are presented as clickable buttons

Ok, this looks pretty cool.. maybe need to contact them and discuss

* ideas & concepts

[2020-06-06] hyfen.net/memex/updates/bad-remembrance-machines triplestore [[lifelogging]]

This maps pretty well to the triplestore architecture that stores triples of subject-predicate-object

[2019-12-03] Digital Tools I Wish Existed: A centralized search interface for my digital brain [[jonbo]]

This tool should: accept and parse the following queries:
 spacex announcement type:video 2016
 links from:jon@test.org topic:python
 paper on temperature, productivity referenced in book:Uninhabitable Earth
 type:pdf habits digital interfaces
 reading comprehension type:blog post
 printer ink receipt
 type:book read:2017 finance
 file:py datetime parse

[2020-05-10] lehrjulian/status/1259526773236215814 [[timeline]]

I like the idea of converting a calendar into a diary / life log by integrating different data layers.
Other layers I'd like to add:
• Locations (Google Maps, Swarm)
• Media consumption (books, Netflix)
• Browser history / Screentime
• Stress levels (Oura, Apple Watch)

@aaronzlewis : concept: a Spotify calendar integration that lets you see what you were listening to alongside your old meetings and events. revisit the vibe of any moment with the Musical Time Machine

maybe prolog for queries? [[memex]] [[hpi]]

[2020-01-08] samsquire/ideas: life engine

Life engine is a dashboard that attempts to collect information about your life and display relevant data on a single screen.

[2021-03-22] What have you failed to build? | Lobsters [[objectbrowser]]

I’ve been dreaming of making a “semantic history” browser add-on for ages, but never started.
(As in something that would collect all the RDFa/microdata/microformats/JSON-LD/… objects on web pages you’ve seen, and give you an interface to browse not just pages, but these various objects like Organization, Person, Article, etc.    )

* features & usecases

show random photos [[spacedrep]] [[lifelogging]]

[2021-03-26] Nextcloud - Wikipedia [[location]] [[degoogle]] [[memex]]

Viewer for Maps

hmm, wonder if it could replace gmaps?

* communities [[social]]

This is something we can't build alone. Let's find each other and cooperate.

[2020-05-28] karlicoss/status/1266090022123470851

I think I want to create some sort of community chat on the topic of knowledge management and tools around it, with the emphasis on interoperability, malleability, owning your data, local-first, org-mode etc.
  • [2020-06-18] I think I want the focus on existing tools and setup rather than discussing mockups and vague concepts. both are important, but I want to build something now
  • [2020-06-18] I want it to be a space to discuss configuration, and get detailed technical help etc. So needs to be more like an IM chat, with fine grained topics (so you can steer off a discussion without spamming everyone)

[2021-01-04] sadly haven't had time to set up something so far, also wouldn't want to overlap with existing ones

Some existing communities:

[2018-09-04] tesseract is best apparently? but couldn't handle elliptical photos.. [[ocr]]

[2020-10-07] eh, would be really nice to have some sort of memex at this point [[promnesia]] [[memex]]

maybe it could have some basic core (e.g. with couchdb), and then used in different apps?
e.g. promnesia uses it to jump and browse the history
dashboard uses to display all events
timeline – similarly for all life events

ugh. it's still more convenient to use google location than any of my tools.. [[dashboard]] [[grafana]] [[memex]] [[location]]

  • [2021-02-22] to be fair I didn't really do much on it yet

[2021-02-23] Экзокортекс 3.5 [[memex]]

[2021-02-23] Экзокортекс: минимальная функциональность [[memex]]

[2021-03-14] good summary and memex design requirements (in Russian)

----

Tweet from @mekarpeles [[memex]]

https://twitter.com/mekarpeles/status/1271226785439428608

@mekarpeles: Finally made a short 📽️ of https://t.co/glrT8wpAk2: Free + open source v. of @wikidata meets @RoamResearch (both which I 👍)

[2020-11-30] appaquet/exocore: A distributed private application framework

Exocore is a distributed applications framework with private and encrypted data storage. Think of like an infrastructure that allows a user to own his own personal cloud that is extensible via WebAssembly applications and accessible via Web/Mobile SDKs. It is designed to be resilient to failures, allow offline usage (ex: on mobile).

[2021-03-23] Biograph [[lifelogging]] [[inspiration]]

nice 2d representation

[2021-04-16] SQLite the only database you will ever need in most cases | Lobsters [[location]] [[sqlite]]

I used to use SQLite all the time for geospatial data using the SpatiaLite extensions, it made dealing with data in many different formats much easier (and scriptable) and just simplified a lot of the work we had to do to manage weird datasets on nationalmap.gov.au(/renewables - sadly recently made defunct due to lack of government funding).
We’d pretty regularly get CSVs with columns for LAT and LON, and need to do some actual work with the data, or turn it into another format like GeoJSON. Or we’d get a bunch of GeoJSON data that we wanted to manipulate.

[2020-08-28] from email discussion

Having stale data from manual exports is still useful, but adds a lot of mental friction ("is the export up-to-date enough to actually have what I need?").
Very good point! Just thought, perhaps some meta information about the 'recency' of the data could be included in the interface, that might remove some of the friction.
📖 stoa (open document) at doc.anagora.org/memex
⥱ context
⥅ related node [[annotation]]
⥅ related node [[as-we-may-think]]
⥅ related node [[dashboard]]
⥅ related node [[degoogle]]
⥅ related node [[device]]
⥅ related node [[hpi]]
⥅ related node [[memex]]
⥅ related node [[ocr]]
⥅ related node [[orger]]
⥅ related node [[palimpsest]]
⥅ related node [[pkm]]
⥅ related node [[project]]
⥅ related node [[promnesia]]
⥅ related node [[qs]]
⥅ related node [[social]]
⥅ related node [[spacedrep]]
⥅ related node [[timeline]]
⥅ related node [[tools-for-thought]]
⥅ related node [[vannevar-bush]]
⥅ related node [[worldbrain]]