#activitypub Timeline

190d

Happy 17th Year Anniversary #Fediverse social network!

Always strong! 🎊🎉🎂🍻🎆🥳🤹🏽

( #FediverseDay #SNS #SocMed #SocialMedia #SocialWeb #OpenMicroBlogging #OStatus #ActivityPub #Laconica #Identica #Web3 )

0 1 0 View Post & Replies See Original

190d

Happy 17th Year Anniversary #Fediverse social network!

Always strong! 🎊🎉🎂🍻🎆🥳🤹🏽

( #FediverseDay #SNS #SocMed #SocialMedia #SocialWeb #OpenMicroBlogging #OStatus #ActivityPub #Laconica #Identica #Web3 )

0 0 0 View Post & Replies See Original

282d

Excited to share that Fedify CLI is now available on Scoop for #Windows users! You can easily install it with scoop install fedify. One more way to get started with #ActivityPub development!

https://github.com/ScoopInstaller/Main/pull/6371

#Fedify #fedidev #Scoop

0 0 1 View Post & Replies See Original

282d

Hah! I knew it. I knew the fediverse would pop up as I explore Gemini. Adding this to my collection of platforms to try.

https://github.com/dimkr/tootik/releases/tag/0.15.3

#Gemini #Gopher #HomeLab #ActivityPub #Fediverse

0 0 1 View Post & Replies See Original

336d

Looking for a side project to do over the holidays? Why not create your own #ActivityPub server with #Fedify?

https://fedify.dev/tutorial/microblog

1 0 1 View Post & Replies See Original

272d

We'd like to introduce the #Fedify project family—a set of related tools that make building #ActivityPub applications more accessible:

@Fedify

@Fedify (@fedify) is a #TypeScript library for building federated server applications powered by ActivityPub and other #fediverse standards. It provides type-safe objects for Activity Vocabulary, WebFinger client/server, HTTP Signatures, and more—eliminating boilerplate code so you can focus on your application logic.

@Hollo

@Hollo (@hollo) is a single-user microblogging server powered by Fedify. While designed for individual users, it's fully federated through ActivityPub, allowing interaction with users across the fediverse. #Hollo implements Mastodon-compatible APIs, making it compatible with most Mastodon clients without needing its own web interface.

Hollo also serves as our testing ground for bleeding-edge Fedify features before they're officially released.

@BotKit

@BotKit (@botkit) is our newest family member—a framework specifically designed for creating ActivityPub bots. Unlike traditional Mastodon bots, #BotKit creates standalone ActivityPub servers that aren't constrained by platform-specific limitations (like character counts).

BotKit's API is intentionally simple—you can create a complete bot in a single TypeScript file!

All three projects are open source and hosted under the @fedify-dev GitHub organization. While they serve different purposes, they share common goals: making ActivityPub development more accessible and expanding the fediverse ecosystem.

If you're interested in trying any of these projects or contributing to their development, check out:

Fedify: https://fedify.dev/
Hollo: https://docs.hollo.social/
BotKit: https://botkit.fedify.dev/

#fedidev

0 0 1 View Post & Replies See Original

189d

PieFed adds PassKeys! As in, log in only with your passkey. Not just as a 2FA addition to your username/password.

https://piefed.social/post/762082

#ActivityPub #FediDev #PieFed

0 0 1 View Post & Replies See Original

337d

Strangely on a Sunday morning, I'm glad to announce the release of version 2.67 of #snac, the simple, minimalistic #ActivityPub instance server written in C. It includes the following changes:

The search box also accepts post URLs; the post is requested and, if it's found, can be interacted with (liked, boosted, replied to, etc.).

IP addresses for failed logins are tracked and throttled to mitigate brute force attacks (see snac(8) for more information).

Fixed a bug regarding repeated attachments when editing a post.

Mastodon API: Improved timeline pagination in some clients (details: an HTTP Link header has been added), fixed missing audio attachments, fixed an incorrect value for the bot field in newly created accounts, fixed a crash, implemented markers (contributed by nowster).

When running in server mode, the pidfile is locked to avoid concurrent running of the same server instance.

Added documentation and some tweaks to enable static compilation with musl (contributed by Shamar).

https://comam.es/what-is-snac

If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/

#snacAnnounces

In the northern half we'll celebrate #SolInvictus by listening to the song One Perfect Sunrise by #Orbital.

0 0 1 View Post & Replies See Original

335d

I'm looking for your opinions from the developers of the fediverse.

A common HTML web page can contain related links via the <link> tag. I would like to do the same for Activity Streams objects, for example:

{ "@context": "https://www.w3.org/ns/activitystreams", "id": "https://writings.hongminhee.org/ap/2024/12/a-year-with-the-fediverse.json", "type": "Article", "name": "A year with the fediverse", "content": "2024 was truly a year where I was deeply immersed in the fediverse. …", "url": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/", "attachment": [ { "type": "Link", "rel": "alternate", "hreflang": "ko", "href": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.ko-hang-kr.html", "mediaType": "text/html" }, { "type": "Link", "rel": "alternate", "hreflang": "ja", "href": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.ja.html", "mediaType": "text/html" } ]}

Do you think this makes sense, and would it be appropriate to put Link objects in the attachment?

#fedidev #ActivityPub #ActivityStreams

Edited 335d ago

0 0 1 View Post & Replies See Original

282d

Week in Fediverse 2025-02-14

Servers

- Mbin v1.8.0
- snac v2.72
- Lemmy v0.19.9
- flohmarkt v0.8.0
- GoToSocial v0.17.4
- Hollo v0.5.0
- Manyfold v0.100.0
- Mitra v3.17.0
- ActivityPub for WordPress v5.2.0
- Pleroma ActivityRelay v0.3.4
- NeoDB v0.11.4.7
- tootik v0.15.3
- kmyblue v17.0
- Trunk & Tidbits, January 2025
- Bringing Quote Posts to Mastodon

Clients

- Mangane v1.13.6
- Thunder v0.6.1
- Fediboat: Mastodon TUI client with a Newsboat-like interface

Tools and Plugins

- Event Bridge for ActivityPub v1.0.0 (WordPress plugin)
- Enable Mastodon Apps for WordPress v1.0.0
- LemmyWebhook v0.19.0
- Mastodon – Simplified Federation v2.2.1
- Utsukta Hub themes: A collection of custom themes developed for Hubzilla

For developers

- BotKit v0.1.1
- TootSDK v13.0.0
- apsig: Signature implementation used in ActivityPub (python)

Protocol

- FEP-efda: Followable objects

Articles

- Tumblr to join the fediverse after WordPress migration completes
- Last Week in Fediverse #103

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/0194e1e4-74a9-17c1-c347-9674b1a3f9c9

0 0 1 View Post & Replies See Original

331d

Week in Fediverse 2024-12-27

Servers

- Hubzilla v10.0.0
- snac v2.67
- tootik v0.14.0
- activity-pub-relay v0.8.0
- Mastodon: Annual Report 2023
- μpub: micro social network, federated

Clients

- Tusky v27.0
- Tuba v0.9.1
- Pixelix v3.0.0
- Voyager v2.22.0
- Tesseract v1.4.21

Tools and Plugins

- FediAM v0.2
- Threativore v0.7.0
- Posty: This is How You Take Your Posts With You

For developers

- Bovine v0.5.15

Articles

- botsin.space postmortem
- How much does the fediverse cost?
- Building a Better Social Web
- Surf is a “Social Browser” App From Flipboard

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/0193e565-a77c-3eb7-5957-9d3d3367f05d

0 0 1 View Post & Replies See Original

185d

I've just updated my #Snac instance to version 2.77 👍 🎉
You don't know Snac? But you should: https://codeberg.org/grunfink/snac2
A simple, minimalistic #ActivityPub instance server written in C, no database needed, totally JavaScript-free, no cookies either, not much bullshit.

0 0 1 View Post & Replies See Original

123d

<p>This release introduces a redesigned Followers table that’s easier to navigate and customize—hide columns, change how many entries you see, or remove followers directly. Migrations are now simpler: just paste in a WebFinger ID or profile URL, and the plugin takes care of the rest. We’ve also fixed an issue where old, unfederated posts could be mistakenly re-sent—those will now stay quiet unless they’re recent. Plus, lots of behind-the-scenes improvements for a smoother experience.</p>

This release is mostly made up of behind-the-scenes improvements, but one update you’ll notice right away is the refreshed Followers table. It now looks and feels much more like the standard WordPress admin tables: you can customize it with screen options to hide columns or change how many followers are shown per page, and you can now delete individual followers using inline action links. We also polished the layout by increasing information density and improving the readability of date columns.

We’ve made migrations easier to kick off by automatically resolving account aliases and saving their ID form. That means you can now paste in WebFinger IDs, profile URLs, etc. and the plugin handles the rest, as long as it resolves to an ActivityPub profile.

This release also fixes a long-time annoyance: unfederated posts (like those published before the plugin was activated or imported later) will no longer be sent out to followers just because they were updated. For now, we use a simple cutoff for posts older than a month, which should cover the majority of those cases.

Coming Soon: Following Others!

Most of the work that went into this release is still invisible, hiding behind a feature flag in Advanced Settings (you can find it by opening Screen Options in the ActivityPub settings screen).

There’s really no functionality around it yet, beyond following accounts from other instances, as we have yet to start processing incoming posts and adding the ability to interact with them. But if you just can’t wait to show your appreciation for other accounts by following them, go wild!

Behind the same feature flag, we’ve also added initial beta support for Fediverse Starter Kits. This lets new users follow a set of recommended accounts from a predefined list, following the format proposed by @dansup for Pixelfed. For now, only Actor objects are supporteded, but we’re hoping to expand that over time.

Full Changelog

Added

Added a first version of the Follow form, allowing users to follow other Actors by username or profile link.
Added initial support for Fediverse Starter Kits, allowing users to follow recommended accounts from a predefined list.
Ensure that all schedulers are registered during every plugin update.
Followers and Following list tables now support Columns and Pagination screen options.
The featured tags endpoint is now available again for all profiles, showing the most frequently used tags by each user.
The following endpoint now returns the actual list of users being followed.

Changed

Follower tables now look closer to what other tables in WordPress look like.
Improved Account-Aliases handling by internally normalizing input formats.
Minor performance improvement when querying posts of various types, by avoiding double queries.
Set older unfederated posts to local visibility by default.
Step counts for the Welcome checklist now only take into account steps that are added in the Welcome class.
Table actions are now faster by using the Custom Post Type ID instead of the remote user URI, thanks to the unified Actor Model.
The following tables now more closely match the appearance of other WordPress tables and can be filtered by status.

Fixed

Ensure correct visibility handling for Undo and Follow requests
Ensure that the Actor-ID is always a URL.
Fixed a bug in how follow requests were accepted to ensure they work correctly.
Fixed an issue where the number of followers shown didn’t always match the actual follower list.
Fixed a PHP error that prevented the Follower overview from loading.
Fixed missing avatar class so that CSS styles are correctly applied to ActivityPub avatars on the Dashboard.
Fixed potential errors when unrelated requests get caught in double-knocking callback.
Improved WebFinger fallback to better guess usernames from profile links.
Prevent WordPress from loading all admin notices twice on ActivityPub settings pages.
Removed follower dates to avoid confusion, as they may not have accurately reflected the actual follow time.
Stop purging Follow activities from the Outbox to allow proper Unfollow (Undo) handling.

Downloads

WordPress.org: activitypub.7.1.0.zip
GitHub: tag/7.1.0

Thank you!

Big thanks to everyone who contributed code, feedback, testing, or encouragement—this community helps make the fediverse more connected with every release. ❤️

Update to 7.1.0, try it out, and tell us what you think!

Takahe has limited support for this type: See Original Article

Cartoon-style Wapuu character in a spacesuit floating in space, holding a wrench while repairing a control panel with colorful indicators. Surrounded by cables, pipes, and machinery, the Wapuu looks intense as it works.

ALT

Edited 123d ago

0 0 1 View Post & Replies See Original

329d

Hollo 0.4.0 released! #Hollo is a single-user federated microblogging software which is #ActivityPub-enabled and powered by #Fedify.

The key changes of this release include:

Hollo is now powered by Node.js 23+ instead of Bun for more efficient memory usage.

Added an experimental feature flag TIMELINE_INBOXES to store all posts visible to your timeline in the database, rather than filtering them in real-time as they are displayed. This is useful for relatively larger instances with many incoming posts, but as of now it may have several bugs. It is expected to be the default behavior in the future after it is stabilized.

Now you can import and export your data from the administration dashboard in CSV format: follows, lists, accounts you muted, accounts you blocked, and bookmarks.

You can now make your profile discoverable.

The profile page now shows an account's cover image if it has one.

Many bug fixes.

For the details, see also the full changelog.

You can upgrade to Hollo 0.4.0 using the following ways:

To Railway users: Just redeploy the Hollo service!

To Docker users: Switch your Hollo image to ghcr.io/dahlia/hollo:0.4.0 or simply latest!

To manual installers:

Install Node.js 23 or higher.

Install pnpm.

Fetch the stable branch and switch over to it.

Run pnpm install.

Run pnpm run prod to start the Hollo server.

0 0 1 View Post & Replies See Original

330d

I'm currently brainstorming a framework for creating fediverse bots called #BotKit, based on #Fedify. It's less flexible than Fedify, but the goal is to make it possible to create simple fediverse bots with much less code. What do you think?

#fedidev #ActivityPub

$import { createBot, mention, text } from "@fedify/botkit"; import { RedisKvStore } from "@fedify/redis"; import { Redis } from "ioredis"; // Create a bot instance: const bot = createBot({ // The bot will have fediverse handle "@greetbot@mydomain": username: "greetbot", // Set the profile icon (avatar): icon: new URL("https://mydomain/icon.png"), // Set the bio: bio: text`Hi, there! I'm a simple fediverse bot created by ${ mention("@hongminhee@hollo.social").}`, // Use Redis as a key-value store: kv: new RedisKvStore(new Redis()), // Use Redis as a message queue: queue: new RedisMessageQueue(() => new Redis()), }); // A bot can respond to a mention: bot.on(/hi|hello|what'?s\s+up/i, (ctx) => { return ctx.reply(text`Hi, ${ctx.actor}!`); }); // Or, a bot also can actively publish a post: setInterval(async () => { await bot.publish(text`Hi, forks! It's an hourly greeting.`); }, 1000 * 60 * 60); export default bot;$

ALT

2 0 1 View Post & Replies See Original

330d

I rather like the recent addition of likes/reposts on Federated wordpress blogs.

Before this add, you couldn't directly see how many likes/reblogs you had in the web interface. You had to dig. Now you don't, and it's quite nice.

#wordpress #ActivityPub #plugin #SelfHosted #blog

a screencap showing 16 reposts and 24 likes, with all the user icons in little overlapping circles displayed in a straight line, chronologically left to right from latest to oldest.

ALT

Edited 330d ago

0 0 1 View Post & Replies See Original

1d

🆕 blog! “Now witness the power of this fully operational Fediverse!”

How can you measure the popularity of a social network site? Perhaps by counting the number of active accounts, or the quality of the discourse, or even how many people reply to your witty memes.

Me? I prefer to look at how many people visit my blog…

1 0 1 View Post & Replies See Original

96d

Here's a thought, the more I make my blog compatible with the fediverse, at some point I can just use my blog instead of mastodon right? What would the benefit be to have a separate mastodon account? #fediverse #activitypub #mastodon

1 0 1 View Post & Replies See Original

103d

We'd like to recognize the valuable contributions from two developers who participated in Korea's #OSSCA (Open Source Contribution Academy) program. Both contributors identified important gaps in #Fedify's functionality and documentation, providing thoughtful solutions that benefit the broader #ActivityPub ecosystem.

@gaebalgom contributed PR #365, addressing issue #353 regarding NodeInfo parser compatibility, originally reported by @andypiper. The issue arose when Fedify incorrectly rejected #NodeInfo documents from snac instances due to overly strict version string parsing that required semantic versioning compliance. Their solution improves the fallback behavior in the parseSoftware() function to handle non-SemVer version strings by parsing dot-separated numbers and defaulting to zero for missing components. The implementation includes thorough test coverage for various edge cases, including single numbers (3), two-part versions (2.81), and malformed version strings. This fix provides immediate compatibility improvements across the fediverse while maintaining backward compatibility, and will be included in Fedify 1.9. The contribution serves as an interim solution, with a more comprehensive fix planned for Fedify 2.0 (issue #366), where the NodeInfo software.version field will be changed from the SemVer type to a plain string to fully comply with the NodeInfo specification.

@z9mb1 contributed PR #364, resolving issue #337 by adding practical examples for Fedify's custom collection dispatchers feature. Custom collections were introduced in Fedify 1.8 but lacked clear documentation for developers seeking to implement them. Their contribution provides a comprehensive example demonstrating how to set up custom collections for tagged posts, including proper routing patterns, pagination handling, and counter functionality. The example includes mock data structures, shows how to configure collection dispatchers with URL patterns like /users/{userId}/tags/{tag}, and demonstrates the complete request/response cycle using federation.fetch(). This work provides developers with a clear, runnable reference that reduces the complexity of implementing custom collections in ActivityPub applications.

We appreciate these meaningful contributions that help make Fedify more accessible and robust for the entire ActivityPub community.

#opensource #fedidev #fediverse

0 0 1 View Post & Replies See Original

269d

Fun! I like this style of these live streams, more casual and more focused on the person rather than just the code. Check it out.

https://stream.firesidefedi.live/federation/rUzol4tNR

#Fediverse #ActivityPub #FediDevs

0 0 1 View Post & Replies See Original

191d

Ω🪬Ω
#FediAlgo, the customizable timeline algorithm / filtering system for your Mastodon feed, is now deployed on Github Pages and can be used from your web browser.

* Link: https://michelcrypt4d4mus.github.io/fedialgo_demo_app_foryoufeed/
* Code: https://github.com/michelcrypt4d4mus/fedialgo_demo_app_foryoufeed
* Video of FediAlgo in action: https://universeodon.com/@cryptadamist/114395249311910522

#activitypub #algorithm #algorithmicFeed #algorithmicTimeline #Fedi #FediTips #FediTools #Fediverse #Feed #FOSS #Masto #MastoAdmin #Mastodon #mastohelp #MastoJS #nodejs #nod #opensource #SocialWeb #timeline #TL #webdev

Edited 182d ago

0 0 1 View Post & Replies See Original

1y

I believe the W3C should reconsider splitting the #ActivityPub Recommendation into three documents: Core/Shared requirements, S2S (Server-to-Server, "social/federation protocol"), and C2S (Client-to-Server, "social API"). I think it would reduce developer confusion and help them focus on requirements that are relevant to their work (typically, S2S/Core). It would also allow C2S to be improved independently so that more developers might consider using it.

0 0 1 View Post & Replies See Original

103d

Some recent #Smithereen updates:
- Finished discussion boards in groups
- Server rules (with translations)
- New reporting flow, almost like Mastodon's
- Moderators can now exclude content from reports
- ...as well as add extra content via the new "content" tab in user moderation UI
- Admins can now specify custom CSS for their server
- Admins can create announcements that display under the main menu for all users

#activitypub