no

there is no “use case” here

Like having some portals or borders which lead to the next server

you don’t need federation to do that though… the server could Just™ send a packet to the client to redirect it to another server. minecraft for example already has this functionality and nearly all “large” servers make use of it.

honestly all use cases people think of for federated (in the AP way) game servers just feel like an attempt to cram federation as a buzzword anywhere they can think of “because its the next best thing trust me”, similar to many other bubbles (NFTs, AI)

i don’t blame them honestly. there’s no real point to having activitypub federation in a game beyond silly experiments like this. (the low latency needs of a game would absolutely require a different protocol at the very least, even if federation made sense which i doubt)

yeah no i seriously don’t see how that one actually helps anything. maybe for the odd self hoster it could make sense but realistically it’s way too under-defined (but then that’s the norm for ap, sadly)

let’s say lemmy implemented it. ok. what now? my current account is still under lemmy.blahaj.zone. i still can’t move to some other instance without changing my account’s id and breaking all the existing object ids. i can move my posts between instances (or perhaps connect multiple instance software to the same actor, though a generic C2S server can in theory accomplish something of that sort without needing to alter other instances communicating with mine) but my identity is not any more portable than without it.

actor relative ids requires everyone to anticipate being portable and set their account up with it from the very start. maybe the existing account migrations can be used to one-time migrate a non-portable account to a portable one, but you’re still required to host your own account on your own “identity instance” yourself, and you are more or less stuck on that identity instance if it ever goes down without you sending the same account move activity we already have out. it’s not as simple as taking an account from one instance and moving it to another.

https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md is imo better at accomplishing the goal, and unlike relative URLs it has real existing implementations proving it’s viable in the first place. but it has it’s own downsides as well (severly limiting domain block effectiveness for authorized fetch enabled instances, no key rotation afaict, …)

as a side note, don’t get too hyped up by feps. they have no power over anything and an existence of one does not mean anything for the future of the protocol. implementations are still the only ones making the final call on how the protocol actually functions (because real governance and “spec compliance” is anywhere between doesn’t exist and being actively hijacked by threads via swf), and the only implementation that actually matters in terms of protocol improvements is mastodon.