Jan Lehnardt 
This is why I see the BlueSky lifetime as a grace period for fedi to get its act together. It’ll be a lot of work, we better start now. https://mastodon.social/@molily/113480811492965996
toto@janl @molily Yes 100% The fact that Mastodon did get neither quote posts nor search not to speak of anything innovative done since the Twitter acquisition is really something. There is of course also the fact that money is missing. @MastodonEngineering just needs money to hire a few people to get more than the absolute basics done.
@mrtoto they shipped search tho :)
@janl Well, yes. Functionally it's there. But e.g. why am I not asked as part of the onboarding process if I want to opt in for example.I mean is there even an onboarding?
Also there needs to be some kind of broker to search across the fediverse, not only instance local.
The only place I see these things being done is @dansup (who never seems to sleep!) with @loops. That looks like steps in the right direction which gives me a bit of hope :)
Also there needs to be some kind of broker to search across the fediverse, not only instance local.
The only place I see these things being done is @dansup (who never seems to sleep!) with @loops. That looks like steps in the right direction which gives me a bit of hope :)
Renaud Chaput@mrtoto @janl @dansup @loops Well, this is completely not true. We (the Mastodon project) are publicly working on https://www.fediscovery.org thanks to a grant from the NGI program, with the goal to solve the (very hard) discovery/search problem in the Fediverse, in a privacy-compliant way.
Quote Posts are also in progress, well specified so the other Fediverse software can implement them and with a lot of controls to respect users choice and privacy. We publish monthly blog posts with our progress
Quote Posts are also in progress, well specified so the other Fediverse software can implement them and with a lot of controls to respect users choice and privacy. We publish monthly blog posts with our progress
@renchap @janl @loops I know you are and looking very much forward to the results (see https://social.mrtoto.net/@mrtoto/113481096839149350 ) 😊 And the problems are indeed hard, no question about it. Also that the resources are limited (probably the main problem compared to places like bluesky).
My point was more frustration about the speed of progress. The fact that Mastodon does not seem to be more attractive to the new wave of refugees (neither from 🇧🇷 nor now the 🇺🇸) is concerning.
toto (@[email protected])
@[email protected] True. There is also more progress I know Wordpress (if that's still a thing), Flipboard, Ghost are all embracing AP. Threads is also moving forward as is https://www.fediscovery.org so things are moving, albeit slowly.
@mrtoto Yes it is, and comes from multiple factors. One being the resources, Bluesky has at least 10x our resources, they have been able to recruit a top notch team, do marketing, comms and overall execute very well. I am personally doing my best to get things moving with whatever means I have, and I like to think that this shows real results (for example the projects mentioned above, as well as tripling the engineering team over the last year)
matthewAre there fundamental flaws to AP that make it hard to really give the UX that people expect though? Im particular I think of the problem where you don't see all replies from your own app, and need to navigate to the origin thread to see them. That's a hugely confusing and bad experience for users. And from my understanding of how AP works, is that even fixable?
@matthew Those are very complex issues related to how distributed collaborative systems work. There are solutions, but they:
- need to be carefuly considered on the performance standpoint, multiple things we looked at had the potential of multiplying the instance-to-instance trafic by a lot
- same for anything related to privacy and trust & safety
- require a lot of careful and expert work to be done correctly
A contributor is currently attempting to solve this here: https://github.com/mastodon/mastodon/pull/32615
Isn't this an AP problem, not a Mastodon problem? I'm replying to you now from a non-Mastodon AP instance, and I suffer from this problem greatly (because I run a solo instance and there's not as much chatter).
What's the AP-level solution to this problem? I have a hard time thinking there can be one, for the reasons you just mentioned.
What's the AP-level solution to this problem? I have a hard time thinking there can be one, for the reasons you just mentioned.
@matthew The above PR attempts to refresh the replies from the upstream instance when the status context is requested from the API, if it is less fresh than X seconds, asynchronously. Then the frontend can check if the refresh has finished, and get the updated list of replies
I'm not following. How does a PR to Mastodon fix a protocol-level bug? Shouldn't there be a change to the protocol to address this problem?
@matthew We think the protocol does not need a change, but most implementations do need a change. And it might not work in the real world due to performance issues. I can not say what other AP implementations plan to do about it, but so far nothing in AP has proved blocking on our side from what I understand (I have not looked at this topic very deeply yet)
Mark Malstrom@matthew I believe the ActivityPub client-to-server protocol may be able to solve this specific problem, at least. Allowing the clients to talk directly to the other servers to receive the full reply history rather than only talking to your own server