> There is another possible problem that had not even occurred to me. The candidate failed the trivial question because they tried to write the answer in Java.
As an instance admin there is no good reason not to be transparent about your blocklist. Any security through obscurity you gain is a spectre, as it's trivial to throw up a new instance on Heroku or something to get around it when a malicious party determines they're blocked. Your users deserve to know who they can and can't talk to from your box.
just another reminder: I've moved over to https://mastodon.xyz/@er1n for the forseeable future.
if anyone hasn't senn @sarahjeong's article on Motherboard abt mastodon yet, go check it out. it's pretty great at explaining what mastodon and federation are to laypeople.
hypothesis: if too many early users sign up on mastodon.social instead of other instances, federation will end up becoming a second-class feature. (imagine what email today would look like if gmail had existed in the 90s.)
other instances need to be able to compete with mastodon.social for growth, or https://github.com/tootsuite/mastodon/issues/177 should be implemented.
lmao this post just showed up on my home tl
@Gargron i'm curious what the explanation for the *massive* timeline lag/fucky ordering is, seems like a very interesting issue
Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!