#fedidev

If you update an account profile in the fediverse, who should you send the Update(Person) activity to?

#ActivityPub #fedidev

Developer question: If you build a minimal ActivityPub server for development purposes, do you have to run it on a registered domain with an SSL certificate for it to be able to connect to anything else (like a big Mastodon instance)?

Or is running it on some kind of dynDNS or ngrok type service (so it has a static domain name) enough just to test things out?

(Boosts for reach gratefully received 🙏)

#ActivityPub #FediDev #Fediverse #MastoDev

If you'd like to support the development of @fedify or @hollo, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

#fedidev

Starter Kit situation: After a few bad attempts using new frameworks, I decided to go back to basics (php, html) and build the skeleton with all the backend logic so I can easily style it all later.

My goal is to get the MVP shipped before bed (its only 12am) and style it over the weekend.

I love side quests like these after a long and stressful week, something quick and impactful to help me get back on track.

#fediDev #apska #starterKits

I have a question about signature handling in #ActivityPub relays. As I understand it, relays forward activities between instances that aren't directly connected. Let's say we have this flow: foo.com (source) → bar.com (relay) → baz.com (destination). The activity created by foo.com includes HTTP Signatures, but when bar.com forwards it to baz.com, wouldn't the original signature become invalid since the Host header needs to change? How do relay implementations handle this issue?

#fedidev

Have you heard of Val Town? Val Town is a kind of code pastebin + serverless function.

Actually, #Fedify works just fine with Val Town. Here's a piece of ActivityPub software, implemented in about 170 lines of code, running on Val Town. Of course, it's built with Fedify!

Give it a follow @demo, and it will follow you back.

Curious to see how it was implemented? Check out the source code!

https://www.val.town/v/minhee/FedifyOnValTown

#ActivityPub #fedidev

We've added the build guide to the CONTRIBUTING.md docs in the #Fedify repository. We hope this is helpful for those who want to contribute to Fedify!

https://github.com/dahlia/fedify/blob/main/CONTRIBUTING.md#build

#fedidev

What are your thoughts on Fedify's docs?

#Fedify #ActivityPub #fedidev

Visualize your server in the fediverse with the fedify node command and share it with us using the #FedifyNode hashtag!

(See also how to install the fedify command.)

#ActivityPub #fedidev

The version 1.2.0 of #Fedify, an #ActivityPub server framework, released! The key changes include:

• Added InboxContext.recipient property. It's useful for determining whether it is a shared inbox or a personal inbox, and whose personal inbox is invoked.

• Added getNodeInfo() function, a NodeInfo client.

• Added followedMessage property, which corresponds to _misskey_followedMessage, to Actor type in Activity Vocabulary API.

• Log messages now can be traced using LogTape's implicit contexts, which means you can filter log messages by requestId (an HTTP request identifier) or messageId (a background task identifier).

• Now you can choose an AMQP driver (which supports RabbitMQ) for the message queue in the fedify init command.

• Added the fedify node subcommand, which fetches the given instance's NodeInfo document and visualizes it in neofetch-style.

For details, see the full changelog as well!

Fedify 1.2.0 is available at JSR and npm.

#fedidev

It's been a busy year at Newsmast for The Newsmast Foundation team, but we've done a lot!

We've actually done too much to fit it into one post 👀

So, we broke out the video editing skills... hope you like it!

#Fediverse #Mastodon #SocialWeb #FediDev #SocialMedia #BuildInPublic

Starting with the next release of #Fedify, v1.2.0, we will support traceable logs for easier debugging. Fedify's traceable logs are implemented using the implicit contexts introduced in LogTape 0.7.0, and most of the logs that Fedify records are given a requestId or messageId. This means that logs can be grouped into requests or background tasks for better analysis.

Want to try it out in advance? Try Fedify v1.2.0-dev.468+2e17cd69 (JSR & npm)!

#fedidev #ActivityPub

In #Misskey, does the icon for the server information that I see in the remote note come from the favicon for that server?

#fedidev #ActivityPub

Alright, #FetchAllReplies , backend edition is open as a PR against upstream masto: https://github.com/mastodon/mastodon/pull/32615

Please roast me for my code and help me get it into a state where we can make this default behavior for masto instances and remove one of the biggest contributors to the reply guy problem on the fedi <3

#MastoDev #FediDev

#FediDev: What’s the point of having separate signing keys for each actor if they all end up getting managed by the same instance?

Ideally (“even if no fedi client does it atm”), should users hold keys in their client, and sign the posts on the local machine before passing them to their server to forward to the recipients?

Or am I missing something?

The version 1.1.0 of #Fedify, an #ActivityPub server framework, released! The key changes include:

• Added uility functions for traversing remote collections. See also the Traversing remote collections section in the docs.

• Added EmojiReact class to Activity Vocabulary API. [FEP-c0e0]

• Added successor property to the Actor types in the Activity Vocabulary API.

• Added DidService class to Activity Vocabulary API. [FEP-9091]

• Added Export class to Activity Vocabulary API. [FEP-9091]

• Added service property to the Actor types in the Activity Vocabulary API. [FEP-9091]

• The default time window for verifying HTTP Signatures of incoming requests is now an hour (was a minute). This new default window is according to the ActivityPub and HTTP Signatures document.

• In the fedify inbox command's web interface, the Raw Activity tab is added to show the raw JSON object of the received activity.

For details, see the full changelog as well!

#fedidev

A summary of the two existing emoji reaction APIs: the Pleroma/Akkoma family and the Fedibird/kmyblue family.

https://github.com/cheeaun/phanpy/issues/598#issuecomment-2423923528

#fedidev

The value of the form at://… in the alsoKnownAs property of the actor generated by @bsky.brid.gy is not actually a valid URL? It cannot be represented as a URL object in Node.js or Deno.

#ActivityPub #fedidev

#ClubsAll (a threadiverse/lemmy/mbin/piefed web frontend project) want to open source it and are looking for someone to do a code review/security analysis first... Are you into security and the fediverse *and* stuff being open source? Then respond here!

