@silverpill @raphaelRaphael Lullis @julian @mariusormarius

The killer app for the fediverse is not nomadic identity. That is either a protocol capability or may refer to an Identity Management app, a solution design.

Problem is, it is no use discussing here. No convergence takes place, other than spontaneous / random convergence. But it does not lead anywhere, not to a common consensus. Not to robust foundations to build on without continuous worries that things break. Microblog communications does not support this, and lacking that support manual processes are needed.

Even the #ActivityPub #FEP only offers convergence to certain extent. The process is a band-aid, a best-we-have.

In analogy of the horserace, spontaneous convergence and ad-hoc alignment on FEP puzzle pieces by implementers equates to the horseback riders figuring out some basic rules to avoid serious accidents. But this FEP adoption at the same time warps the track, hems them in, alters reality and the future.

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

@silverpill @raphaelRaphael Lullis @julian @mariusormarius

Yes, I agree. Though I would rather see a generic server having much less functionality than a Mastodon API exposes, since much of that is app-specific, Microblogging domain already. The generic server should make Mastodon possible as a solution design modeled on top of its #ActivityPub networking layer.

In such a way where we can finally consider the protocol layer to be robust, and are able to treat it as a black box, and are not confronted with all its implementation details when we are doing a solution design.

I think we are probably on the same page, but..

> If you want to go beyond Mastodon API capabilities, you need a truly generic server. Something akin to Nostr relay.

This I would reformulate as:

"If you want to go beyond an app-centric fediverse bound to a Microblogging domain, then you need a generic server conformant to the ActivityPub specification."

Which also indicates I think we need to aggregate puzzle pieces into an AP 2.0

@silverpill @raphaelRaphael Lullis @julian @mariusormarius

In my book if a side effect is part of the protocol specification, then it constitutes a protocol capability. If not, then it is part of some app's / solution's business logic.

The definition of "ActivityPub extension" by itself is unclear. With overloaded use causing confusion. It may refer to:

- Protocol extension
- App / solution built on top of the protocol

To deal with protocol capabilities they must have water-tight specs, well-defined behavior and strict consistent use across the fediverse.

To deal with side effects that are part of solution designs for a particular application or business domain things go from simple to very complex in the amount of introspection and machine-readability that the #ActivityPub Actor abstraction offers.

Simplest is finding the URL where the docs of the extension / solution design sit. Most complex is full introspection and handshaking. The latter is the Solid route.

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

@silverpill @raphaelRaphael Lullis @julian @mariusormarius

I sometimes picture fediverse as one of these old horseracing toys from the 50s, where the horses represent all the various perspectives and expectations people have of the fediverse. There is no horse to bet on, positions change all the time, horses change tracks randomly. And furthermore there no finish line, the race is an endless slog. The prize of a robust #ActivityPub protocol forever out of reach, getting more elusive as time progresses.

@raphaelRaphael Lullis @julian @mariusormarius

Another example of the need for careful terminology use is in the post that @silverpill quoted above:

> prevent actors on the same server from deleting each other posts

"post"? There is no post in #ActivityPub, not as a verb and neither as a noun. While I am not worried that silverpill used the word in a wrong meaning here, the terminology easily leads to confusion where someone who interprets AS/AP to be equivalent to the fediverse we have today, pictures in their mind as Mastodon posts or toots in fedi slang, or elsewhere called statuses.

That is app terminology. AP only knows Actor, Activities, Objects, and perhaps Collections. Period. The rest is solution design.

Where they are transferred they can be said to be messages, and messaging happens.

@raphaelRaphael Lullis @silverpill @julian @mariusormarius

I agree. Aboveall we need to know where protocol ends and 'app' begins. Be generally more deliberate in terminology use, and no longer talk in overloaded terms that have different unclear meanings to different people in different settings (to avoid using 'contexts' one of such overloaded words)

I've noticed for instance people having a very different notion of what a 'generic server' is, in definitions that are almost diametrical opposites.

