Yes, but what if someone just creates a new instance and adds previous accounts. How do other instances know that the running instance has changed and didn’t just go offline if it’s registered on the original domain?

I feel like this could be abused by a bad actor by recreating instances in several ways:

1. Use the “dead” accounts that are still mods on communities on other instances.
2. Sneakily monitor user behavior (like votes etc.) without looking out of place.
3. Impersonate users.

I feel like it would be a good idea to start a list of the domains of dead instances and add them to a blocklist until the original people start using them again.

there’s no way of knowing for sure if it will be deleted from other instances

You can’t be sure if something is deleted, because there is no way to prove you don’t have something.

However, if you just want to check if the instance claims to have deleted something, you could probably just perform a GET request for the specific object as defined in the activitypub spec.

How can you verify you don’t have something?

Do you mean verification to prove something is deleted?

Have you asked the admins/mods of lemmy.world about this before posting this?

1. Onboarding
2. It lacks the critical mass to accumulate more users
3. Account migration / excessive defederation

I get what you mean but I don’t really think that applies here. He’s arguing that Rust is worse than Go because Gopher is better than Ferris, it really isn’t that serious.

Circular references and objects shared by multiple scopes (e.g. a lambda that uses the value of an UI element) are still quite annoying to work with and require a lot of boilerplate code because it requires wrapping it with a Rc and RefCell. None of this requires any additional effort when using a GC language like Kotlin or C#.

I have used Rust to write GTK applications but it wasn’t pretty and I ended up using GTKSharp in the end.