With respect to #ActivityPub
-
smallcircles (Humanity Now π)replied to 1A last edited by
This is specifically addressed by considering the Fediverse to be part of a bottom up 3-stage standardization of which also the FEP is part, among others. Here there's no such thing as "control" but things bubble up to W3C from a decentralized ecosystem. See:
3-Stage Standards Process: Guaranteeing an open and decentralized ecosystem
Open ecosystem, open ecosystem, open ecosystem In various channels where the Standards Process is discussed thereβs mention of a 2-stage structure that goes like: FEP β W3C. As I proposed many times before (like here, aβ¦
SocialHub (socialhub.activitypub.rocks)
-
Ben Pate π€π»replied to smallcircles (Humanity Now π) last edited by
@smallcircles @lily @jenniferplusplus @puppygirlhornypost2 @hrefna @helge
Yeah, maybe "must" is too strong. I just don't see a viable way forward if we just throw *everything* away.
But what *could* we do to make development easier? I'd start with:
- a strict schema for objects and activities that defines what is a string, what's an object, and what's an array
- something better than HTTP sigs OMG
- real use cases for user-level interop, like FEP-3b86
-
@lily @puppygirlhornypost2 @jenniferplusplus @hrefna
"Strict" mode isn't a real thing -- it's just a fantasy of mine where we have actual definitions of what objects/properties are and how they're used.
Imagine something like "use strict" in Javascript applied to ActivityPub. (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode)
In the ActivityPub world, it would have saved me 80% of the code I wrote to get Emissary to Federate.
-
@laurenshof @puppygirlhornypost2 @jenniferplusplus @hrefna @benpate my issue with atproto is that its vision is incompatible with how the fediverse operates
the fediverse forms a lot of natural circles based on how things federate while on atproto you see everything from everywhere which is not even a bad thing in itself, but combined with the main audience of bluesky (because that's the only noteworthy atproto implementation atm) (mostly ex-twitter users, where the culture is completely different and focused on numbers instead of interaction), it makes me feel alienated. it's that feeling that i'm interacting with people but there is no connection made -
Ben Pate π€π»replied to Ben Pate π€π» last edited by
@lily @puppygirlhornypost2 @jenniferplusplus @hrefna
RIP LitePub: https://litepub.social
I think something like this is the most realistic way to simplify ActivityPub development, so it would be invaluable to understand why LitePub is now a ghost town.
If any of the elders here know the story of what happened there, this'd be a story worth telling.
Call it ActivityPub 2.1. It could start with some simple refactors to make all of our outbound messages rational and self-authenticating.
-
@lily @laurenshof @puppygirlhornypost2 @jenniferplusplus @hrefna
I donβt know if thatβs because of the AT protocol or the community/culture of ex-Twitter users.
Same with Nostr (an interesting technical idea) vs. the Nostr community of crypto-bros and βdonβt tread on meβ / βfree speech absolutistsβ
-
@benpate @puppygirlhornypost2 @jenniferplusplus @hrefna @laurenshof i think it's both. when you see literally everything that's being talked about, that's so much stuff to be constantly paying attention to, and it gets hard to build meaningful connections
-
@lily @puppygirlhornypost2 @jenniferplusplus @hrefna @laurenshof yeah, I see that too. I also have a lot of trouble with updates on Macedon. For example, even in this thread, itβs hard to always know whatβs happening in the conversation.
I blame that on the clients, and lazy UX design, and not ActivityPub itself. But who knows? The protocol could easily be skewing things in One Direction or another.
-
smallcircles (Humanity Now π)replied to Ben Pate π€π» last edited by
@benpate @lily @jenniferplusplus @puppygirlhornypost2 @hrefna @helge
Many points have been brought up in the course of the year and discussed in a variety of different contexts. Trouble is that all of that is now fragmented and dispersed.
Ideally we should exchange ideas and insights in a more central location. SocialHub may be too AP-themed for this.
I can offer forum space at https://discuss.coding.social and a dev portal at https://fedi.foundation and also Hedgedoc, Codeberg org, Matrix space.
-
smallcircles (Humanity Now π)replied to smallcircles (Humanity Now π) last edited by
@benpate @lily @jenniferplusplus @puppygirlhornypost2 @hrefna @helge
Note that I won't be direct member of the initiative but can facilitate it within Social Coding movement, where the initiative itself retains full independence.
-
smallcircles (Humanity Now π)replied to smallcircles (Humanity Now π) last edited by
@benpate @lily @jenniferplusplus @puppygirlhornypost2 @hrefna @helge
Note that I won't be direct member of the initiative but can facilitate it within Social Coding movement, where the initiative itself retains full independence.
The initiative falls within scope of the movement which is dedicated ultimately to the vision of the Social Web. "Social reimagined".
-
@lily @puppygirlhornypost2 @jenniferplusplus @hrefna @benpate One way out of this particular chicken-and-egg conundrum is to provide a reference translation layer or proxying client that will provide compatibility with AP whilst allowing implementers time to migrate. Then you can make decisions about what subset of features to expose without having to burden your protocol with compatibility. Experience with AP suggests to me there's significant value in reference implementations.
-
@sebinthestars @lily @puppygirlhornypost2 @jenniferplusplus @hrefna
Depending on the specific changes/simplifications to AP, this could be an excellent solution... like a single you attach to your USB-A cables so they plug into a USB-C port.
-
@[email protected] @[email protected] @[email protected] @[email protected] @[email protected] Can we replicate how that breaks power delivery by making it invalidate HTTP Signatu.. oh fuck. yeah im seeing a problem here
-
@puppygirlhornypost2 @sebinthestars @hrefna @jenniferplusplus @lily
*Depending on the specific changes...
Of course HTTP signatures throws a monkey-wrench in any migration plan (not to mention "Authorized Fetch")
But all of this is academic until we have a specific list of changes. I'm pretty certain (depending on the list) that we could chart a smooth-ish migration path forward.
I'm happy to write up my own thoughts for others to pile on to. We have to start somewhere, yeah?
-
@[email protected] @[email protected] @[email protected] @[email protected] @[email protected] also although it might sound nihilistic to list out every potential problem it is actually worthwhile to come up with a list of "potential issues" to workaround.
-
@puppygirlhornypost2 @sebinthestars @hrefna @jenniferplusplus @lily
So, apparently I'm collecting a list of #ActivityPub pain points, now.
(shit)
What's your top ten list? I'd love to compare, and make sure I collect a complete picture, even if I don't have a good solution to the problem just yet.
-
Mike Macgirvin π₯οΈreplied to Hrefna (DHC) last edited byReally the biggest issue I've encountered is that the people who have been driving the bus when it comes to specifying the transfer of ActivityStreams between actors can only see the world through Twitter-coloured glasses.
ActivityStreams itself is what it is. Like HTML, it's a mess. Best practices will emerge (this is still happening) and eventually the spec will evolve. FEPs are a good step forward. Not perfect either, but it's a really just collecting the best practices and extension proposals and letting folks pick and choose. Some FEPs will turn out to be 'Recommended' and a few 'Mandatory'. The hardest part will be keeping brands and politics and corporations the hell away from messing with the Mandatory column. -
-
Johannes Ernstreplied to Ben Pate π€π» last edited by
@benpate @puppygirlhornypost2 @sebinthestars @hrefna @jenniferplusplus @lily
One of my pet peeves: Guarantee that the the "fetch"-based sequence of activities is the same as the "POST"-based sequence. In other words, guarantee that if I missed receiving a POST, I can recover by browsing the outbox.