structure:
	decide on a proper structure for Message objects, and write it down

general bridging:
	pfps
		xmpp: serve pfps from file, on request
		xmpp: obtain pfps and turn them into a public url
		discord: obtain pfps into a file
	edits and deletions
		Message should have a type field, everything needs to support that
	messages without a body but just attachments

config:
	some ui for changing bridge settings/adding new buses at runtime
	? should this rewrite the config file or something?

logging:
	subloggers, somehow
	pass this into r.web and so on, somehow
	
puppeteering:
	detect existing nicks in use, avoid collisions, keep this in sync

store:
	nicer web ui
	fts 
	sort by channel, etc


irc:
	port to unrealircd s2s protocol
	OR switch to multiple c2s connections