Go to file
sneak bf404db2af
Some checks failed
continuous-integration/drone/push Build is failing
bump to go 1.14
2020-03-30 16:06:44 -07:00
cmd/feta updated for new git locationupdated for new git location 2020-02-04 23:55:31 -08:00
database major overhaul, including: 2020-03-30 16:05:53 -07:00
ingester major overhaul, including: 2020-03-30 16:05:53 -07:00
instance now actually does something 2020-03-27 19:57:58 -07:00
jsonapis now passes linting 2019-12-19 05:20:23 -08:00
locator builds again 2020-03-27 18:17:52 -07:00
manager now actually does something 2020-03-27 19:57:58 -07:00
process major overhaul, including: 2020-03-30 16:05:53 -07:00
seeds working toward storing state in db 2020-03-27 16:02:36 -07:00
storage now actually does something 2020-03-27 19:57:58 -07:00
toot now actually does something 2020-03-27 19:57:58 -07:00
view major overhaul, including: 2020-03-30 16:05:53 -07:00
.drone.yml remove circleci config, don't push on drone build 2020-03-27 16:07:55 -07:00
.gitignore now actually does something 2020-03-27 19:57:58 -07:00
Dockerfile bump to go 1.14 2020-03-30 16:06:44 -07:00
go.mod major overhaul, including: 2020-03-30 16:05:53 -07:00
go.sum major overhaul, including: 2020-03-30 16:05:53 -07:00
Makefile working toward storing state in db 2020-03-27 16:02:36 -07:00
README.md builds again, not sure how i broke it, also: 2020-03-27 20:20:53 -07:00

feta

archives the fediverse

todo

  • scan toots for mentions and feed to locator
  • put toots in a separate db file
  • test with a real database
  • save instancelist to store more often (maybe on each new one added not during initial load)
  • verify instances load properly on startup
  • do some simple in-memory dedupe for toot storage
  • make some templates using pongo2 and a simple website
  • update json APIs
  • index hashtags
  • index seen urls

status

Build Status

ethics statement

It seems that some splinter groups are not well acquainted with the norms of publishing data on the web.

Publishing your toots/messages on a server without marking them private or requiring authentication and thus making them available to the web is an act of affirmative consent to allowing others to download those toots/messages (usually by viewing them in a browser on your profile page). If you don't want your toots downloaded by remote/unauthenticated users on the web, do not publish them to the web.

If you publish them to the whole web (and your home instance serves them to all comers), do not be surprised or feel violated when people download (and optionally save) them, as your home instance permits them to.

We do not have a right to be forgotten, as we do not have a right to delete legitimately-obtained files from the hard drives of other people.

Author

Jeffrey Paul <sneak@sneak.berlin>

@sneak@sneak.berlin