Notices by Renaud Chaput (renchap@oisaur.com), page 4

@iju @Mastodon I do not think we plan to move operations to the US, even if we do not get the non profit status back in Germany. As explained il the blog post. We never used the status to get tax-free donations, so there it is not really mandatory for us.

@GossiTheDog I am not sure this works for Twitter nowadays, as they cut off they API / firehose

@GossiTheDog We do not have sourcemaps, and I do not think that they crawl the various RSS feeds we publish (there are a lot of them!). A Google team reached out to us to see how we could improve our indexing so more “real-time" posts are surfaced on search, so there may be some improvements in the coming months if we figure out how to do it properly.

@silverpill @julian @pfefferle@mastodon.social @pfefferle@community.nodebb.org @nutomic I am not very knowledgable about ActivityPub so I cant discuss the specifics, but we would like to improve how non-Note objects are processed/displayed in Mastodon.
If there are discussions about this, or a WG working on the topic, please send me the links so I can reference them for us to read when we start working on this :)

One of the ideas would be to support an embedded "view more" modal, that somehow displays the remote content.

Nobody seems to have noticed it apart of @thisismissem, but the Mastodon project have been granted funding by @NGIZero in the Entrust fund.

This is amazing, but the best part is that this funding is targeted at implementing… Quote Posts 🎉

This effort started several months ago and we already did some preliminary work, but this will be a big feature for our next 4.4 version. This funding will cover the ActivityPub work, as well as backend, web frontend and official mobile app implementation.

@GossiTheDog but we shoud maybe panic at the number of other projects that may have been infiltrated by this actor under other names and have never beeen noticed?

@Sarahp Meta has this number, but it is not exposed publicly yet. We asked for them to publish it like other Fediverse servers in their nodeinfo API, but from what I understand publishing any user count is requiring a lot of work to get approved.

In the meantime, and this is a partial view, but at the moment, mastodon.social knows of 2800 accounts from threads.net. At the most active Fediverse server, it can give a good estimate.

Mastodon now supports automatic switching between the light and dark theme, depending on your system setting.

It will be available in the upcoming 4.3 version, or is already there if your instance runs the nightly code.

You can switch to this new automatic theme in your Appearance preferences. Instance admins can also set it as the default theme (I just did it on mastodon.social and mastodon.online).

This has been done in https://github.com/mastodon/mastodon/pull/29748, thanks a lot to @nshki for the initial PR!

@GossiTheDog We use a maximum number of pixels, defined here: https://github.com/mastodon/mastodon/blob/77897cd24cbf9802bd000c88ab3c7bfb6714f968/app/models/media_attachment.rb#L73

This might change one day, when we have time to rework the whole media pipeline…

@lisamelton The back button change has been reverted for the advance UI: https://github.com/mastodon/mastodon/pull/29669

We will add back the notification filters, trying to do it this week.

Those changes have not yet been deployed on mastodon.social, no ETA for this yet.

@Gargron

@qurlyjoe Those changes are not done in isolation or by a single "coder”, and we think quite a lot about them and how they can impact users. Sometime we might miss something, but we also deploy those changes early on our own instances to be able to gather feedback from a larger audience and adjust accordingly.

@lisamelton @Gargron

@lisamelton @qurlyjoe @Gargron We are a very small team and do not have the time to properly triage, reply or process all issues, but we read them.
No timeline, for the reasons above, and also it is evening here in europe.

@lisamelton I do not know what else I can say. This might be fixed tomorrow, or in a few days, and then deployed to mastodon.social. This is not an attempts at breaking the way the you Mastodon, and as I said, we are taking feedback into account. It will be fixed, and I may have more details tomorrow when the team had time to discuss this.
@qurlyjoe @Gargron

@lisamelton From what I read, a PR is in the works (but it requires some design).

Also we accept and read feedback, especially when it is not aggressive and provides examples of what it breaks. GitHub issues are the best place for this, as we read them all (which is harder to do with posts).

@qurlyjoe @Gargron

An alternative is to use polyfill-fastly.net, generously provided by Fastly (@devs) to help migrate to another more maintained solution.

It has been set up by the original project author (now working at Fastly), runs the code that was running previously on the main domain, and have an amazing track record at supporting OSS projects.

Their announcement with more details here: https://community.fastly.com/t/new-options-for-polyfill-io-users/2540

If you are using the polyfill.io service for your website, you may want to reconsider. This was an amazing product, but the last maintainer sold the project and the domain to a China-based company without warning, and the domain is now pointing to a chinese IP running unknown code.

Birdside announcement by the project original author: https://twitter.com/triblondon/status/1761852117579427975

More context in a GitHub issue: https://github.com/polyfillpolyfill/polyfill-service/issues/2834

@cliffwade We have a lot of ideas, need some people/time to work on them now…
I wrote this last summer, this still stands at the best way of solving these issues to me: https://renchap.com/blog/post/evolving_mastodon_trust_and_safety/

@cliffwade The most immediate change we are making is disabling registrations on newly installed instances, and displaying a banner to state that open registrations require a reactive moderation team.
Captcha support has been introduced in 4.2 (in reaction to another abuse wave), but we need to improve it. It was initially intended to be automatically enabled when an abnormal rate of signups was detected, but we did not had time to finish this (see https://github.com/mastodon/mastodon/pull/25032)

@filippo We are in touch with the Masto.host admins and they should be able to soon deploy something that will mitigate those.
@mastohost @ivory

@filippo This will be changed in the next version.