Skip to content

Comment on We tried to run a social media site and it was awfulparent

Comments

I have my own instance, and it eats disk space, in a fun and sometimes difficult to recover way.

It caches all media that you view, and I assume it might prefetch stuff to. It has a tool that prunes out old cached images and such. However that script isn't setup to run automatically (or if it is, its far too loosey-goosey)

However the biggest killer is that it doesn't clear cached user page header images. Here is the output of my cache. Headers are not cleaned, and need to be deleted manually.

  Attachments: 1.43 GB (8.19 MB local)
  Custom emoji: 61.9 MB (0 Bytes local)
  Preview cards: 344 MB
  Avatars: 3.01 GB (71.7 KB local)
  Headers: 6.69 GB (172 KB local)
  Backups: 0 Bytes
  Imports: 0 Bytes
  Settings: 36.2 KB
AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.