Hey everyone! I'm excited to introduce [BotKit], a new framework specifically designed for creating standalone ActivityPub bots. What makes BotKit different from typical Mastodon bot approaches is that it creates fully independent ActivityPub servers. This means your bots aren't constrained by platform-specific limitations like character limits or attachment restrictions. Each bot is a complete ActivityPub server in itself. The API is designed to be extremely straightforward. You can create a complete bot in a single TypeScript file, with intuitive event handlers for follows, mentions, replies, and more. Here's a quick example: ```typescript const bot = createBot<void>({ username: "mybot", name: "My Bot", summary: text`A bot powered by BotKit.`, kv: new MemoryKvStore(), queue: new InProcessMessageQueue(), }); bot.onMention = async (session, message) => { await message.reply(text`Hi, ${message.actor}!`); }; ``` BotKit currently supports Deno, with plans to add Node.js and Bun support in future releases. It leverages all the federation capabilities of [Fedify] but abstracts away the complexity, letting you focus purely on your bot's behavior. The framework is still in early development, but we'd love to hear your thoughts and feedback. Feel free to try it out and let us know what kind of bots you build with it! - Repository: https://github.com/dahlia/botkit - Documentation: https://botkit.fedify.dev/ [BotKit]: https://botkit.fedify.dev/ [Fedify]: https://fedify.dev/

Reading the spec, I can't see why not, wondering if anyone knew.

The version 1.3.0 of Fedify, an ActivityPub server framework, released! The key changes include: - [Instrumented spans for OpenTelemetry] are added. In most cases, it's automatically enabled if your application configured [OpenTelemetry SDK]. - Since Fedify 1.3.0, you can configure different [`MessageQueue`]s for incoming and outgoing activities. - [Fedify now allows you to manually route an `Activity` to the corresponding inbox listener.][1] It is useful for invoking an inbox listener for an `Activity` enclosed by another `Activity`. - `Context.sendActivity()` and `InboxContext.forwardActivity()` methods now reject when they fail to enqueue the task. - Thanks to [@robin_maki@planet.moe](https://planet.moe/@robin_maki), [@fedify/fedify/x/sveltekit] module is added for integrating with [SvelteKit] hook. - Fedify now makes HTTP requests with the proper `User-Agent` header, e.g., `User-Agent: Fedify/1.3.0 (Deno/2.1.2)`. For details, see the [full changelog] as well! Fedify 1.3.0 is available at [JSR] and [npm]. [Instrumented spans for OpenTelemetry]: https://fedify.dev/manual/opentelemetry [OpenTelemetry SDK]: https://opentelemetry.io/docs/languages/js/ [`MessageQueue`]: https://jsr.io/@fedify/fedify@1.3.0/doc/federation/~/MessageQueue [1]: https://fedify.dev/manual/inbox#manual-routing [@fedify/fedify/x/sveltekit]: https://fedify.dev/manual/integration#sveltekit [SvelteKit]: https://kit.svelte.dev/ [full changelog]: https://github.com/dahlia/fedify/releases/tag/1.3.0 [JSR]: https://jsr.io/@fedify/fedify@1.3.0 [npm]: https://www.npmjs.com/package/@fedify/fedify/v/1.3.0

cross-posted from: https://lemmy.ml/post/21657544 > Finally, [Hollo 0.1.0] released! Hollo is a single-user federated microblogging software which is ActivityPub-enabled and powered by Fedify. > > Hollo has the most of features that Mastodon has except for moderation tools, and also include: > > - CommonMark (a.k.a. Markdown) and up to 4,096 characters per post > - Misskey-style quotes (compatible with Misskey, Akkoma, Fedibird, etc) > - Misskey-style emoji reactions (both Unicode emojis and custom emojis are supported; compatible with Misskey, Akkoma, kmyblue, etc) > - Generally much relaxed limitations (more poll options, more attachments, and so on) > - … and [many more][1]! > > If you're interested in Hollo, please give it a try! There are several ways to install it: using [Railway], using [Docker] (and Docker Compose), or [manually]. > > If you're already using Hollo, please upgrade it to v0.1.0: > > - To Railway users: [Just redeploy the Hollo service][2]! > - To Docker users: Switch your Hollo image to [`ghcr.io/dahlia/hollo:0.1.0`] or simply [`latest`]! > - To manual installers: Fetch the [`stable` branch] and switch over to it! > > [Hollo 0.1.0]: https://github.com/dahlia/hollo/releases/tag/0.1.0 > [1]: https://docs.hollo.social/intro/ > [Railway]: https://docs.hollo.social/install/railway/ > [Docker]: https://docs.hollo.social/install/docker/ > [manually]: https://docs.hollo.social/install/manual/ > [2]: https://docs.hollo.social/install/railway/#upgrading > [`ghcr.io/dahlia/hollo:0.1.0`]: https://github.com/dahlia/hollo/pkgs/container/hollo/292999204?tag=0.1.0 > [`latest`]: https://github.com/dahlia/hollo/pkgs/container/hollo/292999204?tag=latest > [`stable` branch]: https://github.com/dahlia/hollo/tree/stable

