Defederating cuts off the whole instance. They just blocked those three piracy communities as far as I understand.

Remember that lemmy.world has to keep a copy of whatever content appears in a federated community on their servers, making them legally liable for the content. At least they just blocked the community instead of defederating.

A strength and a weakness. The strength, as you say, is being able to move to a different instance. However, the weakness is that Lemmy (the software) requires each instance to keep a copy of every federated post for its users to interact with. This means they have to host (and be legally liable for) data that they can’t police beyond blocking the community / instance.

It is fairly common among Catholics. I’ve known some fairly progressive Catholics who are Republicans because abortion. Now, that isn’t to say that a good number haven’t bought into the divisive rhetoric and gone full maga, but that’s not where they started.

It is a wedge issue that has locked a portion of the population who are single issue voters into being Republicans despite literally all their other beliefs. That is basically what all the non-financial planks of the Republican platform have in common.

Call me when you get past the “first step” where Reddit controlled NFTs somehow make communities independent from Reddit.

There is no point to linking communities- if they are going to have identical content, just pick one or the other.

A better option would be for cross posts (using the Lemmy cross post feature) to exist as a single entity that is visible in multiple communities. This would allow for some differences in moderation which is the justifiable reason for multiple communities on the same topic in the first place.

Huh, don’t know what that was about. Edited.

Somebody might be getting a nasty AWS bill at the end of the month.

Lemmy won, because Lemmy users numbered in the hundreds before the fiasco. The software is now growing by leaps and bounds.

Reddit may have won the battle, but not the war, and certainly not without casualties.

Are you logged in to the instance that hosts the sub? There is a known bug that some stuff doesn’t work for remote mods.

I think this is essentially the answer to OP - Cats understand the concept of feeding their family, and eventually figure out that the person is a pretty effective provider.

The fediverse is the name for services that use ActivityPub - a communication protocol. What you are saying is like saying “tech companies, banks and regulators need to crack down on http because there is CSAM on the web”.

As noted elsewhere, do everything you can to avoid handing your card to anyone.

Use tap to pay wherever possible, then chip - neither of those methods give the card number to the merchant. Do not swipe unless you absolutely have to, and then inspect what you are swiping to make sure nothing is attached to the card reader.

For online purchases, do everything you can to avoid giving your card number to anyone - use ApplePay / GooglePay / Amazon Pay / PayPal etc. wherever possible. These can be used to put charges on your card without giving your card # to the merchant. These are one-time authorizations (unless you explicitly identify it as a subscription / recurring charge), so they can’t reuse the transaction token they get.

Interesting - TIL. I wonder how Lemmy resolves the post #, since it is different between instances, and if it re-syncs comments when you do that. The post # thing is annoying, btw, because it makes it impossible to use relative links in posts/comments.

A better analogy is how Lemmy and Mastodon are theoretically compatible. Yeah, you can get federated content, but it really isn’t usable.

Kbin is just a different implementation of Lemmy, intended to be compatible (not coincidentally compatible through the protocol).

Kind of. My observed behavior of Lemmy, combined with comments from some developers (I haven’t read the code):

Post goes up on community hosted on instance A, Message goes out to B and C: “here’s a new post”

User x@B comments on post. Message goes from B to A saying “here’s a new comment”. A adds the comment, then sends a message to C “here’s a new comment”

User y@C upvotes the comment. Message goes from C to A, then A sends a message to C.

Each of those messages are confirmed by the recipient, and there are timed retries. However, there have been plenty of cases where one of those messages get lost, and the communities get out of sync. As I understand it, the message traffic is only changes. They don’t talk to each other to see what the current state of the content is. So whenever a sync break happens, it is permanent. New content/changes are fine, but stuff that gets lost in transit is lost for good.

I’m not sure ActivityPub is suitable for implementation of Lemmy/Kbin. ActivityPub seems to be a push (with retry) protocol, where if a message gets lost, the protocol doesn’t seem to have a means to recover synchronization. Theoretically, instances could verify synchronization on a periodic basis, but that would be a massive increase in traffic.

I can’t speak for the posting bots, but game day bots are pretty fundamental to sports communities - like, we have no shot at attracting any interest to our community if there aren’t game day bots. We’re literally running the same code as the reddit bots, just using the lemmy API. So that same traffic exists on Reddit, it is just that there is so much other traffic that they aren’t as prominent.

As a (hopefully good citizen) bot maintainer, the best advice I can give is to not follow active or new. Hot and top should not show bot posts unless they are being upvoted.