Hard coding other website engine names into the structure of your own website engine seems… not great.
Lemmy doesn’t show posts from Mastodon for the exact same reason it doesn’t show posts from Loops. Or PixelFed. Or Miskey. Or Bookwyrm. Or other Lemmy users.
A “Mastodon” feed would encompass all of those things. And it would promote the idea that all that exists outside of Lemmy are the most popular wish.com versions of existing mainstream services. It neither leaves room for acknowledging less popular options, nor anything that’s genuinely new.
Plus, there are already website engines that let you follow both groups and users. If that’s something you want, mbin is right there. Why not use that?
You know how there’s All, Home and Local? I’m basically suggesting adding “other federated services” to that list so that you can specifically go and look at things outside of the service you use that have found their way to your instance.
Would it actually be a useful way of perusing that content? Not particularly, but it would probably get a lot more people to see and get interested in the other federated services and actually see how federation works
Would this be better as a front-end project instead? Definitely, but I wrote that comment literally as the words were flowing out of my brain while on a work break and didn’t realize that at the time.
Hard coding other website engine names into the structure of your own website engine seems… not great.
Lemmy doesn’t show posts from Mastodon for the exact same reason it doesn’t show posts from Loops. Or PixelFed. Or Miskey. Or Bookwyrm. Or other Lemmy users.
A “Mastodon” feed would encompass all of those things. And it would promote the idea that all that exists outside of Lemmy are the most popular wish.com versions of existing mainstream services. It neither leaves room for acknowledging less popular options, nor anything that’s genuinely new.
Plus, there are already website engines that let you follow both groups and users. If that’s something you want, mbin is right there. Why not use that?
You know how there’s All, Home and Local? I’m basically suggesting adding “other federated services” to that list so that you can specifically go and look at things outside of the service you use that have found their way to your instance.
Would it actually be a useful way of perusing that content? Not particularly, but it would probably get a lot more people to see and get interested in the other federated services and actually see how federation works
Would this be better as a front-end project instead? Definitely, but I wrote that comment literally as the words were flowing out of my brain while on a work break and didn’t realize that at the time.