Getting closer to 1.0 (Patreon)

Technical stuff

Media attachments now generate URLs in the body of the status, allowing you to post statuses without any commentary. Removing an attachment from the compose form correctly removes the URL from the body again.

Clicking on usernames in statuses will open the profile in the UI as opposed to sending you to the user's website. Replying to a status will now correctly pre-fill all involved user's usernames, excluding yourself.

Infinite scroll on all columns.

Improved UI on smaller windows. It's still not responsive but areas that are larger than the screen will now allow themselves to be scrolled.

Settings page styled and linked from the UI.

Rendering performance improved, making the site's pages load a bit faster. Similarly, the static pages like public profiles and statuses that are meant for outside viewers no longer load the JavaScript required for the logged-in UI.

Detailed view for statuses is now finished (example in screenshot).

30 characters limit for usernames and 500 characters limit for statuses added.

New logo by Fairpixels!

Added a landing page that briefly explains what Mastodon is.

Reblogs of the same status by multiple people on your home timeline will now be condensed into whoever reblogged it last. The same status cannot be reblogged by the same person more than once.

Default avatar added.

Statuses can now be deleted from the UI. Reblogs and favourites can also be undone.

Added API versioning (v1), added client registration API so that 3rd party apps can authenticate against any given Mastodon instance without prior knowledge.

More various fixes and improvements.

Patreon stuff

There is now a Discord server that you will get access to if you pledge to this Patreon. I will be on that server and you can talk to me about Mastodon and what you'd like to see implemented, etc.

Roadmap

I'm talking to some people who have been dealing with content moderation and user abuse for more than a year and I am hoping to construct a good plan of what features Mastodon needs to have to be better than Twitter in that regard. I'm hoping to implement blocking and related functionality as soon as possible, and then move on to creating an admin UI from which content, user reports, etc can be overviewed.

At this stage, even though there is currently no blocking, I think the project is far ahead enough that I would like to see some real use. Feel free to spread the word about it and try it out.