found via this post [https://lemmy.world/post/20828200] on Lemmy by ClubsAll dev @vinay_clubsall

#fediverse #infosec #fedidev #floss
https://clubsall.com

#Fedify now has an #AMQP driver! This means you can use #RabbitMQ as Fedify's message queue. To use it, first install the @fedify/amqp package, then set it up like below:

import { createFederation } from "@fedify/fedify";
import { AmqpMessageQueue } from "@fedify/amqp";
import { connect } from "amqplib";

const federation = createFederation({
  queue: new AmqpMessageQueue(await connect("amqp://localhost")),
  // ... other configurations
});

Oh, and we've also added results from AmqpMessageQueue to our benchmarks.

#fedidev

Write.as announces an integration with sub.club, a way to offer premium content in the fediverse to subscribers.

https://write.as/blog/write-as-x-sub-club

#Fediverse #FediDev

Even though I am a slow coder, it only took me about a month to create most of #Hollo's features in #Fedify. Having a framework makes a huge difference in productivity.

#fedidev

Hamabē is born!

I just released the very first version of Hamabē, and the official demo instance went live!

Hamabē is a successor of Audon, but a new platform speaking ActivityPub and independent of Mastodon API.

You can follow Hamabē accounts from AP platforms and can receive notifications when a space starts (if your platform supports Event activity)

Right now Hamabē only has voice chat (along with simple text chat) to cover Audon's use cases, but there's a plan to add text-based group chat later.

I also created Matrix Space for general discussion. Comments and suggestions are very appreciated!

The documentation is not ready yet. I'd write deployment guide soon.

If you wanna give it a shot, you can create your account here: https://try.hamabe.space

(Disclaimer) Hamabē is still in the very early stage of development. Expect a lot of bugs!

Thank you and happy chatting

#hamabe #audon #fedidev

According to the Activity Vocabulary specification, the summary property should be HTML encoded, but #Mastodon is putting plain text in the summary property. #Hollo is putting #HTML in the summary, but should I change Hollo's behavior?

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-summary

#ActivityPub #fedidev

Looks like around a month ago, the developer of Kaiteki, a flutter based fediverse client, closed shop. They left the source code available to anyone that might want to pick it up, however!

https://activitypub.software/TransFem-org/Kaiteki/kaiteki

#FediDev #FediApp

Yay! Another music platform adding support for the fediverse. 🎶🎶

https://mastodon.moule.world/@MOULE/113248290568082105

#Fediverse #Music #FediDev

If you're an advanced user with programming skills who is wanting to do custom stuff with Fediverse connections (or even wanting to create your own Fedi platform), you might want to check out the activitypub.rocks SocialHub forum:

https://socialhub.activitypub.rocks

I'm not a software developer so I can't help with these topics, but enough people have asked that it seemed a good idea to give the forum a mention!

#ActivityPub #Fediverse #FediDev

If you're considering creating your own implementation of #ActivityPub, consider #Fedify.

Implementing ActivityPub from scratch requires more than you might think. WebFinger, HTTP Signatures, Linked Data Signatures, Object Integrity Proofs, NodeInfo, queues for sending and receiving activities, followers collection synchronization, remote object lookups, interoperability with Mastodon, Akkoma, Misskey, Threads, and more…

Just use Fedify and feel free to create your own ActivityPub implementation!

#fedidev

https://fedify.dev/

独自のActivityPubの実装を作りたい方は、Fedifyを検討してみてください。

ActivityPubをゼロから実装するには、想像以上に多くの物を作る必要が有ります。WebFinger、HTTP Signatures、Linked Data Signatures、Object Integrity Proofs、NodeInfo、アクティビティの送受信のキュー、フォロワーコレクションのシンクロ、リモートオブジェクトの照会、MastodonやMisskey等との相互運用性の為の雑多な処理まで…Fedifyを使えば簡単に自分だけのActivityPubの実装を作る事が出来ます！

https://fedify.dev/

#Fedify #ActivityPub #fedidev

Adding vocabularies for FEP-9091 to #Fedify.

https://github.com/dahlia/fedify/issues/146

#fedidev #ActivityPub

Did you know that? The #Fedify CLI has a command called fedify lookup, which can easily look up ActivityStreams objects on servers with authorized fetch (a.k.a. secure mode) enabled by turning on the -a/--authorized-fetch flag.

Here's demo!

#fedidev #ActivityPub

You can now see #emoji #reactions in #Hollo (but you can't leave emoji reactions yet). We've implemented the FEP-c0e0 spec and tested it on #Misskey, #Akkoma, and #Fedibird.

#ActivityPub #fedidev

Introducing Fedify: Build Your Own Fediverse App with Ease! 🚀

Are you excited about the #fediverse but find implementing #ActivityPub daunting? Meet #Fedify, a #TypeScript framework that simplifies building federated server apps. Whether you're creating the next Mastodon, Pixelfed, or something entirely new, Fedify has you covered.

#fedidev

What Fedify Offers:

• 🧩 Type-safe Activity Vocabulary objects
• 🔍 WebFinger client and server
• 🔐 HTTP Signatures, Linked Data Signatures, and Object Integrity Proofs
• 📨 Easy-to-use inbox listeners
• ℹ️ NodeInfo protocol support
• 🛠 CLI tools for testing and debugging

Fedify abstracts away the complexities of ActivityPub, letting you focus on your app's unique features. It's designed to work seamlessly with popular web frameworks like Hono, Express, and Fresh.

Get Started Today!

Check out our step-by-step tutorial to create a microblog: https://fedify.dev/tutorial/microblog

Explore the discussions, contribute, or just star us on GitHub: https://github.com/dahlia/fedify

Join the Fedify community! Questions? Ideas? Find us on Matrix: #fedify:matrix.org.

Let's build a more diverse and interoperable fediverse together with Fedify!

I'm adding the #EmojiReact (FEP-c0e0) class to #Fedify… It will be coming in Fedify 1.1.0.

https://w3id.org/fep/c0e

#ActivityPub #fedidev

Today is #InternationalPodcastDay so we thought we'd shout out https://truefans.fm - a podcast marketplace built on the Fediverse by @samsethi

It was really exciting seeing Sam's demo of True Fans at @fediforum a few weeks ago.

If you're looking for a podcasting alternative on the Fediverse, check it out!

#Fediverse #Mastodon #Podcast #TrueFans #FediDev

Oh gr8, apparently being able to await the results of a batch of sidekiq jobs is an exclusive "sidekiq pro" feature.

So here's the deal: for #FetchAllReplies we need to set some kind of global fetch limit so a maliciously crafted thread tree doesn't keep us fetching forever. Currently it's implemented as a recursive fetch, but I want to move the "expansion" part where we gather the URIs of all the posts to fetch at a top level, and then just dispatch workers to fetch those posts in a flat queue with a global limit

Problem: with current masto impl, you have to already have a status to fetch its replies, so we need to await the results of prior fetch level before starting the next one. Does anyone know how to await sidekiq jobs? We already know the URIs of the posts that are being fetched, but I can't tell how to either a) await the redis job being popped from the queue or b) await a Status object with a matching uri being created. Im also not sure how I could c) use a callback to signal to the initiating worker that a status has been fetched.

Anyone know what the move here is? Im sure there must be some chained workers like this somewhere in masto, but all the examples I can find for sidekiq use the "pro" features.

PR here shows the current recursion I'm trying to flatten: https://github.com/NeuromatchAcademy/mastodon/pull/44

#MastoDev #FediDev

Fedify, an ActivityPub framework, has finally released its first stable version, 1.0.0! Here are key changes:

Deprecation of the term handle

From this version, the term handle across Fedify will only be used to refer to fediverse handles (e.g., @[email protected]). An actor's internal unique ID (e.g., b379dbdc-3b4f-4ef4-88c2-fc25632d1c22) is referred to as an identifier, and the WebFinger name (e.g., hongminhee) is referred to as a username.

The term handle in the API will be maintained for a while for backward compatibility, but deprecation warnings will be logged, and it is planned to be removed in the future.

For more details, please refer to the related documentation.

Linked Data Signatures

Linked Data Signatures is an outdated standard, but it's still relied upon by major fediverse implementations such as Mastodon.

In addition to HTTP Signatures and Object Integrity Proofs, Fedify now supports Linked Data Signatures from this version, thus supporting all types of signature methods used in the fediverse. This makes Fedify an ActivityPub implementation with the best interoperability.

However, Fedify users don't need to do anything special to use Linked Data Signatures. If an incoming activity has Linked Data Signatures, it automatically verifies the signature, and all outgoing activities will have signatures in three formats: HTTP Signatures, Linked Data Signatures, and Object Integrity Proofs.

For more details, please refer to the related documentation.

Activity forwarding

From this version, you can forward activities received in the inbox to other actors using the InboxContext.forwardActivity() method.

At first glance, you might think that you could just resend an activity received in the inbox using the Context.sendActivity() method. However, if you do this, the original signature is removed before the activity is delivered to the inbox, and when sending it, the signature of the forwarding actor is attached instead, causing the receiving side of the forwarded activity to not trust it.

On the other hand, when using the InboxContext.forwardActivity() method, the activity is forwarded with the original signature preserved, avoiding this problem. (Of course, the original activity itself must be signed with Linked Data Signatures or Object Integrity Proofs.)

For more details, please refer to the related documentation.

Sending Delete(Application) on fedify inbox termination

From this version, fedify inbox will send a Delete(Application) activity to all peer servers it encountered when terminated. This is typically an activity sent when deleting an account, which will help prevent residual data related to temporary actors from remaining on other servers.

PostgreSQL drivers

The @fedify/postgres package, which implements PostgreSQL drivers for the KvStore and MessageQueue interfaces, has been released alongside this version.

The PostgreSQL driver is a backend that can be sufficiently used in production, especially recommended for projects already using PostgreSQL.

Additionally, an option to select the PostgreSQL driver has been added to the fedify init command.

Celebrating Fedify 1.0.0

With the release of version 1.0.0, Fedify will now maintain API backward compatibility as much as possible. (Of course, in the long term, there may be a 2.0.0 that breaks backward compatibility.) This should be good news for those who have been hesitant to use Fedify because there hasn't been a stable version until now!

So, hoping that more services will support ActivityPub in the future, I conclude this post!

#Fedify #ActivityPub #fedidev

Looks like #Fedify v1.0.0 will be released this week! Is there anything you'd like to see added or fixed before then?

#fedidev #ActivityPub

I'm polishing the #docs and filling in the gaps before releasing #Fedify v1.0. Is there something else you'd like to see in the @fedify docs?

#fedidev #ActivityPub

The next version of #Fedify, v1.0, adds ParallelMessageQueue, which makes it easy to parallelize sending and receiving activities without increasing the number of processes or nodes.

It's available for preview in v1.0.0-dev.408+f4e245b4 (JSR & npm).

https://unstable.fedify.dev/manual/mq#parallel-message-processing

#ActivityPub #fedidev

We were very excited to demo Channel. org & Patchwork at the fourth edition of FediForum - the virtual unconference moving the decentralised social web forwards.

You can see the video here: https://spectra.video/w/42kMTHaxxqYwD6nYYeK1MZ or on YouTube (we'll add a link further down the thread).

Keep reading to see a summary of our time at @fediforum from @FreddieJ 🧵 👇

#FediForum #Mastodon #Fediverse #FediDev #FediAdmin #Technology #Demo #TechDemo

Q: Which does your #ActivityPub implementation implement, HTTP Signatures, Linked Data Signatures, or Object Integrity Proofs?

Fedify: Y·E·S!

#Fedify #fedidev

Fedifyの次のバージョンであるv1.0.0がリリースされれば、APIは安定化される予定です。APIが安定化する前に入れて欲しい機能は何か有りますか？

#Fedify #fedidev #ActivityPub
QT: https://hollo.social/@fedify/019208ce-cf81-717e-9239-6757a5494510 [参照]

Once the next version of #Fedify, v1.0.0, is released, the API will be stabilized. Are there any features you'd like to see before the API is stabilized?

#fedidev #ActivityPub

alright, after like a year of halfheartedly trying on and off, #FetchAllReplies is pretty much finished - the problem of not being able to see all replies to a post is one of the largest complaints that people have with mastodon in particular but also the fedi in general. It is an especially potent problem for smaller servers, making them feel lonely, and making the whole fedi seem quiet. It is also a large contributor to the 'reply guy' problem where a moderately popular post will get the same replies over and over again and people won't even know they're doing it.

This patch recursively fetches replies using activitypub collections. it does it respectfully, only when someone is explicitly looking at a post (rather than fetching all replies for everything all the time) with some debounce, and spaces out the recursive calls to the other servers in deep threads.

the only thing left is to make the posts get inserted into the web client as they are received, currently you need to refresh to see them.

trying it locally now and it is a game changer.

i'm not "good at ruby" so if you ever wanna see this upstream, kindly spare a code review?

https://github.com/NeuromatchAcademy/mastodon/pull/44

#FediDev #MastoDev #UnFuckTheFedi #PubSubIsCoolButPresentsPrettySeriousUsabilityProblems #JustSmallInstanceThings

I'm working on a Rust library for building ActivityPub apps:

https://codeberg.org/silverpill/mitra/src/branch/main/apx_sdk

This code was originally a part of Mitra, but over time I moved re-usable functions into independent packages and then started using them in other projects, Activity Connect and fep-ae97-client. Compared to activitypub-federation-rust, it is a low-level library with fewer dependencies, suitable for both servers and clients. The key feature is support for nomadic identity.

Currently there's no documentation and API is not well designed, but I will be improving it. The license is AGPL-3.0

#fedidev #fep_ef61

One of the benefits of #Fedify is that you don't have to worry about whether a property of an Activity Vocabulary object has a URL or embeds an actual object. If you need an object, you can call the `getObject()` method (which will fetch a remote object if necessary). If you need a URI, you can access the `objectId` property.

https://fedify.dev/manual/vocab#object-ids-and-remote-objects

#ActivityPub #fedidev

Quick question: would it be okay to embed a collection object in the `as:replies` property of `as:Note` & `as:Article` objects instead of putting the URL to the collection in the `as:replies` property? In theory, it would be okay, but would the actual implementations handle it well?

#fedidev #ActivityPub

Phanpy and Elk are both great web clients for fediverse platforms that support the mastodon api.

Did you know that both utilize a third party mastodon api library written in JavaScript?

Masto.js makes those applications possible! Give some props to the creator and maintainer, @neet

https://github.com/neet/masto.js

#FediDev #Mastodon

#Fediforum has a Saturday schedule, and it's starting in less than two hours. You can still register to attend, with some (almost) free tickets available at $1.99 if the regular rate is too high - a bargain for attending a single day of the event.

My favorite part is the demos - you get to see the people behind the sites and apps you use (or will be using), demoing their latest fediverse related projects!

https://fediforum.org/

#FediForum #Fediverse #FediDev

Compared to @hollo, @fedify seems to have less people contributing patches. Would this imply that #Fedify's codebase is harder to read or to modify?

#fedidev

The next version of #Fedify will support #LDSignatures (#RsaSignature2017), which means that Fedify will be able to verify activities forwarded by #Mastodon from other servers.

In addition, activities sent with the Context.sendActivity() method will have Linked Data Signatures attached in addition to HTTP Signatures if any RSA-PKCS#1-v1.5 key pairs are present.

We were not motivated by implementing Linked Data Signatures, which is already an outdated standard, but we hope this change will lead to better compatibility and interoperability of Fedify apps!

#fedidev #ActivityPub

Show time: Patchwork & Channel. org debut 💫
 
In a couple of hours we’ll be back at #FediForum and we’re excited to be debuting our new projects on Saturday, Channel. org and Patchwork - opening for early access soon.

#SocialMedia #Fediverse #Mastodon #MastoDev #FediDev #FediAdmin #MastoAdmin

Working on @fedify's docs about #LDSignatures… I hope someday #Fedify drop the support for Linked Data Signatures… 😇

#fedidev #ActivityPub

The next #Fedify release will finally be 1.0.0. Stay tuned!

#fedidev

#Fedify has a side effect that when you call the getter method of an Activity Vocabulary object, the property that was internally a URI is populated with the actual ActivityStreams object. Today, someone at Ghost gave us a cool term for this: #hydration.

#fedidev #ActivityPub

Does #Misskey also attach #LDSignatures to activities? If so, what types of activities does it attach LD Signatures to?

#ActivityPub #fedidev

The `fedify inbox` command, which is shipped with @fedify/cli, is a tool that creates an ephemeral #ActivityPub server so that you can debug and test the activities you send.

Here's a demo of it.

https://fedify.dev/cli#fedify-inbox-ephemeral-inbox-server

#fedidev

I received a request from @ghost today to add #LDSignatures to @fedify for compatibility with #Mastodon, as Mastodon does not plan to implement Object Integrity Proofs (FEP-8b32) for the near future. 😩

However, Mastodon's implementation of LD Signatures does not even use valid JSON-LD properties (despite the name), so I'm not sure how to make it compatible with Mastodon since #Fedify does JSON-LD processing. 🤔

#ActivityPub #fedidev

Fedify, an #ActivityPub server framework, has released v0.15.0! The key changes include:

• There's a new tutorial for creating a microblog.
• Actors, collections, and object dispatchers can now have URIs that do not include a WebFinger username, meaning actors can now change their fediverse handles.
• Article, ChatMessage, Note, and Question classes now have a quoteUrl property. This property corresponds to three properties at once: as:quoteUrl, misskey:_misskey_quote, and fedibird:quoteUri.
• Changed the element type of the liked collection from Like to Object | URL.
• Added Context.lookupObject() method.
• The default document loaders can now recognize ActivityStream objects from the Link header or the <link>/<a> tag in HTML.
• Added -r/--raw option to the fedify lookup command.

It is now available in JSR and npm.

#Fedify #fedidev

I have a question about the `liked` collection in the #ActivityPub specification. According to section 5.5, the liked collection is “a list of every object from all of the actor's `Like` activities”, whereas the side note in section 5.7 says it is “a collection of `Like` activities performed by the actor”. What is the element type of the liked collection, `Object` or `Like`?

• Section 5.5: https://www.w3.org/TR/activitypub/#liked
• Section 5.7: https://www.w3.org/TR/activitypub/#likes

#fedidev

I'm glad that @fediforum added a weekend date. It's tough to get away during the week for me. FYI, the demos are usually first thing in the mornings and are a can't miss - worth the price for those alone IMO.

Check WeDistribute for live coverage of the event!

https://flipboard.com/@wedistribute/across-the-fediverse-i6a1ubvjz/-/a-npYBPFU6ToK2o1DCWJG8ng%3Aa%3A4015545021-%2F0

#Fediverse #FediDev #FediForum

As Firefish maintenance begins to wind down, IceShrimp offers a migration guide.

https://iceshrimp.dev/iceshrimp/iceshrimp/src/branch/dev/docs/migrate.md

#Firefish #IceShrimp #FediDev #Fediverse

In the next version of #Fedify, it will allow you to decouple actor URIs from WebFinger usernames with the mapHandle() method. For example, you can use UUIDs for actor URIs but let users use their own username of choice for their fediverse handle.

You can preview it in v0.15.0-dev.382+a8a9b73b: JSR & npm.

#ActivityPub #fedidev

I wish #Mastodon would just implement FEP-8b32 instead of the LD Signatures which is obsolete.

https://w3id.org/fep/8b32

#ActivityPub #LDSignatures #fedidev

I often struggle with working on non-trivial, long standing projects because when I sit down to do the work after some hiatus, I can't seem to find the pain points I wanted to fix quickly enough.

It feels like trying to get a bandaid off when you can't find an edge where it comes unstuck easily enough.

The largest piece of bandaid that I wasn't able to get unstuck from the ActivityPub adjacent work is getting the HTTP-signatures working well with the rest of the fediverse (by which I mean Mastodon).

Today I might have got the corner of another little bit of bandaid unstuck which hopefully will help in the long run.

#ActivityPub #fedidev #GoActivityPub

👀 Very interesting post visibility comparison table by Stefano, on this code review for adding Akkoma/Pleroma's Local-only posting on Phanpy https://github.com/cheeaun/phanpy/pull/657#discussion_r1745903955

#FediDev #MastoDev

We just finished drafting a new tutorial for #Fedify! This tutorial will walk you through the steps of creating your own federated #microblog. It's pretty long, though.

Please read it, give us feedback, and have fun!

https://unstable.fedify.dev/tutorial/microblog

#fedidev #ActivityPub

Are there any features you'd like to see in #Fedify?

#fedidev #ActivityPub

Fedifyは、TypeScriptとJavaScriptで書かれたActivityPubサーバーフレームワークです。分散型のソーシャルネットワークを構築するためのサーバーアプリケーションを作る際の複雑さと冗長なコードを排除し、ビジネスロジックとユーザー体験の開発に集中できるようにすることを目指しています。

現在提供している主な機能は以下の通りです：

• Activity Vocabularyのための型安全なオブジェクト（一部のベンダー固有の拡張機能を含む）
• WebFingerクライアントとサーバー
• HTTP SignaturesとObject Integrity Proofs
• ウェブフックを処理するためのミドルウェア
• NodeInfoプロトコル
• Node.js、Deno、Bunのサポート
• テストとデバッグのためのCLIツールチェーン

興味がある方は、Fedifyのウェブサイトをご覧ください！包括的なドキュメント、デモ、チュートリアル、サンプルコードなどが用意されています：

https://fedify.dev/

#Fedify #TypeScript #JavaScript #ActivityPub #NodeInfo #Node #Deno #Bun #fedidev

During the development of #Fedify, I ended up with too many #fediverse accounts that I created to test.

#fedidev

Question for those who have followed the #Fedify tutorial: How long did it take you to follow the tutorial?

#fedidev

I finally finished the first draft of the new #Fedify tutorial, but it's still in Korean. Now I just need to polish it up and translate it into English.

#fedidev

Did you know? #Fedify offers the markdown-it plugins for parsing #Mastodon-style mentions and hashtags syntax:

• @fedify/markdown-it-mention: JSR & npm
• @fedify/markdown-it-hashtag: JSR & npm

Check it out!

#fedidev

I wish there was a more fancy canonical permalink for each #FEP document.

#fedidev #ActivityPub

@index is out with another amusing blog post about their fediverse journey. But the most important thing we learned is that this account exists.

https://mastodon.social/@activitypugtest

#FediDev #ActivityPub #ActivityPug

Dear developers of the #fediverse, has anyone ever encountered a case where a personal inbox in #Threads responds with a 404 Not Found for a POST request?

https://app.warp.dev/block/vKJGDbgWHBEAlAKBl0jlPR

#fedidev #ActivityPub

@subclub is a new way to add a paid subscriber link to your fediverse profile, allowing you to create subscriber only content! You get a really nice "Subscribe" button on the Mammoth and Ice Cubes app.

If you are a fediverse app developer and interested in adding this to your app, reach out to subclub directly and they can get your started!

Here's a walk through of how to get it setup.

https://video.everythingbagel.me/w/rXvUZeaU1b2rnaXGVKzsPe

#FediDev #MastodonApp #MastoDev #Fediverse #Mastodon

Suddenly, I'm reminded of a service called Yahoo! Pipes from about 15 years ago. If anyone remembers, #Pipes handled #RSS as its primitive, and now I'd like to see something like Pipes handle #ActivityPub as its primitive.

https://en.wikipedia.org/wiki/Yahoo!_Pipes

#fedidev #idea

We've released v0.14.0 of #Fedify, the #ActivityPub server framework, with the following key changes:

• It is now possible to set the recipient of the sendActivity() method to "followers" in just the Context instead of the RequestContext.
• Improved performance of the Object.toJsonLd() method by about 3,000 times.
• Added source property to Object.
• Added aliases property to Actor, corresponding to ActivityPub's alsoKnownAs property.
• fedify init command now adds default compilerOptions settings to tsconfig.json and deno.json.

Fedify v0.14.0 is available from JSR and npm. See also the full changelog for details.

Happy #fedidev!

We've added the Inspecting ActivityPub objects section to the #Fedify docs, introducing BrowserPub and the fedify lookup command!

https://unstable.fedify.dev/manual/test#inspecting-activitypub-objects

#ActivityPub #BrowserPub #fedidev

Do you know that? Some of the properties in Activity Vocabulary have been renamed in #Fedify's JavaScript APIs. Below are some examples:

• alsoKnownAs → aliases
• publicKeyPem → publicKey
• hreflang → language
• publicKeyMultibase → publicKey
• orderedItems → items
• oneOf → exclusiveOptions
• anyOf → inclusiveOptions
• votersCount → voters
• attributedTo → attributions
• inReplyTo → replyTargets

#ActivityPub #fedidev

Even I have no idea how much #Fedify's API will change, so I don't know when I'll release Fedify 1.0.0. 🤦

#fedidev

Is there any standardized #spec for #Misskey-style quotes?

#ActivityPub #fedidev

Hollo를 소개합니다!

Hollo는 개인을 위한 연합형 마이크로블로그 소프트웨어입니다. Fedify와 Bun으로 만들어졌으며, #ActivityPub 프로토콜을 통해 다른 인스턴스 및 서비스와 교류할 수 있습니다.

Hollo의 특징은 한 사용자를 위해 설계된 전용 인스턴스라는 점입니다. 이를 통해 사용자는 자신만의 공간을 가지면서도 #Mastodon, #Misskey 및 기타 ActivityPub 지원 서비스의 사용자들과 소통할 수 있습니다.

독자적인 웹 인터페이스는 없지만, Mastodon API와 호환되어 기존의 많은 Mastodon 클라이언트 앱을 사용하여 Hollo에 접근할 수 있습니다. 이로 인해 익숙한 인터페이스로 Hollo를 이용할 수 있습니다.

주요 기능으로는 게시물 작성·편집·삭제, 답글, 미디어 첨부, 투표, 좋아요, 북마크, 고정 등이 있습니다. 또한 프로필 편집, 팔로우/팔로워 관리, 리스트 생성 등도 가능합니다. 더불어 Markdown을 지원하여 게시물이나 프로필의 서식 설정을 쉽게 할 수 있습니다.

Hollo는 현재 개발 초기 단계에 있으며, 지속적으로 기능 추가와 개선이 이루어지고 있습니다. Bun을 사용함으로써 빠른 성능과 효율적인 개발이 이뤄지고 있답니다. 오픈 소스 프로젝트로 GitHub에 공개되어 있으며, 커뮤니티의 기여를 환영합니다.

개인 블로그와 소셜 미디어의 장점을 결합한 Hollo는 프라이버시를 중시하면서도 더 넓은 커뮤니티와의 연결을 원하는 사람들에게 적합한 플랫폼으로 거듭나고 있습니다.

https://github.com/dahlia/hollo

#Hollo #Markdown #Bun #Fedify #fedidev

Holloを紹介します！

Holloは、個人向けの連合型マイクロブログソフトウェアです。FedifyとBunを基盤に構築され、ActivityPubプロトコルを通じて他のインスタンスやサービスと連携することができます。

Holloの特徴は、一人のユーザーのために設計された専用のインスタンスという点です。これにより、ユーザーは自分だけのスペースを持ちながら、Mastodon、Misskey、その他のActivityPub対応サービスのユーザーとも交流できます。

独自のウェブインターフェースを持たない代わりに、MastodonのAPIと互換性があるため、既存の多くのMastodonクライアントアプリを使用してHolloにアクセスできます。これにより、使い慣れたインターフェースでHolloを利用することができます。

主な機能には、投稿の作成・編集・削除、返信、メディア添付、投票、お気に入り、ブックマーク、ピン留めなどがあります。また、プロフィール編集、フォロー/フォロワー管理、リスト作成なども可能です。さらに、Markdownをサポートしているため、投稿やプロフィールの書式設定が容易に行えます。

Holloは現在開発の初期段階にあり、継続的に機能の追加や改善が行われています。Bunを使用することで、高速なパフォーマンスと効率的な開発が実現されています。オープンソースプロジェクトとして、GitHubで公開されており、コミュニティからの貢献を歓迎しています。

個人のブログとソーシャルメディアの利点を組み合わせたHolloは、プライバシーを重視しながら、より広いコミュニティとのつながりを求める人々に適したプラットフォームとなっています。

https://github.com/dahlia/hollo

#Hollo #ActivityPub #Mastodon #Markdown #Bun #Fedify #fedidev

For educational purpose, I've created a federated microblog example using #Fedify, with a total of about 30 commits, which you can follow step by step.

Now, I'm starting to write a hands-on Fedify tutorial based on this example code. I'll make it public when I'm done!

https://github.com/dahlia/microblog

#fedidev #ActivityPub

I've rewritten #Fedify several times and in several languages. The first time it was written in #TypeScript, then #Python, then C#, then back to TypeScript. (It was codenamed FediKit at the time of development.) I settled on TypeScript for the following reasons:

• It has a decent JSON-LD implementation.
• Lots of people use it. (I wanted Fedify to be widely used.)
• It's type-safe enough.

Even if I were to build Fedify again, I would choose TypeScript.

#fedidev #CSharp #dotnet #JavaScript

Also, a new logo for #FediDev KR has been designed!

https://github.com/fedidevkr/logo

#FediDev KR has decided to organize a sprint meetup later this month in Gangnam, Seoul (yes, the same Gangnam from Gangnam Style)!

Security alert for Fedify users

We've patched a vulnerability in the getActorHandle() function. Versions prior to 0.13.1 and 0.12.3 are affected.

Upgrade immediately:

• npm: 0.13.1 & 0.12.3
• JSR: 0.13.1 & 0.12.3

#Fedify #securityupdate #fediverse #fedidev #ActivityPub

In the next version (v0.14.0) of #Fedify, the performance of the Object.toJsonLd() method will be dramatically (~3k ×) faster. This is expected to improve the overall performance of Fedify apps!

#fedidev #JSONLD #ActivityPub

I feel that the current abstraction level of #Fedify is not high enough which makes the tutorial lengthy, so I'm considering adding a higher-level API. One way would be to add a façade to the @fedify/fedify package, and another way would be to create a sort of metaframework as a separate package (e.g., @fedify/start?). Which way would be better?

#fedidev

I'm writing a #Fedify tutorial, and I keep saying things like “you don't need to know what Ed25519 is” and “you don't need to know what JWK is for this tutorial.” Would this be okay?

#fedidev

The JSON-LD processor ended up being #Fedify's bottleneck, so I'm in the process of fixing Fedify to generate JSON-LD without the proper JSON-LD processor.

#JSONLD #fedidev #ActivityPub

Does anyone know of any docs or specs for the #EmojiReact activity type that #Misskey and #Pleroma use?

#fedidev

"We want to bring organisations and content creators into the Fediverse, step by step."

Our Foundation co-founder has just published an interesting piece on how we're working to help organisations and content creators find their way to the Fediverse!

For more information on what we plan to do as a charity and how Patchwork, a new service we'll be launching soon, can help 👇
https://www.blog-pat.ch/enter-the-fediverse/

#Fediverse #SocialMedia #FediDev #FediAdmin #MastoDev #MastoAdmin #Technology

Fedify, the #ActivityPub server framework, has released v0.13.0. Key changes include:

• Added fedify tunnel command to expose the local server to the public internet.
• Added Express and Nitro integration templates to the fedify init command.
• Added option to skip HTTP Signatures validation for easier testing.
• Added Question.closed property.
• Added Question.voters property.
• Removed several deprecated APIs.

#Fedify v0.13.0 is available now from JSR and npm.

https://github.com/dahlia/fedify/releases/tag/0.13.0

#fedidev

question: is anyone federating thumbhashes of media yet? is there an existing extension i can adopt or should i just come up with my own?

i know mastodon federates blurhashes. i'm specifically asking about thumbhashes (evanw.github.io/thumbhash/) instead.

#activityPub #fediDev #fediDevs

What other web frameworks would you like to see #Fedify integrate with more?

#fedidev

Introducing @fedify/express, a package that integrates Express, a popular web framework in Node.js, with Fedify. You can install it with the following command:

npm add @fedify/express

This package provides a middleware called integrateFederation() that allows you to integrate #Fedify with #Express:

import express from "express";
import { integrateFederation } from "@fedify/express";
import { federation } from "./federation";  // Your `Federation` instance

export const app = express();

app.set("trust proxy", true);

app.use(integrateFederation(federation, (req) => "context data goes here"));

https://github.com/dahlia/fedify-express

#fedidev #ExpressJS

i wonder how many #fedidev people realize that building a fedi viewer is on the scale of complexity of building a web browser

This is a milestone worth celebrating! :fediverse:
In development as we speak, @forgejo can now federate comments (and tons of other stuff) from issues in repos!!!

The first screenshot is @algernon (a Forgejo account able to be tagged in this post!) commenting on the issue: https://shoes.forgejo.madhouse-project.org/algernon/federation-test/issues/4 as seen in @phanpy while logged into my Mastodon account!
#fediverse #ActivityPub #FediDev #federation #forgejo #git #GitFederation

@mastometrics is a unique way to look at statistics about your own account - for free. It's even connected directly from your profile in the @IceCubesApp app.

But all that data and storage costs money! Please consider contributing to keep this service going - and if the goal is reached, open sourced to make it self-hostable.

https://ko-fi.com/robertvh

#FediFund #OpenSource #Mastodon #MastoDev #FediDev

We’re committed to helping people find their place in the Fediverse and wider Social Web.

We’ve helped hundreds of people, across multiple platforms, understand the idea by stripping down the tech and reimagining it.

We’ve put that learning in a video. It won’t answer all the questions, but it’s a strong starting point to help explain the Fediverse to outsiders.

Please share it to help educate others.

https://youtu.be/upEHFtO9vrI

#Fediverse #FediTips #MastoDev #FediDev #MastoAdmin #FediAdmin

#fedidev #fediblockmeta #fediadmin what are your lists of moderation wish list features? (or anti-features you wish didn't exist?)

If you read a #Fedify #tutorial, what #ActivityPub software would you like to see as an #example in the tutorial?

#fedidev

A good issue to contribute to #Fedify for the first time. Anybody interested?

https://github.com/dahlia/fedify/issues/109

#fedidev

I finally turned the Federation class into an interface now!

https://github.com/dahlia/fedify/commit/4c3015145a10804a5ec8debdc8bb394fe6ed819d

#Fedify #fedidev

"Our Foundation mission is “knowledge for all for good”. Using social media to share knowledge for the benefit of society."

Our co-founder, @michael , is discussing why The Newsmast Foundation is building new technology to benefit organisations and server admins on the Social Web.

Read it here: https://www.blog-pat.ch/content-technology-community/

#SocialMedia #FediDev #FediAdmin #MastoDev #MastoAdmin #Tech #Nonprofit #OSS #BuildInPublic

#Fedify, an #ActivityPub server framework, has released v0.12.0. It's a minor release in about a month, so there's quite a few changes:

• The fedify command can now also be installed with npm. It can be installed with npm i -g @fedify/cli in Node.js and bun i -g @fedify/cli in Bun.
• Added the fedify init command to help set up a new Fedify project.
• Incoming activities are now also queued and inbox listeners are now processed in the background worker. If you were already queuing outgoing activities, this will just take effect with a simple upgrade to v0.12.0.
• Retry policy for failed tasks processed in the background worker is now customizable and defaults to backoff with decorrelated jitter.
• Added ChatMessage, Move, Read, Travel, View, TentativeAccept, and TentativeReject classes. (Thanks to @moreal!)
• Improved multitenancy (virtual hosting) support: You can now easily determine the host of the current request via the hostname, host, and origin properties of the Context.
• When validating HTTP Signatures and Object Integrity Proofs, once fetched public keys are now cached.

It's available on JSR and npm now, and you can upgrade it using the deno add command on Deno:

deno add @fedify/fedify@^0.12.0

Or using the bun add command on Bun:

bun add @fedify/fedify@^0.12.0

Or using the npm add command on Bun:

npm add @fedify/fedify@^0.12.0

#fedidev

Since #Fedify v0.12.0, when verifying HTTP Signatures or Object Integrity Proofs, it will cache the public keys once fetched. It is okay even if a cached key becomes outdated because a verification failure due to a cached key will invalidate the cache and force a verification retry.

This feature is available for preview in v0.12.0-dev.307+235629d5 (JSR or npm).

#fedidev #ActivityPub

Working on the `fedify init` command, the project setup wizard for #Fedify…

#fedidev

"Our aim is to offer organisations and server admins an easy-to-use console where extra features can easily be added to their Mastodon server."

If you liked our update on Patchwork from @FreddieJ yesterday, we have good news!

Newsmast Foundation co-founder @michael has just shared a look behind the scenes at Patchwork production ready for @fediforum in September.

Check it out: https://www.blog-pat.ch/patchwork-progress/

#fediverse #fedidev #fediadmin #mastodon #developer #technology #tech #OSS #BuildInPublic

Just read an email newsletter from @newsmast about their upcoming Patchwork platform. It’s a plugin system to extend existing fediverse platforms.

One of their upcoming plugins will be local only posts. It’s a nice feature I used on Firefish, allowing nonfederated community discussions. Looking forward to it!

https://newsmast.social/@newsmast/112807985173916786

#Fediverse #FediNews #ActivityPub #FediDev

This week we want to talk to you about Patchwork, an upcoming project, using technology we developed for Newsmast to make new and existing spaces on the social web more safe, more connected and more fun!

Here’s an update from our Foundation Ambassador @FreddieJ 👇

#SocialMedia #Fediverse #FediDev #FediAdmin #Technology #Tech

It’s been a week since the UK General Election. As one of the UK’s leading Fediverse projects, we thought this would be a good time to look into the new government's digital policy and what it could mean for Fedi.

You can read the full blog by @FreddieJ here: https://www.newsmastfoundation.org/our-blog/impact-of-uk-election-result/

Or check out the thread below 👇

#Fediverse #government #UK #politics #technology #datapolicy #FediDev

#Fedify offers robust logging capabilities through integration with LogTape. This feature allows you to easily debug and monitor your Fedify app!

To enable #logging, simply install the @logtape/logtape package and configure it in your app's entry point:

import { configure, getConsoleSink } from "@logtape/logtape";

await configure({
  sinks: { console: getConsoleSink() },
  filters: {},
  loggers: [
    { category: "your-app", sinks: ["console"], level: "debug" },
    { category: "fedify",   sinks: ["console"], level: "info" },
  ],
});

Fedify uses hierarchical categories for fine-grained control over log output. Key categories include ["fedify", "federation", "http"] for HTTP requests/responses and ["fedify", "federation", "inbox"]/["fedify", "federation", "outbox"] for incoming/outgoing activities. (There are more categories.)

With #LogTape integration, you gain valuable insights into your Fedify app's behavior, making troubleshooting and optimization much more straightforward!

https://fedify.dev/manual/log

#fedidev

let's say Monday is the due date for the docs rewrite.

and July is single instance buildin' month.

August is fediverse vocab buildin' month.

Wanna have something to talk about at the #fedidev Denver meetup September 3rd.

I want to create good first issues for @fedify, but I don't have a good idea of appropriate tasks for first-time contributors. Any ideas?

#Fedify #fedidev #opensource

Ready to simplify your #fedidev? Check out #Fedify!

• Tutorial
• API reference
• Examples

Join us in building a more connected and decentralized web! 🌐 #ActivityPub

In #Fedify's next release, v0.12.0, we'll be adding support for integration with Astro, a web framework for content-driven websites.

https://unstable.fedify.dev/manual/integration#astro

#Astro #fedidev

We released #Fedify 0.9.2, 0.10.1, and 0.11.1, which patched the last reported #vulnerability, CVE-2024-39687, but the vulnerability of SSRF attacks via DNS rebinding still exists, so we released Fedify 0.9.3, 0.10.2, and 0.11.2, which fixes it.

If you are using an earlier version, please update as soon as possible.

Thanks to @benaryorg for reporting the vulnerability!

#SSRF #security #fedidev

Streams just nonchalantly mentions adding nomadic identity over ActivityPub in the latest release. 🤯

From: @streams
https://fediversity.site/item/d9dd01e1-96fd-4306-9bd9-27c2ebe1a1d5

#Fediverse #FediDev #ActivityPub

We're releasing @fedify/h3! Now you can integrate #Fedify with h3, an HTTP server framework behind Nitro, Analog, Vinxi, SolidStart, TanStack Start, and other many web frameworks.

https://github.com/dahlia/fedify-h3

#fedidev #h3

This morning I'm working through some trailhead modules for Salesforce. They have a social activity feed called "Chatter" that allows you to follow objects of any kind - people, groups, articles, database records.

Sound familiar? For whatever reason, they put a limitation that each account can only follow up to 500 objects. How many heads would explode if someone built an ActivityPub, Nostr or ATProto plugin for Salesforce? :AngeryCat:

https://help.salesforce.com/s/articleView?id=sf.collab_features_compare.htm&type=5

#FediDev #Salesforce

Finally, @ghost has open sourced their #ActivityPub implementation powered by #Fedify! For Fedify users, this means another production-grade example code.

If you'd like to follow updates on #Ghost's ActivityPub implementation, you can do so by following @index!

https://github.com/TryGhost/ActivityPub

#fedidev

I jsut wrote a detailed post on my blog about @ghost's #funding for @fedify! (Both English and Korean available.)

https://writings.hongminhee.org/2024/07/ghost-funds-fedify/

#Fedify #fedidev

#Fedify now has a queue for incoming activities and they are automatically retried when they fail. The default retry strategy is good enough (exponential backoff + decorrelated jitter), and it's even fully customizable. Updated also the docs:

https://unstable.fedify.dev/manual/inbox#making-inbox-listeners-non-blocking

You can give it a try by installing 0.12.0-dev.265+cb851932, the latest unstable release:

https://jsr.io/@fedify/[email protected]ev.265+cb851932
https://www.npmjs.com/package/@fedify/fedify/v/0.12.0-dev.265

#fedidev #ActivityPub

In the next version of #Fedify, the #RetryPolicy type is introduced to let you fully customize the retry policy of the task queue for incoming and outgoing activities. Of course, you can also simply adjust the parameters of the built-in exponential backoff + decorrelated jitter policy.

#fedidev #ActivityPub

Basic implementation of the inbox queue is complete and documentation is being worked on.

https://hollo.social/@fedify/0190687b-1a09-728b-8a0d-bcbd4dca54cd

#Fedify #fedidev

In the next version of #Fedify, the Context.hostname, Context.host, and Context.origin properties will be added for better multitenancy/virtual hosting support.

https://github.com/dahlia/fedify/issues/66#issuecomment-2198967566

#fedidev #ActivityPub

When there is no queue, if the process fails, the inbox can just respond with a 500 server error and the sender will resend it.

But with a queue, by the time the inbox responds, it doesn't know if the process will fail because it hasn't run yet. So the sender won't retry whether it fails or not.

So, should it have its own retry logic when there is a queue?

#Fedify #fedidev #ActivityPub

I'm adding a queue for incoming activities in #Fedify, and I have a concern. If an error occurs while processing an activity, should it retry?

https://hollo.social/@fedify/0190687b-1a09-728b-8a0d-bcbd4dca54cd

#fedidev #ActivityPub

#Fedify has always been queuing outgoing activities, but not incoming activities. Thanks to @ghost's sponsorship, we are now implementing queues for incoming activities!

https://github.com/dahlia/fedify/issues/70

#fedidev #ActivityPub

#ActivityPub, #FediDev and #security question: If instances generally collect only one copy of each post and then share it with the users that need to see it, does that mean nonoriginating instances are trusted to not show that post to users the poster has blocked (or who shouldn't see it because they're not following etc depending on visibility)?

How do the collecting instances know who should see it? (A cached copy of the poster's follow list?)

And does #authorized_fetch change any of this?

Today we created #FediDev KR, a community for Korean people who are not only implementing fediverse servers, but also those who are running them, such as server operators, moderators, client app developers, bot developers, writers, translators, researchers, and more. For now, we're based on a Discord server, but we hope to eventually organize offline meetups and workshops. We'd love your support!

https://fedidev.kr/

How long (hours, roughly) would it take to implement a basic #ActivityPub server from scratch in #Java — absoluet bare bones, like a proof of concept just capable of sending and receiving posts, which could then be developed more before becoming a finished, user-ready system?

#FediDev #Fediverse #Mastodon #MastoDev

먼저 Discord에 #FediDev KR 서버를 하나 만들었습니다!

https://discord.gg/B2ABMBpHNA

서울에서 #fedidev 모임하는 생각 💭

#Fedify is an #ActivityPub server framework in #TypeScript & #JavaScript. It aims to eliminate the complexity and redundant boilerplate code when building a federated server app, so that you can focus on your business logic and user experience.

The key features it provides currently are:

• Type-safe objects for Activity Vocabulary (including some vendor-specific extensions)
• #WebFinger client and server
• HTTP Signatures
• Middleware for handling webhooks
• #NodeInfo protocol
• #Node.js, #Deno, and #Bun support
• CLI toolchain for testing and debugging

If you're curious, take a look at the Fedify website! There's comprehensive docs, a demo, a tutorial, example code, and more:

https://fedify.dev/

#fedidev

#Fedify has supported optional queuing for outgoing activities, with two built-in message queue backends: InProcessMessageQueue, which is suitable for development, and DenoKvMessageQueue, which is only available in Deno.

Fedify has also had two built-in cache backends, MemoryKvStore, which is suitable for development, and DenoKvStore, which is only available in Deno.

Now, however, by installing the @fedify/redis package, you can use #Redis as both a message queue backend and a cache backend! Unlike DenoKvMessageQueue and DenoKvStore, it's also available for #Node.js and #Bun.

This feature was made possible with the support of @ghost.

https://github.com/dahlia/fedify-redis

#fedidev

@kodingwarrior 한국에도 #fedidev 모임 같은 거 개최하면 좋겠어요 ㅎㅎ

#Fedify now has the official #Hollo account! Please follow @fedify!

https://hollo.social/@fedify/01905d6a-5d70-75bc-881e-d6c155a5051c

#fedidev

Hello, #fediverse! It's the official fedi account of the Fedify, an #ActivityPub server framework!

#Fedify #fedidev

Found a memory leak (on #Bun) in recent commits of #Fedify—be careful when using the unstable versions.

#fedidev

I wish there was a #fedidev meetup in #Korea too…

#Hollo development is often motivation to add features to #Fedify, for example, most of the commits I added to Fedify today were for Hollo.

#fedidev

If you'd like to support the development of #Fedify or #Hollo, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

#fedidev

Introducing #Hollo. Hollo is an #ActivityPub-enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

It's headless, meaning you can use existing #Mastodon client apps instead, with its Mastodon-compatible APIs. It has most feature parity with Mastodon. Two big differences with Mastodon is that you can use #Markdown in the content of your posts and you can quote another post.

Oh, and Hollo is built using #Bun and #Fedify.

https://github.com/dahlia/hollo

#fedidev

Version 0.10.0 of #Fedify, an #ActivityPub server framework, has been released! Starting with this release, Fedify, previously distributed under AGPL 3.0, is now distributed under the MIT License to encourage wider adoption. Here are the major changes:

• In addition to RSA-PKCS#1-v1.5, Fedify now supports Ed25519 for signing and verifying the activities.
• FEP-521a: Multiple key pairs can now be registered for an actor.
• FEP-8b32: Implemented Object Integrity Proofs.
• Added Arrive and Question classes.

#fedidev

https://github.com/dahlia/fedify/releases/tag/0.10.0

TIL when you upload a video file to Mastodon, it generates a preview thumbnail. The thumbnail isn't passed through to other servers in the ActivityPub payload (similar to preview cards).

Each receiving platform handles this situation differently. Some regenerate a thumbnail (processing again). Some ignore it and don't show one. Others create blank thumbnails to appease the Mastodon API.

A blurhash is passed, tho, and could be used as a placeholder.

#FediDev #Mastodon

@hollo is a testbed for the bleeding edge of #Fedify. 😂

#fedidev

#Mastodon sends Create(Question) for the poll, even though the Question itself is an Activity. Does it see Question as a regular Object rather than an Activity?

#Mastodon #fedidev #ActivityPub

I'm very excited that the #Ghost team has chosen #Fedify to implement #ActivityPub. I've been working closely with the Ghost team, and it's been a lot of fun, and I can't wait to see the ActivityPub implementation at Ghost.

https://activitypub.ghost.org/day-4/

#fedidev

Ghost will be using the open source Fedify server framework to manage the activitypub bits and pieces of their service.

https://activitypub.ghost.org/day-4/?ref=build-log-newsletter

#FediDev #ActivityPub #Fedify #Ghost

Thanks to @silverpill, #Fedify is finally FEP-8b32 compliant! Though it's not ready for general release yet, it's passing tests in the latest main branch. I'll test it with Mitra and other FEP-8b32-compliant implementations, and if it works well, it'll be included in 0.10.0.

You can try it out in version 0.10.0-dev.205+0cbca257.

https://jsr.io/@fedify/[email protected]ev.205+0cbca257

#fedidev #ActivityPub

I just released #Fedify 0.9.1, which fixed one small bug.

https://github.com/dahlia/fedify/releases/tag/0.9.1

#fedidev

#Hollo now supports sharing posts (reblogs)!

#fedidev #ActivityPub

Bonfire, the modular Fediverse platform, is looking for five Elixir developers to act as test subjects to improve the developer onboarding experience. Participants can receive a €50 stipend for their one-hour session.

Please share with your elixir dev friends, and boost!

https://bonfirenetworks.org/posts/surveying_expedition/

#Elixir #FediDev #Fediverse #MyElixirStatus

Implementing Object Integrity Proofs (FEP-8b32) and my implementation is not passing the test vectors. I haven't found the reason for 24 hours… 😫

#Fedify #fedidev #ActivityPub

FEP-521a has been implemented in #Fedify.

Actors now have the #assertionMethods property, and the #Multikey class has been added. For example, if you look at the the actor from the Fedify Example Blog (https://fedify-blog.deno.dev/users/fedify-example), you can see that it has the assertionMethods property in addition to the publicKey property.

You can try it out in version 0.10.0-dev.196+55cc34d1.

https://jsr.io/@fedify/[email protected]ev.196+55cc34d1

#fedidev #ActivityPub

#Misskey throws an error when a remote actor has multiple public keys, so I sent a patch to fix this bug.

This is my first patch for Misskey!

https://github.com/misskey-dev/misskey/pull/13950

#fedidev #ActivityPub

As a first step towards adding Object Integrity Proofs (FEP-8b32) to #Fedify, I've made it support #Ed25519 keys. I've also enabled multiple keys to be associated with an actor. For example, if you look at the actor from the Fedify Example Blog (https://fedify-blog.deno.dev/users/fedify-example), you'll see that it has two public keys, one for RSA and one for Ed25519.

You can try it out in version 0.10.0-dev.190+4dffb89a.

https://jsr.io/@fedify/[email protected]ev.190+4dffb89a

#fedidev #ActivityPub

Version 0.9.0 of #Fedify, an #ActivityPub server framework, has been released! Here are the main changes:

• Added Tombstone, Hashtag, and Emoji classes.
• Added normalizeActorHandle() function to normalize an actor handle. This is needed when the domain of the actor handle is an IDN, or when the domain contains capital letters.
• Added an option to the sendActivity() function, excludeBaseUris, to exclude specified servers from sending activities. This can be used when you don't want to send activities to your own server.
• Added Context.parseUri(), a method to parse actor, object, inbox, and collection URIs.
• The time window for HTTP Signatures verification is now configurable.
• The @fedify/fedify/httpsig module has been renamed to . This is in preparation for implementing additional object integrity proofs other than HTTP Signatures.
• Improved interoperability with #Misskey.

#fedidev

https://github.com/dahlia/fedify/releases/tag/0.9.0

Now #Hollo has several more features:

• Following/unfollowing accounts
• Following/unfollowing hashtags
• Post visibility
• Post language
• Editing profile
• Mentions
• Likes
• Bookmarks
• Notifications
• Markers

#fedidev

I'm rebuilding #Hollo from scratch, and I've implemented some #Mastodon-compatible APIs to let me do the following actions with #Phanpy and #Elk now:

• Logging in
• Composing a post
• Writing a reply
• View posts
• Public timeline
• Home timeline

✌️

#fedidev