I'm an old redditor that left the platform for Lemmy. I have been using Sync and using lemm.ee. I have heard so much about activity pub and simply don't understand how to use it. Do you use a browser to visit another website that is like a Lemmy instance? Is there an Android app that connects a bunch of instances like pixelated and Lemmy instances together? Or is Sync able to do all this but there is a setting I need to do. Can someone please help shed some light to this? Thank you.

publicado de forma cruzada desde: https://lazysoci.al/post/12745625 > Looks like it's really happening!

Is it possible to get a list of all the users/accounts that liked(or disliked) a particular post or comment?

Hello everyone! Recently I have removed a couple of bot users from my Lemmy instance via DB query (I removed them from `person` table). Those bots were subscribing to hundreds of communities on other instances which I don't really want to spend resources on fetching new posts and updates. I have purged those communities from my instance but they keep reappearing. As far as I can tell, this happens because other instances still "think" that users from my instance (bots, which don't exist already) are still subscribed, and therefore send updates to my instance. How can I completely get rid of those communities?

Hello. Is it planned to make up and downvotes of posts non public by default? Right now everyone can see which posts a certain user up- or downvoted. Which can be problematic. Regards

> The new standalone app will be based on Instagram and integrate with **ActivityPub**

Is it store and forward system, when a server/instance is down - I assume? Curious how comment from A reply from B reply from C Works if A never gets the message from the user on instance B due to an Internet connection problems...

cross-posted from: https://lemmy.ml/post/952618 > Fediverse is going mainstream fast. And it is going to be a corporate hellhole if the grassroots initiatives that drove it to its current success are losing their grip on evolution in proper direction: Humane tech that is to the benefit of the people andd society, free culture thriving. > > While corporate threads are looming, meanwhile the activated developer community is once again splintering, fragmenting initiatives appearing that dilute attention to focus on common efforts, cohesion, cross-pollination and collaboration. The "herding cats" problem of grassroots movements. > > Great opportunity is now. Cohesion means that initiatives remain independent, but take care to coordinate with what is going on elsewhere. > > 👉 You can help! Avoid a CorporaVerse where you are exploited and milked. Bring attention to the opportunity and participate in the related initiatives to help bring them closer together. You might also boost my [related toot](https://social.coop/@dansup@mastodon.social/110195527051725892#).

cross-posted from: https://lemmy.ml/post/639707 > The Fediverse going mainstream is ablaze with new developer activities. Many new projects are starting. I am co-maintaining 3 lists, part of the [delightful project](https://codeberg.org/teaserbot-labs/delightful) (this is similar to Github Awesome lists, but only for FOSS, Open Data and Open Science, and without sponsored ads) and can need your help to keep the lists up-to-date. > > Find a new project or an entry that needs updating? Please PR to one of the following repositories: > > - https://codeberg.org/fediverse/delightful-fediverse-apps > - https://codeberg.org/fediverse/delightful-fediverse-clients > - https://codeberg.org/fediverse/delightful-activitypub-development > > The apps and ActivityPub resources from these lists will be hand-picked for inclusion in [Fediverse Party](https://fediverse.party) website. And the lists are auto-compiled into the [Delightful Club](https://delightful.club) website. > > If you want to become part of the Delightful Club and maintain a sub-list on a subject of your choice, then [file an issue](https://codeberg.org/teaserbot-labs/delightful/issues) to the top-level ist.