Fandom and Federation (Collection) [pixietails.club]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Fandom and Federation (Collection) ======
Notes from discussions about moving fandom spaces into the fediverse (or not).

===== Distributed and Federated Fandom (notes to self) by cesperanza (2018) =====
> I'm now thinking about .dat or p2p for hosting and serving art and video fanworks (for me, that network would have to be about fanworks, I'm not seeding non fanworks or risking hosting non fanworks; I'm willing to stand behind a broad array of fanworks as the AO3 does but NOT, say, pirated movies or porn that has nothing to do with fandom) and federated social networking (hubzilla, mastedon, any social media site that gives you a nomadic identity and is interoperable with other systems) for engagement. In my dream of dreams this would be backed up by something like an OTW-run deposit library that stored but didn't serve fanworks. 

==== My Comment ====
>Most of this is beyond my current understanding BUT I do wonder if having all three systems (archiving/hosting/social networking) in one thing would be a good idea (or possible)-- surely that would take a lot of computing power? Internet power? Plus then building the whole system itself seems like an enormous task. I do look forward to seeing what people come up with, though!

>I guess technically we could cobble some of this together right now while we wait for The Big One. Like, a seedbox or two (or more) for hosting fanvids and art, maybe, plus Mastodon plus (archive). Or using IRC again, THAT would be a throwback. Of course, we don't own those servers, etc.

<wrap hi>Source: [[https://cesperanza.dreamwidth.org/577622.html|cesperanza's Dreamwidth Journal]] / Noted: 2018 December (Pinboard)</wrap>

===== Federation and Fandom by impertinence (2018) =====
>Fandom is, once again, in flux. Anyone who's been around for more than a few years knows the signs have been building: deleted accounts and new terms of service, followed by talk of moving elsewhere, fracturing communities over multiple platforms, sometimes breaking communities entirely. It's a common pattern a lot of us have come to see as an inevitability, just something that happens every five or ten years. But of course there is a cost, archival as well as communal. That chatfic you loved gets deleted. The old homepage of your favorite vidder goes down. Entire fandoms' discussions disappear forever.

>We've all been there at least once, Or we're about to be there, because again: it's happening with Tumblr. People won't all leave at once. The demise of LJ was measured in years, not days. But eventually, even if it's still up, it won't be what it was. Content will slowly degrade - image hosting, external links, even the posts themselves deleted due to inactivity or changes in management. Link rot, in other words.

>So. It's happening. What can be done about it?

>There have been a lot of really good discussions so far. Consensus so far appears to be some combination of the following: the new platform must allow photo/text/video sharing as well as conversations; the new platform must allow NSFW content and have robust filtering; the new platform must be resistant to the kind of profit-driven vicissitudinous behavior most tech companies embrace.

>I agree with all of this. I also agree with the problem statement, which I've seen repeated again and again, that fandom should be more distributed - that no single (especially not corporate-owned) social network should be the point of failure.

>So. Let's talk about server federation.

<wrap hi>Source: [[https://impertinence.dreamwidth.org/699092.html|impertinence's Dreamwidth Journal]] / Noted: 2018 December (Pinboard)</wrap>