#ActivityPub platform feature want: similar to "no boosts" from accounts followed, do not see their replies to people on domains you have blocked.

Presumably, if you have decided an entire domain's worth of accounts should never appear in your feed or receive your own emanations, you have reasons. Which are probably offended seeing an account you *do* follow having exactly the kind of conversation you are avoiding experiencing directly.

The official FitPub Matrix Space is now available! 🥳

Join the community to discuss about FitPub, get support, contribute to development, or connect with instance maintainers.

The space includes dedicated rooms for:

📢 Announcements
💬 Users
⚙️ Maintainers
🛠️ Developers

Join here: https://matrix.to/#/#fitpub:matrix.org

Help us build a vibrant FitPub community. We'd love to see you there!

#FitPub #Matrix #Fediverse #ActivityPub #OpenSource

The official FitPub Matrix Space is now available! 🥳

Join the community to discuss about FitPub, get support, contribute to development, or connect with instance maintainers.

The space includes dedicated rooms for:

📢 Announcements
💬 Users
⚙️ Maintainers
🛠️ Developers

Join here: https://matrix.to/#/#fitpub:matrix.org

Help us build a vibrant FitPub community. We'd love to see you there!

#FitPub #Matrix #Fediverse #ActivityPub #OpenSource

Another Mastodon weirdness: somebody responded to one of my posts, but it didn't show up in my notifications.

I had to go to my original post and check the responses to see it?!

#mastodon #mastoadmin #mastolivre #fediverse #usability #federation #bug #error #fail #ux #activitypub #notifications

A technical #ActivityPub question for a Sunday: is it possible/desirable to have every Actor on an instance share the same key pair?

I'm building something vaguely in the vein of FediMeteo, where all the accounts are automated and you'd generally follow one of those automated accounts to get the weather for your locality. Now, FediMeteo has a different key pair for each account, so the bot for Birmingham's weather has a different public key to Manchester.

But it's not a requirement that each account has a unique key, if the keys are only used for signature verification, right? Like, I don't think it'd be a security issue if "Weather for Birmingham" was signed with the key from "Weather for Manchester".

My question: is this another one of my Sunday Bad Ideas, and I should really have a key pair per account instead of trying to have the whole instance share?

A friend of mine is working on a cool project ofor his master thesis in digital humanities: a federated calendar software based on #activitypub
The idea would be to have a system specifically to share and push events on the federated network!
I love the idea, and I can definitely see it being a great way to organize both local and decentralized communities.

https://github.com/burnoutberni/everycal

A friend of mine is working on a cool project ofor his master thesis in digital humanities: a federated calendar software based on #activitypub
The idea would be to have a system specifically to share and push events on the federated network!
I love the idea, and I can definitely see it being a great way to organize both local and decentralized communities.

https://github.com/burnoutberni/everycal

Installed #yunohost yesterday on my Proxmox home server to fiddle around and was about to deploy #GoToSocial. But this "Danger" Box in the docs, saying the domain will be taken forever by this instance of GTS scares me. Or is this the case for every #ActivityPub Server anyway?

I thought, only the full handle like "@user@social.domain.net" can be problematic when being refused because of caching and generated keys. Any experience with that? https://docs.gotosocial.org/en/v0.22.0/getting_started/

#selfhosting

Loops + Direct Messages

Shipping soon 🎉

#loops #directMessages #activityPub

Summer is the worst season for animals. As the holidays get closer, shelters fill with pets left behind.

My cat and dog came from there. Haru (the cat) waited two years in a shelter, and our dog (Tanos) is one a relative could no longer keep. A black cat and a malinois, now sharing the same stairs.

Out of conviction, I built https://pawfed.org/how-it-works, a service working with #ActivityPub and #OSM.

It is not the perfect solution, but if you can help your local shelter, please do.

Installed #yunohost yesterday on my Proxmox home server to fiddle around and was about to deploy #GoToSocial. But this "Danger" Box in the docs, saying the domain will be taken forever by this instance of GTS scares me. Or is this the case for every #ActivityPub Server anyway?

I thought, only the full handle like "@user@social.domain.net" can be problematic when being refused because of caching and generated keys. Any experience with that? https://docs.gotosocial.org/en/v0.22.0/getting_started/

#selfhosting

@strypey @rl_dane

Btw, I am keeping a list for myself on projects that enter the fediverse that use AI and/or are proprietary. I see these as risk factors to trigger unwanted corporate interest when they demonstrate there's open market space in the new niches they are exploring. And able to do that very quickly with LLM help, or more smartly (than the average FOSS project) with an enterpreneurial mindset.

And the weird thing is.. there is another Harmony project with a similar but different codebase and different website. And this one has #ActivityPub support. It is also AI-coded (project was at v1.2 when the repo was only 2 weeks old, with a huge codebase):

https://mony.lol

https://github.com/y4my4my4m/harmony

#TIL about #Harmony, a bleeding-edge project to build a decentralised replacement for Miscord using ActivityPub, E2EE using Vodozemac, a cryptography library used in Matrix software;

https://joinharmony.app/

Source code is on GritHub, under AGPL;

https://github.com/zcharef/harmony

Anyone know anything about this? So far I haven't been able to find fediverse accounts for the project itself, or the creator.

#fediverse #ActivityPub #Vodozemac #Matrix

Week in Fediverse 2026-07-17

Servers

- flohmarkt v0.20.0
- Vernissage Server v1.40.0
- FitPub v1.2.0
- Wafrn v2026.07.02
- TinyAP v0.1.11
- NeoDB v0.16.5.0
- PieFed v1.7.6
- Catodon v26.7.0
- Trunk & Tidbits, June 2026 (Mastodon)
- matrix-appservice-activitypub: Turns your Matrix server into a fully functioning ActivityPub server
- Discord–Fediverse Bridge: A self-hosted bridge between Discord forum channels and ActivityPub community actors
- ~petersanchez/honk: Fork of honk

Clients

- PeerTube Mobile v2.2.0
- Photon v2.4.0
- Tesseract v1.5.5
- Aria v1.5.8
- Mitra Mini v0.5.0

Tools and Plugins

- Enable Mastodon Apps v1.6.1 (WordPress plugin)
- Polls for ActivityPub v1.0.9 (WordPress plugin)
- Telegram ↔️ Mastodon Bridge Bot: A Python bot that forwards text messages, photos, and albums from a Telegram chat to your Mastodon account

For developers

- @shootpub/activitypub-types: ActivityPub types package with support for FEP-2277 Activitypub core types (duck typing)

Articles

- The Long Tail of Work Left Until ActivityPub Has E2EE

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/019f4de5-e808-73f3-96d7-1c4948c2a47a

Week in Fediverse 2026-07-17

Servers

- flohmarkt v0.20.0
- Vernissage Server v1.40.0
- FitPub v1.2.0
- Wafrn v2026.07.02
- TinyAP v0.1.11
- NeoDB v0.16.5.0
- PieFed v1.7.6
- Catodon v26.7.0
- Trunk & Tidbits, June 2026 (Mastodon)
- matrix-appservice-activitypub: Turns your Matrix server into a fully functioning ActivityPub server
- Discord–Fediverse Bridge: A self-hosted bridge between Discord forum channels and ActivityPub community actors
- ~petersanchez/honk: Fork of honk

Clients

- PeerTube Mobile v2.2.0
- Photon v2.4.0
- Tesseract v1.5.5
- Aria v1.5.8
- Mitra Mini v0.5.0

Tools and Plugins

- Enable Mastodon Apps v1.6.1 (WordPress plugin)
- Polls for ActivityPub v1.0.9 (WordPress plugin)
- Telegram ↔️ Mastodon Bridge Bot: A Python bot that forwards text messages, photos, and albums from a Telegram chat to your Mastodon account

For developers

- @shootpub/activitypub-types: ActivityPub types package with support for FEP-2277 Activitypub core types (duck typing)

Articles

- The Long Tail of Work Left Until ActivityPub Has E2EE

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/019f4de5-e808-73f3-96d7-1c4948c2a47a

Summer is the worst season for animals. As the holidays get closer, shelters fill with pets left behind.

My cat and dog came from there. Haru (the cat) waited two years in a shelter, and our dog (Tanos) is one a relative could no longer keep. A black cat and a malinois, now sharing the same stairs.

Out of conviction, I built https://pawfed.org/how-it-works, a service working with #ActivityPub and #OSM.

It is not the perfect solution, but if you can help your local shelter, please do.

Summer is the worst season for animals. As the holidays get closer, shelters fill with pets left behind.

My cat and dog came from there. Haru (the cat) waited two years in a shelter, and our dog (Tanos) is one a relative could no longer keep. A black cat and a malinois, now sharing the same stairs.

Out of conviction, I built https://pawfed.org/how-it-works, a service working with #ActivityPub and #OSM.

It is not the perfect solution, but if you can help your local shelter, please do.

Big news for Org Social! 🎉 The Relay now has bridges: you can follow Mastodon (ActivityPub) accounts and RSS/Atom feeds directly from any Org Social client.

A bridge is a virtual social.org feed generated by the Relay. Just add its URL to your follow list like any other feed:

Follow a Mastodon account:
https://relay.org-social.org/bridge/activitypub/@mastodon@mastodon.social/

Follow an RSS feed (e.g. xkcd):
https://relay.org-social.org/bridge/rss/?url=https%3A%2F%2Fxkcd.com%2Frss.xml

Docs: https://github.com/tanrax/org-social/blob/main/README.md#follow-a-mastodon-account-or-an-rss-feed

#OrgSocial #ActivityPub #Fediverse #RSS #IndieWeb

While most of you know my main account for #Fedilab, months ago I wanted to work on something new.
Being able to publish this code in production is an important step for me.
Yes, it is possible to run an #ActivityPub server on your phone, with #E2EE DMs and a portable identity.
And you are no longer tied to a single model like text, media or video. No need for separate apps: one account does it all, and you switch in one tap. Only your device owns the data, and the rules are on your side.

While most of you know my main account for #Fedilab, months ago I wanted to work on something new.
Being able to publish this code in production is an important step for me.
Yes, it is possible to run an #ActivityPub server on your phone, with #E2EE DMs and a portable identity.
And you are no longer tied to a single model like text, media or video. No need for separate apps: one account does it all, and you switch in one tap. Only your device owns the data, and the rules are on your side.

Week in Fediverse 2026-07-17

Servers

