ShittyKopper [they/them]

tbf Lemmy’s behavior is documented and standardized (https://codeberg.org/fediverse/fep/src/branch/main/fep/1b12/fep-1b12.md) it’s just that their fallback code for instances that don’t federate the Lemmy way also boosts the target posts for each update as opposed to just once on creation like you’d expect

5. Linux tech support

how many times did you edit that post per chance? Lemmy seems to boost edited posts for some odd reason

see https://brain.d.on-t.work/notes/9md8phwlkzlj0xe9 and https://brain.d.on-t.work/notes/9m1y542jlg8002bj for it happening on my misskey instance hacked together to support Lemmy federation

FYI misskey does not implement the masto api. some software like pleroma/akkoma, gotosocial and yes, a few misskey forks do (in various states of brokenness, with iceshrimp being the most compliant one) but misskey itself does not.

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

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

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

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

one of the misskey forks. imo “vanilla” misskey is lacking a fair bit of essential stuff (post editing being a giant one)

the most interesting ones to watch for now are iceshrimp (misskey v12 hardfork based on an early version of firefish, mainly focused on backend tech work compared to new features) and sharkey (misskey ”v13” softfork, aimed at qol changes and other feature work while keeping up to date with misskey itself)

akkoma is alright if you need something light on resources but I personally can’t get used to it’s interface

and mastodon is just… too bland in comparison to both

misskey and it’s forks (firefish, iceshrimp, sharkey, and the approx. million others) use a node/ts backend with a vue/ts frontend. peertube also uses node to the best of my knowledge.

that said:

• misskey itself is developed almost entirely in japanese so you probably won’t be able to help out too much.
• firefish in my experience is doing a LOT of questionable design decisions (hello scylladb migration!) so i’m not sure if it’s in a good shape right now
• iceshrimp is forked off from firefish and seems to be aiming to fix things up as opposed to introduce new features (their matrix chat has been really interesting to lurk in especially when it comes to database performance talk)
• on the other hand, sharkey follows the latest versions of misskey and has been adding a fair amount of useful features on top of it (post imports that actually work without sending notifications to everyone, message editing which misskey itself found too hard to do, etc.)

i can see why you may not want this but have you potentially considered rehosting/attaching any images from image posts in the bot’s replies? as lemmy doesn’t federate those properly just yet (https://github.com/LemmyNet/lemmy/pull/4035/commits/ecd8e3b11b5292bad73d48c2fbf11db00bc432c2 will fix it for posts originating in lemmy AFAIK) it’d make the bot quite a lot more useful and things like memes do tend to get boosted a lot more widely than links, though i can definitely see why it may feel a bit like freebooting (so, it could perhaps be a per-community option for non-OC-heavy communities?)