[sticky entry] Sticky: Got Issues?

Nov. 8th, 2020 03:39 pm
squidgestatus: (Default)
Here's a new sticky for Got Issues.  If you have an issue, post it here. 

BEFORE YOU POST! Important to know:
  • Maintenance for SquidgeWorld Archive happens every Sunday morning from 7am to 9am Pacific Time. This means during this timeframe, the server will NOT be avaialble. This is necessary to keep the archive running smoothly.
  • If you are trying to sign up for Squidge Images, signups are open twice a day from 10am to 2pm Pacific Time, and again from 10pm to 2am Pacific Time. During those timeperiods, you can sign up here: https://images.squidge.org/signup .
squidgestatus: (Default)
We're still behind in our support tickets - so please be patient with us. But I wanted to address one ticket that I got from someone with a first name and GMail address that starts with a "K" because their email bounced. Their question is:
Where does this site sit on censorship? Is it like AO3, or will you be censoring works based on personal morals? Your FAQ does not clarify this.

Personally, I don't know what this question is asking. But I will say this: SquidgeWorld takes a dim view on censorship. Censorship is a slipperly slope to "You'll read what I want you to read," which is something we do NOT stand for. We do not censor on SquidgeWorld with the only exception being people who jeopardize our IRS 501c3 non-profit status with requests for support via Ko-Fi, Patreon, and the like. If we find those in people's works, we ask that they be removed. And if the author does not respond to our request within a reasonable (72 hour) timeframe, we will remove the link ourselves. If you're talking about allowing non-consensual (e.g. rape), underage sexual content, and incest fics, the archive DOES allow these fics to be added with the rule that they should be marked as restricted to SqWA users only (not visible to guests without an account). And, on occasion when someone adds one of these types of fics and does NOT lock it, we will come behind them and mark it as locked/restricted. And the only other type of censorship that's "allowed" is if someone uploads a work that is not theirs to the archive; we hide those so that they can only been seen by admins.

Want to discuss? That's good - we can do that. But if you want to sit back and call us names, then you're not really in the right place. There are plenty of other sites out there for you to peruse.
squidgestatus: (Default)
Our ISP notified us that they will be doing maintenance on fiber lines (which is what we're on) on November 12th from 00:00 (midnight) Pacific. Time to 06:00 (6am) Pacific Time. They said that we will experience intermittent outages of up to 15 minutes, multiple times during that timeperiod. Tags indicate all the services (everything but FenRecs.com) will be affected.

So if you're up and about during this time, be aware that connectivity will be hit and miss.
squidgestatus: (Default)
First off, a gentle reminder on a few things.

1) You may NOT post another person’s works, even with their permission. We’ve found half a dozen of these types of works, often marked as “NOT MINE, Please credit original author” and such. If you want to share someone’s work, then share it amongst your friends, but DO NOT POST to SquidgeWorld.

The only exception we’ll allow is if BOTH the poster AND the original author have SqWA accounts, and the poster posts the fic and makes the original author as one of the “owners” of the work. Then, of course, proper attribution is given, like, “Originally posted to AO3 by (oringal author) who is marked as a coauthor here.”  

Otherwise, DO NOT POST.

2) Profile pictures do not work. This is intentional due to a security incident. Sorry, but no exceptions.

3) We do not allow Ko-Fi, Patreon, or other links to be added to people’s profile, nor in their works. The only exception to this rule is if you are creating works in the public domain (e.g. Bram Stroker’s novel ’Dracula’, Charles Dickens’s ’A Chrismas Carol’, works by Shakespeare). Otherwise, it jeopardizes our 501c3 non-profit status.

What you can do, if you’re one that has Patreon/Ko-Fi, etc., is you can create a space off of SquidgeWorld that has links to your support platforms, like on Tumblr or a personal webpage or the like. Then you can add in your stories, “Learn how you can support my work!” and link to that Tumblr/personal blog/etc.. But, unless it’s public domain OR original works, you cannot include links to financial-gain websites.

