@maikel I also wish Mastodon followed the specs closer.

At the risk of sounding like an apologist, real-world constraints and deadlines were probably a factor. Shipping stuff is *hard* and there are always difficult tradeoffs to be made.

C2S API is a good example. They NEEDED a mobile client, but the standard wasn’t enough.

However we got here, it’s on the standards community to build a spec that will work in the real world, then make incentives for the market leader to follow.

@DePemig

Hey Gilles! It looks like several other *far more knowledgeable* people have already chimed in, but yeah.. this would probably be best as a filter on your client or your own home server.

I *think* Mastodon already does something kinda like this.. allowing you to filter out boosts from accounts you follow. It's a nice add that we could probably expand on.

I'm a software developer working on a bunch of #Fediverse things: #Emissary, #Bandwagon, and bandwagon.fm - with several more in the pipeline.

It's a pretty strange mix that doesn't really fit today's Fediverse, but it makes sense when you see the end goal.

I got an opportunity at #Fedicon to explain myself, so here it is:

https://spectra.video/w/eod3ybLu7sHzAEMihej8km

It's not the greatest talk about Fediverse tech, but it's the best I've got so far, and I hope it inspires you to make great things here with me.