Interesting! We’ve had quite a noticeable spike of sign-ups on lemm.ee as well

Hey! I’m not really sure about this at the moment. I can tell you that if the authors (or any legal entity) would contact me about this and ask for links to be removed, then I would comply, rather than try to fight it.

I think it’s not really on your side, most likely either just something wrong on kbin.social itself, OR a side-effect of the measures lemmy.world implemented against kbin.social recently.

They are basically local-only communities on lemmy.world at this point, unfortunately. There is no federation to any other instance for any lemmy.world user posts on those communities.

Maybe this community is a good target for that? Let me know your thoughts.

FWIW I know some users often check their local announcement/support communities through other instances during downtime, so it can actually be quite nice to have such communities federated to other instances.

It’s not really a bug, it’s just a case where app developers need to update their code to support a small change in the Lemmy API. More details here: https://lemm.ee/post/34259050/12479585

Regarding your question:

Lemmy federation basically works by copying stuff from their source instance to all other federated instances. So if I write a comment on lemm.ee, other federated instances will get their own copy of my comment. They will also all know that the “authority” for this comment is lemm.ee.

If an admin on another instance decides to delete their local copy of my comment on lemm.ee, then they are always free to do so (for example, some instances might want to moderate more strictly), but any actions they take like this are limited to their own instance - for the rest of Lemmy, lemm.ee remains the authority for this comment, so individual remote instance admins taking actions won’t have any effect on any other instances.

As for the original topic of modlog federation, basically it just boils down to this: just like with the comment example above, Lemmy instances also save a local copy of incoming federated mod logs. The Lemmy software does not yet have 100% coverage in terms of federating mod logs (for example, there are no federated logs yet for instance admins banning remote users), but this coverage has been increasing, and I expect this will eventually get to 100% (just needs more dev time really).

Also, if some instance admins try to tamper with their mod logs, then other instances can still see the real history, because there is no way for an instance admin to delete copies of their mod log from other instances.

Banning a local user from a local community does actually federate already

Most actions federate, any exceptions which aren’t federated yet are generally just there because the federation logic has not been implemented (but improvements are constantly being worked on).

Generally federating the modlog is mostly just there for informative purposes. As in, we can check what mod actions were taken on instance A through the modlog on instance B (and there is no mechanism in Lemmy for other instances to retroactively remove or hide federated modlog items, btw).

It’s the first option in the dropdown:

Big thanks to all maintainers and contributors!

I’m already accustomed to the light theme of Lemmy and can’t find how to switch from dark to light in “Next.”

This is planned after the 3rd milestone is complete!

The red, green, and blue buttons in the footer seem to do nothing.

They should change the primary color in the UI - are you sure it’s not doing this for you? Maybe it’s just enough of a subtle change that it’s not immediately noticable?

The notion on every post that “Your IP is hidden from another Lemmy instance” is kind of annoying and useless. Why is it there?

Most (all) other Lemmy frontends will always leak your IP to external media hosts, I wanted to handle this a bit differently in lemmy-ui-next by proxying by default (to improve user privacy). The message is there to let you know if a specific piece of media is being proxied or not - and the only way for something to not be proxied is for the user to manually approve it first.

I guess not all users will care about this, so maybe I can add a setting to hide the proxy indicator completely… I will think about it!

I dislike a little that it tries to copy the old Reddit interface. Although that interface wasn’t bad, and I’m the one who would first say “don’t fix what isn’t broken,” I’m more prone to seeing something new, some experimentation. Right now it feels more like “next to the old Reddit,” which isn’t exactly bad, but still…

It was an initial goal and guiding principle to heavily take inspiration from the great UIs of existing link aggregators like old reddit and hackernews. At the same time, I realize that this approach is not for everyone, so I am not against adding some different layouts (especially for the post list view) in the future.

Thank you for all the feedback!

This is planned after the 3rd milestone is complete!

Interesting idea, I think that will also require a small change in the Lemmy backend, but I think it’s doable. Thanks!

You can check the federated/defederated instances for any instance on the /instances page. For example:

https://sh.itjust.works/instances

https://beehaw.org/instances

deleted by creator

deleted by creator

deleted by creator

That’s true, it will only show content which has been federated to lemm.ee, so indeed if you want to search for more content than is available on your instance, you would need some additional tools for that.

I’m a simple man:

“What day is it?” asked Pooh.

“It’s today,” squeaked Piglet.

“My favorite day,” said Pooh.