My table of markdown editors has been put through the ringer, with a lot of changes and updates over the past six months. The latest additions include Kraa, Nota, Octarine, ZenNotes and VSCodium.

Among today’s links are markdown editors Markpad, ZenNotes, Memos and an update from Binderus. Plus there’s a quick look at Albireo, a flat-file CMS

#markdown #markdowneditors #opensource #Obsidian #ZenNotes #Memos #Binderus #Markpad #Notepad #Albireo

Has anyone else had this experience? I've checked that the post author is correct.

cross-posted from: https://lemmy.ml/post/42828264

I've recently made some updates to the ActivityPub Relay I maintain. This includes a regularly updated list of connected instances for monitoring their status and having an easy way to refer to instances for inquiry. I've also added a relay policy which states instances will be banned for featuring bigoted content or having poor admin/uptime.

I definitely have room for some more Mastodon, Misskey, and Pleroma instances.

The relay server itself is located in the east coast of the United States, but open to all regions.

ActivityPub Relay, US East: https://circlewithadot.net/services/aprelay.html

Follow on Mastodon for relay status updates and info: https://mastodon.circlewithadot.net/@cwad

I'm trying to find out where the development is at right now for ActivityPub, specifically about data (posts) portability, and persistent IDs.

For the former I think that's fairly self-explanatory, I'm just trying to get a flavour of if it's a priority, who's working on it, what the anticipated timeline is etc. It's a clear advantage that ATproto has, so are we trying to close the gap?

By the latter I mean is there work happening to work towards us being able to have one ID that can be used to log in to any fediverse network (as per nostr)? This approach makes so much sense to me - is it even possible?

The link here to W3.org doesn't seem that up to date - but I'm not that knowledgable so may have misinterpreted that site. So I'm looking for education on this subject 😊

My #LocalHistory website, @hoxsie.org, is now federating freely!

Happy to say that @activitypub solved a problem for me.

So if you're into random snippets of history about #Albany, #Schenectady, and #TroyNY, go ahead and give it a follow – it works!

#history #histodons #UpstateNewYork #UpstateNY

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:

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/

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 MessageQueues for incoming and outgoing activities.
• Fedify now allows you to manually route an Activity to the corresponding inbox listener. 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, @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.