My definition of generic is 'not specific' i.e. a generic server is a pure #ActivityPub protocol implementation (which is something to agree upon, what that exactly entails), having no knowledge of *any* app / solution built on top of it or 'passing through' its messaging architecture.

In the other meaning a generic server 'knows/does/has it all' i.e. it understands everything we comprise to be 'the fediverse' in a kind of hard-wired fashion based on the functionalities that (marginally) interoperate today.

Week in Fediverse 2026-02-27

Servers

- Bookwyrm v0.8.5
- Gush! v0.0.31
- Hollo v0.7.4
- flohmarkt v0.16.0
- Mastodon v4.5.7
- Wafrn v2026.02.02
- GoToSocial v0.21.0
- Loops v1.0.0-beta.10
- Ktistec v3.3.1
- Mitra v4.19.0
- Stegodon v1.8.0
- Hometown v1.2.0
- gathio v1.6.1
- Castopod v1.15.5
- NodeBB v4.9.0
- PieFed v1.6.7

Clients

- Pachli v3.4.0
- tooi v0.22.0
- Summit v1.78.1
- Photon v2.3.0
- Blorp v1.10.3
- Phanpy changelog

Tools and Plugins

- Poduptime v6.2.1
- Fediverse invitation

For developers

- Fedify v2.0

Protocol

- FEP-a427: Server Domain Migration
- FEP-fc48: Generic ActivityPub server

Articles

- Self-Hosting Pixelfed: Federated Instagram Without the Algorithm

-----

#WeekInFediverse #Fediverse #ActivityPub

Previous edition: https://mitra.social/objects/019c7c6f-742a-7930-2413-73b1d9611c99

When I first started working with #ActivityPub, before #Fedify existed, it felt like writing web apps in Perl and CGI in the late '90s. Interesting, even exciting—but never comfortable. That era where your business logic and your protocol plumbing were just… the same thing:

print "HTTP/1.1 200 OK"
print "Content-Type: text/html"
print
print "Hello, world!"

Decades of web development have given us layers of abstraction we now take for granted. Nobody hand-parses application/x-www-form-urlencoded query strings anymore. Nobody writes their own JSON codec, or manually constructs HTTP request/response messages. These things just aren't your problem when you're building an app.

ActivityPub development still feels like they are your problem. What do you do when the https://www.w3.org/ns/activitystreams#actor property comes in as a string instead of an array? What about when https://www.w3.org/ns/activitystreams#object is an embedded entity rather than a URI? How exactly do you implement HTTP Signatures? And wait—what's Linked Data Signatures, and do you need that too?

The real issue isn't that ActivityPub is complicated per se. It's that you can't get away with understanding it at a high level. You have to know it the way an implementor knows it—every edge case, every inconsistency in how different servers serialize JSON-LD, every signature scheme that exists in the wild. That's a lot to learn before you can even start thinking about your actual app. And when developers understandably cut corners on the protocol to focus on their product, it quietly becomes an interoperability problem for the whole ecosystem.

What I want ActivityPub development to feel like: you spend a day understanding the big picture, and then you just… build your app. That was the goal when I started Fedify, and honestly, we're not fully there yet. But it's where I want to get.

#fedidev #fediverse

Has anybody thought about modelling #activitypub with a tool like https://alloytools.org/book.html
to find potential exploits? Thinking about the spec it’s missing any algorithms for authorization, but I already found a couple of edge-cases that make a server DoSssable or give an attacker the ability to spoof messages …

an interesting thread on Bluesky about why people are choosing to build on #ATProto instead of #ActivityPub
https://witchsky.app/profile/did:plc:rtf3bjc3w2yn4syxtm4r7jt2/post/3mfrp6tovy22g

Recently, there was a discussion about generic #ActivityPub servers. Several people claimed that they were working on one, but it turned out that their "generic" servers only support activities defined in the ActivityPub specification. Such a server shouldn't be called generic. It is not difficult to build, neither it is an interesting concept because competing protocols (e.g. Nostr) already offer much more.

I've been writing a #FEP that describes how to build a real generic server. It is not finished yet, but I feel like now is a good time to publish it:

