Search

UPDATE (4/27): There were two reasons that affected federation between Ani.Social and Lemmy.World.

The first reason was an outgoing activity that got stuck in queue. This was resolved by manually marking that activity as successful.

The second reason was a subsea fiber cut between Europe and Asia which caused incoming activities from Lemmy.World to lag behind.

The original plan was to move Ani.Social closer to Lemmy.World this weekend but seeing the activity queue rapidly dropping over the past two days, it's unlikely this will push through. We will continue to monitor this however.

Again, thanks to @wjs018 for informing me about this and for keeping others up to date in this post's comments. Thank you MrKaplan from Lemmy.World for helping us resolve the issue!

---

There are ongoing issues between incoming and outgoing activities between Ani.Social and Lemmy.World. Posts, comments, and votes from both instances are not in sync with each other.

The exact cause is to be determined. The instance may experience downtime and interruptions until further notice.

In the meantime, we suggest using an account on an instance that is federated with both Ani.Social and Lemmy.World.

Thanks to @wjs018 for informing me about this issue. Thanks also to MrKaplan from the Lemmy.World team for continuously helping us resolve this issue.

We will be upgrading to Lemmy v0.19.3 on 2024-01-27 09:00 UTC+8. During this time, this instance will be temporarily unavailable for approximately three hours as we perform the maintenance.

You can view the instance status updates here.

We apologize for any inconveniences.

We successfully upgraded to Lemmy v0.19.1! (Yay~!)

Unfortunately, you might need to login again on your Lemmy apps and front-ends.

More importantly, if you had 2FA enabled previously, you need to re-enable it again as Lemmy v0.19 has an improved 2FA implementation.

A few other notable major changes in Lemmy v0.19 include:

• Improved post ranking (scaled sort)
• User-level instance blocking
• User data export/import

You can read more about all the new changes here.

Additionally, we made a few changes to the instance that may or may not be a concern for you:

• Increased max image resolution to 4096px
• Disabled external image caching
• Migrated to object storage
• Switched email provider to MXRoute from Lark Suite

If you have any questions, feel free to ask here or create another thread at [email protected].

2023-12-21 15:41 UTC+8

Upgrade complete.

---

We will be upgrading to Lemmy v0.19.1 on 2023-12-21 12:00 UTC+8. During this time, this instance will be temporarily unavailable for approximately four hours as we perform the maintenance.

You can view the instance status updates here.

We apologize for any inconveniences.

For context on the topic, please read this post.

After reaching out to the Lemmy.ml admins and Lemmy developers regarding the defederation of ani.social from Lemmy.ml and the exclusion of ani.social from join-lemmy.org, they have chosen to remain defederated from ani.social for "[containing] a lot of sexualized images and partial nudity" which goes against their rule against pornography.

However, because they have found no evidence of CSAM in ani.social, they have agreed to merge our pull request to include ani.social in join-lemmy.org.

We'd like to thank the Lemmy.ml admins and Lemmy developers for their careful consideration of our request. Although we had hoped to federate once again with Lemmy.ml, we believe they have valid reasons to remain defederated. We hope that this may be revisited in the future as Lemmy continues to evolve.

We apologize to our local users who regularly visit Lemmy.ml communities. If you wish to continue accessing Lemmy.ml communties, we suggest moving to an instance that is federated with both Lemmy.ml and ani.social.

As of November 7, 2023 09:23 both Lemmy.World and lemmy.dbzer0.com have federated with us again. Thank you for quickly reviewing the situation and reversing your decision.

We hope that Lemmy.ml will follow soon.

Please do not say anything hateful to the Lemmy.ml admins or the developers. Before commenting on this thread, please read the post completely.

---

We (ani.social) have been defederated from Lemmy.ml a few hours ago presumably for the reason of being "full of CSAM" which I disagree.

What happened?