4) We go down every Sunday for maintenance. Usually just 2 hours, but it might take longer (we’ll plan for 3 hours total, 7am Pacific to 10am Pacific) on this older piece of hardware we’re on.

And now a happy thing to post.

Because I “ran out of spoons” and didn’t finalize Squidge’s “Hot Fic Summer” fundraiser at the end of September like I was supposed to do (hey, ::waves hands at the state of the world::) and because the AO3 incident has led to Squidge being a lot busier than normal, it’s been decided that “Hot Fic Summer” is going to extend until November 30th, 2026. This doesn’t really mean much, besides the fact that anyone who has donated at least $10 from May 2026 to the end of November (even if you gave $2 five times) will get a Hot Fic Summer sticker. And anyone who has donated at least $100 gets a Hot Fic Summer t-shirt.

More details after November 30th; we’ll contact donors by email to arrange stickers and t-shirt sizes and such. Until then, keep being awesome, and long live fandom!
squidgestatus: (Default)
Thanks to the time change here in the US, it was rather easy to get out of bed at 3am. Did some work, and the SquidgeWorld server seems to be responding. It's chugging through the last step (albeit one that takes at least an hour), but it seems stable. So by the time you read this, SquidgeWorld Archive will be back up! Albeit on a slower processor, but we maxxed out on the RAM so here's hoping that things process at least as well as they did on our last server. So don't expect AO3-like performance! I know the crush after 24 hours of downtime will be large, but give us some grace.

I also want people to know: Yes, we're still utilizing the invitation queue. BUT, if you are a community mod and you need a collection or to run a fest or such, please contact me (preferably here, but any of our social media should suffice) so that I can bump you to the front of the line.

We're using your donations to buy a new, more powerful server to host SquidgeWorld, and we'll be taking time at the end of the year to upgrade everything to the latest & greatest code and bug fixes. That will be another multi-day project. But that's for later.

And finally, I want to thank everyone for their kind words. This has truly been a humbling experience, and your kindness has helped me deal with the stress this has caused.

For now, enjoy!
squidgestatus: (Default)
Well, we tried.

For most of the day we were plagued by technical issues. We've conquored all of them - but one. And that one is what's keeping us down at the moment. After many, many hours, things are at a standstill.

So we're kind of stuck at the moment.

We're going to kick off again in a few hours, but don't expect anything tonight. More updates in the morning.
squidgestatus: (Default)
It's currently 14:45 Pacific Time, and here's the update:

Swapping out machines meant network configuration changes. Things were fine earlier, but the network continued to disconnect after 3 minutes for some reason. Tried a few things, and I think it's finally up to stay. However, it's on a slower network interface at the moment. So, we're going to continue to bring the server up, and will send out notification when it's completed.

Hardware issues always keep you on your toes. I'm just kind of over it today, though!

More soon.
squidgestatus: (Default)
We are NOT up. Hardware issues. We're dealing with it best we can. Hope to have the system up in the next couple of hours.

More soon.
squidgestatus: (Default)
Lots of people didn't see the big banner saying we were going down today.  So here's what's up.

First off, SquidgeWorld goes down every Sunday from 7am to 9am for routine maintenance. But today we were also doing hardware maintenance. So we planned on being down 7am to 11am Pacific.

Hardware maintenance just finished. Now we bring the server up. It will take anywhere from 1-2 hours to bring the system up from this point.

