no

there is no “use case” here

not much beyond “look at what other apps you’re trying to interoperate with output and try to reverse engineer your way through”. reading through the sources of other apps may be a good idea.

some links that may get you started, picked from https://socialhub.activitypub.rocks/t/guide-for-new-activitypub-implementers/479 :

• https://flak.tedunangst.com/post/ActivityPub-as-it-has-been-understood
• https://www.w3.org/community/reports/socialcg/CG-FINAL-apwf-20240608/
• https://swicg.github.io/activitypub-http-signature/
• https://seb.jambor.dev/posts/understanding-activitypub/
• https://tinysubversions.com/notes/reading-activitypub/

and depending on which ecosystem you’re targeting:

• https://docs.joinmastodon.org/spec/activitypub/
• https://join-lemmy.org/docs/contributors/05-federation.html

counter intuitively, avoid reading the specs if you’re looking to federate with existing software. the official specs are… extremely lacking beyond giving you the bullets to shoot yourself in the foot with (half of what little it defines goes unused in the real world, important things like “how do i know this activity is sent by the person it claims to be” is completely undefined (hint: everyone has more or less settled on http signatures).

once you get something federating, you can then look in the specs in an attempt to learn the concepts in depth, but writing code following the specs will result in code that simply won’t federate.

this is what it feels like reading a post from a mastodon.social user except they have a character limit of like 2 so instead of separating the #hashtags they will #PutThemInline #LikeThis so you get an #aneurysm reading a post

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.

OP edited them out after posting for whatever reason

yup: https://akko.erincandescent.net/objects/478dec04-ea38-44b4-8b85-2336306f8fd5

A popular misconception is that Firefox runs Gecko. And while that is kinda true, the real problem is much more interesting when you come down to the technical details.

Because it’s the other way around. Firefox doesn’t run Gecko, Gecko runs Firefox. Firefox is built in Gecko. In a similar vein, Thunderbird also runs inside Gecko. It’s why they look so similar despite one being a browser and the other being an email client. Gecko is, in a way, a proto-Electron.

You cannot “rip off” Gecko from Firefox and embed it inside something like you can do with Blink/Chromium (unless you’re on Android and use GeckoView), which means the only way to have a “Firefox based browser” is to fork the entirety of Firefox. There are forks like the TBB or Librewolf that do this, but the embeddability of Chromium makes it much easier for devs to make something that diverges from Chromium in major ways (stuff like Qutebrowser, for example)