summaryrefslogtreecommitdiff
path: root/scripts/sshd_config
blob: 4669f7fd4c9b82955a05c5545772fdbf3dfd2c64 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
UsePAM no

Match User chat
	PasswordAuthentication yes
	PermitEmptyPasswords yes
	ChrootDirectory /home/chat
	ForceCommand catgirl-prompt

	AllowAgentForwarding no
	AllowTcpForwarding no
	AllowStreamLocalForwarding no
	MaxSessions 1
	X11Forwarding no
27 -0500 committerlogin (tilde.temm)2020-02-21 23:27:27 -0500 commit61355a43749cb5507792482e64f45ad5883580dd (patch) tree10b7c85123eb43a3e54dd772d99d4297bfc52797 /tcoin.cpp parent4f1c68ddeda50c5ed971650e4fc9981d019a2c72 (diff)
Implemented message-character limits in tcoin.cpp and pcoin.cpp
After having received a 10000-character transaction message from ~jan6@envs.net, I finally came around to implementing character limits on transaction messages. Previously, I was of the opinion that one should be able to send a movie as a transaction message if one so wished. I took inspiration for an appropriate character limit from Australia's NPP (New Payments Platform), which has a 280-character limit on transaction messages. I strongly suspect this limit came from Twitter's analysis of tweets in different languages and Twitter research that concluded that a 280-character tweet was the appropriate length of tweet. A transaction message is supposedly like a tweet with some money sent along with it.
Diffstat (limited to 'tcoin.cpp')