ale (@ale@social.manalejandro.com)
El #takahe me chiva los tuneos que hace la gente con #activitypub
ERROR - ('Invalid JSON-LD syntax; "@id" value must be a string.',)
Type: jsonld.SyntaxError
Code: invalid @id value
Details: {'value': None} | from: users.identity actor:https://cryptid.cafe/users/rowan @cryptid.cafe
Show Original Post
superuserdo (@superuserdo@punkstodon.de)
I need to learn how to install #snac software on my own. I want to run a server for my own use.
#snac #software #singleuser #activitypub #fediverse
Show Original Post
LiquidParasyte (@LiquidParasyte@pawb.fun)
Hey hi I need a favor done
If you have an akkoma account, can you post a comment with a content warning here real quick? I need to see something
#pleroma #akkoma #activitypub #activitypubdebug #boostsWanted, #pleaseBoost
Show Original Post
HolosSocial (@HolosSocial@mastodon.social)
In the #Fediverse, most software is built around a specific platform model. One for microblogging, one for video, one for photos... and new ones will keep coming.
With #Holos, your phone runs your own #ActivityPub server. You control your data and can use your own domain as your identity.
Built on the protocol, not a platform model, Holos is not limited to a single use case. One account that adapts to your needs.
That's where we're heading, and we hope for your support.
Show Original Post
notes (@notes@rmendes.net)
This should go to my roadmap page perhaps but I’m keeping it here as a note just to remember :
ActivityPub
- Improve Quotes display on my AP reader
- Improve image rendering
- Improve Quick Reply (replies that are not stored in this blog database and instead only exist as AP replies) feature so that it shows the actual post, not the JSON representation of my quick reply
- Improve CSS of the AP reader, links are hard to read (blue on grey)
- Fixed hashtags
Conversation aka Brid.gy like
- rebuild reply context to posts so that my replies to other users replies also show up in the right order in the reply thread
Eleventy
- Find a way to render #hashtags in posts, link them to my categories
🔗 https://rmendes.net/notes/2026/02/28/5a764
Show Original Post
smallcircles (@smallcircles@social.coop)
@fox @silverpill @raphael @julian @mariusor
Yes. I tooted about the need for Grassroots open standards and Grassroots standardization this morning..
https://social.coop/@smallcircles/116147786851664068
In a decentralized grassroots movement, somewhere there needs to an aggregation of the solution artifact. In this case a robust, comprehensible #ActivityPub standard that can be readily implemented in libraries, frameworks and SDK's upon which then subsequently #SocialNetworking solution design can take place.
This is not centralization, this artifact can be federated. But there must be a place of convergence where consensus on protocol design comes together.
There might be a crowdsourced ActivityPub 2.0 specs + documentation site, plus a process around it to make it work.
Show Original Post
smallcircles (@smallcircles@social.coop)
SX defines the concept of a Grassroots open standard, and a domain of Grassroots standardization.
These are direly needed to be able to healthily evolve #ActivityPub to where it can be the future of social networking, and support a peopleverse.
Show Original Post
smallcircles (@smallcircles@social.coop)
For Protosocial I was musing on a role for the Profile in modeling identity. Protosocial emphasizes the actor-based nature of #ActivityPub and folllows the actor model in general.
Though these are just showerthoughts atm, a #SX solution on the wire is represented with an Application actor, which can be introspected to find the #SocialWeb services it offers, and these are accessible as service actors.
The Protosocial fediverse is an actor-based service-oriented distributed messaging architecture, combined with a linked data social and knowledge graph distributed data store.
A person should be able to have as many identities as they wish, some anonymous, some pseudonymous, some fully verified. These are all Person actors.
All actors have an ActorID, but they only identify the actor objects themself. The Profile would be a verifiable identity statement. A contextual visitor's card to pass along.
Show Original Post
smallcircles (@smallcircles@social.coop)
@silverpill @raphael @julian @mariusor
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
Show Original Post
smallcircles (@smallcircles@social.coop)
@silverpill @raphael @julian @mariusor
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
Show Original Post
smallcircles (@smallcircles@social.coop)
@silverpill @raphael @julian @mariusor
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
Show Original Post
smallcircles (@smallcircles@social.coop)
@silverpill @raphael @julian @mariusor
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.
Show Original Post