I think fedibird is a hard fork, so I guess it makes sense to count it separately compared to a soft fork like glitch or chuckya

I’m more surprised why there aren’t any misskey instances on the list. if fedibird is on there misskey should certainly be there

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

if you were to focus this on just Lemmy itself as opposed to the wider fedi (“Especially given that there was just an update allowing for individuals to block instances they don’t like” implies that’s the case) you already have nothing to worry about as you encountering a threads user here will be even slimmer than encountering a mastodon user.

threads is primarily targeting the microblog/personal side of fedi. the incentives and privacy expectations are quite different compared to this side of fedi

re active users: they’re a large open registration instance, they likely have a fair chunk of twitter people who joined during one of the many migrations and decided not to stick around.

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

well I just checked and while “sync contacts” did not turn itself on, “allow contacts to add me” did. there’s definitely something going on

.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

I personally find the development to be more “sensible”. firefish bungled up their flagship with a (imo) failed transition to scylladb and hasn’t been doing much of importance since then (they changed the boost icon to a rocket though!)

compared to that, iceshrimp rewrote their mastodon api compatibility layer to the point where it may be the most compliant one among misskey forks, uncovered several perf bottlenecks (one really big one related to word mutes since fedia migrated over), fixed the http signature security vuln ahead of firefish (and provided the patch to them, which they didn’t put in a stable release for something like two days even after merging)

quite a lot of firefish instances seem to be migrating over to sharkey for similar performance and stability reasons, but if you like the firefish UI/UX compared to the “classic” misskey one (or want a smoother migration path from firefish that doesn’t involve a major version bump) then iceshrimp is the one to check out imo