Please be patient. And monitor one of our social media links. We hope to be up by 12Noon Pacific today at the latest.
squidgestatus: (Default)
This is mostly about SquidgeWorld Archive, but there are also other things about Image Hosting later on.  First thing, this is what's currently posted as a SquidgeWorld News Item, but posting here so everyone can see it. If you're seeing this from BSKY, Tumblr, or Mastodon, you might want to click the link and read everything going on. Especially the upcoming embargo on new Image Hosting accounts at the bottom.
Here at SquidgeWorld Archive (SqWA) we do things differently than what you're used to. For example:
1) We are much smaller than AO3. Please remember this if and when things get busy on the site.
2) SqWA came out of the old Peja's Wonderful World of Makebelieve - and some of the stories in our archive are up to 30 years old. So we are rich in some older fandoms that aren't as big today.
3) Quite a lot of the old fandoms, especially those where the user is no longer with us for one reason or another, stories are marked as "Display to registered users only." This prevents spam comments and the like. If see there are 200 stories in your chosen fandom, but you aren't logged in and can only see 50 stories? That's because you're not logged in. Create an account and log in if you want to read ALL works in the archive.
4) AO3 has dozens of computers in datacenters around the world. They raise millions of dollars to pay for this. SqWA? We're a single server and separate database server. So no, we're not going to be as speedy as AO3 - especially with thousands of new users joining at once.
5) We do tag wrangling different. You can read our tag wrangling guidelines here. Especially pay attention to our non-traditional pairings designations! Our relationship tag in the News Posts will give you more details. And actually, going through our admin posts may not be a bad idea for many newbies.
6) You can change the skins to however you'd like. There are may published skins listed in the footer, and you can create your own. Dark mode is my favorite.
7) There are two links under the Contact Us in the footer; one for questions and abuse, and one for technical support and feedback. We'll respond as soon as we can.
8) We do NOT allow AI generated written content in the archive at all. AI generated content is not welcome, and if found will be removed. We trust you to label your content accurately.
NEW: 9) For performance purposes we have disabled downloads.
NEW: 10) And we just had our first commission spammer. We don't play here - you leave commissioin spam, your account and comments/works/etc. are GONE. We don't put up with that shit here. (Our #1 rule is "Don't Be A Dick", so I can say shit.)
NEW: 11) Performance is still bad. It will even out, but we do have some growing pains with 12,000+ new users in less than 24 hours.
NEW: 12) Icons DO NOT WORK. This is by design as a security precaution. I will invite everyone to stick to their standard profile picture for the time being until this can be fixed.
NEW: 13) We got like 100 trouble tickets overnight. It's going to take some time to get through to everyone, especially since not everyone will read these notices.

Now that everyone's seen that, I need to point out a few things again (as people neglect to read):

  1. Guest comments are OFF due to commission spammers.

  2. Performance is bad. We've added 18,000 users in the last 26 hours, and expect to add at least another 10,000 over the course of the weekend.

  3. SquidgeWorld will be down for probably 4 hours during our regular maintenance window, which starts Sunday, November 1st at 7am Pacific. This is to add in some power for the server.


Now a few final words.

  1. Thank you to everyone who has donated to Squidge since the AO3 downtime started. Well, thank you everyone who has donated. There was a bad link for the donation, but it has been fixed. If you're curious, you can get information at this link, or simply donate via PayPal by sending a donation to the email address donation@squidge.org

  2. Speaking of bad links, there may be some links that aren't working due to whatever reason. We'll clean these up as they are reported.

  3. With regards to Image Hosting: If you already have an account, there's no need to worry. If you do NOT have an account and want one, you must sign up by November 1st, 2026 at 02:00 (during the 10pm to 2am window). We will need to stop creating accounts during this massive upheaval for load balancing. People who have accounts do not need to worry; you can still upload as you wish. But people without accounts will not be able to sign up until things on our network stabilize. Probably December.

  4. We will be going back to an invitation queue starting on Sunday, November 1st, 2026 after maintenance.


