I agree that AP/AS has its limitations and shortcomings, but —
I want this to work with Fediverse software.
If I choose a Linked-Data namespace not supported by any Fediverse software, it won't be.
There are a couple of #ActivityPub projects that focus on providing the good tools that abstract away the complexities of wire-level network comms
You're talking to a developer of such project.
There is no "wire chaos", where did you get this idea from?
New post: Can we have a more “social” media?
https://profpatsch.de/essays/a-more-social-media
On advertising, the Fediverse, and what a more human social web could look like.
Special mentions: @smallcircles, @phnt, @happy-programming
@Profpatsch You need to create a new signature because the request target is changing. It is a part of a signature base, so the initial signature becomes invalid when the client follows a redirect.
@Profpatsch @liaizon The guide recommends limiting the response size, to prevent DoS.
I also found this in your SECURITY.md:
@smallcircles its called ruby text! Very intentional. It's a way of writing out the pronunciation of one script with another that's common with CJK languages but not really outside of those. Tho the html feature can be added to any language
@smallcircles Fediverse is not like email because ActivityPub has many different message types. What kind of client API developers use is irrelevant.
@smallcircles OK, great. Let's try to keep the conversations there instead of here, so everyone can participate.
@smallcircles @phnt @happy-programming I am skeptical of that, because of the mess that is the matrix protocol
@smallcircles I'm not sure. It's pretty important for me to track user stories as issues -- that's been the best way to get things done in task forces so far.
Great, thanks.
@smallcircles @julian I think we might have different ideas about what the ActivityPub API task force is for.
To me, it's about making it possible for clients to use different servers, and different implementations of the API. That's going to include the social API defined in the ActivityPub standard, but it will also encompass things like rate limits, authentication, caching, CORS, and so on.
How that all gets documented will probably be in one or more community group reports.
The extent to which the default profile becomes a 'straightjacket' impact scope, applicability, and usability. I guess its alright as long as there's sufficient flexibility and extensibility taken into account. Guess the "sufficient" does the heavy lifting here.
@smallcircles @julian I think that's always a tension in standards! How do you make it explicit enough that developers can build interoperable software, but extensible enough that they can try new things?
I think one pattern that works well is some base-level standards assumed, and easy ways for extensions to be discoverable and negotiable. If your preferred extension isn't available from the software on the other side of the line, you fall back to the base-level standard.