I've had an idea, that I could easily pivot to this and become a FOSS solution. But, I wonder if it actually solves a problem. Essentially, I wanted my lemmy instance to allow sign-ups. But, the posts and channels were auto-generated. So when you log into the app or sign-up it creates a community in the instance along with it. (loom.nyc/c/pexavc) and then all the posts are automatically generated from the posts you save anywhere in the fediverse. (The app supports lemmy and mastodon for now). But, this would also allow all your bookmarks to essentially "federate".

Edit: Tbh, it sounds like a more "silent" cross-posting

[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] pexavc 1 points 1 year ago

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.