Questions? Let us know.
squidgestatus: (Default)
This is mostly about SquidgeWorld Archive, but there are also other things about Image Hosting later on.  First thing, this is what's currently posted as a SquidgeWorld News Item, but posting here so everyone can see it. If you're seeing this from BSKY, Tumblr, or Mastodon, you might want to click the link and read everything going on. Especially the upcoming embargo on new Image Hosting accounts at the bottom.
Here at SquidgeWorld Archive (SqWA) we do things differently than what you're used to. For example:
1) We are much smaller than AO3. Please remember this if and when things get busy on the site.
2) SqWA came out of the old Peja's Wonderful World of Makebelieve - and some of the stories in our archive are up to 30 years old. So we are rich in some older fandoms that aren't as big today.
3) Quite a lot of the old fandoms, especially those where the user is no longer with us for one reason or another, stories are marked as "Display to registered users only." This prevents spam comments and the like. If see there are 200 stories in your chosen fandom, but you aren't logged in and can only see 50 stories? That's because you're not logged in. Create an account and log in if you want to read ALL works in the archive.
4) AO3 has dozens of computers in datacenters around the world. They raise millions of dollars to pay for this. SqWA? We're a single server and separate database server. So no, we're not going to be as speedy as AO3 - especially with thousands of new users joining at once.
5) We do tag wrangling different. You can read our tag wrangling guidelines here. Especially pay attention to our non-traditional pairings designations! Our relationship tag in the News Posts will give you more details. And actually, going through our admin posts may not be a bad idea for many newbies.
6) You can change the skins to however you'd like. There are may published skins listed in the footer, and you can create your own. Dark mode is my favorite.
7) There are two links under the Contact Us in the footer; one for questions and abuse, and one for technical support and feedback. We'll respond as soon as we can.
8) We do NOT allow AI generated written content in the archive at all. AI generated content is not welcome, and if found will be removed. We trust you to label your content accurately.
NEW: 9) For performance purposes we have disabled downloads.
NEW: 10) And we just had our first commission spammer. We don't play here - you leave commissioin spam, your account and comments/works/etc. are GONE. We don't put up with that shit here. (Our #1 rule is "Don't Be A Dick", so I can say shit.)
NEW: 11) Performance is still bad. It will even out, but we do have some growing pains with 12,000+ new users in less than 24 hours.
NEW: 12) Icons DO NOT WORK. This is by design as a security precaution. I will invite everyone to stick to their standard profile picture for the time being until this can be fixed.
NEW: 13) We got like 100 trouble tickets overnight. It's going to take some time to get through to everyone, especially since not everyone will read these notices.

Now that everyone's seen that, I need to point out a few things again (as people neglect to read):

  1. Guest comments are OFF due to commission spammers.

  2. Performance is bad. We've added 18,000 users in the last 26 hours, and expect to add at least another 10,000 over the course of the weekend.

  3. SquidgeWorld will be down for probably 4 hours during our regular maintenance window, which starts Sunday, November 1st at 7am Pacific. This is to add in some power for the server.


Now a few final words.

  1. Thank you to everyone who has donated to Squidge since the AO3 downtime started. Well, thank you everyone who has donated. There was a bad link for the donation, but it has been fixed. If you're curious, you can get information at this link, or simply donate via PayPal by sending a donation to the email address donation@squidge.org

  2. Speaking of bad links, there may be some links that aren't working due to whatever reason. We'll clean these up as they are reported.

  3. With regards to Image Hosting: If you already have an account, there's no need to worry. If you do NOT have an account and want one, you must sign up by November 1st, 2026 at 02:00 (during the 10pm to 2am window). We will need to stop creating accounts during this massive upheaval for load balancing. People who have accounts do not need to worry; you can still upload as you wish. But people without accounts will not be able to sign up until things on our network stabilize. Probably December.


Questions? Let us know.
squidgestatus: (Default)
After our self-imposed 24 hour downtime due to PHP vulnerabilities, we have patched our PHP versions, and are back! All sites should be up and functioning. If you see something, please log a ticket. Thanks!

DOWNTIME

Oct. 21st, 2026 02:34 pm
squidgestatus: (Default)
This is what's posted on BSKY and Mastodon:

FYI, due to PHP vulnerabilities, all webhosting services on Squidge.org (including Squidge Images, custom domains, etc) are DOWN. They will be back ASAP once patches are released.