- flohmarkt v0.20.0
- Vernissage Server v1.40.0
- FitPub v1.2.0
- Wafrn v2026.07.02
- TinyAP v0.1.11
- NeoDB v0.16.5.0
- PieFed v1.7.6
- Catodon v26.7.0
- Trunk & Tidbits, June 2026 (Mastodon)
- matrix-appservice-activitypub: Turns your Matrix server into a fully functioning ActivityPub server
- Discord–Fediverse Bridge: A self-hosted bridge between Discord forum channels and ActivityPub community actors
- ~petersanchez/honk: Fork of honk

Clients

- PeerTube Mobile v2.2.0
- Photon v2.4.0
- Tesseract v1.5.5
- Aria v1.5.8
- Mitra Mini v0.5.0

Tools and Plugins

- Enable Mastodon Apps v1.6.1 (WordPress plugin)
- Polls for ActivityPub v1.0.9 (WordPress plugin)
- Telegram ↔️ Mastodon Bridge Bot: A Python bot that forwards text messages, photos, and albums from a Telegram chat to your Mastodon account

For developers

- @shootpub/activitypub-types: ActivityPub types package with support for FEP-2277 Activitypub core types (duck typing)

Articles

- The Long Tail of Work Left Until ActivityPub Has E2EE

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/019f4de5-e808-73f3-96d7-1c4948c2a47a

Big news for Org Social! 🎉 The Relay now has bridges: you can follow Mastodon (ActivityPub) accounts and RSS/Atom feeds directly from any Org Social client.

A bridge is a virtual social.org feed generated by the Relay. Just add its URL to your follow list like any other feed:

Follow a Mastodon account:
https://relay.org-social.org/bridge/activitypub/@mastodon@mastodon.social/

Follow an RSS feed (e.g. xkcd):
https://relay.org-social.org/bridge/rss/?url=https%3A%2F%2Fxkcd.com%2Frss.xml

Docs: https://github.com/tanrax/org-social/blob/main/README.md#follow-a-mastodon-account-or-an-rss-feed

#OrgSocial #ActivityPub #Fediverse #RSS #IndieWeb

Week in Fediverse 2026-07-17

Servers

- flohmarkt v0.20.0
- Vernissage Server v1.40.0
- FitPub v1.2.0
- Wafrn v2026.07.02
- TinyAP v0.1.11
- NeoDB v0.16.5.0
- PieFed v1.7.6
- Catodon v26.7.0
- Trunk & Tidbits, June 2026 (Mastodon)
- matrix-appservice-activitypub: Turns your Matrix server into a fully functioning ActivityPub server
- Discord–Fediverse Bridge: A self-hosted bridge between Discord forum channels and ActivityPub community actors
- ~petersanchez/honk: Fork of honk

Clients

- PeerTube Mobile v2.2.0
- Photon v2.4.0
- Tesseract v1.5.5
- Aria v1.5.8
- Mitra Mini v0.5.0

Tools and Plugins

- Enable Mastodon Apps v1.6.1 (WordPress plugin)
- Polls for ActivityPub v1.0.9 (WordPress plugin)
- Telegram ↔️ Mastodon Bridge Bot: A Python bot that forwards text messages, photos, and albums from a Telegram chat to your Mastodon account

For developers

- @shootpub/activitypub-types: ActivityPub types package with support for FEP-2277 Activitypub core types (duck typing)

Articles

- The Long Tail of Work Left Until ActivityPub Has E2EE

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/019f4de5-e808-73f3-96d7-1c4948c2a47a

Check out https://rel.re #relre if you are looking for a strong #activitypub #relay , I'm constantly trying to improve it or find quirks of specific relaying implementations to support as many AP services as possible (that do relaying). tor onion relaying also possible. (oh now that i think about it, ill generate a tor onion link for relre)

Check out https://rel.re #relre if you are looking for a strong #activitypub #relay , I'm constantly trying to improve it or find quirks of specific relaying implementations to support as many AP services as possible (that do relaying). tor onion relaying also possible. (oh now that i think about it, ill generate a tor onion link for relre)

Check out https://rel.re #relre if you are looking for a strong #activitypub #relay , I'm constantly trying to improve it or find quirks of specific relaying implementations to support as many AP services as possible (that do relaying). tor onion relaying also possible. (oh now that i think about it, ill generate a tor onion link for relre)

I'm adding support for multiple public keys per actor in Smithereen for future-proofing purposes. Are there any signature algorithms other than RSA currently in use on the fediverse? ECDSA maybe?

#ActivityPub #mastodev

Made a lot of progress on the #FedBOX test containers setup.

We now can have moderately complicated testing setups that will soonishly replace the old integration tests.

#ActivityPub

Made a lot of progress on the #FedBOX test containers setup.

We now can have moderately complicated testing setups that will soonishly replace the old integration tests.

#ActivityPub

I'm adding support for multiple public keys per actor in Smithereen for future-proofing purposes. Are there any signature algorithms other than RSA currently in use on the fediverse? ECDSA maybe?

#ActivityPub #mastodev

FitPub is a new fitness tracking platform for the Fediverse, sort of an alternative to Strava. You can follow their official account for more news:

➡️ @fitpub

There are also more details on FitPub's Codeberg page:

➡️ https://codeberg.org/fitpub/fitpub

