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:

 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

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 @[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

On est en train de finir notre #contribatelier : plusieurs dizaines de contributions à Common Voice et des discussions très sympathiques.

Rendez-vous au prochain le mercredi 13 novembre, on y explorera la fédération, @activitypub @mobilizon, @Mastodon, @peertube pour comprendre tout ça !

My #activitypub server is mostly coming along nicely but I'm having one problem with which I'd appreciate a little insight and help.

Right now I have this server (from which I'm writing now) operating in production, and I have a development version sitting behind a SSH tunnel from my public webhost. That version, like the production version, is proxied via nginx.

The problem is that for the development server only, much of the time servers from which I request public information complain that the server key I use to request most public data is "not found." This doesn't happen in production, and the code for this is identical to production, with the only system differences being that one is behind a tunnel and operating via a different domain name and server key.

Some relevant URLS, to make things concrete:

• webfinger
• [Profile](https://svadhi

I know it's not a new thing to write guides on ActivityPub, but I wanted to throw my own into the ring. Lists information, common questions, links to many different variations of software, the varying stances on Threads, and also apps available to those who like to be on they phones.

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?