Jokingly:
webweb, 'cause it’s a web of websites.
cross-fora, 'cause they’re like cross-posts but entire forums.
newsvents, 'cause a lot of the activity is venting in news post comments. 😉
memecycling centers, 'cause it’s a lot of reposts of old memes/shitposts.
Realistically:
Whatever instance/site I’m directing someone to.
stick-in-the-mud-tangent
I’d never tell someone to go to WordPress if I was telling them to go to a site built with Wordpress, that’d be silly and out of touch. It’d also be out of touch to use some jargon that means nothing to them like “threadiverse”.
All the pointing to these backends as though they’re platforms like the corporate platforms shows how much they’ve conditioned people into thinking in their terms. The major benefit to these backends is they’re more open, enabling greater mobility between the instances of them/sites built with them.
All the pointing to these backends as though they’re platforms like the corporate platforms shows how much they’ve conditioned people into thinking in their terms.
I see where you come from, but it’s still a platform, a network. It’s way more connected that WordPress.
Piefed, Mbin and Lemmy have back and frontends, it’s not like you’re connecting directly to the instance using API calls
I see where you come from, but it’s still a platform, a network.
But that network is not Lemmy or kbin or mbin or piefed. That network is activitypub, the platform is activitypub. Those backends are just what you use to connect to the network, but you could use any other implementation (just that there aren’t that many right now).
Just because an application supports ActivityPub doesn’t mean it will be compatible.
Well of course, but it could be made to be compatible!I feel like we’re kind of missing out here on the threadiverse cause we can’t see all those other things happening elsewhere.
Relevant: the Tesseract front-end for Lemmy provides an automatic embedded player for Loops videos: see e.g. https://tesseract.dubvee.org/c/loops@midwest.social. So those kinds of cross-integrations definitely are happening, but they take time and effort to implement and refine.
What to call this stuff…
Jokingly:
webweb, 'cause it’s a web of websites.
cross-fora, 'cause they’re like cross-posts but entire forums.
newsvents, 'cause a lot of the activity is venting in news post comments. 😉
memecycling centers, 'cause it’s a lot of reposts of old memes/shitposts.
Realistically:
Whatever instance/site I’m directing someone to.
stick-in-the-mud-tangent
I’d never tell someone to go to WordPress if I was telling them to go to a site built with Wordpress, that’d be silly and out of touch. It’d also be out of touch to use some jargon that means nothing to them like “threadiverse”.
All the pointing to these backends as though they’re platforms like the corporate platforms shows how much they’ve conditioned people into thinking in their terms. The major benefit to these backends is they’re more open, enabling greater mobility between the instances of them/sites built with them.
I see where you come from, but it’s still a platform, a network. It’s way more connected that WordPress.
Piefed, Mbin and Lemmy have back and frontends, it’s not like you’re connecting directly to the instance using API calls
But that network is not Lemmy or kbin or mbin or piefed. That network is activitypub, the platform is activitypub. Those backends are just what you use to connect to the network, but you could use any other implementation (just that there aren’t that many right now).
Just because an application supports ActivityPub doesn’t mean it will be compatible.
Lemmy and Peertube are barely compatible. Interoperability between fundamentally different software could be achieved, but is not a priority
Well of course, but it could be made to be compatible!I feel like we’re kind of missing out here on the threadiverse cause we can’t see all those other things happening elsewhere.
Relevant: the Tesseract front-end for Lemmy provides an automatic embedded player for Loops videos: see e.g. https://tesseract.dubvee.org/c/loops@midwest.social. So those kinds of cross-integrations definitely are happening, but they take time and effort to implement and refine.