darkhavens (darkhavens) wrote in bloodclaim,
darkhavens
darkhavens
bloodclaim

Two Bloodclaims: A Clarification

There are now two Bloodclaims. The original, at Livejournal: [info]bloodclaim, and the new one, at Dreamwidth: [info]bloodclaim. (This post has been x-posted to both BCs.)

Why? What does that mean?

A [info]bloodclaim fan offered me a Dreamwidth invite code on the understanding that I would create a 'backup' Bloodclaim community over there. And my first impulse was to create it and regularly 'import' the contents of BC@LJ, so it's all there in case something happens to LJ, or to BC@LJ. (I have a regularly updated copy saved to my harddisk.) But then I noticed that some people were making plans to migrate to DW (and some have already done so!), using the automatic cross-post facility to post to their LJ too, and I wondered how consistent they might be at crossposting to LJ comms when they had goodies to share. And I got worried.

I don't want to miss out on new Spander, and I don't want everyone who watches BC to miss out on new Spander, so I tried to figure out the best way forward, and to me, that meant opening the doors to posting at [info]bloodclaim and finding ways to have content from each available in the other. This idea is still a WiP, but the rss feeds (bloodclaim_dw at LJ; bloodclaim_at_lj_feed and bc_updates_at_lj_feed, both at DW) are a fast and simple solution until I see exactly how things are going to go.

If/when posting at [info]bloodclaim picks up, I will probably be looking for volunteers (at both sites) to collate links into posts similar to those at [info]bc_updates, so a regular post would appear at each journal, linking to the non-crossposted content of the other journal. But, as I said, we have to see how it goes.

So, there are now two Bloodclaims, and they are both run on the same rules. Fics with other pairings are allowed, so long as the predominant pairing is Spander. Crossovers are allowed, so long as Spander is a substantial pairing within the story - not necessarily predominant, but not just hovering in the background either.

I track both communities, so I receive email notification of any new posts, whether or not I'm sitting here obsessively ;) refreshing my flist(s), but I do occasionally miss things, which is why there is contact info on the profile page of my journals, and also on the profile pages of both comms. I also respond to LJ/DW PMs.

Writers, if you cross-post between the two communities, please make a note to that effect in both sets of headers. It will save everyone time and pageloads, and any future link-collaters will love you for it. Thank you. :D

In conclusion:

There are now two Bloodclaims.

Crossposting is allowed, even encouraged, but please make sure that both posts mention the fact.

[info]bloodclaim will not be leaving LJ due to any actions on my part. We're here to stay. Over my dead body, etc etc. *g*

ETA: I've just looked at DW's Import function again and can see no way to easily import a community's contents (as of now), so that original idea was never going to fly anyway. *hands*
Tags: !modpost
Subscribe
  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic
  • 7 comments
https://bloodclaim.livejournal.com/2995356.html
bloodclaim.livejournal.com
crawl=CC-MAIN-2020-45
358050
application/http; msgtype=response
sha1:3K4FEDLAPG766P4UA5WQ7NMNQMLO7ETQ
<urn:uuid:52a030c4-5108-40a3-925a-ae7356a52172>
2020-10-19T15:41:34Z
13.88.179.33
text/html
sha1:4QL5CG2W4QUYK7L6JPA4NWU2N32SMTGK
<urn:uuid:147c6951-718d-4e23-ac18-7858d3b6a992>
https://bloodclaim.livejournal.com/2995356.html
response
<urn:uuid:fccb570f-5140-4731-b872-e70772c7106f>
isPartOf: CC-MAIN-2020-45
publisher: Common Crawl
description: Wide crawl of the web for October 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-242.ec2.internal
software: Apache Nutch 1.17 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/