No, I meant lock as in disable login, remove email address, 2FA and freeze all content. This feature might not yet exist in lemmy but it probably should be implemented. Apart from a user leaving this might actually be required to properly handle a user passing away.
Lock this account here, I mean.
I thought beehaw.org defederating from us would not affect post/comments on shared source instances, e. g. lemmy.wtf, which is neither defederated from beehaw.org nor us:
https://lemmy.world/post/149743
Why do I see posts/comments from beehaw users on communities outside lemmy.world and beehaw.org?
That’s because the “true” version of those posts is outside beehaw. So we get updates from those posts. And lemmy.world didn’t defederate beehaw, so posts/comments from beehaw users can still come to versions hosted on lemmy.world.
https://codeberg.org/fediverse/fep/src/branch/main/fep/1b12/fep-1b12.md#the-announce-activity
After the group successfully verifies and wraps the received activity, it sends it to the inboxes of its followers. Followers then use the outer
Announceactivity to verify that the content was really approved by the group. After this step theAnnouncecan be discarded and only the inner activity shown to users.
Since lemmy.world is now behind Cloudflare, is it possible that federation is hit by Cloudflare Challenges as described here?
lemmy.worldlemmy.world: https://lemmy.world/post/2219417lemmy.world to sourcelemmy.world: https://lemmy.world/comment/1749875Note that I pulled my post to the source instance by searching for it from there, but updates/edits are still not federated. This post also has a reply from a lemmy.zip user which hasn’t been federated to lemmy.world yet.
You can select more than one language by holding down [Ctrl] when clicking.
There is actually an ongoing discussion on GitHub about caching/proxy-ing image resources to improve performance and hide user IPs, etc.:
The user has been banned but those communities have not been deleted yet (for whatever reason).
The Hammering, indeed.
@ruud@lemmy.world Deleting those communities takes one SQL statement and hence less time than creating them, right?
It appears to be working now … did not change anything on my side … it just suddenly worked. … but everything is so painfully slow … and I also had at least one case where I was automatically logged out again after about 2 minutes …
I’m not hating it at all. Stuff like this just happens. Lemmy (the software) as well as this instance was pretty much overrun by a stampede of new users while trying to make its first baby steps. What would you expect?
Eveyrthing (UI) is extremely slow now. Not an improvement at all.
@ruud@lemmy.world Whatever you just did … was good! I’m noticing that (changes to) posts and comments are now pushed much faster than before.
@VioletteRei@lemmy.world Are you also noticing a difference?
Also, Captchas have just been merged to LemmyNet/lemmy:main ➡ https://github.com/LemmyNet/lemmy/pull/3289
And the first Relase Candidate 0.18.1-rc.1 has been tagged. 🙂
Well, it was fun while it lasted. The bubble is back. It’s like being diconnected from the rest of the fediverse …
… and merged to LemmyNet/lemmy:main 🙂
That’s pretty much what I yesterday called the lemmy.world bubble.
@ruud@lemmy.world Is there anything we/you could do about this until 0.18.1 is released with support for Captchas?
OK, then I just wait and stop using this account until such feature gets implemented. Deletion is not an option as it would also delete all posts/comments. At least local ones, maybe even posts/comments on other instances. Dunno, if the User/Delete Activity is propagated to other instances (yet).
Bye and Thanks for all your hard work!