This is something I’ve been feeling “all along”, but clearly the mental image of a typical Twitter use cases varies too much between stakeholders e.g. Mastodon backend devs, frontend Twitter app devs, casual users and heavy users. And Twitter employees, too.
To an addict like I am, Twitter timeline is something measured in tweets per second. It is a constant flow, a time synchronized operation, not something that I expect to be event based.
Mastodon devs and ActivityPub spec devs must have a complete opposite of that, that users only post content when there is something to say, and the post will be pushed when a post was made.
The latter model is certainly doable with the ActivityPub protocol, $20/month budget, and by stretch can be handled by Mastodon as it is built. But I think there is this misunderstanding, and it just seems that none of it is built to cater for those with the former model.
Comments
This is something I’ve been feeling “all along”, but clearly the mental image of a typical Twitter use cases varies too much between stakeholders e.g. Mastodon backend devs, frontend Twitter app devs, casual users and heavy users. And Twitter employees, too.
To an addict like I am, Twitter timeline is something measured in tweets per second. It is a constant flow, a time synchronized operation, not something that I expect to be event based.
Mastodon devs and ActivityPub spec devs must have a complete opposite of that, that users only post content when there is something to say, and the post will be pushed when a post was made.
The latter model is certainly doable with the ActivityPub protocol, $20/month budget, and by stretch can be handled by Mastodon as it is built. But I think there is this misunderstanding, and it just seems that none of it is built to cater for those with the former model.