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

Browser extensions can have access to a lot of data, including the websites you visit, but they can also inject scripts and other code on the webpages, allowing them to improve your experience. But they can also inject malicious code, and when someone comes out of the blue and offers to “acquire” your extension for a few hundred thousand dollars, they do not really care about your users, but their data… Some examples: https://github.com/extesy/hoverzoom/discussions/670. 3/7

Maintaining an Open Source project is hard work, lot of pressure, very often no money, and many many people end up being burned out.

Then, sometimes, a company comes up and offers you a large sum of money for it, enough for you to live a better life and never have to feel this pressure, and you accept. This is nowadays very common for browser extensions, can you guess why? 2/7

So a few months ago we learned that the individual running polyfill.io silently sold the service to an obscure chinese company.

This popular (and well done / very useful) service was created by the Financial Times, who stopped maintaining it and "donated it to the community", meaning that it relied on a few volunteers to continue running it (and on Fastly who provided the hosting for free). 1/7

@gruber @Gargron probably the same as Jetpack: bots reposting from other sources (RSS, websites…). Those tend to post orders or magnitude more than human users, 24/7

@joenepraat @kissane Claire started to look at it and even drafted an FEP. But this will require significant work and probably changing how replies are managed in Mastodon from an user-perspective.
A big issue is knowing who is allowed to decide who can reply in a thread: the author of the post you directly reply to? Mentioned people? The top post author (making them owners of the whole thread).
Lot of complexity here, especially in a distributed network. This will require significant funding

@kissane @b0rk We want this is Mastodon as well but this will be a huge undertaking because of the way we do thing on the ActivityPub level.
At least we intend to do it properly from the start with Quote Posts

Thanks everybody, after fixing a few small issues it seems to work fine with streaming, it is a delight to see them update live!

There is still significant work to be done, both to handle some special cases (slow mode, avoiding screen jumps when scrolling, unread notifications, disconnections…) and visual improvements, but we are making progress.

Current status: testing the upcoming grouped notification feature to check if the new code works as expected.

This is the last missing feature before we release the first Mastodon 4.3 beta. It took a lot of time to get it right, but we think we got it done correctly now!

Feel free to favorite and boost so I can check that it really works :D

If you want to learn more about their commitment to Open Source, you can head to https://www.fastly.com/fast-forward/ and follow them: @devs

Special shout out to @anildash and @haubles who are doing incredible things to help the Fediverse grow and be sustainable. We need more people (and companies) like you if we want to reclaim the internet!

I have been using #Fastly nearly since their inception, and it is one of the few tech companies that never disappointed me. They are very obsessed by performance and customer service (< 5 minute response time on tickets).

They love the Fediverse and OSS, and are providing a lot of projects (including Mastodon) with a lot of resources.

Their biggest issue? There was no free plan. But this is now fixed 🎉

No excuse to not try the service and see by yourself: https://fastly.com/pricing

This WWDC keynote would have been much better if it stopped before the IA stuff. At least the first hours was good and only contained 2 mentions of machine learning.

Some IA features looks potentially useful, if they are local, but I hope I can disable all the crap granularly, like the image generation thing.

#wwdc24

@clacke @box464 @MastodonEngineering The position has been filled, so the job offer is no longer available.

@box464 @MastodonEngineering The link was disabled by mistake, it should now be back online!

@Setok the position is for a strong backend person, as I hope is clear in the description. But being a very small team (and no budget yet for anotjer hire) doing some frontend work will probably be needed. If we get enough donations I would be very happy to open up a frontend dev position

We just published our first Trunk & Tidbits post! This will hopefuly be a monthly update where we showcase what we worked on last month, and what's coming next.

I hope this will bring more visibility to all the efforts and love that put on Mastodon

https://blog.joinmastodon.org/2024/05/trunk-tidbits-april-2024/

#mastoadmin #mastodev #mastodon

If you deploy nightly Mastodon releases or directly from the main branch, you may want to check https://github.com/mastodon/mastodon/pull/30203

We merged a migration yesterday and it is far too expensive to run on large servers, so we are rolling it back. If you already applied it, please check the link above to revert it before upgrading.

It is probably best to skip today's nightly build, if you did not deploy it yet.

#mastoadmin

@mike @pcottle we are working on it!

@joeo10 @iju @Mastodon its not.

@iju @Mastodon we are still EU-centric, the goal for the US structure is to be able to gather more funding in the US, the german structure remains our operating entity

@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.