1. I am not aware of any further communication. T1C says there was no communication about it and I am not aware of claims from .art that state otherwise.
2. That is ridiculous. Yes, it’s their decision if they wanna federate with firefish.social or not. But accusing someone to support/accept racism needs some proof baking it.

1. No, he was just de-federated with absolutely NO previous communication.
2. There is still no real proof that Eris actually is racist at all. Everything is always “someone said/claims”.

Multiple people were able to reproduce this.
So, the assumption that the screenshot is fake is probably wrong.

Altogether, please don’t take screenshots as proof of anything.
They are always subjective to how much you trust the source they are coming from.

See https://pleroma.envs.net/objects/5ed98350-328b-42ff-8005-4137fea8642d for a more complete statement.

HL3

The internet

It sounds like military service with cameras 😆

I wonder if it is somewhat related to that?

https://discuss.grapheneos.org/d/5235-stepping-down-as-project-leader-of-grapheneos

I have talked to them, should be fixed by now 🙂

Now do it with IPv6 😅

In general, yes. Lemmy 0.18.1 does federate again with kbin, mastodon and all the others.

But I think there are still some issues with lemmy.ml and kbin.
Not exactly sure why, but I have them informed already 🙂

As far as I know, lemmy.ml itself is not blocking kbin requests, at least not on purpose.
But I will try to get some official information from one of the lemmy.ml admins.

There were some issues with the federation of non-Lemmy instances in general.
Multiple issues caused these and affected incoming and outgoing communication.

https://github.com/LemmyNet/lemmy-ansible/issues/106
https://github.com/LemmyNet/lemmy/issues/3354

The latest Lemmy version 0.18.1, which was released yesterday, should fix most of the issues, but some instances still need some fixing on the nginx side.

As far as I know, lemmy.ml itself is not blocking kbin requests, at least not on purpose.
But I will try to get some official information from one of the lemmy.ml admins.

There were some issues with the federation of non-Lemmy instances in general.
Multiple issues caused these and affected incoming and outgoing communication.

https://github.com/LemmyNet/lemmy-ansible/issues/106
https://github.com/LemmyNet/lemmy/issues/3354

The latest Lemmy version 0.18.1, which was released yesterday should fix most of the issues, but some instances still need some fixing on the nginx side.

Mh… there is still some beach left where you can add even more lanes!
This will definitely solve the problem!

Looking through the rest of the comments, I think there were already enough explanations.

Making the accusation towards Lemmy that admins can see passwords in clear text is misleading.
It suggests that this is different from other platforms, which it is not. All admins can get your password from/for their respective websites. Either by logging the traffic before the password gets hashed or by modifying the application so that the password gets transferred in plaintext. This applies to Lemmy, Facebook, Google and literally any other service where you enter a password.

What you are saying is somewhat misleading 😒
But did you know over 50k people can see your Facebook password 🤔

But seriously, everything you send to a website/server can, of course, also be seen by it.
This has always been the case everywhere. I am a little surprised that this is suddenly something new…

Reading this, I wonder if we talk about the same Debian 😆

I bet his instances will be one of the few actually federating with them 😔

I sense you do not like cats that much 😆

https://inwx.com