Apps


Now that we’ve got this cute lil document store, it would be nice to build some “apps” on top of it. As tech demos, for utility, etc. Wallabag/Wayback I think this would be fairly easy to do (famous last words). The implementation is straightforward though: a (baked in?) template type for archived URLs. it only needs parameters for “URL” and “frequency” a Cron hook that refreshes them if necessary/archives them creating a WARC which is attached to the record as an attachment updating the contents field with a markdownified preview of the article a la Firefox’s readability. CalDav it would provide API endpoints to behave as a CalDav server, and also potentially produce an iCal file like Google calendar does the iCal file is relatively more trivial, but the CalDav endpoint configuration, I guess we would choose a backend where new events are automatically added. Additionally scoping it within a project is potentially interesting, so e.g. we could have a url for just the gallantries calendar, and we could freely share that url, and anyone with it could create events on the calendar for us WebDAV or at minimum a file/folder browser view of files and attachments similar to how next cloud shows files and folders. except each folder is a note, and the files are the attachments

Now that we’ve got this cute lil document store, it would be nice to build some “apps” on top of it. As tech demos, for utility, etc.

Wallabag/Wayback

I think this would be fairly easy to do (famous last words). The implementation is straightforward though:

a (baked in?) template type for archived URLs.
- it only needs parameters for “URL” and “frequency”
a Cron hook that refreshes them if necessary/archives them
- creating a WARC which is attached to the record as an attachment
- updating the contents field with a markdownified preview of the article a la Firefox’s readability.

CalDav

it would provide API endpoints to behave as a CalDav server, and also potentially produce an iCal file like Google calendar does

the iCal file is relatively more trivial, but the CalDav endpoint configuration, I guess we would choose a backend where new events are automatically added. Additionally scoping it within a project is potentially interesting, so e.g. we could have a url for just the gallantries calendar, and we could freely share that url, and anyone with it could create events on the calendar for us

WebDAV

or at minimum a file/folder browser view of files and attachments similar to how next cloud shows files and folders.

except each folder is a note, and the files are the attachments