ActivityPub: The "Worse Is Better" Approach to Federated Social Networking https://blog.dereferenced.org/activitypub-the-worse-is-better-approach-to-federated-social-networking
@kaniini There are a couple of good points in here, but this is a really cynical take on AP.
I'd agree it has some blindspots that need to be addressed, but lines such as "In an ideal world, the number of ActivityPub implementations would be zero." is pure hyperbole.
Further I would give it more deference if it presented a viable option as opposed to "this is bad, but I don't know how to do it better"
We gotta do better than this if we are to push forward.
@jalcine Aight, cool. Hopefully will get better because this isn't a great start.
There are some salient points about security that I absolutely agree with, but most of it just seems like editorializing.
I'd rather see problems identified and then explorations of possible ways to improve.
But I guess they're saving that for later. I hope.
Yeah I know. I just think that's a poor way of going about it.
The proliferation of AP is providing a real opportunity for us to not only think about how we communicate but more effective ways to do it, a couple of which you name, which is cool.
I'm so down w/ the protocol being changed in a way that makes it better, but saying we shouldn't be using it at all is step backwards.
Cool. I'll wait for that. I really want to see viable options. Especially if they work
This. The challenge of federation is social, not technical. It's a much better situation to have an imperfect protocol that everyone uses than to endlessly iterate - every fork of the shared protocol splinters the network and gets us further away from the dream of an open, connected web.
@sean @kaniini @jalcine
Sure, but what are the chances that competing protocols will actually maintain compatibility with each other? The web is built on a stack of shared protocols - imagine if every website didn't use HTTP! ActivityPub is a 90% solution, and I think the last 10% can be built on top of it without breaking compatibility.
@jdormit @jalcine @Are0h @sean @kaniini I think AP is under-specced primarily due to constraints impose by W3C (time and otherwise) and a desire to formally pin down as much as possible while Mastodon was ploughing ahead with its implementation to minimize the risk of it rolling out too many bad ideas ad-hoc. I think Chris (Webber, co-editor of AP) is aware of the gaps and interested in seeing them filled. For example mentioning OCAP here: https://dustycloud.org/blog/spritely/
I agree Mastodon itself has shown good restraint in only causing "minor damage" considering its out sized influence. That said Eugen seemed to be a bit of a catalyst in pulling such advice out of Social CG. It's good and bad in different ways.
Chris is this deep thinker and I think tried to make sure AP was flexible enough to address future concerns, but is the antithesis of Eugen who forges ahead to scratch itches. @kaniini seems to provide balance.
@msh @jdormit @jalcine @sean And just to piggy back on this comment, if it turns out that what Masto is becoming is not conducive to the changes that need to be made to AP, I will abandon it in a _heartbeat_.
Popularity shouldn't be the defining factor of the what the protocol should be. Stability and security has gotta be at the core of it. That's something I hard agree with @kaniini on
Honestly, I'm not too worried about their being different forks, because that breeds diversity and resists stagnation.
That said, we do need to come to some type of common ground that we can build from. If it's not going to be AP, I want to see a tangible option so the proliferation of the fediverse isn't stunted.
@jdormit @Are0h @sean @kaniini That's _still_ something that can be worked around. In the #IndieWeb, there's a service that converts from different protocols (http://granary.io/) and even backfeeds and emits stuff to other platforms (http://brid.gy/ and http://fed.brid.gy/). We can push forward without leaving anyone behind.
@jalcine That's fantastic...thanks for linking to that!
I had too many thoughts about this to fit here, so I wrote them up in a blog post: https://jeremydormitzer.com/blog/activitypub-good-enough-for-jazz/
I don't understand the need to abandon the spec so early when there is an opportunity to shape it a direction that is conducive to security and safety.
If we can fix it, let's do that rather than squander all of the activity around it and start again from scratch. That's not good for the fedi. Constantly reinventing the wheel will send it back into obscurity.
@Are0h @kaniini @jdormit @jalcine @sean There is also always the option of making the weaknesses known to end users well enough, so they won't use a thing for the wrong purpose As in: No one puts anything really sensitive into a real-world postcard, because they understand postcards. So if I understand what to put into a particular social media thing and what not, I can still be reasonably safe.
But I'd prefer to have something more safe too, hence we're working on darcy.is :)
Regarding privacy and future deniability: I am in a very privileged position of not having to overly worry about these things, so yes, I personally fail at this when writing webpage blurbs. That is why we won't build anything before having talked to people who do care more about this. 1/2
Also: We don't want to supplant other solutions. Darcy is supposed to play nice with those and respect those communities that have specific needs for privacy or security. 2/2
@kaniini @jdormit @Are0h @jalcine @sean
thanks! Also, just as a clarification: We probably won't use Solid as the social layer (which timbl will probably be cross about), but as the datastore. So your content (posts, media, comments) will be stored on your Solid pod, instead of your chosen instance. Instance and Pod may be the same system, but they don't have to.
If you do separate them, you can move instance while keeping your data.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!
Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!