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 a

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 a

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 a

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 a

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 @[email protected], [@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 ava

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 @[email protected], [@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 ava

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 @[email protected], [@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 ava

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 @[email protected], [@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 ava

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 us

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 us

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]!