FEP-fc48: Generic ActivityPub server

This kind of server:

- Can process any object type, and can process non-standard activities like EmojiReact.
- Compatible with FEP-ae97 clients.
- Does not require JSON-LD.

I attempted to implement it when I was researching security properties of FEP-ae97 API: https://codeberg.org/silverpill/fep-ae97-server. Back then I didn't know what to do with side effects, but now I think that we can simply force clients to specify them.

Special thanks to @mariusormarius and @trwnhinfinite love ⴳ for their input.

#C2S

Backlinks to quote posts.

https://codeberg.org/fediverse/fediverse-ideas/issues/132

#AskFedi #FediIdea #fediverse #ActivityPub

Started laying out a rough plan for implementing FEP-ef61: Portable Objects in #Fedify—server-independent #ActivityPub identities backed by #DIDs, multi-server replication, and client-side signing. It's going to be a long road (13 tasks across 5 phases, with a few open questions that need answering before we even begin), but I think it's worth doing right.

https://github.com/fedify-dev/fedify/issues/288#issuecomment-3971459585

#fedidev #fediverse #PortableObjects

Anyone asked where the #ActivityPub dev community’s communication went to, can let a broad beaming smile come to their face, svivel their eyes skywards, then make a broad gesture with their arms, and exclaim solemnly “To the fediverse, my friend. To the fediverse”. And the dotted clouds high above in the steel blue sky will smile back at them, wave and gesture, and sing in a non-melodious cacophony “Here we are, come join us”.

And so we all do. It is a sight to behold. 🥹

Or with a tad less sarcasm, you might also say: Even though it is a medium that is not up to the task of holding a grassroots open-standards based ecosystem together, #Microblogging #SocialMedia has become the preferred channel for communication in the app-centric #fediverse. Majority of dev happens in the federated cloud and is driven by app owners.

Though luckily there is also a minority of ecosystem atmosphere custodians who help study the weather patterns of the future #SocialWeb.

RE: https://mastodon.social/@glyph/116140431530202122

give @glyph cash

ignore tags

#mutualaid #fediverse #selfhosting #retroComputing #python #dev #indiedev #foss #hosting #mastodon #activitypub #joinIn #video #software #politics #windows #linux #macos #ios #android #fedi #support #help #patreon #indieweb #internet #webDev #homelab #diy #maker #charity #donations #money #rant #writing #writingcommunity #drawing #dragons #furry #furryart #anime #art #server #education #absurdAmountOfTags #humor #satire #meme #joke #pol #lifestyle #give #today #fyp

The intro to HDA (Hypermedia-Driven Applications) I've been raving about today seems relevant to the ongoing discussions about C2S APIs for the fediverse, especially the proliferation of the monolithic server+web-app antipattern. I've started a SH topic on it;

https://socialhub.activitypub.rocks/t/could-hypermedia-driven-application-architecture-be-useful-for-ap-c2s/8521

But SH seems like a ghost town ATM. Tried to post on ActivityPub.space but their interface hates my mobile browser (Fennec from F-Droid) 🤷‍♂️

#FediDevs #ActivityPub #C2S

I’m building a new tool and looking for volunteers to test it! A #fediverse linktree.

It’s designed for two types of people:

Normies / newcomers – Think of it like a free, privacy-respecting Linktree. No trackers, no ads. But here's the cool part: it's a Trojan horse for the fediverse. Your profile link is itself an ActivityPub actor. That means people can interact with it directly in the fediverse, and it encourages exploration of open platforms.

