For example, CLD3 returns the code "iw" for Hebrew, even though that code has been deprecated and it's "he" now. So it fixes that kinda thing.

Upon @shel's notification I have added the "mute conversation" button to all own toots, not just ones in notifications column, so you can stop notifications for a toot before you start getting them.

Upon @halcy's notification I made it so if the `visibility` param in the POST /api/v1/statuses request is missing, the user preference for default privacy is used instead of public.

The embed codes now contain a <script> along with the <iframe>, which ensures that the iframe's height corresponds with the iframe content's height. If the script doesn't load, you just get scrollbars on the iframe.

Hopefully I can do the final release tomorrow. Gotta prepare the fanfares - remember, it's a big deal.

None of this would be possible without the support of my Patrons. Thank you.

Patreon: https://www.patreon.com/mastodon
Liberapay: https://liberapay.com/Mastodon/

List of sponsors: https://github.com/tootsuite/documentation/blob/master/Contributing-to-Mastodon/Sponsors.md

@gargron @shel @halcy mmm there was a reason we did this... I think it was because "mute notification" only affects notifications, it doesn't mute things from e.g. the timeline

@nightpool @shel I don't think there's such confusion from the way I did it.

@gargron @shel okay! just trying to make sure we remember *why* we made certain design decisions so we don't revert them w/o taking that into account

@Gargron neat, I guess now that following/followers are public, it could be periodically synchronized, it could help with @squirrel's issue. Also, maybe if a change in account key is detected, either automatically unfollow, or send a follow request?