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)

Simply by choosing a lesser used fedi software you’re helping keep the fediverse from being dictated by a single software’s whims. So that’s a big plus there. Federation issues with kbin/mbin/azorius/other lesser used instance software will inevitably happen as people only test against the largest player in the field (in the ““threadiverse”” that’s Lemmy, in the microblogging fedi that’s Mastodon). So simply by not picking the largest you’re, even if in a small way, helping not only mbin but all the lesser used fedi software as a whole.

Your own local communities being “dead” mainly boils down to communities themselves having a network effect around them where the largest one keeps growing larger as everyone focuses on it. And the largest communities are usually on lemmy.world (or occasionally other Lemmy instances). There isn’t that much you can do there.

In my experience, it’s always the smaller software that innovate. The same is true in the microblogging fedi (emoji reactions, quote posts, markdown, nomadic identity, reply permissions) just as it’s true in the ““threadiverse”” (combining communities together, the ability to follow people, polls apparently (?)).

So really, don’t worry about the size of your own instance’s communities. As long as you trust your instance’s staff to keep you safe there’s no real reason not to get on a smaller instance, or on different software. Especially on here, where “discoverability” is not as much of an issue as it is in the microblogging fedi.

ah, gotcha. this instance is still on 0.18 so that’s why my tests didn’t work out. I’ll edit that part out

you can disable the webpage and unauthorized API if you so choose. mastodon and pleroma/akkoma provide these settings. gotosocial hides all posts with an unlisted visibility from public pages.

authorized fetch only provides protection for activitypub, it’s just a single component of a layered stack of protection you can enable depending on your exact threat model.

the privacy threat model of Lemmy is significantly different from a microblog, which is the current target of threads.

(also have none of you heard of consent?)

cc @FaceDeer@kbin.social this reply also applies to your reply

no, not really.

i have attempted to build my own federated stuff (none of them actually federated “in real life” though) so i did read the specs but quite a lot of these are from my memory and if there’s anything i know is that my memory fuckin sucks lol

Which could still be millions?

sharedInbox handles this.

mastodon.social sends a single federation activity to www.threads.net’s sharedInbox. threads’s internal systems handle all the visibility and routing to followed users and whatnot. the same thing happens in the opposite direction for threads->mastodon (or whoever).

now in theory this is an optional part of the specification and you can in fact send one activity per person if you really want to, but considering how widespread it is (and how relatively easy it is to implement) you’d have to be intentionally and explicitly malicious to not use a sharedInbox if the remote server indicates it supports it.

just want to clarify something:

However, the way that activitypub works, the outgoing data is publicly available. Defederating with Meta doesn’t prevent that,

there is a technical solution to this in the form of authorized fetch: https://hub.sunny.garden/2023/06/28/what-does-authorized_fetch-actually-do/

mastodon implements it, pleroma/akkoma probably implements it, pixelfed implements it, firefish and iceshrimp implement it (sharkey has a PR implementing it opened just today), gotosocial not only implements it but enforces it, with no ability to turn it off

notably, none of the threadiverse software implement it, and no software other than the aforementioned gotosocial enable it by default.

they will have an excuse to do it openly instead of trying to do it secretly and inevitably getting caught

how will this deal with communities and instances having different rules and “culture” of their own?

oh, and which community’s moderators are going to have permission to moderate the comments section?

I have not seen a clear answer to either of these questions on any variation of this proposal. do y’all see every community as the same thing with a different domain at the end?

there was a fdroid client that did something similar using mastodon and hashtags but I can’t remember which one it was and if it’s still doing that

so, are you paying for it?

git commit -m $(date)

I’m mildly worried I know (as in, am aware of their existence, thankfully not having interacted with them) who you’re talking about

I didn’t tested non-followed community, but the bot works with mention event instead of comment. But still not sure, I’ll test this one 🙏

oh, I meant for the actual post watching part, summoning via mention should work without any subscription

in theory as you operate both the server and the bot you could modify lemmy to tell the bot when a new comment hits a thread instead of polling, which would be more efficient (but definitely harder to do!)

also does it handle the case where nobody from your instance is following a community? to make sure you get all the replies reliably the bot would need to subscribe to each community it’s watching a post from

that said, great work. I may end up using it if I don’t end up forgetting about its existence :p

.world is a newer gTLD whereas .ml is a more well known country code TLD. whatever auto linking code the lemmy UI uses likely just isn’t up to date with all these comparatively recent TLDs

https://fedidb.org/software/iceshrimp is a thing, and there are several general purpose instances such as fedia.social and iceshrimp.social (which isn’t anything official despite the name)

not having an (open) flagship is, to the best of my knowledge, an intentional choice as moderating it would take time away from development