reiver (@reiver@mastodon.social)
I've seen an ongoing debate between "Note" versus "Article" in ActivityPub / ActivityStreams.
When is something a "Note"‽
When is something an "Article"‽
Personally — I would probably have made the distinction this way.
An "Article" has a title.
A "Note" doesn't have a title.
(In ActivityPub / ActivityStreams, a 'title' seems to tend to get represented in the "name" field.)
#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse
Show Original Post
naturzukunft2026 (@naturzukunft2026@mastodon.social)
@silverpill
What's going on with
https://codeberg.org/fediverse/fep/src/branch/main/fep/0837/fep-0837.md
are there any activities ?
Show Original Post
smallcircles (@smallcircles@social.coop)
Thank you, that is nice to hear. I am however not an expert, am but a humble generalist and a person who'd love to be in that Solution developer stakeholder role. Who however does not see the fediverse trend in a direction where I'd adopt the technology for what I have in mind. Drifting away from "the promise" that I read in the #ActivityPub specs in 2017, which made me decide to lend a helping hand here and there.
Show Original Post
naturzukunft2026 (@naturzukunft2026@mastodon.social)
Have I already mentioned that the “Show thread” request is slowly driving me crazy?
Show Original Post
naturzukunft2026 (@naturzukunft2026@mastodon.social)
I opened a issue in the swicg ActivityPub API repo about a gap i keep running into: how does a C2S client access server-local metadata about foreign objects?
Thread collections, read status, notifications — your server knows things about remote objects that the client needs, but AP has no vocabulary for it.
https://github.com/swicg/activitypub-api/issues/60
Show Original Post
smallcircles (@smallcircles@social.coop)
> it's ok if you haven't heard of a REST API.
Well, you be you. I consider this a 'typical Evan remark' by now, dripping with sarcasm. It is a weird fit for someone who want to lead the #SocialCG efforts, I'd say.
Ah well. What I am talking about is architecture and design, and all the things that allow people to easily form a clear mental picture on how things fit together, wrap their head around the fediverse.
A HTTP interface is a very low-level thing, and clearly but one of the many moving parts that play a role in #ActivityPub based solution development.
Never defining this well, and having the documentation be scattered all across the fediverse in 1,001 random locations doesn't help. Meanwhile the dev talk that is going on for years remains very inefficient due to endless Babylonian speech confusion.
https://social.coop/@smallcircles/116109447243110037
Show Original Post
smallcircles (@smallcircles@social.coop)
The current fediverse is an evolutionary dead-end for 2 reasons:
1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay.
2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out.
Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep #ActivityPub experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with.
To avoid fedi to become less and less attractive to newcomers, we must now consider:
“Why do we want to grow the open social web, and for whom?” -- @ben
http://coding.social/blog/shared-ownership/
Show Original Post
smallcircles (@smallcircles@social.coop)
Another issue: Unclear protocol layers.
> I am not a fan of the idea that #ActivityPub is a message-passing system; it's a read-write API.
I'm not sure what a "read-write API" is, really. It 's a fuzzy term, whereas message based systems have well-defined architecture patterns and a body of IT knowledge and practice to apply them in robust communication systems. A 'Message API' has a generic, consistent interface.
The overarching goal of AS/AP should be empowerment of the Solution developer so they can directly focus on building use cases for their application or business domain. They should not have to think about any of the intrinsics of the protocol, like particular GETs and POSTs used to model protocol capabilities in the HTTP transport layer.
Solution design then involves:
0. Model the domain
1. Data modeling, msg formats + validation
2. Define actor msg exchange patterns
3. Document design
--
4. Improve these steps. Add native protocol + tool support over time.
Show Original Post
smallcircles (@smallcircles@social.coop)
Note that there is an accompanying issue in the #ActivityPub API repository, where I transferred my reply to in the following comment:
https://github.com/swicg/activitypub-api/issues/9#issuecomment-3938841868
I also added a very nice demonstration that is interesting for the #Mastodon folks, as it is using #Ruby in the event-sourced set up.
https://github.com/ismasan/sourced_todo
Show Original Post
post (@post@lemmy.world)
So I have activitypub up and running on my wordpress blog, but posts don't show
https://lemmy.world/post/43410626
Show Original Post
bendik (@bendik@bendik.social)
Federation and decentralisation is how I want the “world wide web” to be.
#fediverse #activitypub #www #internet #worldwideweb #socialmedia #mastodon #toot
Show Original Post
everton137 (@everton137@social.vivaldi.net)
I think it's great that we can now comment on replies made by #BlueSky users to my #BridgyFed account.
From a user perspective, if we have really interoperable #ActivityPub and #ATProtocol, I find that very positive.
Would you say that instances that opted for the AT Protocol are part of the #Fediverse if that happens more smoothly in the future?
Show Original Post