Block a user
timestamp on front update
just realised this is not a table anymore for about 92384729 updates hahaha. so this actually depends on coding the front log, since the latest entry to that will be the timestamp source
validation on imports
all types of imports should be checked, there needs to be validation on the fields included to, to futureproof the feature. probably a ci issue. be mindful of this basically
remove sub directories from exports
not doing this, it makes re-importing everything a thousand times easier haha