@pglpm IMO it would be a way of interfacing with the site but not the site on its own.
Stackexchange sort of provides an archive of answers while Fediverse is about transient exchanges.
I could see Fediverse feeds to help people contribute to the site, but the site itself needs to be more than a scrolling feed to provide answers to future searchers, if that makes sense.
@volkris@volkris I get your point, but maybe you're thinking more specifically about mastodon than the fediverse? Though I'm still quite new to the fediverse, I didn't know all fediverse apps are feed-based.
@pglpm no, I’m talking about Fediverse, or more specifically, I’m thinking about the ActivityPub protocol that runs it.
AP is all about delivering streams of content left and right from content producers to the applications and websites that want it. But the streams themselves are a little ephemeral so it’s up to the end use to decide what to do with them.
So Fediverse might deliver an answer to a question, and while a platform like Mastodon might just throw it up on the screen for an hour, it takes a more specialized website to actually display the answer that was provided and keep it around for future users to find.
in other words federated isn't the best way to reproduce stackexchange where you need a silo, unlike mastodon for example, where less than 3% of mastodon users want to be part of archived search. i doubt the figures for lemmy or kbin would be any different.
i use #emacs & #denote to store info from the fediverse.
the costs of one peertube instance the size of youtube would be insane, so you would need a very large indexer of all the peertubes & other fediverse apps sharing video for example
the fediverse is designed really to be many small islands where you have to rely on the federation effect to propagate links to content, but this really isn't designed as an archive
Add comment