squidgestatus

As of right now, 11:53am on Tuesday, December 30th, 2025 SquidgeWorld Archive is back up and running!  If you see any oddities, please don't hesitate to let us know.

For transparency, here's basically what happened:

• The server had a hard disk corruption that had to be corrected


• Corrections were made, but there was an internal database that contained further corruption. The internal database was replaced with a backup so that the "redis" server (software that is required for SqWA to run) would come back up as well


• With all corruption errors addressed, the system processed the data chunks like it normally does when it comes up.

We should be good to go from here on out. This does make a redeployment of SqWA a higher priority.  We're in the beginning stages of this.  More information will come about when we're ready to go.

We've had a huge influx of people to SquidgeWorld in the last week or so, and it seems to come down to an incident at AO3 with underage fics.  This email is to respond to the half a dozen emails/trouble tickets that we've gotten asking us to clarify our stance on the issue.  Even though it's explicitly stated in the SqWA Posting Help section, we're pointing it out here, word-for-word.

Point 1 - Use of the Underage tag: The SquidgeWorld Archive does allow Underage fanworks to be added to the archive.
Point 2 - Use of the Underage tag with respect to fic ratings: Any fic that features the Underage tag and where the rating is Mature or Explicit, that fic must be locked to Archive users only. No exceptions.
Point 3 - Use of RPF tag: The SquidgeWorld Archives does allow Real People Fiction - RPF - to be added to the archive.
Point 4 - Underage/RPF tags on the same fic: If a user adds an Underage fic that is about RPF - Real Person Fiction - that fic must be locked to Archive users only. No exceptions.  NOTE: This rule is new, added in response to this very situation.

While some people may not agree, this is our stance.  We refuse to become gatekeepers of those who use the site; we will never tell you what you can and cannot post to the archive.  However, we want to make sure that people who use the archive and do not want to see those works are not inadvertently exposed to them.  This is why we have our locking policy in place.  If it's in the archive and meets the above points, locking must be completed appropriately.  And if it is not—and a recent quick check showed that people are not always respecting this rule—the locking will be done for you by the admins.

If you have any more questions, feel free to ask them.  But if you just want to sit back behind an anonymous keyboard and call us names, that's fine. We just don't need to know about it; don't send us a note to let us know you're calling us an asshole somewhere on the Interwebs. People already do this, and it's tiring.

So we had an equipment failure for The SquidgeWorld Archive that makes the current machine unusable.  We're weighing options, but there will be no update available for the immediate future.  We will be back up, but it's going to depend on a few things.  First of all, we just ordered the necessary equipment as a backup, but we're going to attempt to move the "innards" of the server to a new machine that we have already on hand.

It will probably be Sunday before the server is back up and running again, though we cannot guarantee this.

The good thing is, with our judicious backup policy, we're sure no data is lost.  Indeed, the drives are working just fine.  We just now need to solve a few technical issues before we can come back.

If you're part of SquidgeWorld Archive, you may notice that the site will be down briefly throughout the day - today, October 26th, 2025.  This is because we are going to be adding a few things here and there to add links to Squidge.org's fandom offerings in the Community links/page, as well as additional clarification information for commenting.  The Community links additions will link to some of our pages on Dreamwidth where you can get additional information about Squidge and learn about challenges that are currently happening, and the additional information for posting comments is around discouraging commission spammers from posting.

As always, if you've got questions, don't hesitate to contact us!

I have to say that this is probably my favorite thing about being a part of Squidge.org and all the various entities. Sure, you can see the growth of fandom spaces and how people are using them - but when it comes to the year in review, this is where you can see the real, tangible evidence of what's been going on for the last year. So without further ado, I present SquidgeWorld's Year in Review based on what's been read! Please note this is graphics-heavy so I'll attempt to hide behind a cut.

( Read more... )

So that's how 2023 went. We shall see how this year shakes out to be! Thanks to everyone who was part of SquidgeWorld.org and helped make these statistics come about, and thanks to everyone for being a part of Squidge.org!

Per the post on SquidgeWorld, the SquidgeWorld Archive will be enter extended downtime on Friday, November 24th from 06:00 Pacific (14:00 UTC).  It's currently not known what time we will be back up, but this will be longer than the current usual 30 minutes Sunday morning maintenance.

No other Squidge services will be down.

There have been a few questions today about AI and Squidge.org's approach, so I thought I would drop a blogpost here so people know.  Here's our philosophy:

While AI (Artificial Intelligence) can be a great thing in the realm of medicine, like computers spotting lung or breast cancer before a human can, AI shouldn't have any place in the fanfiction world.  Honestly, probably not in the pro-fiction world, either, but every day companies like Grammarly are rolling out, "Try our new AI tool to assist your writing!" programs.  When it comes to writing, each voice is unique - and that's a wonderful thing.  Bringing AI into the realm of fanfiction is just asking for those unique voices to be squashed in favor of bland, generalized voice that is "safe for the masses."

That's not what we're here for.

Starting soon (days, not months) we'll make a concerted effort to keep screen-scraping bots away from Squidge.org properties, including SquidgeWorld Archive, Squidge.org homepages, and Squidge Images.  That's not to say more sophisticated screen scraping programs won't be able to slip through the cracks.  However, most generic screen scraping programs that AI uses can be identified and blocked.

Additionally, there are two settings that will protect you better on SquidgeWorld Archive.  Those are:

• In your profile preferences, there is an option called "Hide my work from search engines when possible."  This will discourage your work from being found by Search Engines, not necessarily by screen scrapers.

• For the works that you choose to archive within SquidgeWorld Archive, please make sure that this checkbox is ticked.  That way your fanwork will be available only to registered users - and prevent both Search Engines and screen scrapers from being able to access your works.  The setting looks like this:
  
•  
• Your work will show up in the list of results, just like before screenshot below.  Notice the lock next to the penname?  That means that this work can only be read if you are logged into an Archive account.

Please reply with what questions you have.  And thanks!