smallcircles (@smallcircles@social.coop)
💫 "As fediverse developer I am schooled in the arcane arts of #ActivityPub wire incantations"
versus ..
🚀 "As fediverse developer I grab an ActivityPub library or SDK and build that new solution"
Where do you want to go today?
Show Original Post
gutocarvalho (@gutocarvalho@bolha.us)
O jedi mostrou a instância https://activitypub.academy que pode ser usada para testes e desenvolvimento.
A instancia é zerada diariamente.
https://bolha.video/activitypub
#bolhaverso #estudos #activitypub
Show Original Post
gutocarvalho (@gutocarvalho@bolha.us)
Estamos construindo um bot com botkit/fedify do TS pra activityPub.
https://bolha.video/activitypub
#bolhaverso #estudos #activitypub
Show Original Post
smallcircles (@smallcircles@social.coop)
Yes, for the ideation on Protosocial as an #ActivityPub compliant extension (going back to the roots with blank slate W3C specs) I imagined mapping the AS primitives to consistent protocol capabilities and thereby define a set of normative architecture patterns, like "this is how we do CRUD, this is Publish/Subscribe, this is an Event stream and this a Collection", etc.
Then Protosocial library and SDK implementers would need to deal with #ActivityStreams at a low-level plumbing impl detail, while solution developers would have a higher-level API to invoke these patterns. And other than that would not need to touch #ActivityStreams which is now entirely reserved to making AP work on the wire.
A combination of linked data practices and schema-based design would be used for both open-world and closed-world extension modeling. But here too the solution developer should be shield from the nitty gritty internal mechanics.
Show Original Post
gutocarvalho (@gutocarvalho@bolha.us)
Já estamos na sala!
https://bolha.video/activitypub
#bolhaverso #estudos #activitypub
Show Original Post
gutocarvalho (@gutocarvalho@bolha.us)
É hoje povo, de graça voce vai ver um JEDI, isso mesmo, um mestre JEDI aqui na bolha, criado em Coruscant, com passagem por Kamino e Tatooine mostrando como usar ActivityPub com JS.
Vai perder?
Separe seu sabre de luz (lá ele), e vem.
19:30 no melhor jitsi dessa parte do fediverso.
https://bolha.video/activitypub
#bolhaverso #estudos #activitypub
Show Original Post
smallcircles (@smallcircles@social.coop)
Btw, some time ago in a matrix discussion I sketched how I'd like to conceptually 'see' the social network. Not Mastodon-compliant per se (though it might be via a Profile or Bridge) but back to "promised land". Where the protocol is expressed in familiar architecture patterns and borrows concepts from message queuing, actor model, event-driven architecture, etc.
Then as a "Solution designer" I am a stakeholder that wants to be completely shielded from all that jazz. That should all be encapsulated by the protocol libraries and SDK's that are offered in language variants across the ecosystem. #ActivityPub et al is a black box. I can directly start modeling what should be exchanged on the bus, and I can apply domain driven design here. And if I have a semantic web part of my app I'd use linked data modeling best-practices.
I would have power tools like #EventCatalog and methods like #EventModeling.
https://www.eventcatalog.dev/features/visualization
Show Original Post
chillicampari (@chillicampari@layer8.space)
Move Slowly and Build Bridges: Mastodon, the Fediverse, and the Struggle for Democratic Social Media by @rwg
ActivityPub: Programming for the Social Web by @evan
Governable Spaces: Democratic Design for Online Life by @ntnsndr
Is that a good start already or is there something I am missing?
#fediverse #askfedi #activitypub
Show Original Post
smallcircles (@smallcircles@social.coop)
#ActivityPub builds on top of #ActivityStreams in the sense that it adopted a number of its 'social primitives' defined in its vocabulary, and Collection being among those. These particular uses become 'protocol space', but other than that AS from the perspective of AP solution development is purely a set of social primitives, granular building blocks that one *may* use in a solution. AS is a utility library of sorts then. Or is that a wrong perception?
A 'feed' is something that lives in solution space, and I would only choose Collection to model it, if it offers a perfect fit in functionality. And aboveall.. does not assign some new app-specific use along the way.
I tooted today that I feel the biggest folly of the fedi is that everyone tries to cram their domain into the AS namespace. The AS primitives should not be Swiss army knives and have only singular well-defined meaning and purpose, yet they have become that along the way.
https://social.coop/@smallcircles/116096886732404993
Show Original Post
p (@p@photos.cosocial.ca)
I half-ran an #ActivityPub API task force call between leaving the house and getting into my seat on the airplane. Absolutely mysterious.
Show Original Post
objects (@objects@social.rjp.is)
The Mastodon API could do with an expires_at option for posting non-poll statuses which are useless after a specific date (such as gig notifications, etc.)
(Akkoma/Pleroma support it as a custom extension but Mastodon/GotoSocial don’t seem to.)
(Obviously I can rig something up to remember what’s been posted in SQLite and delete/mark them expired when their time is up but it’d be easier if it was part of the general API.)
Show Original Post
lps (@lps@mograph.social)
I was just reminded of the awesomeness of #castopod the self-hosted #podcasting platform that is connect to the #fediverse by #activitypub
This allows us to follow, comment etc etc from #mastodon or similar apps:)
And discovery is easy:).
https://index.castopod.org/#&language=en
And to get you started, for the techies out there, may I suggest
the latest episode is amazing!
"Guerrilla Infrastructure in the Age of the Electrostate"
Show Original Post