So we are down until PHP packages can be downloaded and patches made.

edit: This affects Squidge.org, hosted websites and archives, and Squidge Images. This does NOT affect SquidgeWorld, Discord/IRC chat, or FenRecs.com (which, I need to do an official relaunch soon!).
squidgestatus: (Default)
Please remember that Squidge Images accounts are available for signup from 10am to 2pm Pacific Time, and again from 10pm to 2pm Pacific Time. During that timeperiod, go to https://images.squidge.org/signup and you will be able to sign up for an account.

THIS IS THE ONLY WAY TO GET AN ACCOUNT. Sending in a ticket asking for an account will be automatically closed. This information is also on the Squidge Web Blog on the right-hand menu.

And again, Squidge Image accounts are for personal, fandom use only. We had someone distributing 30% off coupons to their skin-care line via Squidge Images and, after asking them to remove it and being ignored for 72 hours, had to delete it ourselves. Using Squidge Images for for-profit purposes jeopardizes our non-profit status.

Thank you for understanding.
squidgestatus: (Default)
Before this goes any further, I would like to give my sincerest apologies to the following users: ratkingpoe, Himbonotes, cassieoh, haid3018, and the last user which was accidentally deleted and not banned so I do not have their username. Yesterday's deletion of your images was a knee-jerk reaction, and it was unjustified on my part. While I can restore that part of the database, unfortunately the software that we use for image hosting does not have an "undelete" feature. As such, I ruined the hard work that you put into logging your works onto Squidge Image Hosting. And no amount of apologies is going to do anything to restore those images that you had hosted on Images. Nor is it going to restore the weblinks that you obviously need to now replace on countless websites.

I wish I could go back in time and reverse my decision. But I cannot.

By way of explanation for what happened, we have been advised about hotlinking of our services to things that can cause our non-profit status to come into question. Specifically people using Patreon, Ko-Fi, and the like to paywall items that were located on a Squidge.org property. And so over the years, we have taken action by having these accounts removed. In all, we're talking about 20 different accounts over our 34 year history. On Sunday, September 13th, when running an audit for Patreon images, we came across the above five users with Patreon within their images, from filenames to Patreon usernames and the like. This, at the time, seemed like an immediate Terms of Service violation. And because of this, I went with my gut and deleted all images in these people's accounts and then banned them - except for the one person who was accidentally deleted instead of banned.

Again, this is my fault. My knee-jerk reaction was wrong.