Fediverse users, If you have multiple accounts (#Mastodon, #Pixelfed, Loops, a federated blog…), you know the struggle: sometimes you just want one persona to follow. This tool gives you that. It doesn’t post on its own (read-only), but it boosts all your other accounts and even has its own #ActivityPub inbox. PLUS it can receive and show your badges issued by @badgefedThe BadgeFed Project !

Interested in testing? Reply here, I will reach out in the next 24-48hrs with an invitation link.

#Introduction - A new home for longer mountain ramblings & tech dabbling!

After years on a managed Mastodon instance, I've finally jumped into the #selfhosted world! Say hello to my new personal #ActivityPub instance, powered by #GoToSocial from home.

While I test the waters here (and learn all the complexities of managing self-hosting!), this space will be for the longer-form, deeper-dive content:

1. Extended mountain trip reports with more photos.

2. Ramblings on my rather amateur adventures in #technology, #landscapephotography, #lora mesh networks, #degoogling efforts, and #linuxphone solutions.

Think of it as my digital base camp. If you're a mountain person who loves tech (or a tech person who loves mountains), we probably have things in common. Boosts and introductions are welcome!

So on the official #matrix page it says there are no bridges for #activitypub is this the case or is it there’s no official ones. Would love to hear from anyone with experience.

Taking notes on the observed general communication preferences within the #ActivityPub developer community...

1. Microblog, microblog, microblog
2. Seek one-to-ones, mentions-only
3. Don't care about spread of the msg
4. Don't boost, don't use hashtags
5. Tooted today, gone tomorrow

Convenient? Pragmatic? Desirable? idk.

@damon

Thank you. Yes, indeed. As it happens I was just in chat with Sébastien yesterday. They'll give a presentation at the #Solid Practitioners Meetings on the 5th of March.

#ActivityPods is positioned to bring "app development" to the intersection of the #ActivityPub and #SolidProject ecosystems, and that is very valuable. And also an #OpenStandards focused initiative.

I have revamped the #fediverse delightful lists to de-emphasize app domains and apps that have already established themselves, to highlight the innovative projects that can bring fedi to higher levels. @activitypods is on the developer list.. https://delightful.coding.social/delightful-fediverse-development/#application-development

They are well positioned to offer the 'Solution developer' stakeholders an attractive set of tools. And the opportunity is to marriage the best of 2 worlds. Which is at the same time the big challenge, coping with the worst of 2 worlds. The other day I tooted about this here: https://social.coop/@smallcircles/116113963712755122

There's now a proper rendered web interface for FEPs at https://fediverse.codeberg.page/fep/fep/*/, which is much nicer to read than the raw Markdown source on Codeberg. But the canonical permalink, https://w3id.org/fep/*, still redirects to the Markdown file rather than the rendered page.

Would it make sense to update the w3id.org redirect to point to the rendered version instead? It seems like the better experience for anyone following a FEP link, and arguably what a “permanent” link should resolve to—something human-readable.

I'm not sure who manages the w3id.org/fep/ redirect configuration. (It lives in the perma-id/w3id.org GitHub repo, so it would just be a PR, but I'd want to get community consensus first rather than just send one in unilaterally.)

#fedidev #fep #fediverse #ActivityPub

Fireside Fedi 77 - Shade of Creativity: Lorenzo’s Fediverse Art Talk

Special thank you to @lrnz@feed.lrnz.it ** **!

🚀 **Watch the full VOD:** tubefree.org/w/nMnNvXvyTgTPU...
🔎 **Explore more episodes:** tubefree.org/a/ozoned/video-channels

🔔 Subscribe to the RSS feed so you never miss a future deep‑dive.

📡 **Subscribe via RSS:** tubefree.org/feeds/videos.xml?videoChannelId=5934
🎧 **Podcast feed:** tubefree.org/feeds/podcast/videos.xml?videoChannelId=5934

#FiresideFedi #FiresideChat #Podcast #VideoPodcast #Fediverse #Fedi #ActivityPub #BSKY #DecentralizedSocial #OpenSocialWeb #Community #TechCulture #FutureOfSocial #TechTalk #DevCommunity #CodingFun #art #comics #ghost #machine

Less than a week till @fediforum's Growing the Social Web unworkshop! Get all the latest from @tchambersTim Chambers's Surf feed:

https://surf.social/feed/surf%2Fcustom%2F01jvprse7ptd6b9gccy3m9g547

#FediForum #SurfFeeds #ActivityPub #Decentralization #SocialWeb

@testman oh hey, interesting story behind this!

