I was informed that EncyclopediaDramatica had some big cash flow problems, and they need your monetary support. Yeah, they can be pretty wanktastic, mean and probably deserve some of the reputation they have… but as a wiki community, they can be pretty awesome and supportive of other wikis out there. If you’re a member of the wider wiki community, please consider helping out.
Archive for the ‘wikis’ category
A few days ago, I published a blog entry titled The problems FanLore faces are not unique: Learning from Fan History’s experience. In the course of editing it, we removed some bits that weren’t relevant to what we were responding to. One bit I thought was still pretty interesting so, lo! The bit reappears here!
Fan History’s admins all been in fandom a long time, and sometimes this whole issue of doing crosstalk in an collaborative way that anyone can contribute can be intimidating. In fandom, this just is not done. With a piece of fan fiction, the process is solitary in creation and when the story is finished, there is no real questioning the process, questioning the organization, suggesting ways to improve the story. It just isn’t something that is fundamental to our cultural practices. People don’t ask “Why did you have Harry Potter doing that particular spell in that scene? Could you use this spell instead?” If they do that, it tends to be viewed as antagonstic, or questioning the author’s writing ability. And on the off chance the author and their supporters do agree that something could have been done differently, most of the time the author doesn’t go back and change it. And if they do? The audience doesn’t generally go back and read it. Our cultural practices from the fan community just don’t lend themselves to crosstalk as equals.
We at Fan History love wikis. And we love seeing wikis do well. So when wikInvest sent us an e-mail asking people to vote for them to win a Webby, I thought I would pass it along so you can support other great wiki projects.
We recently created a collection of articles about fandom related wikis on Wikia. The list isn’t complete as Wikia has over 24,000 wikis listed on their own internal list. Six to eight hours of data crunching left us exhausted and so we have about 8,000 or so wikis we haven’t looked at, couldn’t figure out how to handle the problem of ten wikis from the same fandom and language having the same name. That said, we can still give you an idea of some of the most popular fandoms to create wikis about. They are:
- Star Wars – 161+ wikis
- Pokemon – 135+ wikis
- Music wikis (not fandom specific) – 102+ wikis
- Movie wikis (not fandom specific) – 100+ wikis
- Runsescape – 91+ wikis
- Naruto – 88+ wikis
- Warcraft – 84+ wikis
- Nintendo (non fandom specific) – 75+ wikis
- Anime (non fandom specific) – 70+ wikis
- Halo – 66+ wikis
- Club Penguin – 62+ wikis
- Yu-Gi-Oh – 59+ wikis
- Dragon Ball – 48+ wikis
- Fan fiction (non fandom specific) – 46+ wikis
- LEGO (non fandom specific) – 45+ wikis
- Comics (non fandom specific) – 44+ wikis
Yes, Jason is trying to get people to leave wikia. (He has never approached us!) Given the licenses of most wikis on Wikia, he doesn’t really need to approach anyone: He can just copy the whole thing on to Mahalo, find some one willing to curate and be done with it. If he is only offering half the money to one person, large wikis aren’t going to move. If he doesn’t have the domain, there isn’t going to be a lot of money unless he can squeeze Wikia and beat them on SEO for the same content.
It will be interesting to see how this plays out.
Edited to add: Linked to Jason’s twitter account and the leavewikia account on #wikia on irc.freenode.net to mostly complain about Jason’s lack of understanding of wiki communities and fan communities. The result: [14:42] -ChanServ- You have been devoiced on #wikia by Dantman (Nadir_Seen_Fire) .
During the past few days, we’ve been working on trying to visualize our organizational patterns on Fan History in order to understand our own patterns, how we conceptualize fandom, to check for organizational consistency, create tools to help users understand our organizational patterns, to identify areas where we lack stub content. This is our second post in this series. This one is about Harry Potter.
Click on the image to view it full size.
There are things about the top level category that drive me nuts. Namely, the category seems to have way too many categories for specific sites: LiveJournal, GreatestJournal, EZBoard, InvisionFree, JournalFen, Yahoo!Groups. I’m not certain how this can be fixed with out a major category restructure. The major hesitation about doing that is it would disturb our existing patterns, would make the tree a lot deeper and harder to navigate.
Once I start looking at the structure regarding communities in depth, it appears that we have started to move that content into its own separate structure. It just was never fully implemented. Or quite possibly, it was implemented and then people went in and changed it not realizing that we had attempted a restructure. This is a wiki and anything is possible.
Our character and pairing structure was taken apart at one point, with articles removed from them. There is the whole question of if we should restore that and put the articles back into the subcategories and restore that. Some like Draco/Hermione have a lot of content that could go in them including stories around the ship, etc. Having that structure existing just makes it easier to navigate and conceptualize in my opinion. If you specifically find that Snape/Harry LiveJournal community, than it helps to have that sorted if we don’t have an article list of Snape/Harry LiveJournal communities.
The Harry Potter fandom also seems to be structured around pairings, characters and houses. The community doesn’t necessarily have the emphasis on a coherent community identity. Thus, it seems logical to me to structure the fandom more around these articles and rebuild them that way as a history of the fandom would be much more accurate if told from that perspective.
There is also the issue of how to organize fan fiction. We have fan fiction archives, fan fiction, stories, slash, saffic… and all of these deal with fan fiction. Should those sub categories be moved into Category:Harry Potter fan fiction? And looking at that category now, it really looks like everything in it should be moved to Category:Harry Potter stories. Oye. If we combined communities and organized that way, it feels like it would be logical to combine this one too. Things just seem really scattered like this; would it make it easier for article contributors to link various parts of the history they tell if the category structure made those connections more obvious?
If you have any feedback on this tree, any questions about how it developed, we would love your feedback. Do the organic patterns we’ve developed make sense? Is this construction too artificial? Is it not logical? Does it make sense in relation to the fandom this structure represents? And if you’re really motivated, we’ve really like that feedback on the relevant talk pages for those categories.
When looking at large scale preservation projects, a lesson I have learned from the Geocities situation, is that one person cannot do it all. Two people cannot do it all. Three people cannot do it all. Four people cannot do it all, even if they are dedicated, well meaning, have certain skills and are willing to put the time into saving and preserving the history of an online community. I’m ecstatic about what we accomplished but I’m also disappointed. I feel like we could have done more, if there was more than a core team of a few of us at Fan History.
In doing a preservation project, one person trying to save things means that things will be missed. The process can be greatly aided by institutional help in determining the size and scope of what needs to be saved, and in developing a list of resources that need to be saved. The following of institutional structures that would have been useful for us to have had relationships with:
- Yahoo/Geocities. ArchiveTeam tried to reach out to them and were rebuffed.
- Open Directory Project. We didn’t really need them because they helpfully provide a list of all the sites listed on DMOZ. We were able to utilize this. For that, we are happy.
- WebRing. Lots of Geocities sites hosted there. Couldn’t scrape them easily to try to easily pull a url list. Didn’t respond to our contact requests. Couldn’t find anyone associated with them on Twitter to help us get that. We probably should have called and called and nagged. :/
- ArchiveTeam. We used one of the lists they provided to get urls to scrape but most of what they provided publicly wasn’t that useful for our needs. I did a comment on their blog. We should have reached out more to them. They had the technical knowledge to do things, had the computers, had the dedication to do this. We have the structure to provide a historical framework for some of what they were doing.
- The Internet Archive. They archive old copies of pages across the Internet.
- Organization for Transformative Works. They are dedicated to preserving fandom history. Repeatedly reached out to them on Twitter, on LiveJournal, via e-mail and elsewhere. Never responded. EXTREMELY FRUSTRATING. They have manpower and a shared purpose that would have been helpful.
We should have gotten institutional support. They could have provided us with three things: 1] A (structured) list of fandom related urls, 2] Technical assistance, 3] Community support and manpower. Some of that we got because these institutions provide some of this as part of their own efforts and mission.
After institutional support, we needed technical assistance. We were lucky in that we got some assistance from Lewis Collard and illyism. We just didn’t think to ask some people until too late, about two weeks before Geocities closed. Asking two individuals for all our technical assistance and implementation of technical solutions isn’t fair, won’t result in a timely solution. It doesn’t allow enough time for integration with institutional support. Lewis scraped about 5,000 pages and screencapped them. He downloaded about 2,000 files. In doing all this, he blew through his monthly bandwidth allotment. Illyism developed a Firefox plugin. There are several resources we could have, probably should have tapped in our own community, the wiki community and the fandom community. They include:
- #mediawiki, #wiki, #yourwiki, #recentchangescamp, #wikia, #pywikipediabot, #wikihow on irc.freenode.net. These chat rooms have awesome people in them. They do a lot of open source projects.
- Organization for Transformative Works. They are training female programmers for their projects.
- ArchiveTeam and Internet Archive. They already have technical people.
- Idealist.Org. Listing requests for volunteers might have gotten some assistance.
- Wikimedia related mailing lists.
- Tech and programming people we met at RecentChangesCamp.
- Relevant LinkedIn communities.
- weget developer community.
- identi.ca. They have a lot of developers on the site who use it instead of Twitter. It is smaller and more intimate. It has a lot of open source advocates who like doing things for the greater good.
There are probably a few more places where we could have asked for help. We could have used help creating a list or urls, screencapping sites, creating tools to automatically input the attained data into a usable format, and tools to make it easier for non-tech people to contribute.
The last component in the we cannot do it by ourselves and succeed is community support. In our case, that community involves fandom. We needed the community to help edit relevant articles to do deeper documentation on stub articles created by our core team and created with assistance from our tech team. Sometimes in fandom, it is easy to get locked into a box of thinking of your corner as representative of everyone. The more people we had, the smaller that box would have been. We should have been more aggressive with our outreach to that community and to internet news and mainstream news sites that would have covered our project and helped us get greater exposure with our core audience. Places we should have been more aggressive include:
- wikiFur, Transformers Wiki, Futurama Wiki, Battlestar Galactica Wiki, Wikia, other fandom related wikis. The content we created on Fan History that preserved the history of those fandoms could have been shared with them so everyone could have won. If we had reached out.
- Twitter. We should have been tweeting damned near every fan person who mentioned Geocities on Twitter to beg for assistance.
- Facebook, MySpace, Yahoo!Groups, Ning. We didn’t reach out there at all. Large fan communities exist on them and are ones that probably used Geocities.
- Fanac Fan History Project and other science fiction historical projects. They stood/stand to lose a lot of their own history too. This includes convention reports, early histories of scifi fandom on Geocities, pictures, etc.
- Fansites. Lots of domain level fansites will plug meaningful projects. They could have helped us get the word out, helped us to recruit people with this project.
We mostly tried to mobile through LiveJournal, through blogging outreach, on IRC, through contacts on the wiki community (Thank you ProjectOregon and AboutUs!) and our own personal network of acquaintances. This wasn’t as successful as a method as it could have been.
Repeating: One person (or a small team) cannot do it all. For this type of project to be successful, you need three things: Institutional support, technical support and community support. If we hear that other sites are at risk in the future, we now know what needs to be done and better understand the consequences of failing. We’ve learned an important lesson.
In the meantime, we’ve still got a lot of data that needs to be processed into the wiki into a usable format. We could use some technical and community assistance in accomplishing that. How do we get 3 gigs of screencaps uploaded? What is the best way to upload 1,000 text files to a wiki? Is there a way to scan those text files to make sure that they are what we think they are? As a community member, can you help us improve articles we did create? Can you help by improving descriptions on the screencaps we do have uploaded? We still need help.
Now, I’m going [maybe] to take a bit of a wiki break, data mining break, data processing break because I’ve pretty much been doing that straight through for the past week.