Search results

Update: we've decided to go ahead and submit the CFP to @COSCUP 2026. The track will be called Fediverse & Social Web—think FOSDEM's Social Web devroom, but in Taipei. is free to attend, like FOSDEM.

If the track is accepted, would you be interested in coming to Taipei (Aug 8–9) to give a talk?

(Boosts appreciated!)

https://hollo.social/@hongminhee/019ca8b2-ecca-7150-a237-37f35de45401

0

Update: we've decided to go ahead and submit the CFP to @COSCUP 2026. The track will be called Fediverse & Social Web—think FOSDEM's Social Web devroom, but in Taipei. is free to attend, like FOSDEM.

If the track is accepted, would you be interested in coming to Taipei (Aug 8–9) to give a talk?

(Boosts appreciated!)

https://hollo.social/@hongminhee/019ca8b2-ecca-7150-a237-37f35de45401

0
2
0

Okey, so, and knowers: is there an established procedure for changing your server's domain?

I understand this case is (unfortunately) not covered by the protocol, and thus is not doable optimally. I don't care about that, I just want to know the closest to optimal method.

Is there some way to set up another instance on the new domain and migrate all the data over? Make some kinda redirect before ultimately abandoning the old domain some years down the road?

0
0

I've been meaning to finish my ActivityPub guide since I started the first draft back in June 2018.

Yeah, I got a bit busy with Pixelfed and my other projects, but I have been working on it periodically since then.

I really do think we have the advantage in many respects, and now we have fully featured AP SDKs like @fedifyFedify: ActivityPub server framework, now more than ever we need better dev resources and guides.

Can't wait to ship this!

ActivityPub.social preview, Understanding the Protocol guide
0

Unfortunately, was not selected for NLnet funding. It is disappointing, but I understand how competitive these calls are. As a fully independent project sustained entirely through community support, relies on patron support to cover its ongoing infrastructure and resource costs. That support now matters more than ever for the project’s future. ❤️

0
0
0
0

@applepine yes. I held this poll a couple days ago, with delightful results on the social experience of the current : Dispersed cozy villages with here and there a bustling city..

social.coop/@smallcircles/1161

That is a great outcome, and something to cherish and protect.

Currently I feel the slow growth of the fediverse is healthy and natural growth we can cope with. And being the lightning rod for corporate attention, borrows more time to mature and evolve.

The dynamics will totally change if the technology adoption lifecycle gets beyond early adopter phase, and 1,000's of commercial vendors start to launch products in this new market space that we, pioneers, made available to them.

The question is whether we can handle that. I think currently we cannot and we have to hand over fedi's fate to the market and hope for the best.

0
0
0
0

I mean, I see no reason why this wouldn't work. `alsoKnownAs` is an array of names.

I suppose if Alice is following both Bob and Chuck, then B & C are merged into Dave, she won't "double follow".

But I wonder if there are any other gotchas?

I have recently created and launched a new platform called Inkwell. It's designed to integrate with ActivityPub, using open-source code available on my GitHub. There is a lot of work to do, but I'm excited, as I loved online journaling as a kid. Now, having a space I can create as my own (with community feedback) is a dream come true. Here's hoping to others join us on Inkwell and become Pen Pals!

0

RE: w3c.social/@w3c/11621607036256

FWIW, I have been storing Linked Data (including ActivityPub) in an INI like format — because I find INI-like formats more human-friendly (to both read and write) than JSON.

YAML is probably better than JSON, too, in that respects. But I think INI-like formats are better than YAML.

0
0
3
0

I see the announcement by a commercial marketing agency of a venture capital based app store joining the fediverse.

Is the we have capable of avoiding as it grows and attracts an increasing number of corporations, who make it their market?

Is our landscape resistant to corporate capture and eventual takeover and domination? Just like the Corporate Web, also decentralized.

There are nice niches on the web, like a bloggosphere, bulletin boards, and news readers, that all still exist. But web as a whole is predominantly corporate, arguably not commons based, for the people by the people.

Social experience design defines "commons based" as "where people are in control of their future on a path of healthy evolution and natural growth". A core principle is being sustainable at all times, and timely acknowledge and mitigate risks.

Is fediverse commons based? Did we cocreate the Future of Social networking?

0
4
0
0
0
0