What I shared was a link to the actual post on Liliputing, but when I pasted in the URL it suddenly disappeared leaving behind what I thought was a link preview.

But now I see it's actually not a link preview but a quote post! So, the Liliputing *website* itself hooked up directly to #ActivityPub, is that how it works @liliputing? 😮

Hear me out: #ActivityPub-backed faxing 📠

#Fediverse #Faxiverse

Now on stage, the man who published the very first post on the #SocialWeb in May 2008 and is often called the father of the #Fediverse: Evan Prodromou @evanEvan Prodromou Co-author of the #ActivityPub protocol at @swf
He presents the structure and dynamics of the social web, including the benefits and disadvantages of this architecture, the products and protocols, people and organizations involved in its development.

#FediMTL #DigitalSovereignty

@steveSteve Bate seems possible to me too, and is also the premise of Protosocial #ActivityPub extension.

What if... you had one Fedi account on a generic headless #ActivityPub server that simply hosts and federates your data... and had C2S UIs for microblogging, long form writing, media editing and sharing, link aggregation, games, fitness tracking, and so on, that all used that same Fedi account. Technically, it's a similar concept as ATProto (but no relay and app view) and Solid Pods (but no RDF).

It seems possible... if we can improve the AP C2S API/protocol sufficiently.

#Mastodon, a #decentralised #socialmedia platform, is introducing #newfeatures to attract creators and make the platform more approachable for newcomers.

🎉 These updates include a #redesigned user profile, an enhanced compose experience, and new admin tools for server operators.

💆 The changes aim to #promote #smallinstances and make the onboarding process more understandable.

👉 https://techcrunch.com/2026/02/18/mastodon-a-decentralized-alternative-to-x-plans-to-target-creators-with-new-features/?Fedizen.EU #Fedizen #Fediverse #ActivityPub #News

@hrast

Social coding commons at https://coding.social considers the online #SocialNetwork to offer a person integral social experiences. As they navigate the #SocialWeb their needs are satisfied by interoperable solutions, provided by apps and services that are delivered to the network. Social experience design #SX drives both the evolution of the technology base, as well as evolution of the ecosystem responsible for cocreating it. This results in a social-first approach focused on service delivery.

Current app-centric #fediverse follows a tech-first maturity model where app needs are leading. Individual app's requirements and features are source of truth, and secondary concern is 'pushing that on the wire'. Apps evolve as siloes independently of each other, and deal with interop issues later (and all the time, a continuous process as there is no real standard way).

So this merging will be very hard. The #ActivityPub API offers opportunity to improve ecosystem development methods.

A couple days ago, I got a DM from a #Bonfire user. I happily replied and sent a follow request—but the Accept never came back, even though they hadn't enabled manuallyApprovesFollowers. My DM reply probably never arrived either. Classic interop bug.

I checked out the Bonfire source and dug in. Turns out Bonfire hasn't implemented RFC 9421 yet, so it was silently discarding any activity signed with it. That alone would be workable, except for one more issue: Bonfire was responding 200 OK even when signature verification failed, instead of 401 Unauthorized.

This matters because Fedify implements a double-knocking mechanism—if a request signed with RFC 9421 fails, it retries with the older draft cavage signature. But since Bonfire returned 200 OK on the failed first knock, #Fedify had no reason to send a second one.

I filed two issues on the Bonfire #ActivityPub repo—one requesting RFC 9421 support, and one about returning 401 on invalid signatures. For the latter, I also sent a PR, which got merged pretty quickly: bonfire-networks/activity_pub#9.

That said, individual Bonfire instances won't pick up the fix until they actually deploy it. So in the meantime, I patched Hollo and Hackers' Pub to use draft-cavage-http-signatures-12 as the firstKnock, so Bonfire instances can at least understand the first request.

One last thing: Fedify caches whether a given server supports RFC 9421, and the Bonfire servers I'd already talked to were cached as “supports RFC 9421”—because they'd been returning 200 OK. I had to manually clear that cache on both hollo.social and hackers.pub before everything finally worked.

After all that, the mutual follow went through and my DM reply landed. Worth it.