Today was...something. I tried to make better clarification for the Images Terms of Service, as well as the consent screen (which, multiple versions are now floating out on the Internet; I should delete them once this is posted), but that just opened MORE cans of worms. So, in an effort to take a look at this situation from another point of view, I realized that everything could have been avoided by just modifying Image Hosting's web configuration file. And that part has been done. Our configuration for Images webhosting now has directives that will block any hotlinking to either Patreon.com, and Ko-Fi.com. Further, we have contacted Patreon's support and have asked them to institute a blacklist of the Images URL (https://images.squidge.org) from being used anywhere on their service. We have yet to hear back from them on this, but even this is overkill since we have made it so you cannot hotlink on either website. It's a safeguard, however.

This whole thing could have been handled better. I should have handled things better. But I did not. And in doing so, I have tarnished Squidge's 34 year reputation with you, our users. I can not do anything except say that I apologize and will strive to do better in the future. I know that an apology is not enough, as there are still people calling for my head on various social media accounts, as is their right. But I do sincerely apologize.

If you have questions, please ask.
squidgestatus: (Default)
We're going to put this to all Squidge Images users one last time: IF YOU USE SQUIDGE IMAGES FOR IMAGE HOSTING AND THEN TURN AROUND AND SELL THOSE IMAGES ON PATRON, KO-FI, OR THE LIKE, YOUR ACCOUNT AND IMAGES WILL BE DELETED.

Today we have uncovered SEVERAL accounts doing this, and are currently in the process of deleting said accounts and banning those users from all Squidge systems. Even SquidgeWorld. These people are jeopardizing Squidge.org's 501c3 non-profit status with the IRS. And if we do an audit and this process continues, we will permanently disable account creation. No exceptions.

As the saying goes, one bad apple can destroy the entire bunch. And these people trying to profit off of a non-profit are leading the charge.

This is the last time we post this. After today if we catch it again, we will take action.
squidgestatus: (Default)
The move back into our little datacenter is complete, and things seem to be stable. As always, log a ticket if you see oddities.
squidgestatus: (Default)
Now that all THAT is done and things seem stable, tomorrow we're going to have a short downtime to move the new Squidge.org server and all of its services back into our little datacenter. That means taking it down, disassembling a few things, and then reassembling them back in our garage datacenter. This will happen tomorrow morning, between 07:30am and 08:30am Pacific Time (click to find what time this is in your timezone).

As always, if you spot any oddities, send us a support ticket.
squidgestatus: (Default)
Our final few items seem to have come and gone, so as of now, Squidge should be just fine.

  • The Squidge IRC daemon is up and running, and has been validated. Host remains the same: squidge.org or irc.squidge.org, port 6667

  • Webmail is up and running just fine.

  • We're in the process of dealing with older websites; those that can be moved to the Classic webserver will be over the next few days


Finally, about Squidge Images. We get no less than half a dozen tickets a day asking for access to create accounts at Squidge Images. Account creation has been down since our upgrade, but will be up once again starting on Sunday, September 13th. And like before, image hosting signups will only be available between 10am-2pm Pacific Time and 10pm-2am Pacific Time. If you want an account on Squidge Images, wait until Sunday, May 13th and signups will be available during these time periods. If you miss one time period, you can come back during the next. The address will become available only during those times, and will be https://images.squidge.org/signup

If you notice anything, please don't hesitate to let us know on one of our socials (ALL are linked at the top of the blog) or log a ticket at https://www.squidge.org/support
squidgestatus: (Default)
On top of all other items that are once again running, all Sympa/Mailing lists are now populated and running. You can send messages and have them go out just like before. That said, our mail backup service (which holds email until it can be delivered to Squidge) is most likely caught up. So if you sent a message to the mailing list server and didn't see it come through, you'll probably want to resend it.

Currently, these are the outstanding issues:

  • Any website that needs PHP below version 8.x is still down.

  • IRC remains down. I'm currently working on this one.

  • Squidge Webmail is up, but apparently you can not log in. Just found this.

  • For Squidge mail users, the old system of sending spam to a designated spam folder is not working. I've got to figure out why. In the meantime, spam will go to your Inbox like it used to (and does for most email providers).


Again, if you see issues or have problems, respond to this message or hit us up on Discord.
squidgestatus: (Default)
The Squidge.org upgrade is mostly complete. For most people, you have access to what you need, from Squidge Image, the Jinjurly Archive, and other web services.

Here's a list of what I'm still working on, and why:

  • Mailing lists: There are two parts to this that need attention and they are

    • Mailing lists themselves: Email is being accepted by the system, but it is not being distributed to mailing list participants.

    • The web interface to the mailing lists: For some reason, the FastCGI process is not working though it seems to be configured correctly.



  • IRC: The NGIRCD process and supporting files are not installed yet. This is a little bit of a lower priority and will be completed in the next few days. We'll get there soon!

  • Websites needing PHP prior to our current version: We will work on getting these set up as we can. There are multiple items that can be done and we're evaluating those


If you see anything that's odd, please let us know. You cn reply to this post on the Squidge Blog, on Bluesky, Mastodon, or Tumblr. Or you can join us on the Squidge.org Discord server (which, if you need an invite to said server, let us know).

November 2026

S M T W T F S
1 2 34567
891011121314
15161718192021
22232425262728
2930     

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Nov. 20th, 2026 03:30 pm
Powered by Dreamwidth Studios