Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
As you can follow anyone on almost any Fediverse service, is there a need for this? It would render the instance’s “All” pretty much unusable.
I could see it working if you had a one-person instance or an instance devoted to a single celebrity. There you’d basically have one such community channeling all their social media in.
What I could see a potential for is FediFeed where you could turn any collection of communities or individuals into a single feed, possibly even RSS. Although I presume most Fediverse services have or could be made to generate an RSS feed anyway.
Ah yes! I almost do that already. With RSS as well. So you can combine communities and RSS Feeds, not mastodon users yet though. It’s kind of fun standardizing all the different ActivityPub implementations into a single data model. Mastodon timelines or users are essentially whole communities.
To be honest, building a web-version of that pipeline as a NPM package might be helpful for others, piping in all the different types of fediverse content into a single stream.
As you can follow anyone on almost any Fediverse service, is there a need for this? It would render the instance’s “All” pretty much unusable.
I could see it working if you had a one-person instance or an instance devoted to a single celebrity. There you’d basically have one such community channeling all their social media in.
What I could see a potential for is FediFeed where you could turn any collection of communities or individuals into a single feed, possibly even RSS. Although I presume most Fediverse services have or could be made to generate an RSS feed anyway.
Ah yes! I almost do that already. With RSS as well. So you can combine communities and RSS Feeds, not mastodon users yet though. It’s kind of fun standardizing all the different ActivityPub implementations into a single data model. Mastodon timelines or users are essentially whole communities.
To be honest, building a web-version of that pipeline as a NPM package might be helpful for others, piping in all the different types of fediverse content into a single stream.