#fedidev #fediverse #Hollo #HackersPub

#HolosDiscover is back, from a clean slate.
A #Fediverse search engine that uses standard #ActivityPub federation. It follows you like any account, respects indexable flags, #nobot, #noindex, locked accounts. Deletions, edits, blocks are processed instantly through ActivityPub.
You have full control. Block it, mention it with "unfollow", or disable indexing in your settings.
Source code under AGPL-3.0 on #Codeberg.

Details: https://discover.holos.social/how-it-works

Account: @HolosDiscover

What is the process of publishing #ActivityPub “notes” in the W3C SocialCG or one of its Task Forces (if it’s a different answer)?

@xoronxoron @khleedril

Other than that, some musings..

Your project looks very nice. Kudos! However, the past couple years I've probably seen a quadrillion instant messenger projects pass by. The screenshot on the website is "yet another familiar IM chat UI".

But if I just read your tagline of "Decentralized #P2P encrypted messaging" and I close my eyes a bit, I can picture 'universal messaging' and see something very powerful.

In #ActivityPub conceptual architecture this exists in theory, but the #fediverse diverges from that. In #XMPP and #Matrix protocol realms you hear people say "you can build any social networking use case with the protocol", but then all the documentation and discussions relate narrowly to IM and some of the hardwired abstractions assume IM (like Room in matrix).

With universal messaging I might be empowered with https://eventmodeling.org and https://eventcatalog.dev like solution design, using SDK's on top of a robust p2p protocol component. To model IM and more.

@cwebberChristine Lemmer-Webber @eyeinthesky @smallcircles🫧 socialcoding.. @evanEvan Prodromou Apart from the fact that I would prefer turtle, I am very happy that AP ‘prescribes’ json-ld. This opens the door to many of my ideas. It makes possible what would be very complicated without #RDF. It's about time that the AP developers got to grips with it! https://rdf-pub.org/#rdf

#changinggraph #activitypub

@benBen Werdmuller

What we need is the ability to support #ChaordicOrganization on the #ActivityPub #fediverse.

https://coding.social/blog/reimagine-social/#chaordic-organization

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

To get back to 'shared ownership' and @benBen Werdmuller article that triggered my blog post.

The #fediverse is certainly not all cheerleaders, but the question is whether critical notes can be properly heard and addressed in any meaningful way. After all who are the ones who should hear them and act on them? It is "the herd", the crowd, the commons that happens to receive toots via their social graph, and to the extent these manage to penetrate bubbles and echo chambers. To make a strong argument, to reach people, the only strategy is social media influence marketing of sorts. You have to dare to rock the boat enough to be heard. And that's a very bad way to grow a healthy ecosystem I think.

It relates to the oft-heared criticism that on the app-centric #ActivityPub fediverse, it is the app devs who are de-facto in charge and decide what goes and what goes not.

The social dynamics are tricky but fascinating. I hope to be able to spend more time at https://coding.social

@eyeinthesky

Here we come to my new interest area.. I spent a metric ton of time advocating for #fediverse and #ActivityPub and that was initially all on a very optimistic note on how our ecosystem would mature and grow over time, fostering a healthy future for itself.

That however didn't go as planned. You might say that the entirety of the fediverse is still primarily tech-driven. Tech-first approaches that do not differ too much of the much reviled and rejected 'techbro approach'.

Sure, there are plenty discussions on whether an app feature is 'ethical' or not, with discussions on e.g. opt-in vs. opt-out. But that is again purely app-centric.

Where is the dev ecosystem headed, where should they focus, what externalities exist? Where do we want future #fediverse as a whole to be? What's the vision?

And then we come to the social side of things, both in the small, but also in-the-large. Technosphere aligned and subservient to Sociosphere. That is focus of https://coding.social

@eyeinthesky @cwebberChristine Lemmer-Webber @evanEvan Prodromou @deadsuperheroSean Tilley

There are a couple of really great #IETF documents on protocol design and maintenance. You often see me mentioning protocol decay, which is only a paragraph in the splendid #RFC9413 Maintaining Robust Protocols.

