Right now we're using SQL hosted on a separate machine.
TO-DO:

• investigate block storage solutions
• investigate dedicated SQL hosting (amazon, etc.)

POSSIBLE MITIGATIONS:

• limit file-size (already done, max-upload changed on homeserver from 10M -> 5M)
• auto-expire history (per account? per room?)

• what is redaction?
• what are the basic useful commands? (/nick, /invite, /join, etc.)
• GUI-oriented explanation
• (etc.)

• bot?
• MOTD-like function?

Notes:

• important to not be annoying/pushy (pop-over CSS functionality?)
• not greet every user, only appear on request/perception of 'needing help'?
• ideally have a ubiquitous and consistent GUI method

Facebook got it right, given a gigantic userbase we need PM filtering.

• based on 3pid meta-data? i.e. more 3pid better filter weight, zero 3pid resulting in negative weight, etc.

We're mostly storing UTF-8 JSON, we can compress the fuck out of it.

• while in-database when moving to cold storage?

  • how to de-compress on request?

• on insertion?

  • expensive I/O? maybe not? gzip?

Probably need to create new URLs on main site, i.e. /learn-more/

Split into a 'hot' (=<1 month) system and a 'cold' (>1 month) system. use lazy, deferring to 'hot' within a window.

hot db:

• highly available, relatively high requests

cold db:

• highly redundant for long term-storage
• low I/O needs, any given user likely to paginate/search (barring user history dump requests, high redundancy should make synchronicity an option? maybe generate zip & URI?)

citus?