(To avoid confusion, FitPub is a totally separate project to the Fediverse trail and journey tracker Wanderer, which you can find out more about at https://wanderer.to )

#Fitness #FitnessTracker #Fediverse #ActivityPub #FitPub #Strava #Alternatives

FitPub is a new fitness tracking platform for the Fediverse, sort of an alternative to Strava. You can follow their official account for more news:

➡️ @fitpub

There are also more details on FitPub's Codeberg page:

➡️ https://codeberg.org/fitpub/fitpub

(To avoid confusion, FitPub is a totally separate project to the Fediverse trail and journey tracker Wanderer, which you can find out more about at https://wanderer.to )

#Fitness #FitnessTracker #Fediverse #ActivityPub #FitPub #Strava #Alternatives

FitPub is a new fitness tracking platform for the Fediverse, sort of an alternative to Strava. You can follow their official account for more news:

➡️ @fitpub

There are also more details on FitPub's Codeberg page:

➡️ https://codeberg.org/fitpub/fitpub

(To avoid confusion, FitPub is a totally separate project to the Fediverse trail and journey tracker Wanderer, which you can find out more about at https://wanderer.to )

#Fitness #FitnessTracker #Fediverse #ActivityPub #FitPub #Strava #Alternatives

Preparing a new Loops release, possibly related to my upcoming FediCon talk!

I can't stop smiling. 😁

#Loops #FediCon #ActivityPub #W3C

Preparing a new Loops release, possibly related to my upcoming FediCon talk!

I can't stop smiling. 😁

#Loops #FediCon #ActivityPub #W3C

@tomootes @jelte @DigitaleOverheid @Gina

To those not aware I would like to point out two relevant @forgejo locations where contributions can be readily made..

The delightful #forgejo curated list, where #FOSS contributions can be added via a PR or by creating a new issue in the repo's issue tracker:

https://delightful.coding.social/delightful-forgejo/

And the forgejo-contrib organization, where among others the #ActivityPub based forge federation project is taking shape:

https://codeberg.org/forgejo-contrib/federation/

Related to the latter, I'd also like to give attention to the #ForgeFed ActivityPub protocol extension, which is really promising but needs an impetus from the community to bring the specifications to a higher level of maturity, and get good reference implementations to help open standard adoption:

https://forgefed.org
cc @forgefed

@tomootes @jelte @DigitaleOverheid @Gina

To those not aware I would like to point out two relevant @forgejo locations where contributions can be readily made..

The delightful #forgejo curated list, where #FOSS contributions can be added via a PR or by creating a new issue in the repo's issue tracker:

https://delightful.coding.social/delightful-forgejo/

And the forgejo-contrib organization, where among others the #ActivityPub based forge federation project is taking shape:

https://codeberg.org/forgejo-contrib/federation/

Related to the latter, I'd also like to give attention to the #ForgeFed ActivityPub protocol extension, which is really promising but needs an impetus from the community to bring the specifications to a higher level of maturity, and get good reference implementations to help open standard adoption:

https://forgefed.org
cc @forgefed

FitPub 1.2.0 is here!

This release brings finer privacy controls, local visibility, commutes, a major federation rewrite, improved profiles, verified email changes, durable email delivery, and a much more capable admin area for users, federation queues, logs, diagnostics, and monitoring.

It also includes extensive reliability, security, performance, and UX improvements.

Full release notes:
https://codeberg.org/fitpub/fitpub/releases/tag/1.2.0

#FitPub #ActivityPub #Fediverse #SelfHosting #OpenSource #DigitalSovereignty

FitPub 1.2.0 is here!

This release brings finer privacy controls, local visibility, commutes, a major federation rewrite, improved profiles, verified email changes, durable email delivery, and a much more capable admin area for users, federation queues, logs, diagnostics, and monitoring.

It also includes extensive reliability, security, performance, and UX improvements.

Full release notes:
https://codeberg.org/fitpub/fitpub/releases/tag/1.2.0

#FitPub #ActivityPub #Fediverse #SelfHosting #OpenSource #DigitalSovereignty

#ThoughtProvoker 🤔

#Fediverse is a *social* network, right? About being different from corporate anti-social media. Has ambitions to be more diverse, inclusive, cohesive. To provide inter-community social networking where people with similar interests find each other and interact.

Like the #ActivityPub developer community, for instance. The group of people who make all this possible in the first place. Together they uphold the fediverse technology ecosystem and are collectively responsible for evolving it. They chose fediverse as their communication medium, dogfooding their creations, even though this comes with its disadvantages. #Microblogging is ephemeral and fleety and discussions are dispersed and fragmented. There are clear points of improvements for the #fedi, frequently discussed.

What's very odd is that most AP devs hardly:

1. Engage with other AP devs posts.
2. Boost each other's msgs for visibility.
3. Use hashtags for discoverability.

Low-hanging fruit for improvement?

This week, we cover the writing layer of the fediverse: Ghost, WriteFreely, Micro.blog, Plume, WordPress, and Flipboard. Text was ActivityPub's first real workload, but these platforms didn't all arrive at federation the same way.

Ghost: a UK non-profit that funds Fedify (by @hongminhee) the framework its federation is built on. it's a publisher and a fediverse client at once, with an inbox as well as an outbox. Our newsletter is also powered by it, so @index is followable from any Mastodon app right now.

WriteFreely: one primary maintainer, Matt Baer (@matt), roughly 1,400 of 1,900+ commits, going since 2015. Funded by his own hosted product, Write.as.

Micro.blog: a Kickstarter By Manton Reese (@manton) that funded the platform before it had a single user. POSSE, native ActivityPub, and native Bluesky, no bridge.

Plume: a simple platform that also supported collaborative multi-author blogs. But no longer actively developed - it recommends WriteFreely and WordPress instead of itself.

WordPress: built-in ActivityPub (using plugin by Matthias Pfefferle - @pfefferle) plus a native AT Protocol plugin and real moderation tooling.

Flipboard: curating other people's writing rather than hosting its own.

Part 3 of the "Fediverse Beyond Mastodon" series.

https://federatedmind.com/the-written-fediverse/?utm_source=mastodon&utm_medium=social&utm_campaign=fediverse-beyond-mastodon-3

#Fediverse #ActivityPub #Ghost #WriteFreely #MicroBlog #WordPress #OpenWeb #Blogging

#ThoughtProvoker 🤔

#Fediverse is a *social* network, right? About being different from corporate anti-social media. Has ambitions to be more diverse, inclusive, cohesive. To provide inter-community social networking where people with similar interests find each other and interact.

Like the #ActivityPub developer community, for instance. The group of people who make all this possible in the first place. Together they uphold the fediverse technology ecosystem and are collectively responsible for evolving it. They chose fediverse as their communication medium, dogfooding their creations, even though this comes with its disadvantages. #Microblogging is ephemeral and fleety and discussions are dispersed and fragmented. There are clear points of improvements for the #fedi, frequently discussed.

What's very odd is that most AP devs hardly:

1. Engage with other AP devs posts.
2. Boost each other's msgs for visibility.
3. Use hashtags for discoverability.

Low-hanging fruit for improvement?

I've added several features to my #ActivityPub C2S (Social API) Server testing tool. There's now an embedded automated test runner, the ability to create and post ActivityPub objects using schema-based forms or JSON templates, a server capability report, server capability JSON export (for custom reports), and an optional sidecar server for analyzing CORS issues.

Thanks to NLNet for funding parts of this tool.

https://github.com/steve-bate/activitypub-c2s-toolkit

I've added several features to my #ActivityPub C2S (Social API) Server testing tool. There's now an embedded automated test runner, the ability to create and post ActivityPub objects using schema-based forms or JSON templates, a server capability report, server capability JSON export (for custom reports), and an optional sidecar server for analyzing CORS issues.

Thanks to NLNet for funding parts of this tool.

https://github.com/steve-bate/activitypub-c2s-toolkit

The Long Tail of Work Left Until #ActivityPub Has #E2EE

#fediverse
https://soatok.blog/2026/07/15/the-long-tail-of-work-left-until-activitypub-has-e2ee/

The Long Tail of Work Left Until #ActivityPub Has #E2EE

#fediverse
https://soatok.blog/2026/07/15/the-long-tail-of-work-left-until-activitypub-has-e2ee/

#ActivityPub carries posts, follows, likes and so on, but not moderation. A ban stays trapped on the instance that issued it. So, for instance, an account banned for racism on one instance stays unknown to the next. Moderation is activity too, and it should travel like the rest: signed and verifiable. This is a real problem, and others have explored it already. I will look into what already exists and see what we could build on for #HolosSocial.

#ThoughtProvoker 🤔

#Fediverse is a *social* network, right? About being different from corporate anti-social media. Has ambitions to be more diverse, inclusive, cohesive. To provide inter-community social networking where people with similar interests find each other and interact.

Like the #ActivityPub developer community, for instance. The group of people who make all this possible in the first place. Together they uphold the fediverse technology ecosystem and are collectively responsible for evolving it. They chose fediverse as their communication medium, dogfooding their creations, even though this comes with its disadvantages. #Microblogging is ephemeral and fleety and discussions are dispersed and fragmented. There are clear points of improvements for the #fedi, frequently discussed.

What's very odd is that most AP devs hardly:

1. Engage with other AP devs posts.
2. Boost each other's msgs for visibility.
3. Use hashtags for discoverability.

Low-hanging fruit for improvement?

Loops now supports enforcing AI, Ad and NSFW labels on videos from specific accounts (local + remote), with the ability to backfill the labels!

https://github.com/joinloops/loops-server/commit/e2e72f4b874b97b4bb09ed7f6c5f609210fd261b

#loops #moderation #activitypub

#ActivityPub carries posts, follows, likes and so on, but not moderation. A ban stays trapped on the instance that issued it. So, for instance, an account banned for racism on one instance stays unknown to the next. Moderation is activity too, and it should travel like the rest: signed and verifiable. This is a real problem, and others have explored it already. I will look into what already exists and see what we could build on for #HolosSocial.

@aproposnix

This is a great and important article by @soatok

It also mentions how anyone, not just #security experts, can help make E2EE on the ActivityPub #fediverse a reality.

For instance by #fedi devs by supporting #FEP 521a: Representing actor's public keys in their #ActivityPub implementation:

https://fediverse.codeberg.page/fep/fep/521a/

Or help improve the #UX of E2EE enabled fedi apps. Or even just spread the word around by boosting the article around, and give impetus to #E2EE adoption.

See also:

https://swicg.github.io/activitypub-e2ee/

https://publickey.directory/

The Long Tail of Work Left Until ActivityPub Has E2EE - Dhole Moments

#activitypub #e2ee #security #fediverse

https://soatok.blog/2026/07/15/the-long-tail-of-work-left-until-activitypub-has-e2ee/

The Long Tail of Work Left Until ActivityPub Has E2EE - Dhole Moments

#activitypub #e2ee #security #fediverse

https://soatok.blog/2026/07/15/the-long-tail-of-work-left-until-activitypub-has-e2ee/

The Long Tail of Work Left Until ActivityPub Has E2EE - Dhole Moments

#activitypub #e2ee #security #fediverse

https://soatok.blog/2026/07/15/the-long-tail-of-work-left-until-activitypub-has-e2ee/

The #W3C is working on end-to-end encryption #E2EE for #ActivityPub, with three main goals: enabling #encryptedmessages with attachments, ensuring #correctencryption, and verifying #usercontrol of signing keys. The Fundamental Goal is being addressed by the SWICG’s ActivityPub E2EE project team, while the Security Goal requires client software to authenticate KeyPackages. https://soatok.blog/2026/07/15/the-long-tail-of-work-left-until-activitypub-has-e2ee/?Fedizen.EU #Fedizen #Fediverse #ActivityPub #News

Preparing a new Loops release, possibly related to my upcoming FediCon talk!

I can't stop smiling. 😁

#Loops #FediCon #ActivityPub #W3C

The #W3C is working on end-to-end encryption #E2EE for #ActivityPub, with three main goals: enabling #encryptedmessages with attachments, ensuring #correctencryption, and verifying #usercontrol of signing keys. The Fundamental Goal is being addressed by the SWICG’s ActivityPub E2EE project team, while the Security Goal requires client software to authenticate KeyPackages. https://soatok.blog/2026/07/15/the-long-tail-of-work-left-until-activitypub-has-e2ee/?Fedizen.EU #Fedizen #Fediverse #ActivityPub #News

#ActivityPub carries posts, follows, likes and so on, but not moderation. A ban stays trapped on the instance that issued it. So, for instance, an account banned for racism on one instance stays unknown to the next. Moderation is activity too, and it should travel like the rest: signed and verifiable. This is a real problem, and others have explored it already. I will look into what already exists and see what we could build on for #HolosSocial.

#ActivityPub carries posts, follows, likes and so on, but not moderation. A ban stays trapped on the instance that issued it. So, for instance, an account banned for racism on one instance stays unknown to the next. Moderation is activity too, and it should travel like the rest: signed and verifiable. This is a real problem, and others have explored it already. I will look into what already exists and see what we could build on for #HolosSocial.

#ActivityPub carries posts, follows, likes and so on, but not moderation. A ban stays trapped on the instance that issued it. So, for instance, an account banned for racism on one instance stays unknown to the next. Moderation is activity too, and it should travel like the rest: signed and verifiable. This is a real problem, and others have explored it already. I will look into what already exists and see what we could build on for #HolosSocial.

What the fresh heck is this... It bogged down my federated #ActivityPub #WordPress Mastodon app enabled website, #MastoAdmin. Now I am scouring my Mastodon instance's server logs for this twit.

The linked readme url https://blog.bmn.dev/fedi-research.txt says, "I currently work on an attempt to build a reasonable recommendation engine for mastodon.
For this I set up a bot to listen to the major instances' public feeds.
If it is causing you considerable annoyances, please contact me!
You can find out more about me, including my contact information here: https://blog.bmn.dev/about

Thank you for running a mastodon instance!"

Their GitHub is https://github.com/fosefx

#fedi #askfedi
Is the #ActivityPub protocol any closer to having data portability?
And how about single ID usable in different apps?
And how about E2EE?

Thank you!

I've just closed the last big blocker before I'm starting to feel ok opening #cookifed to a few folks.
https://codeberg.org/cookifed/cookifed/issues/920

So you can expect more formal communications, and a few invitations going out around september (summer is holidays).

#ActivityPub #Fediverse

I've just closed the last big blocker before I'm starting to feel ok opening #cookifed to a few folks.
https://codeberg.org/cookifed/cookifed/issues/920

So you can expect more formal communications, and a few invitations going out around september (summer is holidays).

#ActivityPub #Fediverse

I've just closed the last big blocker before I'm starting to feel ok opening #cookifed to a few folks.
https://codeberg.org/cookifed/cookifed/issues/920

So you can expect more formal communications, and a few invitations going out around september (summer is holidays).

#ActivityPub #Fediverse

#fediverse support has been added to Agora! You can check out Agora here:

https://github.com/koreesmith/agora

If you'd like to sign up for an account on the flagship instance, go to https://agorasocial.online/

#social #socialmedia #activitypub

#fediverse support has been added to Agora! You can check out Agora here:

https://github.com/koreesmith/agora

If you'd like to sign up for an account on the flagship instance, go to https://agorasocial.online/

#social #socialmedia #activitypub

#fedi #askfedi
Is the #ActivityPub protocol any closer to having data portability?
And how about single ID usable in different apps?
And how about E2EE?

Thank you!

#fedi #askfedi
Is the #ActivityPub protocol any closer to having data portability?
And how about single ID usable in different apps?
And how about E2EE?

Thank you!

Da will man auf seiner Website was ausprobieren und landet plötzlich im Fediverse. 😄

Nach ersten Experimenten mit ActivityPub und Pixelfed ist das jetzt mein erster Beitrag auf Mastodon. Mal sehen, wohin die Reise führt.

https://richards-fotowelt.de/testbeitrag-zwischen-theorie-und-praxis/

#NeuHier #Fediverse #ActivityPub #WordPress #Photography #Germany

Da will man auf seiner Website was ausprobieren und landet plötzlich im Fediverse. 😄

Nach ersten Experimenten mit ActivityPub und Pixelfed ist das jetzt mein erster Beitrag auf Mastodon. Mal sehen, wohin die Reise führt.

https://richards-fotowelt.de/testbeitrag-zwischen-theorie-und-praxis/

#NeuHier #Fediverse #ActivityPub #WordPress #Photography #Germany

A #Mastodon (and #activityPub ?) feature: if #alttext is missing, anyone can click it and suggest alt text (like a reply to alt text) and original poster can accept it (or not).

#HolosSocial relay is confirmed to be very stable. I will officially tag it soon so admins can run their own relay with a script to easily install it on their VPS.
Using Holos with a custom domain and a cloud for media allows you to own your portable identity on the #Fediverse. Relays become only an infrastructure for it. Your device runs the #ActivityPub server and works as smoothly as any other app. Micro-blogging, media, and video, all from a single account. Switch with a simple tap.

#HolosSocial relay is confirmed to be very stable. I will officially tag it soon so admins can run their own relay with a script to easily install it on their VPS.
Using Holos with a custom domain and a cloud for media allows you to own your portable identity on the #Fediverse. Relays become only an infrastructure for it. Your device runs the #ActivityPub server and works as smoothly as any other app. Micro-blogging, media, and video, all from a single account. Switch with a simple tap.

A #Mastodon (and #activityPub ?) feature: if #alttext is missing, anyone can click it and suggest alt text (like a reply to alt text) and original poster can accept it (or not).

@bmann.ca @cwebber @dholms.at at #dwebcamp talking about #activitypub and #atproto

Are there any #ActivityPub server implementations using the actor model of computation? I'm not asking about ones just implemented in an actor model-capable programming language (Elixir), but ones that are fully or mostly implemented using that model. TIA

Are there any #ActivityPub server implementations using the actor model of computation? I'm not asking about ones just implemented in an actor model-capable programming language (Elixir), but ones that are fully or mostly implemented using that model. TIA

🛠️ New #Akkoma feature

Those who like me run Akkoma on home networks may have experienced timeouts when searching for posts by (Mastodon) URL.

That’s because searching #ActivityPub elements using non-canonical URLs involves a bit of back and forth over HTTP, and for some reason Akkoma had a hardcoded timeout of 5 seconds for it - which means that many if not all the searches by Mastodon post URL failed, and the search task also crashed.

This PR adds support for a configurable fetch timeout:

# Set it to e.g. 15 seconds to allow the HTTP task
# more time to fetch remote resources
config :pleroma, Pleroma.Search, fetch_timeout: 15_000

If you want to try it out already (together with other features, such as support for Mastodon the quotes protocol and indexable flag on accounts), you can build Akkoma from my fork.

The closing post in the "Fediverse Beyond Mastodon" maps forums, social reading, and music, the formats that don't fit the microblog.

The Threadiverse (Fediverse's answer to Reddit): Lemmy, Kbin/Mbin and PieFed (created by Rimu - @rimu).

Forums that predate federation: NodeBB (created by @julian) rewrote its core so every new forum federates by default.
Discourse (@Discourse) ships it as an opt-in, per-category plugin.
Both were built years ago to replace phpBB and vBulletin, and both now speak ActivityPub.

Social reading: BookWyrm (created by @tripofmice), a federated Goodreads where your shelves and reviews show up in a Mastodon timeline.

Music: Funkwhale (@funkwhale) - a self-hosted Grooveshark successor.

Bandwagon (created by @benpate) an online music storefront where musicians sell directly, built on the Emissary framework.

Read the full post here:

https://federatedmind.com/forums-reading-and-music-on-the-fediverse/?utm_source=mastodon&utm_medium=social&utm_campaign=fediverse-beyond-mastodon-4

#Fediverse #ActivityPub #Lemmy #PieFed #NodeBB #Discourse #BookWyrm #Funkwhale #Bandwagon #OpenWeb

The closing post in the "Fediverse Beyond Mastodon" maps forums, social reading, and music, the formats that don't fit the microblog.

The Threadiverse (Fediverse's answer to Reddit): Lemmy, Kbin/Mbin and PieFed (created by Rimu - @rimu).

Forums that predate federation: NodeBB (created by @julian) rewrote its core so every new forum federates by default.
Discourse (@Discourse) ships it as an opt-in, per-category plugin.
Both were built years ago to replace phpBB and vBulletin, and both now speak ActivityPub.

Social reading: BookWyrm (created by @tripofmice), a federated Goodreads where your shelves and reviews show up in a Mastodon timeline.

Music: Funkwhale (@funkwhale) - a self-hosted Grooveshark successor.

Bandwagon (created by @benpate) an online music storefront where musicians sell directly, built on the Emissary framework.

Read the full post here:

https://federatedmind.com/forums-reading-and-music-on-the-fediverse/?utm_source=mastodon&utm_medium=social&utm_campaign=fediverse-beyond-mastodon-4

#Fediverse #ActivityPub #Lemmy #PieFed #NodeBB #Discourse #BookWyrm #Funkwhale #Bandwagon #OpenWeb

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

🛠️ New #Akkoma feature

Those who like me run Akkoma on home networks may have experienced timeouts when searching for posts by (Mastodon) URL.

That’s because searching #ActivityPub elements using non-canonical URLs involves a bit of back and forth over HTTP, and for some reason Akkoma had a hardcoded timeout of 5 seconds for it - which means that many if not all the searches by Mastodon post URL failed, and the search task also crashed.

This PR adds support for a configurable fetch timeout:

# Set it to e.g. 15 seconds to allow the HTTP task
# more time to fetch remote resources
config :pleroma, Pleroma.Search, fetch_timeout: 15_000

If you want to try it out already (together with other features, such as support for Mastodon the quotes protocol and indexable flag on accounts), you can build Akkoma from my fork.

🛠️ New #Akkoma feature

Those who like me run Akkoma on home networks may have experienced timeouts when searching for posts by (Mastodon) URL.

That’s because searching #ActivityPub elements using non-canonical URLs involves a bit of back and forth over HTTP, and for some reason Akkoma had a hardcoded timeout of 5 seconds for it - which means that many if not all the searches by Mastodon post URL failed, and the search task also crashed.

This PR adds support for a configurable fetch timeout:

# Set it to e.g. 15 seconds to allow the HTTP task
# more time to fetch remote resources
config :pleroma, Pleroma.Search, fetch_timeout: 15_000

If you want to try it out already (together with other features, such as support for Mastodon the quotes protocol and indexable flag on accounts), you can build Akkoma from my fork.

In case anyone was wondering, yes my project Wordforge is effectively abandoned. I graduated and got a job last year and haven't had the time to work on it. It's a shame really since I really wanted to see something like this on the fediverse, but such is life.

If anyone wants to take over, feel free.

https://codeberg.org/grafcube/wordforge

#wordforge #opensource #foss #fediverse #activitypub #rust #leptos

https://github.com/Haven-Organization/matrix-appservice-activitypub

https://github.com/Haven-Organization/matrix-appservice-activitypub

Holosって仕組みを調べたけど面白いね #holos #fediverse #activitypub

How It Works - Holos: https://holos.social/how-it-works

Flohmarkt is a free open platform for small ads and selling things ("Flohmarkt" is the German for flea market). It's part of the Fediverse so the small ads can federate to other servers, and people can interact with Flohmarkt from Mastodon etc accounts.

If you want to post or browse adverts there is a server list:

🌱 https://codeberg.org/flohmarkt/flohmarkt/wiki/flohmarkt-instances

There is techy info on their Codeberg page:

🌱 https://codeberg.org/flohmarkt/flohmarkt

You can follow their lead dev's account at:

🌱 @grindhold

#Fediverse #ActivityPub

Flohmarkt is a free open platform for small ads and selling things ("Flohmarkt" is the German for flea market). It's part of the Fediverse so the small ads can federate to other servers, and people can interact with Flohmarkt from Mastodon etc accounts.

If you want to post or browse adverts there is a server list:

🌱 https://codeberg.org/flohmarkt/flohmarkt/wiki/flohmarkt-instances

There is techy info on their Codeberg page:

🌱 https://codeberg.org/flohmarkt/flohmarkt

You can follow their lead dev's account at:

🌱 @grindhold

#Fediverse #ActivityPub

@ozoned @itchio

Yea, things are dispersed. The #fediverse org at #Codeberg is a place where a host of people (co)maintain various fedi-related projects, most notably the #ActivityPub #FEP process. I maintain the 3 fedi curated lists there for https://delightful.coding.social initiative.

Seeing how EU uses Absent==Yes as trick to pass #Chatcontrol 1.0 shows we need 100% tranparent and scanned communication of politicans working in the EU.

Furthermore as I mentioned earlier there is massive need for #Tor based #SocialMedia and #Messenger based on #Activitypub and #Matrix .

Based on #Tor #Hidden #Services #Onion addressess, everybody is able to run the instance on his own device(s).

And for the view ones having lots of contacts a pc at home will mostly work to let it run

It took a while, but Shoot now has a role editor (among other guild settings)!

Roles and permissions have been implemented server-side nearly since the beginning but they haven't been available in the client until now.

The UI/UX here is very similar to how Discord's permissions used to work. Roles can be assigned to users and they are evaluated from bottom to top in the role list. Roles can deny or allow permissions, with lower roles in the list being overridden by higher roles. In the screenshots guild, the 'everyone' role allows 'Send Messages' permission, but the 'muted' role denies it. If someone has the 'muted' role, it will override the send messages permission from the 'everyone'/default role and prevent them from speaking.

It's still a bit rough of course, but I'm still having a good time working on the project.

You can try it out yourself/learn more at https://shoot.pub using the registration token `0K2A3` which expires in a week. That's just for anti-spam reasons, let me know if you want to register if it doesn't work :)

#shootpub #activitypub #fedidev

Implementing your own #Fediverse #ActivityPub server sounds like a good idea until you see the mush of half-implemented protocols that #Mastodon actually is. #ActivityStreams Link type? Profile? Tombstone? Whomst?

Why is there a webfinger endpoint? I don't want skeletal twinks fingering my web!?

And also an RSA key pair? Publicly being this embarrassing should be proof enough, nobody would dare pretend to be *this*!

Seeing how EU uses Absent==Yes as trick to pass #Chatcontrol 1.0 shows we need 100% tranparent and scanned communication of politicans working in the EU.

Furthermore as I mentioned earlier there is massive need for #Tor based #SocialMedia and #Messenger based on #Activitypub and #Matrix .

Based on #Tor #Hidden #Services #Onion addressess, everybody is able to run the instance on his own device(s).

And for the view ones having lots of contacts a pc at home will mostly work to let it run

It took a while, but Shoot now has a role editor (among other guild settings)!

Roles and permissions have been implemented server-side nearly since the beginning but they haven't been available in the client until now.

The UI/UX here is very similar to how Discord's permissions used to work. Roles can be assigned to users and they are evaluated from bottom to top in the role list. Roles can deny or allow permissions, with lower roles in the list being overridden by higher roles. In the screenshots guild, the 'everyone' role allows 'Send Messages' permission, but the 'muted' role denies it. If someone has the 'muted' role, it will override the send messages permission from the 'everyone'/default role and prevent them from speaking.

It's still a bit rough of course, but I'm still having a good time working on the project.

You can try it out yourself/learn more at https://shoot.pub using the registration token `0K2A3` which expires in a week. That's just for anti-spam reasons, let me know if you want to register if it doesn't work :)

#shootpub #activitypub #fedidev

For anyone who might find it useful, here's some statistics pulled from two real-world Sharkey instances:

Instance A (3 years old, 12 users (2 active), 472 pub and 491 sub connections):

+-----+---------------+-----------------+--------+----------------------------------------+
|Type |Metric         |Value            |Percent |Description                             |
+-----+---------------+-----------------+--------+----------------------------------------+
|Note |total          |  25,333,836     | 100.00%|All notes                               |
|Note |isSilencedUser |     604,388     |   2.39%|Notes by a silenced user                |
|Note |isSilencedHost |   2,940,962     |  11.61%|Notes from a silenced instance          |
|Note |isSuspendedUser|     282,627     |   1.12%|Notes by a suspended user               |
|Note |isSuspendedHost|      85,732     |   0.34%|Notes from a blocked instance           |
|Note |isPublic       |  11,914,094     |  47.03%|Public notes                            |
|Note |isHome         |  10,246,791     |  40.45%|Home-only / unlisted notes              |
|Note |isFollowers    |   3,156,743     |  12.46%|Followers-only notes                    |
|Note |isSpecified    |      16,208     |   0.06%|Specified / DM notes                    |
|Note |isPoll         |      53,281     |   0.21%|Polls                                   |
|Note |isMedia        |   2,383,375     |   9.41%|Notes w/ media                          |
|Note |isReply        |   9,544,540     |  37.68%|Replies                                 |
|Note |isReplyToSelf  |   2,059,325     |   8.13%|Self-replies                            |
|Note |isBoost        |   6,194,189     |  24.45%|Boosts                                  |
|Note |isBoostOfSelf  |     190,697     |   0.75%|Self-boosts                             |
|Note |isQuote        |     225,291     |   0.89%|Quotes                                  |
|Note |isQuoteOfSelf  |      70,243     |   0.28%|Self-quotes                             |
|Note |isChannel      |           2     |   0.00%|Notes in a channel                      |
|Note |isRemote       |  25,266,647     |  99.73%|Remote notes                            |
|Note |isLocal        |      67,189     |   0.27%|Local notes                             |
|Note |isLocalOnly    |         311     |   0.00%|Local-only (defederated) notes          |
|Drive|totalDrive     |       1,845.8 Gb| 100.00%|Total size of all known media           |
|Drive|internalDrive  |         111.8 Gb|   6.06%|Size of media stored/cached locally     |
|Drive|externalDrive  |       1,734.0 Gb|  93.94%|Size of external media accessed by proxy|
|User |total          |     359,926     | 100.00%|All users                               |
|User |local          |          16     |   0.00%|Local users                             |
|User |remote         |     359,910     | 100.00%|Remote users                            |
|User |isHibernated   |      89,625     |  24.90%|Hibernated (inactive) users             |
|User |isSilencedUser |         475     |   0.13%|Silenced users                          |
|User |isSilencedHost |     101,766     |  28.27%|Silenced users (by instance silence)    |
|User |isSuspendedUser|         465     |   0.13%|Suspended users                         |
|User |isSuspendedHost|       4,153     |   1.15%|Suspended users (by instance block)     |
|User |isDeleted      |      40,069     |  11.13%|Deleted                                 |
|User |isBot          |      33,588     |   9.33%|Bot accounts                            |
|User |isCat          |       4,965     |   1.38%|Users who are cats                      |
|User |isLocked       |      79,259     |  22.02%|Follow requests enabled                 |
|User |isExplorable   |     211,523     |  58.77%|Indexable / searchable users            |
+-----+---------------+-----------------+--------+----------------------------------------+

+-----+---------------+-----------------+--------+----------------------------------------+
|Type |Metric         |Value            |Percent |Description                             |
+-----+---------------+-----------------+--------+----------------------------------------+
|Note |total          |  87,286,880     | 100.00%|All notes                               |
|Note |isSilencedUser |   1,018,720     |   1.17%|Notes by a silenced user                |
|Note |isSilencedHost |  13,409,901     |  15.36%|Notes from a silenced instance          |
|Note |isSuspendedUser|     414,900     |   0.48%|Notes by a suspended user               |
|Note |isSuspendedHost|     819,842     |   0.94%|Notes from a blocked instance           |
|Note |isPublic       |  40,981,524     |  46.95%|Public notes                            |
|Note |isHome         |  28,994,854     |  33.22%|Home-only / unlisted notes              |
|Note |isFollowers    |  17,208,603     |  19.71%|Followers-only notes                    |
|Note |isSpecified    |     101,899     |   0.12%|Specified / DM notes                    |
|Note |isPoll         |     298,047     |   0.34%|Polls                                   |
|Note |isMedia        |   9,728,519     |  11.15%|Notes w/ media                          |
|Note |isReply        |  26,006,452     |  29.79%|Replies                                 |
|Note |isReplyToSelf  |   5,552,908     |   6.36%|Self-replies                            |
|Note |isBoost        |  32,738,677     |  37.51%|Boosts                                  |
|Note |isBoostOfSelf  |     577,898     |   0.66%|Self-boosts                             |
|Note |isQuote        |     398,522     |   0.46%|Quotes                                  |
|Note |isQuoteOfSelf  |     133,251     |   0.15%|Self-quotes                             |
|Note |isChannel      |          34     |   0.00%|Notes in a channel                      |
|Note |isRemote       |  86,209,578     |  98.77%|Remote notes                            |
|Note |isLocal        |   1,077,302     |   1.23%|Local notes                             |
|Note |isLocalOnly    |       2,009     |   0.00%|Local-only (defederated) notes          |
|Drive|totalDrive     |          43.3 Gb| 100.00%|Total size of all known media           |
|Drive|internalDrive  |           0.1 Gb|   0.13%|Size of media stored/cached locally     |
|Drive|externalDrive  |          43.3 Gb|  99.87%|Size of external media accessed by proxy|
|User |total          |     664,938     | 100.00%|All users                               |
|User |local          |       2,734     |   0.41%|Local users                             |
|User |remote         |     662,204     |  99.59%|Remote users                            |
|User |isHibernated   |       1,247     |   0.19%|Hibernated (inactive) users             |
|User |isSilencedUser |         466     |   0.07%|Silenced users                          |
|User |isSilencedHost |     185,793     |  27.94%|Silenced users (by instance silence)    |
|User |isSuspendedUser|       1,033     |   0.16%|Suspended users                         |
|User |isSuspendedHost|      36,152     |   5.44%|Suspended users (by instance block)     |
|User |isDeleted      |         505     |   0.08%|Deleted                                 |
|User |isBot          |      50,328     |   7.57%|Bot accounts                            |
|User |isCat          |       9,090     |   1.37%|Users who are cats                      |
|User |isLocked       |      73,855     |  11.11%|Follow requests enabled                 |
|User |isExplorable   |     381,411     |  57.36%|Indexable / searchable users            |
+-----+---------------+-----------------+--------+----------------------------------------+

Hello World

Coucou! This is just a first post announcing Nuages to the world.

Nuages is an ActivityPub app, connecting to your favourite servers that support the Client to Server API.

Follow us to get our latest updates, we’ll be officially launching the app in the coming weeks 😉

#ActivityPub #c2s #ActivityPubAPI #Fediverse

For anyone who might find it useful, here's some statistics pulled from two real-world Sharkey instances:

Instance A (3 years old, 12 users (2 active), 472 pub and 491 sub connections):

+-----+---------------+-----------------+--------+----------------------------------------+
|Type |Metric         |Value            |Percent |Description                             |
+-----+---------------+-----------------+--------+----------------------------------------+
|Note |total          |  25,333,836     | 100.00%|All notes                               |
|Note |isSilencedUser |     604,388     |   2.39%|Notes by a silenced user                |
|Note |isSilencedHost |   2,940,962     |  11.61%|Notes from a silenced instance          |
|Note |isSuspendedUser|     282,627     |   1.12%|Notes by a suspended user               |
|Note |isSuspendedHost|      85,732     |   0.34%|Notes from a blocked instance           |
|Note |isPublic       |  11,914,094     |  47.03%|Public notes                            |
|Note |isHome         |  10,246,791     |  40.45%|Home-only / unlisted notes              |
|Note |isFollowers    |   3,156,743     |  12.46%|Followers-only notes                    |
|Note |isSpecified    |      16,208     |   0.06%|Specified / DM notes                    |
|Note |isPoll         |      53,281     |   0.21%|Polls                                   |
|Note |isMedia        |   2,383,375     |   9.41%|Notes w/ media                          |
|Note |isReply        |   9,544,540     |  37.68%|Replies                                 |
|Note |isReplyToSelf  |   2,059,325     |   8.13%|Self-replies                            |
|Note |isBoost        |   6,194,189     |  24.45%|Boosts                                  |
|Note |isBoostOfSelf  |     190,697     |   0.75%|Self-boosts                             |
|Note |isQuote        |     225,291     |   0.89%|Quotes                                  |
|Note |isQuoteOfSelf  |      70,243     |   0.28%|Self-quotes                             |
|Note |isChannel      |           2     |   0.00%|Notes in a channel                      |
|Note |isRemote       |  25,266,647     |  99.73%|Remote notes                            |
|Note |isLocal        |      67,189     |   0.27%|Local notes                             |
|Note |isLocalOnly    |         311     |   0.00%|Local-only (defederated) notes          |
|Drive|totalDrive     |       1,845.8 Gb| 100.00%|Total size of all known media           |
|Drive|internalDrive  |         111.8 Gb|   6.06%|Size of media stored/cached locally     |
|Drive|externalDrive  |       1,734.0 Gb|  93.94%|Size of external media accessed by proxy|
|User |total          |     359,926     | 100.00%|All users                               |
|User |local          |          16     |   0.00%|Local users                             |
|User |remote         |     359,910     | 100.00%|Remote users                            |
|User |isHibernated   |      89,625     |  24.90%|Hibernated (inactive) users             |
|User |isSilencedUser |         475     |   0.13%|Silenced users                          |
|User |isSilencedHost |     101,766     |  28.27%|Silenced users (by instance silence)    |
|User |isSuspendedUser|         465     |   0.13%|Suspended users                         |
|User |isSuspendedHost|       4,153     |   1.15%|Suspended users (by instance block)     |
|User |isDeleted      |      40,069     |  11.13%|Deleted                                 |
|User |isBot          |      33,588     |   9.33%|Bot accounts                            |
|User |isCat          |       4,965     |   1.38%|Users who are cats                      |
|User |isLocked       |      79,259     |  22.02%|Follow requests enabled                 |
|User |isExplorable   |     211,523     |  58.77%|Indexable / searchable users            |
+-----+---------------+-----------------+--------+----------------------------------------+

+-----+---------------+-----------------+--------+----------------------------------------+
|Type |Metric         |Value            |Percent |Description                             |
+-----+---------------+-----------------+--------+----------------------------------------+
|Note |total          |  87,286,880     | 100.00%|All notes                               |
|Note |isSilencedUser |   1,018,720     |   1.17%|Notes by a silenced user                |
|Note |isSilencedHost |  13,409,901     |  15.36%|Notes from a silenced instance          |
|Note |isSuspendedUser|     414,900     |   0.48%|Notes by a suspended user               |
|Note |isSuspendedHost|     819,842     |   0.94%|Notes from a blocked instance           |
|Note |isPublic       |  40,981,524     |  46.95%|Public notes                            |
|Note |isHome         |  28,994,854     |  33.22%|Home-only / unlisted notes              |
|Note |isFollowers    |  17,208,603     |  19.71%|Followers-only notes                    |
|Note |isSpecified    |     101,899     |   0.12%|Specified / DM notes                    |
|Note |isPoll         |     298,047     |   0.34%|Polls                                   |
|Note |isMedia        |   9,728,519     |  11.15%|Notes w/ media                          |
|Note |isReply        |  26,006,452     |  29.79%|Replies                                 |
|Note |isReplyToSelf  |   5,552,908     |   6.36%|Self-replies                            |
|Note |isBoost        |  32,738,677     |  37.51%|Boosts                                  |
|Note |isBoostOfSelf  |     577,898     |   0.66%|Self-boosts                             |
|Note |isQuote        |     398,522     |   0.46%|Quotes                                  |
|Note |isQuoteOfSelf  |     133,251     |   0.15%|Self-quotes                             |
|Note |isChannel      |          34     |   0.00%|Notes in a channel                      |
|Note |isRemote       |  86,209,578     |  98.77%|Remote notes                            |
|Note |isLocal        |   1,077,302     |   1.23%|Local notes                             |
|Note |isLocalOnly    |       2,009     |   0.00%|Local-only (defederated) notes          |
|Drive|totalDrive     |          43.3 Gb| 100.00%|Total size of all known media           |
|Drive|internalDrive  |           0.1 Gb|   0.13%|Size of media stored/cached locally     |
|Drive|externalDrive  |          43.3 Gb|  99.87%|Size of external media accessed by proxy|
|User |total          |     664,938     | 100.00%|All users                               |
|User |local          |       2,734     |   0.41%|Local users                             |
|User |remote         |     662,204     |  99.59%|Remote users                            |
|User |isHibernated   |       1,247     |   0.19%|Hibernated (inactive) users             |
|User |isSilencedUser |         466     |   0.07%|Silenced users                          |
|User |isSilencedHost |     185,793     |  27.94%|Silenced users (by instance silence)    |
|User |isSuspendedUser|       1,033     |   0.16%|Suspended users                         |
|User |isSuspendedHost|      36,152     |   5.44%|Suspended users (by instance block)     |
|User |isDeleted      |         505     |   0.08%|Deleted                                 |
|User |isBot          |      50,328     |   7.57%|Bot accounts                            |
|User |isCat          |       9,090     |   1.37%|Users who are cats                      |
|User |isLocked       |      73,855     |  11.11%|Follow requests enabled                 |
|User |isExplorable   |     381,411     |  57.36%|Indexable / searchable users            |
+-----+---------------+-----------------+--------+----------------------------------------+

#HolosDiscover is a search engine dedicated to the #Fediverse. It does not scrape content, because it speaks #ActivityPub and respects each user's choice to opt in or out.
The most respectful alternative, open to all and full of content to explore.

https://discover.holos.social

#HolosDiscover is a search engine dedicated to the #Fediverse. It does not scrape content, because it speaks #ActivityPub and respects each user's choice to opt in or out.
The most respectful alternative, open to all and full of content to explore.

https://discover.holos.social

Hello World

Coucou! This is just a first post announcing Nuages to the world.

Nuages is an ActivityPub app, connecting to your favourite servers that support the Client to Server API.

Follow us to get our latest updates, we’ll be officially launching the app in the coming weeks 😉

#ActivityPub #c2s #ActivityPubAPI #Fediverse

Announcing it here publicly for the first time!

I've been building a general purpose activitypub pwa.

Follow @nuages for official updates!

#activityPubAPI #ActivityPub

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

Hello World

Coucou! This is just a first post announcing Nuages to the world.

Nuages is an ActivityPub app, connecting to your favourite servers that support the Client to Server API.

Follow us to get our latest updates, we’ll be officially launching the app in the coming weeks 😉

#ActivityPub #c2s #ActivityPubAPI #Fediverse

Announcing it here publicly for the first time!

I've been building a general purpose activitypub pwa.

Follow @nuages for official updates!

#activityPubAPI #ActivityPub

Hello World

Coucou! This is just a first post announcing Nuages to the world.

Nuages is an ActivityPub app, connecting to your favourite servers that support the Client to Server API.

Follow us to get our latest updates, we’ll be officially launching the app in the coming weeks 😉

#ActivityPub #c2s #ActivityPubAPI #Fediverse

Announcing it here publicly for the first time!

I've been building a general purpose activitypub pwa.

Follow @nuages for official updates!

#activityPubAPI #ActivityPub

Announcing it here publicly for the first time!

I've been building a general purpose activitypub pwa.

Follow @nuages for official updates!

#activityPubAPI #ActivityPub

The ActivityPub API doesn't define a way to get all server known posts with a specific tag.

There are a few ways this could be done in an ActivityPub client

What behaviour would you prefer when clicking on a post Tag link?

(Any other ideas, comment)
#ActivityPub #c2s #activityPubAPI

Hello World

Coucou! This is just a first post announcing Nuages to the world.

Nuages is an ActivityPub app, connecting to your favourite servers that support the Client to Server API.

Follow us to get our latest updates, we’ll be officially launching the app in the coming weeks 😉

#ActivityPub #c2s #ActivityPubAPI #Fediverse

#ActivityPub over #ATProto 👀

https://berjon.com/ap-at

#ActivityPub over #ATProto 👀

https://berjon.com/ap-at

#HolosSocial relay is confirmed to be very stable. I will officially tag it soon so admins can run their own relay with a script to easily install it on their VPS.
Using Holos with a custom domain and a cloud for media allows you to own your portable identity on the #Fediverse. Relays become only an infrastructure for it. Your device runs the #ActivityPub server and works as smoothly as any other app. Micro-blogging, media, and video, all from a single account. Switch with a simple tap.

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

Week in Fediverse 2026-07-10

Servers

- Betula v1.8.1
- Stegodon v1.8.6
- Ktistec v3.8.0
- Mitra v5.7.0
- Ibis v0.3.3
- Gathio v1.6.3
- NodeBB v4.14.0
- Wanderer v0.20.0
- Wafrn v2026.07.01
- Gush! v0.0.40
- PieFed v1.7.5
- Harmony v1.4.0

Clients

- Mastodon for iOS v2026.05
- tooi v0.27.0
- Voyager v2.47.4
- Aria v1.5.7
- Holos v1.14.0
- Rocinante v1.1.0
- chan-fe: Imageboard-style frontend for Mitra and Mastodon-compatible fediverse APIs

Tools and Plugins

- tag-federation.online: How Widely Do Hashtags Federate?
- Fedigraph: A dashboard for exploring the fediverse

For developers

- BotKit v0.5.0

Protocol

- FEP-4772: Representing bookmarks
- FEP-521b: Switch the default in FEP-521a to be 76171% cooler

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/019f29a4-78da-7a53-805d-72c8e43916c2

#HolosSocial relay is confirmed to be very stable. I will officially tag it soon so admins can run their own relay with a script to easily install it on their VPS.
Using Holos with a custom domain and a cloud for media allows you to own your portable identity on the #Fediverse. Relays become only an infrastructure for it. Your device runs the #ActivityPub server and works as smoothly as any other app. Micro-blogging, media, and video, all from a single account. Switch with a simple tap.

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

The open web is growing.

Communities around Mastodon, the Fediverse and ActivityPub are showing that we don’t have to depend entirely on closed platforms.

What if we take one more step?

Publish important messages on your own website first. Then share them everywhere else.

That’s the idea behind Method M.

https://method-m.eu/M/

#MethodM #Fediverse #Mastodon #ActivityPub #OpenWeb

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

The open web is growing.

Communities around Mastodon, the Fediverse and ActivityPub are showing that we don’t have to depend entirely on closed platforms.

What if we take one more step?

Publish important messages on your own website first. Then share them everywhere else.

That’s the idea behind Method M.

https://method-m.eu/M/

#MethodM #Fediverse #Mastodon #ActivityPub #OpenWeb

@scdh Bestimmt sprecht ihr auch über das #Fediverse, #ActivityPub etc.

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

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

#Mastodon's #ActivityPub inbox treats object types in tiers. Note and Question are supported directly. A second tier, Article, Page, Image, Audio, Video, and Event, gets converted to a title, a summary, and a link; content itself doesn't show. Anything outside both tiers is dropped on delivery, which is a large part of why so much of the fediverse federates as Note regardless of what the object actually is.

mastodon/mastodon#24079 asks for content to show up whenever it's present and the mediaType is supported, independent of type. Open since 2023, and as far as the thread shows, no core team engagement beyond one offhand remark that they're not happy with the status quo either.

Reading the issue text closely, it's a bit ambiguous whether it covers the drop tier or only the convert-to-title-and-link tier. I left a comment asking for clarification, since the fix looks very different depending on the answer.

If you build on ActivityPub, a comment or a reaction there is worth more than another workaround.

#fedidev #fediverse

@thefed @hrefna

I have heard people say "In #ActivityPub there's a timeline and a notification feed". No, there isn't. But perhaps in ones solution, there is. "There are Mentions and Hashtags". No, there aren't. Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly). "There are special hashtags to put in a summary field that machines understand". Nope!

https://social.coop/@smallcircles/116394824802521441

There are #FEP documents. These are just guidance that allow people to align on common ways to achieve things, and are currently the best way to avoid an even larger sprawl of protocol decay. They are non-normative wrt to the AP protocol itself.

I think a large part of the quick rise in attractiveness, popularity and adoption of #ATProto stems from how it offered devs a clear and well-documented introduction and a path to doing solution development on top of a robust protocol, where a dev could say "this is my app, and this is protocol".

@thefed @hrefna

I have heard people say "In #ActivityPub there's a timeline and a notification feed". No, there isn't. But perhaps in ones solution, there is. "There are Mentions and Hashtags". No, there aren't. Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly). "There are special hashtags to put in a summary field that machines understand". Nope!

https://social.coop/@smallcircles/116394824802521441

There are #FEP documents. These are just guidance that allow people to align on common ways to achieve things, and are currently the best way to avoid an even larger sprawl of protocol decay. They are non-normative wrt to the AP protocol itself.

I think a large part of the quick rise in attractiveness, popularity and adoption of #ATProto stems from how it offered devs a clear and well-documented introduction and a path to doing solution development on top of a robust protocol, where a dev could say "this is my app, and this is protocol".

@bmann.ca @cwebber @dholms.at at #dwebcamp talking about #activitypub and #atproto

@thefed @hrefna

ActivityPub at heart is a social graph of addressible actors that exchange activities with an object payload.

There are no "servers", "instances", "users". Neither is there "client", "app", "actor profile", and even not "identity" in #ActivityPub. That these words appear in the specification text, does not make them part of the protocol. Yes, all software runs on a computer system, yet "system" is not part of ActivityPub.

But you'd be forgiven the confusion, as over time app developers have liberally introduced abstractions that were subsequently seen by others as "the way to do it" and became de-facto standards. The name for that is Post-facto interoperability, "follow-the-leader", and it is the predominant way in which the fediverse has evolved unfortunately, without the specs catching up and incorporating the protocol decay this introduces. There were no good rules for protocol extension, and subsequent delineation of what is core protocol and what's an extension.

@thefed @hrefna

ActivityPub at heart is a social graph of addressible actors that exchange activities with an object payload.

There are no "servers", "instances", "users". Neither is there "client", "app", "actor profile", and even not "identity" in #ActivityPub. That these words appear in the specification text, does not make them part of the protocol. Yes, all software runs on a computer system, yet "system" is not part of ActivityPub.

But you'd be forgiven the confusion, as over time app developers have liberally introduced abstractions that were subsequently seen by others as "the way to do it" and became de-facto standards. The name for that is Post-facto interoperability, "follow-the-leader", and it is the predominant way in which the fediverse has evolved unfortunately, without the specs catching up and incorporating the protocol decay this introduces. There were no good rules for protocol extension, and subsequent delineation of what is core protocol and what's an extension.

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

There are two significant new additions in release v3.8.0 of ktistec.

First, the actor cards on the followed/following pages show relevant actor status. On the followed page, it tells you how long it has been since that actor published an activity (create, announce, like, etc.) that was sent to your server. It's a proxy for how active they are (or are not). On the following page, it tells you how long it has been since you have been able to send to that server. It's a proxy for whether that server is reachable or that actor is still alive.

Second, the backend for user-defined algorithmic feeds is in place, along with a keyword/hashtag/mention feeds implementation. You can't set up a feed via the user-interface, but the feeds work if you set one up directly in the database—which is how I've been previewing them.. I plan to release the frontend next week.

Here's the full changelog:

Added

• Display activity status on actor cards.
• Back-end support for user-defined algorithmic feeds.
• Apply community-relayed moderator deletes received as a Group's wrapped Announce.
• Follow a web page's rel="alternate" link when searching.

Fixed

• Avoid loading entire has_many collections when constructing child records.
• Evaluate the same-origin fetch gate against an embedded node's own identifier.
• Accept a delete of an uncached object or actor without verification.
• Catch MIME::Multipart::Error in local file-upload handling.
• Map malformed request-body parse failures to Bad Request.

#ktistec #crystallang #activitypub #fediverse

There are two significant new additions in release v3.8.0 of ktistec.

First, the actor cards on the followed/following pages show relevant actor status. On the followed page, it tells you how long it has been since that actor published an activity (create, announce, like, etc.) that was sent to your server. It's a proxy for how active they are (or are not). On the following page, it tells you how long it has been since you have been able to send to that server. It's a proxy for whether that server is reachable or that actor is still alive.

Second, the backend for user-defined algorithmic feeds is in place, along with a keyword/hashtag/mention feeds implementation. You can't set up a feed via the user-interface, but the feeds work if you set one up directly in the database—which is how I've been previewing them.. I plan to release the frontend next week.

Here's the full changelog:

Added

• Display activity status on actor cards.
• Back-end support for user-defined algorithmic feeds.
• Apply community-relayed moderator deletes received as a Group's wrapped Announce.
• Follow a web page's rel="alternate" link when searching.

Fixed

• Avoid loading entire has_many collections when constructing child records.
• Evaluate the same-origin fetch gate against an embedded node's own identifier.
• Accept a delete of an uncached object or actor without verification.
• Catch MIME::Multipart::Error in local file-upload handling.
• Map malformed request-body parse failures to Bad Request.

#ktistec #crystallang #activitypub #fediverse

#mixi2 ちゃんと継続改善頑張ってて好感持ってる。
#ActivityPub 対応して #Fediverse 化してくれないかな〜いつか…

いずれにしても、応援してます！

https://mixi.social/@nibushibu/posts/5f5c7ead-542b-4d69-a98b-dad541fa0006

Let's talk for a moment about what an actual actor model could look like in a protocol _like_ #ActivityPub. I've done variations on this thought experiment before, but I find it useful to revisit.

alice@servera wants to send a message to bob@serverb. So Alice (A) accesses her profile and pulls a reference to an outbox actor (Ref{O}). She send the message (M) to this outbox:

A -M-> O

With me so far?

The Outbox actor does Something™, it doesn't matter what, but the server that hosts the outbox actor now may do one of two things, depending on whether servera (Sa) already has a reference to an inbox actor (Ref{I}) for bob on serverb (Sb).

The first scenario is a derivation of the second, so let's go through the second.

For this scenario Sa reaches out to webfinger (or some other lookup mechanism, but let's use webfinger) and says to it "gimme the user profile for bob@serverb." Sb returns the user profile Profile{bob@serverb}.

Within Profile{bob@serverb} is a list of actor references with names. One of which is named inbox. So now Sa has Ref{I} and can execute:

Sa -M-> I

In a way, we could end here and be content.

We're not done.

This is basically identical to the current ActivityPub flow with a few notable exceptions:

1. Note that I am not talking about the _user_ as an _actor_. The user is a user. The actor is an actor. Profile{bob@serverb} is not an actor, it's a Profile of a User.
2. I formalized the addition of webfinger. I don't need to do this, and there are alternatives.
3. It could _very_ well be that the inbox reference you are handed is identical between multiple actors.
4. I am treating "The Inbox" as a singular thing, but it _doesn't have to be_. I could have a different reference for where to send Events or calendar entries, I could have a different reference for where to send direct messages versus general posts, etc. All of this could be laid out pretty easily in a single map.
5. Most critically: The "inbox" is not a dereferencable collection. It's an _actor reference_. What gets exposed to the user might be completely different than what gets sent there.

The details don't matter as much as this: the foundational unit by which we reason about the system is different.

Let's talk for a moment about what an actual actor model could look like in a protocol _like_ #ActivityPub. I've done variations on this thought experiment before, but I find it useful to revisit.

alice@servera wants to send a message to bob@serverb. So Alice (A) accesses her profile and pulls a reference to an outbox actor (Ref{O}). She send the message (M) to this outbox:

A -M-> O

With me so far?

The Outbox actor does Something™, it doesn't matter what, but the server that hosts the outbox actor now may do one of two things, depending on whether servera (Sa) already has a reference to an inbox actor (Ref{I}) for bob on serverb (Sb).

The first scenario is a derivation of the second, so let's go through the second.

For this scenario Sa reaches out to webfinger (or some other lookup mechanism, but let's use webfinger) and says to it "gimme the user profile for bob@serverb." Sb returns the user profile Profile{bob@serverb}.

Within Profile{bob@serverb} is a list of actor references with names. One of which is named inbox. So now Sa has Ref{I} and can execute:

Sa -M-> I

In a way, we could end here and be content.

We're not done.

This is basically identical to the current ActivityPub flow with a few notable exceptions:

1. Note that I am not talking about the _user_ as an _actor_. The user is a user. The actor is an actor. Profile{bob@serverb} is not an actor, it's a Profile of a User.
2. I formalized the addition of webfinger. I don't need to do this, and there are alternatives.
3. It could _very_ well be that the inbox reference you are handed is identical between multiple actors.
4. I am treating "The Inbox" as a singular thing, but it _doesn't have to be_. I could have a different reference for where to send Events or calendar entries, I could have a different reference for where to send direct messages versus general posts, etc. All of this could be laid out pretty easily in a single map.
5. Most critically: The "inbox" is not a dereferencable collection. It's an _actor reference_. What gets exposed to the user might be completely different than what gets sent there.

The details don't matter as much as this: the foundational unit by which we reason about the system is different.

In a few days, the last brick of the relay server will be published for an official release and a tag.
A lot of stress when you are alone, but after a few weeks the work has paid off, it is really stable.
Running your own #ActivityPub server on your phone will be as simple as using any other app. You will not be limited to a lookalike: micro-blogging, media, videos, all you want in a simple tap.

#HolosSocial

In a few days, the last brick of the relay server will be published for an official release and a tag.
A lot of stress when you are alone, but after a few weeks the work has paid off, it is really stable.
Running your own #ActivityPub server on your phone will be as simple as using any other app. You will not be limited to a lookalike: micro-blogging, media, videos, all you want in a simple tap.

#HolosSocial

Today @kopper shared a post on the fediverse titled how to not regret c2s, and I found it genuinely interesting to read, even if I'm not sure its proposed architecture actually solves what it sets out to solve.

The author's frustration with naïve #C2S implementations is well-founded. Slapping an #ActivityPub facade onto an existing Mastodon-like server and calling it C2S doesn't buy you much—you end up with the rigidity of a bespoke API without any of the interoperability C2S is supposed to offer. The “JSON-LD flavored Mastodon API” framing is apt.

The proposed solution is to split responsibility more aggressively: the C2S server should be nearly stateless and dumb, storing ActivityPub objects without interpreting them, while a separate “client” layer handles indexing, timelines, moderation, and exposes its own API to the frontend running on the user's device. It's a clean separation of concerns on paper.

But here's what bothers me. When you map this architecture onto familiar terms, it looks roughly like this:

• C2S server ≈ a database (PostgreSQL, say)
• “Client” ≈ an application server (Mastodon, Misskey)
• “Frontend” ≈ the actual client app on your phone

That's not a new architecture. That's just the current architecture with the labels shifted. The interesting question is which interface gets standardized, and the author's answer is the one between the C2S server and the “client” layer—the bottom boundary.

The problem is that what people actually want from C2S is to connect any frontend to any server. The portability they're after lives at the top boundary, between the frontend and whatever is behind it. But the author explicitly argues against standardizing that layer: “we don't really need a standardized api,” they write, leaving each client free to expose whatever API it likes.

Which means frontends remain locked to specific clients, just as Mastodon apps are locked to the Mastodon API today. The interoperability promise of C2S—log in to any server with any app—isn't actually delivered. It's been pushed one layer down, out of reach of the end user.

There's real value in the post's thinking about data hosting vs. interpretation, and about the security implications of servers that understand too much. But as an answer to the question C2S is supposed to answer, I'm not convinced.

#fedidev #fediverse

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

I am psyched about #kazarma, the bridge between #matrix and #ActivityPub

https://kazar.ma/

There are two significant new additions in release v3.8.0 of ktistec.

First, the actor cards on the followed/following pages show relevant actor status. On the followed page, it tells you how long it has been since that actor published an activity (create, announce, like, etc.) that was sent to your server. It's a proxy for how active they are (or are not). On the following page, it tells you how long it has been since you have been able to send to that server. It's a proxy for whether that server is reachable or that actor is still alive.

Second, the backend for user-defined algorithmic feeds is in place, along with a keyword/hashtag/mention feeds implementation. You can't set up a feed via the user-interface, but the feeds work if you set one up directly in the database—which is how I've been previewing them.. I plan to release the frontend next week.

Here's the full changelog:

Added

• Display activity status on actor cards.
• Back-end support for user-defined algorithmic feeds.
• Apply community-relayed moderator deletes received as a Group's wrapped Announce.
• Follow a web page's rel="alternate" link when searching.

Fixed

• Avoid loading entire has_many collections when constructing child records.
• Evaluate the same-origin fetch gate against an embedded node's own identifier.
• Accept a delete of an uncached object or actor without verification.
• Catch MIME::Multipart::Error in local file-upload handling.
• Map malformed request-body parse failures to Bad Request.

#ktistec #crystallang #activitypub #fediverse

If you are at #DwebCamp and you love the #Fediverse please come see my Introduction to #ActivityPub talk at 5pm today in the #OpenSocialWeb tent! It means a lot.

If you are at #DwebCamp and you love the #Fediverse please come see my Introduction to #ActivityPub talk at 5pm today in the #OpenSocialWeb tent! It means a lot.

If you are at #DwebCamp and you love the #Fediverse please come see my Introduction to #ActivityPub talk at 5pm today in the #OpenSocialWeb tent! It means a lot.

There are two significant new additions in release v3.8.0 of ktistec.

First, the actor cards on the followed/following pages show relevant actor status. On the followed page, it tells you how long it has been since that actor published an activity (create, announce, like, etc.) that was sent to your server. It's a proxy for how active they are (or are not). On the following page, it tells you how long it has been since you have been able to send to that server. It's a proxy for whether that server is reachable or that actor is still alive.

Second, the backend for user-defined algorithmic feeds is in place, along with a keyword/hashtag/mention feeds implementation. You can't set up a feed via the user-interface, but the feeds work if you set one up directly in the database—which is how I've been previewing them.. I plan to release the frontend next week.

Here's the full changelog:

Added

• Display activity status on actor cards.
• Back-end support for user-defined algorithmic feeds.
• Apply community-relayed moderator deletes received as a Group's wrapped Announce.
• Follow a web page's rel="alternate" link when searching.

Fixed

• Avoid loading entire has_many collections when constructing child records.
• Evaluate the same-origin fetch gate against an embedded node's own identifier.
• Accept a delete of an uncached object or actor without verification.
• Catch MIME::Multipart::Error in local file-upload handling.
• Map malformed request-body parse failures to Bad Request.

#ktistec #crystallang #activitypub #fediverse

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

This remains one of my least favorite features of #ActivityPub.

1. It violates fundamental type safety principles.
2. "without authentication" means that it needs to be accessible to random people on the internet if read literally, and evidently changing this (along with "we should all require transport layer security") are controversial opinions in fediverse development.
3. Literally everything about that Note makes me die inside.
4. Yet another example of how "there are no servers in ActivityPub" is undermined by the spec. Because this entire concept and its use cases assume a server. "There are no servers" has always been a fiction, but this illustrates the tension.
5. It is the kind of thing that could be better implemented by using actors, but the protocol is unwilling to take that route for how to implement features.

Been thinking about fediverse wiki after @2chanhaeng mentioned it today. Some ideas:

• Cross-instance page linking: [[Page Title@other-instance.wiki]]
• Edit pages on other instances with your home account
• Fork pages across instances: [[Page@instance-a.wiki]] → [[Page@instance-b.wiki]], sharing edit history up to the fork point

• Merge forked pages later when needed

The fork/merge model feels natural for federated collaboration. Thoughts?

#fediverse #wiki #fedidev #ActivityPub

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

This remains one of my least favorite features of #ActivityPub.

1. It violates fundamental type safety principles.
2. "without authentication" means that it needs to be accessible to random people on the internet if read literally, and evidently changing this (along with "we should all require transport layer security") are controversial opinions in fediverse development.
3. Literally everything about that Note makes me die inside.
4. Yet another example of how "there are no servers in ActivityPub" is undermined by the spec. Because this entire concept and its use cases assume a server. "There are no servers" has always been a fiction, but this illustrates the tension.
5. It is the kind of thing that could be better implemented by using actors, but the protocol is unwilling to take that route for how to implement features.

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

@bmann.ca @cwebber @dholms.at at #dwebcamp talking about #activitypub and #atproto

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

@djm62 @shlee

Not sure if there's an existing framework that can be designed to work with #ActivityPub. But I do think that thinking about consent in a more general/generic sense would be a worthwhile effort. This should be something that is picked up at the #SocialCG level, or perhaps in #FEP documents first. A lot of the mechanisms that proliferate now are also app-centric and almost *assume* that #fediverse is a glorified #microblogging environment. The more that trend continues, the more that will indeed be the case. This is what my long blog post was about, that I wrote recently:

https://coding.social/blog/grassroots-evolution

Absolute Madness how everyone thinks it is just okay to sprinkle magic opt-in / opt-out and other control words in the profile description of someone's #fediverse account!

Why do we have #ActivityPub be extensible if not for supporting a native mechanism to deal with consent? Why should there be out-of-bound ugliest of ugliest hacks?

With all that jazz being introduced it is no wonder people opt-in for #ATProto and other more sane social networking protocols that have robust protocol specifications, and not a metric ton of protocol decay to poop on top of your basic AP implementation so it becomes interoperable until the next on-the-fly hack by someone else breaks your nice code..

Fediverse is protocol impl + eternal whack-a-mole development and maintenance this way.

https://github.com/social-web-foundation/tags.pub/issues/37#issuecomment-4923326159

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

@bmann.ca @cwebber @dholms.at at #dwebcamp talking about #activitypub and #atproto

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

To ensure Fedify-built servers federate correctly with the wider #fediverse, we're planning to run automated E2E tests in #CI against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

#ActivityPub #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

@bmann.ca @cwebber @dholms.at at #dwebcamp talking about #activitypub and #atproto

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

Goodmorning fedi, I just woke up in a windy tent in the middle of a field and sleepily scrolled thru all the opening talks at #DwebCamp to figure out what my first stop needs to be: def have to catch @cwebber, @dholms.at and @boris discuss the trade offs, design decisions and points of convergence between #ActivityPub and #ATProto

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

Goodmorning fedi, I just woke up in a windy tent in the middle of a field and sleepily scrolled thru all the opening talks at #DwebCamp to figure out what my first stop needs to be: def have to catch @cwebber, @dholms.at and @boris discuss the trade offs, design decisions and points of convergence between #ActivityPub and #ATProto

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.

AT Protocol feels less like that to me. Running a PDS means a signed repo, a Merkle search tree, a firehose, a DID. It's not a layer you add to an existing site. It's closer to standing up another backend beside it.

I think that's why ActivityPub keeps making sense to me. You can join later. You don't have to have built the whole thing with federation in mind from day one.

#ATProto #ATProtocol #fedidev

One thing I keep coming back to when comparing #ActivityPub and AT Protocol: ActivityPub is basically a convention on top of the #web stuff we already have. An actor is a JSON-LD document you GET. An inbox is an endpoint you POST to. If you already run a website, you can bolt this on without changing the site's basic shape. Ghost didn't set out to join the #fediverse, and then years later it could, just by adding an endpoint.