The next section for instance is on detrimental ecosystem effects if you are either too stricly enforcing standards or are too laissez faire about them.

https://www.rfc-editor.org/rfc/rfc9413.html

#SocialWeb #ActivityPub

To name just one example, where I think there exists a typical use case where #Loops can shine wrt #TikTok is personal Loops for friends and family. Friend of a friend personal social networking.

People make lotsa short vids with their mobile, when going on holiday and do all the things that make life worth living. And currently they share it in #BigTech's apps. Send that vid via #Whatsapp. Or place it on #Facebook or #Instagram.

But it would be perfect short-form content in the family's online corner of the web. Put some more integration with other #ActivityPub apps and services in the mix, and they have a full-service alternative to Big Tech stuffz at their disposal.

This is a different use case than how Loops is currently positioned most of all. It emphasizes the Creator. Creators have a need to publish, to reach audiences, to monetize and be able to live from their work.

The personal social networking case is for me personally the more attractive one.

#Thefediverse is a #decentralised #socialmedia network where users can interact across different platforms and servers.

🙌 It offers advantages like increased #resilience against censorship and enhanced user #privacy.

🎭 While it could simplify #contentcreation and audience growth for #influencers, it still requires #creators to tailor #content to each platform.

👉 https://mashable.com/article/what-is-the-fediverse?Fedizen.EU #Fedizen #Fediverse #ActivityPub #News

@eyeinthesky

I think a problem is more that instead of "ActivityPub has JSON-LD" you might also say that AP delegates to.. or even 'handwaves' to linked data.

#ActivityPub is linked data --> ✅ Extensibility mechanism DONE"

Which is either..

- By far not the case, if you consider the promise and power of ActivityPub

- May perhaps be true, if you have a very particular notion on what the fediverse is and isn't.

That last bit remained unspoken, so what AP vs. fediverse is, is really in the eye of the beholder. There exists no shared (technology) vision. https://discuss.coding.social/t/major-challenges-for-the-fediverse/67

With the extensibility mechanism unclear, there is no clear separation either to what is protocol and what is solution space, and there's continuous confusion around this.

I replied to @evanEvan Prodromou yesterday, as his remark would entail that all post-facto interoperability introduced on-the-fly by app impls would have to be honored now in the standards. What standards process does that give?

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

@reiver@reiver ⊼ (Charles) @thisismissemEmelia @mfru🍉 max frühschütz – нет войне

I made a diagram yesterday that contrasts #ActivityPub and #SolidProject that is I think interesting to consider.

In the past I've been very active on the Solid forum, and tried to get a collab going with #SocialHub community. A number of points that existed then, are still issues today I think.

Like, though anyone could participate in the standards process via chat, the Solid team and Inrupt were not really interested in their community, hardly giving attention while people were building interesting stuff there.

Also at the time basically all available code was Javascript, making Solid uninteresting or hard to access for other language devs.

But I think biggest issue was that Solid didn't know what it was. It was positioned as 'personal data vault' on the landing page then (but not using this term), but was 'secretly' TBL's desire to reboot the #SemanticWeb. The new web would be all 'Solid apps'. But the adoption strategy for that didn't exist.

ActivityPub client developer experience is something like this.

Building a coherent feed with stateful objects requires comparing an Activity from the inbox, with what’s in your outbox.

#ActivityPub #c2s #DevEx

RE: https://mastodon.social/@reiver/112133984854710390

"A guide to implement ActivityPub in a static site (or any website)" by @mapacheMaho 🦝🍻

https://maho.dev/2024/02/a-guide-to-implement-activitypub-in-a-static-site-or-any-website/

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse

Steal this idea: an app that combines YouTube and @peertube into a single YouTube-like interface that treats content from both as equals. Where duplicates exist, PeerTube gets priority by default. Throw in some options for patronizing creators on PeerTube, and it could motivate them to migrate to and stay on decentralized platforms.

Even better if self-hosted with Invidious on the backend.

#activitypub #fediverse #opensource #selfhost #youtube