Big news for Mastodon GmbH. They have formally joined forces with the World Wide Web Consortium (W3C).

If you’re not in the design/tech world, trust me when I say this is a big step for the fediverse. The W3C establishes the standards used for the internet.

This is a solid path forward for small tech.

github.com/w3c/socialwg/blob/m

By the way. They announced this new working group back in January:

socialwebfoundation.org/2026/0

My original link was for the group’s kick-off meeting. I should have linked to the announcement as well.

I hope it went well, @dariusDarius Kazemi! Thanks for being the chair. 👏🏻

0

I've been thinking about adding federation health monitoring to —not as a separate data store or custom API, but by extending the existing integration. The idea is to expose delivery outcomes, signature verification failures, and per-remote-host error rates as OpenTelemetry metrics alongside the spans Fedify already emits. If you already have a Prometheus or Grafana setup, you'd get federation observability basically for free. Circuit breaker behavior (temporarily skipping a remote server that's been consistently unreachable) could surface as OpenTelemetry events, keeping everything in the same trace context rather than scattered across separate logs.

Does this sound useful to you? I'm curious whether people building on Fedify—or running federated servers in general—would actually reach for this, and what kinds of things you'd most want to observe. Happy to hear any thoughts.

0

Release v3.3.3 of Ktistec

Todd Sundsted @toddsundsted@epiktistes.com

I have started work on a Mastodon-compatible API layer intended to support the many Mastodon front-ends available. It is incomplete and requires an explicit build flag to enable, but what's there (the main timeline) already works with the official Mastodon app, Tusky, and Phanpy.

Here's the full changelog:

Fixed

  • Editor focus now stays in the editor after the first draft is saved. (fixes #139)
  • Filter settings instructions. (fixes #135)

Changed

  • Improved consistency of mini button colors.

As always, check out the full diff for the complete details.

#ktistec #crystallang #activitypub #fediverse

Read more →
0

ap, the ActivityPub API command-line client

Evan Prodromou @evanprodromou@socialwebfoundation.org

As part of my book "ActivityPub: Programming for the Social Web", I created a coding example to show how to program for the ActivityPub API. ap is a command-line client, written in Python, for doing basic tasks with ActivityPub.For example, you can log into a server using this command: ap login yourname@yourserver.example Once you're logged in, you can follow someone: ap follow other@different.example Or, you could post some content: ap create note --public "Hello, World" This isn't […]

Read more →
0
0
10
0
0

#ActivityPub support in #Madblog

https://blog.fabiomanganiello.com/article/Madblog-federated-blogging-from-markdown

I am glad to announce that Madblog has now officially joined the #Fediverse family.

If you want to test it out, search for this URL on your Fediverse client.

Madblog has already supported #Webmentions for the past couple of weeks, allowing your blog posts to be mentioned by other sites with Webmentions support (WordPress, Lemmy, HackerNews…) and get those mentions directly rendered on your page.

It now adds ActivityPub support too, using #Pubby, another little Python library that I’ve put together myself (just like Webmentions) as a mean to quickly plug ActivityPub support to any Python Web app.

Webmentions and Pubby follow similar principles and implement a similar API, and you can easily use them to add federation support to your existing Web applications - a single bind_webmentions or bind_activitypub call to your existing Flask/FastAPI/Tornado application should suffice for most of the cases.

Madblog may have now become the easiest way to publish a federated blog - and perhaps the only way that doesn’t require a database, everything is based on plain Markdown files.

If you have a registered domain and a certificate, then hosting your federated blog is now just a matter of:

mkdir -p ~/madblog/markdown
cat <<EOF > ~/madblog/markdown/hello-world.md
# My first post

This is my first post on [Madblog](https://git.fabiomanganiello.com/madblog)!
EOF

docker run -it \
  -p 8000:8000 \
  -v "$HOME/madblog:/data" \
  quay.io/blacklight/madblog

And Markdown files can be hosted wherever you like - a Git folder, an Obsidian Vault, a Nextcloud Notes installation, a folder on your phone synchronized over SyncThing…

Federation support is also at a quite advanced state compared to e.g. #WriteFreely. It currently supports:

  • Interactions rendered on the articles: if you like, boost, quote or reply to an article, all interactions are rendered directly at the bottom of the article (interactions with WriteFreely through federated accounts were kind of lost in the void instead)

  • Guestbook support (optional): mentions to the federated Madblog handle that are not in response to articles are now rendered on a separate /guestbook route

  • Email notifications: all interactions can have email notifications

  • Support for quotes, also on Mastodon

  • Support for mentions, just drop a @joe@example.com in your Markdown file and Joe will get a notification

  • Support for hashtag federation

  • Support for split-domain configurations, you can host your blog on blog.example.com but have a Fediverse handle like @blog@example.com. Search by direct post URL on Mastodon will work with both cases

  • Support for custom profile fields, all rendered on Mastodon, with verification support

  • Support for moderation, either through blocklist or allowlist, with support for rules on handles/usernames, URLs, domains or regular expressions

  • A partial (but comprehensive for the provided features) implementation of the Mastodon API

If you want you can follow both the profiles of my blogs - they are now both federated:

  • My personal blog: @fabio (it used to run WriteFreely before, so if you followed it you may need to unfollow it and re-follow it)

  • The #Platypush blog: @blog

0
0
4
0
0

Hmm.. In case you're wondering which topics could be discussed on an unconference about fediverse integration in/for public institutions...
check out this preliminary overview:
fedivariety.org/noaw-session-p

wow... all kinds of topics still to be shaken *and* stirred at noaw.org of course—looking fwd!

0

Introducing PortaFed — cryptographic account portability for

When your server shuts down, your identity and posts are gone.
PortaFed fixes this with a MigrationProof: a Merkle commitment
over your full export, signed by your ed25519 key, verifiable
by any destination server without contacting the origin.

No blockchain. No registry. No core spec changes.

Spec + Rust implementation:
codeberg.org/portafed/portafed

Feedback welcome — especially from server maintainers.

0

😲…I just realized is in the *same* venue as just *3* days before FOSSY starts!

I'm sad we weren't all in touch as maybe together we coulda gotten a better venue deal, but I hope folks going to event will be able stay in Vancouver for FOSSY!

Also, I suspect would welcome a Fediverse track at FOSSY…
sfconservancy.org/fossy/commun
…maybe as a B-sides event for overflow talks?

Cc: @reiver@reiver ⊼ (Charles) :batman: @evanEvan Prodromou @ossguyDenver Gingerich @karenKaren Sandler

0
0
11
0

Every day I’m more convinced that the Fediverse’s slow mainstream adoption isn’t really about usability.

People say it’s because it’s hard to join, the terms are confusing, or the apps aren’t polished enough. Maybe a little. But honestly… look at the platforms people already use.

Finding anything on LinkedIn is painful.
Trying to locate the original video on TikTok is a scavenger hunt.
Facebook is still full of weird bugs and odd UI choices.
Instagram hides posts behind algorithms.
Twitter/X constantly changes the rules of engagement.

None of these platforms are exactly “easy.”

People stay because their friends are there. Because the big creators are there. Because that’s where the conversation already lives.

And, if we’re honest, because these platforms are engineered around a very effective reward loop: notifications, likes, infinite scroll. A dopamine machine. You learn the confusing terms and awkward interfaces because there’s a constant reward for doing so.

So yes, making the Fediverse easier to join absolutely helps.

But what would help even more is something simpler:
more mainstream, recognizable, official accounts showing up here.

That’s how networks grow.
People follow people not platforms.

0
5
0

With ActivityPub / ActivityStreams...

To me, it feels like there should have been something that is a common parent of both 'Object' and 'Link'.

That just had the "name", "nameMap", and "preview" fields (along with "id" and "type, of course) — since that is what 'Object' and 'Link' share in common.

I'll just call this common parent: 'Entity'.

...

It could have even been an opportunity to talk about how to handle unknown types.

0

Hello ! 🐘

I'm the founder of Synapse Labs, and we're building the infrastructure layer for the "Agentic Web." 🏗️

We focus on 0ms dedicated relays for @base and Farcaster to solve hub latency for AI agents. Also working on Volenti Partners for on-chain consent verification.

Looking to connect with devs, builders, and anyone obsessed with . 🧠⚡️

0
0
0

I wish was a "pull" protocol instead of a "push" protocol. The way it works, whenever you take an action, it sends that action to all followers. I would prefer if it simply stored them and then let each follower pull them when they see fit.

That would introduce latency and more async comms as your messages wouldn't pop up into someone elses feed until their software fetch the data, but I think it would make it easier to self host.

@soapdog There's a poll-based version specced at fediverse.codeberg.page/fep/fe, sadly with no notable implementations (wouldn't be interactable by Mastodon etc.), but it's an opportunity to break new ground as an implementer if you know anyone who'd like to experiment with it.

0

I wish was a "pull" protocol instead of a "push" protocol. The way it works, whenever you take an action, it sends that action to all followers. I would prefer if it simply stored them and then let each follower pull them when they see fit.

That would introduce latency and more async comms as your messages wouldn't pop up into someone elses feed until their software fetch the data, but I think it would make it easier to self host.

0

Hey friends. Are there any new ActivityPub / Mastodon features I should add to ?

It's a small bot-only ActivityPub server in a single PHP file.

gitlab.com/edent/activity-bot/

It can be followed, post images, allow quote posts, etc.

Is there anything else you would like a bot-server to be able to do?

0
3
0

I'm thinking of proposing a /social web community track at @COSCUP 2026 (Aug 8–9, Taipei)—think FOSDEM's Social Web devroom, but in East Asia. Before I submit the CFP, I'd love to get a sense of what to call it. What do you think?

(Boosts appreciated!)

@hongminhee洪 民憙 (Hong Minhee) :nonbinary: @COSCUP

As you know I am proponent to emphasize the social aspects more, to drive healthy evolution of the .

The app-centric is a pure technosphere, where a tech-first approach deals with getting app features to the next app, and the protocol matures via post-facto 'follow-the-leader' . What happens in the sociosphere between people using the tech is de-facto of secondary concern, and apps are tweaked to try to deal with externalities. The resulting social landscape has become one of neighboring app kingdoms with guarded borders separating them. Everyone speaks microblog to each other, albeit with thick accents, hard to understand. The fediverse is social *because* of the people, and despite of the tech, that still severely restrains them.

It would be nice if the track name not just indicated a technology name. E.g. coding.social uses:

- Fediverse, a peopleverse
-
-

0
0

I'm thinking of proposing a /social web community track at @COSCUP 2026 (Aug 8–9, Taipei)—think FOSDEM's Social Web devroom, but in East Asia. Before I submit the CFP, I'd love to get a sense of what to call it. What do you think?

(Boosts appreciated!)

0
2
0
0
0
0

@django @liaizonwakest ⁂ @voboda

Thank you, I really like the article. It describes a whole bunch of activities and consideration where Social experience design evolves methodical solution development practices.

A social experience can be seen as "how people experience a solution" and this includes how that solution interacts with other solutions these people were already exposed to i.e. it accounts for the externalities of technology introduction. Social experiences work at different scales which design perspectives account for:

coding.social/blog/reimagine-s

An issue on the app-centric fedi is that app devs have a technical view of the fediverse, while 'fedizens' have a social one, leading to expectation mismatches. Apps are typically developed for 2 stakeholders: "Users" and the devs themselves (the de-facto owners of 'app-space').

While feature driven app-focused design may improve social experience for app users, it pays insufficient attention to the overall experience of the fediverse.

SX Pyramid of Perspective has 3 layers. The bottom layer starts with the individual perspective where personal needs are satisfied as social activities take place. The layer above focuses on inter-personal perspective where social relationship are formed into a social graph. The top of the pyramid shows the societal perspective where solutions are designed to have societal imprint and may affect entire societal constructs.

@django @liaizonwakest ⁂ @voboda

When looking through the lens of Social experience design we can say that the fediverse-we-have and the social network promise in the W3C specs, have become diverged to the extent they are hard forks.

A solution is said to exist as soon as you can write it down on a sticky note in the form of a vision, need, objective, or solution.

The AS/AP fediverse sticky note reads: "The future of social networking is decentralized".

The fediverse-we-have note reads: "Decentralized microblogging"

Besides that both sticky notes express a tech focus, exist in the technosphere not sociosphere, they express no vision.. A place where we want to be, and why. There is complete misconception both on technical, let alone social direction, and that leads to endless confusion and again those mismatched expectations.

App devs now try to hammer their apps onto "Decentralized microblogging" in hopes "future of social networking" somehow emerges. That is unlikely.

0