The Lemmy developers recently launched the new redesigned join-lemmy.org webpage which provides information about Lemmy and a list of servers that people can join. The redesign looks great! It details a lot of new and useful stuff such as a categorized server list and mobile apps. However, I noticed that our instance (ani.social) was not in the list despite previously being there before the redesign.

After looking through the joinlemmy-site code, I discovered that ani.social was added to the "excluded" list in a commit a few weeks ago. I thought that this was a mistake so I made a pull request to remove us from the excluded list (and also to add our instance's category and language).

Unfortunately, the pull request was closed with a comment that reads "No, that is full of CSAM". The thread was locked so I couldn't reply. I tried to reach out to the developers via Matrix, politely explaining that ani.social has a content policy rule against CSAM which reads:

> 7. Do not submit content depicting a child (both real and virtual) engaged or involved in explicit sexual activities. A child is defined as a person who is under 18 years old; or a person, regardless of age, who is presented, depicted or portrayed as under 18 years old.

Unfortunately, my invitation was rejected and I did not hear back from them.

Shortly after, I discovered that Lemmy.ml had defederated from ani.social. The last post ani.social received from Lemmy.ml was just after the pull request was closed.

What does this mean?

This means that no user from ani.social can interact with communities from Lemmy.ml and vice versa. This affects those who subscribe to communities from that instance.

This also affects the anime community on Lemmy as a whole because the biggest anime discussion community resides on Lemmy.ml ([email protected]) in which their episode discussion bot, @[email protected], is hosted here. It's very concerning that as an anime-themed instance, we're now completely disconnected from this community and other related communities.

This also affects ani.social in the long run as our exclusion from the join-lemmy.org webpage will reduce our visibility. The exclusion from join-lemmy.org and defederation from Lemmy.ml may also prompt other instance admins to defederate from us. Generally, ani.social will be seen in a very bad light.

As the admin of ani.social, I genuinely feel heartbroken after what had happened. Not only do I feel like I'm doing a poor job of building ani.social but I also feel like I've disrespected the work of the Lemmy developers. I really apologize to those who are affected by this. I hope that this is just a misunderstanding and I will do my best to resolve this problem.

2023-09-30 16:19

Upgrade complete.

---

We will be upgrading to Lemmy v0.18.5 on 2023-09-30 16:00 CST. During this time, this instance will be temporarily unavailable for approximately two hours as we perform the maintenance.

You can view the instance status updates here.

We apologize for any inconveniences.

2023-09-17 18:53 CST Update:

The server maintenance is complete.

---

Original message:

We will be conducting general server maintenance on 2023-09-17 18:00 CST. During this time, this instance will be temporarily unavailable for approximately two hours as we perform the maintenance.

You can view the instance status updates here.

We apologize for any inconveniences.

We have upgraded to Lemmy v0.18.3! You can view all the changes here.

If you encounter any issues, please send us an email or leave a comment in this thread. Thank you!

P.S. We've had so many new users come over the past weeks. Welcome to AniSocial!

---

This announcement will be pinned for seven (3) days since the initial posting.

We've received a few messages lately from people who got locked out of their accounts after enabling 2FA and not setting up the authenticator properly. To anyone else who got locked out because of this, you can send us an email at [email protected] with the same email address you used to register. We'll remove 2FA from your account so you can set it up again.

There is an open issue about it on GitHub.

---

Note: This post will be pinned until the 2FA issue has been resolved and until the 2FA implementation has been improved.

We have upgraded to the latest stable version of Lemmy! You can view all the changes in the announcement page.

An important note for this instance:

We are now using ubergeek77's multiarch Docker image (thank you!). Prior to this, we were using masquernya's build script to build our own images which usually took a while. If you encounter any issues while using or interacting with AniSocial, please let us know in this thread or send us an email to [email protected].

P.S. We received a lot of new registrations over the past week. Welcome to AniSocial! We hope you enjoy your stay here!

^{This announcement will be pinned for seven (7) days since the initial posting.}