|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
139 |
|
| 3 |
|
| 2240 |
|
| 800 |
|
| 1571 |
|
| 5 |
|
| 724 |
|
|
| |
|
|
|
|
|
|
|
Fiction Branches
Gender | |
Create your own story website with lots of transformations, especially gender.
|
| |
|
|
From: guest (DL)
, 137 months, post #181 |
Just to confirm its actually the fictionbranches address i said,
not fictionmania. Ill blame that on late time.
|
From: guest (A concerned person)
, 137 months, post #182 |
I have a question. Will we be able to get the old story's from Zach
or will we have to make new ones.
|
From: guest (Brayn)
, 137 months, post #183 |
Read back a page or so, I've said before that Zach has archives of
all the episodes done regularly, some of the last few weeks may be
lost but that's about it. But it really depends when he backed
everything up last.
|
From: guest (allisonvoorhees)
, 137 months, post #184 |
You're right. I *do* have fictionbranches.net.
|
From: guest (krueger)
, 137 months, post #185 |
Thanks to all who are involved in getting this thing moving! You
have my resprect and my gratitude and I'd be happy to chip in a few
quid for the hosting.
@DL: Speaking of hosting: have you checked the hosting conditions
of your provider? While fictionbranches may be text-only, there are
some rather graphical 'elaborations' in some grey areas (including
incest, animals, rape, etc.). We wouldn't want FB to be shut down
due to a provider that is not prepared for kinky stuff...
Thanks again to all!
|
From: guest (DocLock)
, 137 months, post #186 |
You guys probably know more about the seedy underbelly of FBs than
i do. Heres the TOS of one of the hosts were looking at.
http://www.hostgator.com/tos.shtml think FB crosses that in a way
tht would get us in trouble?
|
From: guest (krueger)
, 137 months, post #187 |
Hm, that looks ok to me. The only part which mentions pron is
towards the end of section 2 "Content" and specifically mentions
children. But since FB does not permit uploading (and thus hosting)
of such material, there should not be an issue. Of course if
somebody links to something like that, FB is in trouble. But any
forum-/guestbook containing website has the same risk.
Can anybody else confirm my assumption that this TOS should be
fine?
|
From: guest (allisonvoorhees)
, 137 months, post #188 |
This section may be cause for concern:
7b.) INODES
The use of more than 250,000 inodes on any shared account may
potentially result in a warning first, and if no action is taken
future suspension. Accounts found to be exceeding the 100,000 inode
limit will automatically be removed from our backup system to avoid
over-usage, however databases will still be backed up. Every file
(a webpage, image file, email, etc) on your account uses up 1
inode.
We should check with Zack to make sure his site doesn't use all
flat files.
|
From: guest (Brayn)
, 137 months, post #189 |
The entire contents of FB are stored in a single SQL database, the
only individual files are the main scripts for the site itself. So
it should be ok.
|
From: Weirdoid
, 137 months, post #190 |
I was wondering if FB should be stored on multiple servers to keep
from taking up too much space as one chunk.
|
From: guest (A Concerned preson)
, 137 months, post #191 |
when we make the fiction branches 3.0 (i think)
i have some ideas
1. we should be able to post comments to branches (though that
might cause even more trouble with the size of the sever)
2. we could have a non transformation oriented story
3. we could have a better fourm with a better format in FB so
people can colrabate ideas and discuss prolbems and not have to
navigate through like we do in the branches of stories
these ideas have problably been said in this fourm and im sorrt if
im saying what has already been said
(btw its amazing how fast you people have been working on this, i
wish i could help more)
|
From: Weirdoid
, 137 months, post #192 |
If we are making suggestion for stuff to include in a new FB. I'd
like to see a new top end story that is as flexible as You Are What
You Wish is.
|
From: guest
, 137 months, post #193 |
Great progress guys. Quick question though, how long will it be
until it's back up again?
|
From: guest (DL)
, 137 months, post #194 |
The current goal is to get FB 2.0 back running. A week from now i
should have hosting, and when zach emails me back we can talk about
return dates for fiction branches. I wont be doing any work on the
story itself so i cant tell you about any updates. Even if i wanted
to implement them id need zachs permission (which from what i heard
i doubt id get) and know how his code works.
Im not taking suggestions at this time and until i hear from zach
there is absolutely nothing i can do. The site could be back up by
wednesday if i could just get Zachs permission and backups.
Once the site is at a stage where we can talk about funds,
assistance, likelyhood of any changes and the sort, we will talk
about that. For now were refugees here and we have to wait for a
response from someone.
Because until then, were just guys with hosting space squating on a
domain name.
Good night folks!
Thanks for all the support,
DocLock
|
From: guest (oberon21)
, 137 months, post #195 |
Just want to say good work on the speedy recovery plans for FB,
it's good to see there's still a fair amount of dedication to the
site around.
As a quick suggestion, would we be able to have a slight hierarchy
set up if we're setting things up anew? Just so if the worst
happens again there won't just be the one responsible person to
attempt to contact??
Just a thought for ease of the comunity.
|
From: guest (Brayn)
, 137 months, post #196 |
DL, I proposed rebuilding FB some time ago to Zach, his response
was he's not going to let anyone else code for his "pet project",
any changes made will be by him alone. I've "pestered" him
occasionally since 09 to do some updates, but he's not intersted in
letting anyone touch the code. So a new site would have to be built
and Zach would have to willingly hand over if you want to build an
FB3.0 on the existing stories.
It's all built in PERL, with a single SQL database handling
everything, that's pretty much all there is in the background.
Zach's a big fan of encapsulation too, so that'll give you a basic
idea of how he's built the site, but he hasn't even let me see the
code. So go figure.
|
From: guest (anodyne)
, 137 months, post #197 |
fiction branches needs moar github
|
From: guest (Zach)
, 137 months, post #198 |
Folks, thanks for your efforts. I've contacted DocLock via email
about site requirements.
In the meantime I've resurrected YAWYW on transform.to, although
it's a rather old archive I'm afraid. Maybe it'll tide you over for
a while :-).
Zach.
|
From: guest (DocLock)
, 137 months, post #199 |
Thanks to zach, and ill have to share the good and bad news. Were
working on the relaunch as we speak, and i hope to have things
ready for zach to start the move as soon as tomorrow night.
Badnews, unless we get a hold of countd, we wont get a recent
backup. TheGuest and I are trying to work on a system for backups
thats not in the hands of a single person. Im emailing zach about
what the new site could have along side the original system, and
about what we will have to do.
Sad news: unless countd is found we only have YAWYW to restore. Ill
be chatting about what to do about others and newer additions, but
otherwise its just gonna have to be restored from archives and
caches that are scavanged.
Thank you everyone and when the site is up we may be calling on you
to help restore branches and additions, as well as initiatives to
keep the site up and running.
- DocLock
|
From: guest (Cvlsoldier)
, 137 months, post #200 |
At least something is finally being done to fix this problem. Can't
wait to see what you guys come up with, so good luck!
|
|
|
|
|
|
Add a New Message to This Thread
Posting Guidelines
Primary
- ANY POST(s) MAY BE REMOVED at the discretion of moderators
for violation of this website's guidelines/rules or any law
applicable to this website.
- All discussions must be transformation related OR of interest to
the transformation community.
- Please try to keep posts appropriate for younger teenage eyes to
view (Things you'd be comfortable sharing with a 13 year-old).
- Do not 'attack' other posters. You may attack an individual's
comments but not the individual.
- Be polite, courteous, and respectful. Please keep the conversations
civil.
- While use of an online alias is ok. Do NOT pretend to be another
(or registered) user.
Intellectual Property
- Do not post direct links to complete copyrighted works. Links
provided by (or approved by) the copyright holder may
be exempt.
- Links to content hosted on websites that have a clear, and easy to
find, process for dealing with infringement(s); and a known
reputation for following through with said process, may
be allowed.
- Please read this site's views on copyrighted content on the FAQ
page.
- Do not plagiarize. Credit your sources.
Helpful
- For posts and material that are not safe for viewing in a workplace
or with younger eyes, please mark the thread or post as either, "MATURE CONTENT", "ADULT CONTENT",
or "NSFW".
- Please post clear SPOILER warnings if you intend to give away
details that would spoil the story for those who have not yet seen
the material, preferably by using the spoiler
tags (don't forget to close the spoiler text with the end tag),
like so: <spoiler>Text to be "hidden"
</spoiler>
-- For additional help, please see: HOW TO: Use Spoiler tags
message thread.
- When starting a New Message Thread, please include details about
your topic of discussion or request in the Subject
field to help draw in readers who are interested and avoid wasting
the time of those who are not. Also helpful in searching for the
topic/thread later.
- If you post a link, please provide some detail as to what it is.
Identify the material if possible.
- Please post in English, or include an English translation, when
possible.
- If seeking material / information, include the results of your own
efforts so that others can offer better help (and avoid wasting
time and effort on redundant searches).
- When starting a new thread to request material or information,
please begin the subject with "REQ:"
or "REQUEST".
Etiquette
- Do not post messages in ALL CAPITAL LETTERS.
- Do not attack a user for improper spelling and/or grammar. Not all
of our community uses English as their native language.
- Please do not stray (far) from the topic of the original post.
- If a poster provides their contact information for any reason, do
NOT clutter the Message Board by asking them to contact you. They
gave out their contact information for a reason.
- No begging. Ask nicely.
- Do not feed the trolls and spammers. Please ignore them.
- Do not keep asking for clips after others have already posted
information on where to obtain the material.
- Please have some patience. Not everyone visits the board daily.
Your post may not be seen (by someone with the correct information
or idea) for several days or weeks.
- No bumping. Bumping will be treated as intentional spamming.
Advertising
- Do not post advertisements.
- One exception is for products or services that relate to entries on
this site. And even then, only post an announcement once. You
should add links or content to the appropriate database entries. Do
not repeat this information to the message board. Doing so will be
considered spamming.
Miscellaneous
- This list is neither all-inclusive or all-exclusive in nature, and
is meant to guide everyone on appropriate content for and conduct
on this Message Board.
- The purpose of this Message Board is to share information about
transformation-related content, news, ideas, etc. Also acceptable,
are conversations that are of interest to the transformation
community.
- Moderation of posts for reasons not listed above are at the
discretion of the Trusted Users who moderate this website, for the
purpose of keeping things within the "spirit" of the owner's wishes
and the website's purpose.
- If you disagree with a moderation decision, please make an argument
as to why it should be reinstated. Use the posting guidelines to justify your point.
Do not attack the moderator.
[Edit this Page] | |
|
|
|
| |
|
|
|
|