lemmy: cache posts from post list, too

lemmy: implement comment ModTime

lemmy: implement client-side community, post caching Servers now provide a Cache-Control header in the HTTP response, so we can use that for some dead simple caching.

lemmy/fs: implement post text file

lemmy, lemmy/fs: have comments as entries in post directories

lemmy: make zero client ok

fs: let it compile yeah...

lemmy/fs: KISS. Keep posts and comments as files in the same dir Kinda like NNTP.

cmd/Lemmy: show real usernames, render comment threads To make this easier and smaller, we now use the lemmy package directly rather than the filesystem interface. Can't think of a nice way to use that filesystem (yet?).

lemmy: decode person, counts from API responses We want these so we can render the info easily in clients

lemmy: fix up, export comment path parsing for commands

lemmy: decode published, updated times Now that the Lemmy API returns nice timestamps, it's all done automatically by Go's JSON package.

fs: skip tests if we can't connect to test instance

lemmy: start decoding users in API responses This commit adds tests too as it's starting to get a bit trickier.

add Lemmy command for the acme text editor

Rework, move filesystem into its own package Major rework which keeps Stat, Read and ReadDir away from the filesystem tree and more to the file. The fs package implements extra functionality that doesn't really have anything to do with the core package. It also does not need to know how the core lemmy package is implemented to do anything, so may as well enforce the boundary explicitly.

correct godocs.io link

start documentation!

Only cache communities in filesystem This keeps things simpler

initial commit