Jack Dorsey skipped ActivityPub, built AtProto, lost Twitter, funded Bluesky, watched it become a company with VCs and a board, said it was "repeating all the mistakes," left, and now funds Nostr.
-
@quillmatiq @dansup I do know how toxic the response was to Bridgy Fed when Ryan first announced the Bluesky bridge, and I think his ability to weather that storm will go down as one of the most heroic efforts in the history of the social web.
To be fair, most of what I saw against Bridgy Fed wasn't against _bridging_. It was against (a) the initial decision to make it opt-out, (b) the justification "if we make it opt-in, people might not opt in, so making it opt-out will make it more useful". After Ryan listened to people explaining what's wrong with that, and switched to opt-in (respect to him for listening), I don't remember seeing further opposition, though of course there could've been some I didn't see.
-
@thisismissem @stefan the reason for doing this multiplier is not so much for getting MAU right in absolute terms, but because mastodon/fedi MAU data also includes lurkers in their data. So you need it to get a fair comparison between fedi and the atmosphere
@laurenshof So your estimate is based on one "skeet" from a CTO of a company with a multi-million dollar VC "loan" that *needs* their numbers to look good?
Fair enough!
-
To be fair, most of what I saw against Bridgy Fed wasn't against _bridging_. It was against (a) the initial decision to make it opt-out, (b) the justification "if we make it opt-in, people might not opt in, so making it opt-out will make it more useful". After Ryan listened to people explaining what's wrong with that, and switched to opt-in (respect to him for listening), I don't remember seeing further opposition, though of course there could've been some I didn't see.
@unchartedworlds@scicomm.xyz I don't see it either, but I can certainly believe that @quillmatiq@mastodon.social gets a ton of hate simply for being associated with BridgyFed, which is BlueSky adjacent, which is honestly enough for some people to instantly judge you as a bad person.
-
To be fair, most of what I saw against Bridgy Fed wasn't against _bridging_. It was against (a) the initial decision to make it opt-out, (b) the justification "if we make it opt-in, people might not opt in, so making it opt-out will make it more useful". After Ryan listened to people explaining what's wrong with that, and switched to opt-in (respect to him for listening), I don't remember seeing further opposition, though of course there could've been some I didn't see.
@unchartedworlds @quillmatiq @dansup he got brigaded here and on GitHub. It was toxic.
-
@mastodonmigration @baralheia decentralized *where* and *how*
Is ActivityPub really decentralized when everyone builds for compatibility with Mastodon (apart from Lemmy) or is it only decentralized in operations? Where mastodon.social accounts for a significant portion of the network? What about Pixelfed? How much decentralization there? Loops? I think there's only really one maybe two loops servers of any size?
Decentralization doesn't mean "run absolutely everything myself", I mean, sure, you *could* but that's expensive, complicated, and time consuming. Moderation? Most servers just import some blocklist snapshot at a given point in time.
Thing is, decentralization isn't the goal, the goal is better social apps.
Decentralization focuses on technology, not people. It's the "how" not the "why" and "for who"
"Thing is, decentralization isn't the goal, the goal is better social apps." And that's where I have to disagree. Decentralisation is the goal of the Fediverse and ActivityPub. It isn't for ATProto.
ATProto is designed to replicate a sort of "digital town square" where people meet and talk. ActivityPub in it's design is in a sort like the postal service where a instance can be a city, a neighbourhood or a single street/house.
-
@laurenshof So your estimate is based on one "skeet" from a CTO of a company with a multi-million dollar VC "loan" that *needs* their numbers to look good?
Fair enough!
-
@laurenshof Right. From the same person.
Well, again, fair enough, this all answers my question.
Appreciate it, both of you!
-
@dansup@mastodon.social there are walls.. perhaps you don't see them because Pixelfed is large enough that it gets benefit of the doubt.
I got called a VC funded tech bro once, simply because that person found their public posts and profile on NodeBB (because, you know, federation), and absolutely did not back down until their instance's mod told them to quit it.
The smaller devs doing interesting things with fedi get absolutely fucked over for simply exposing the fact that... public stuff is public. 🤯
That's not even getting into any of the tech arguments that make AP federation harder than it should be.
@thisismissem@hachyderm.io @evan@cosocial.ca @quillmatiq@mastodon.social
@julian @dansup @thisismissem @evan @quillmatiq
I need to call this one out, sorry.
"The smaller devs doing interesting things with fedi get absolutely fucked over for simply exposing the fact that... public stuff is public"
More and more, people joining this space are entirely unaware that this is a technical foundation of the space, and more and more people come to me as a service provider asking me why their content is on Web sites they did not sign up for.
-
@julian @dansup @thisismissem @evan @quillmatiq
I need to call this one out, sorry.
"The smaller devs doing interesting things with fedi get absolutely fucked over for simply exposing the fact that... public stuff is public"
More and more, people joining this space are entirely unaware that this is a technical foundation of the space, and more and more people come to me as a service provider asking me why their content is on Web sites they did not sign up for.
@julian @dansup @thisismissem @evan @quillmatiq
I understand why.
You understand why.
Thousands of people do not, and tens and hundreds of thousands being invited in will also not understand this.
We need to do better than "public is public".
-
@julian @dansup @thisismissem @evan @quillmatiq
I understand why.
You understand why.
Thousands of people do not, and tens and hundreds of thousands being invited in will also not understand this.
We need to do better than "public is public".
@jaz@toot.wales fair, and I'm certainly open to user education, but I refuse to engage with individuals who have demonized me from step 1.
I'm not planning to put in the effort to try to win back the trust of someone when I didn't do a damn thing to lose it.
-
@mastodonmigration @baralheia @cwebber on activitypub, if I have 30,000 followers (1 follower per server), and I want to post a message, my server has to send out 30,000 messages.
In AT Protocol, if I want to do the same write operation, I send one http request to my PDS, the PDS then publishes that message to N connected relays (where N =< 12)
@thisismissem @mastodonmigration @baralheia @cwebber
I would argue that neither the AP nor atproto are built directly for patterns of human communication that exist in the real world.
The "everyone messages everyone else and must have access to any message from anyone at any time" pattern embodied by the present Bluesky is not a real human way of communicating and forming communities, it is a figment of tech companies' imaginations and represents a massive amount of over-indexing that relies on, and therefore tends towards, centralized platforms.
The "everyone preferentially messages people in their nearby vicinity but sometimes people further away" view embodied by most present Fediverse software assumes a flat social network in which "non-local" is functionally the same in all cases and does not model human social networks very well.
AP assumes you are building bunch of villages with a flat road network between them. atproto assumes you are building Saudi Arabia's The Line.
-
A cool project you may like is appviewlite: https://github.com/alnkesq/AppViewLite
You can run an appview entirely locally--i was even able to run this on my phone.
Its possible to directly crawl PDSes, meaning there's no reliance on a relay.
There's also https://reddwarf.app, which runs entirely in your browser, without an appview or relay.
And there's wafrn (which I'm using right now), which natively supports atproto and activitypub. It has its own appview, but it currently uses an external appview for notifications and fetching possible missing posts iirc.
@irelephant yup, and this weird protocol tribalism hurts projects like wafrn and bridgyfed, because it drives a wedge between two communities that roughly care about the same thing: better social media/networking.
-
@cwebber
@thisismissem @mastodonmigration @baralheia Content addressing and portable identity is so important and hurts so much everytime a server closes or (like me) had to switch domain name.@maswan @cwebber @thisismissem @mastodonmigration @baralheia ActivityPub is mostly fine with decoupling domain name and identity. From my understanding, you could have an activitypub account on a self-hosted server and have multiple domain name have webfinger software point to it and that account would have multiple handle.
-
@maswan @cwebber @thisismissem @mastodonmigration @baralheia ActivityPub is mostly fine with decoupling domain name and identity. From my understanding, you could have an activitypub account on a self-hosted server and have multiple domain name have webfinger software point to it and that account would have multiple handle.
@gkrnours @maswan @thisismissem @mastodonmigration @baralheia ActivityPub is mostly oblivious to the concept of "instances". It's more actor model, and more like sending mail, and less like villages. Heck, ActivityPub doesn't even have webfinger. Technically, sharedInbox doesn't even need to be on the same domain!
Both instances-as-important and webfinger are activitypub-in-practice rather than activitypub-as-written. But maybe that's immaterial. "The purpose of the fediverse is what it does"???
-
@skarnio @mastodonmigration @baralheia as someone *actively* developing on AT Protocol, I can tell you that Bluesky PBC could disappear tomorrow, and we'd just work around it. There's complete mirrors of the did:plc directory, and we'd just pick one to replace the existing directory. Sure, it'd be hugely disruptive, but life would go on. We would work around it.
There's alternative relays, hostile migration of PDSes is possible, and changing the plc directory is possible. Blacksky probably couldn't handle all of Bluesky's users suddenly all using it, because they're still new, but *shrug* life would go on.
@thisismissem @mastodonmigration @baralheia When I talk about governance, the "disappearance" of a corporation is the least of the problems. The problem is what that for-profit corporation can do to the network while it retains total control. As long as the code doesn't officially transfer its governance to the community in the form of a non-profit organization or something similar, the technology will continue to be controlled by a corporation. Even with the best intentions of the contributors (which I believe are truly very good), that's the reality.
-
@thisismissem @mastodonmigration @baralheia When I talk about governance, the "disappearance" of a corporation is the least of the problems. The problem is what that for-profit corporation can do to the network while it retains total control. As long as the code doesn't officially transfer its governance to the community in the form of a non-profit organization or something similar, the technology will continue to be controlled by a corporation. Even with the best intentions of the contributors (which I believe are truly very good), that's the reality.
@skarnio @mastodonmigration @baralheia but there is code, that does the same thing that is owned by a community: https://blackskyweb.xyz
Bluesky isn't the only group building the protocol layer parts. The spec is going to the IETF for standardisation, did:plc is being transfered to a swiss association.
So bluesky has as much control over the network as we let them have.
-
@skarnio @mastodonmigration @baralheia but there is code, that does the same thing that is owned by a community: https://blackskyweb.xyz
Bluesky isn't the only group building the protocol layer parts. The spec is going to the IETF for standardisation, did:plc is being transfered to a swiss association.
So bluesky has as much control over the network as we let them have.
@thisismissem @mastodonmigration @baralheia Great. Our main problem isn't technology, but politics... the more independent we can be from corporations, the better. I'll look into this information. Thank you!
-
@gkrnours @maswan @thisismissem @mastodonmigration @baralheia ActivityPub is mostly oblivious to the concept of "instances". It's more actor model, and more like sending mail, and less like villages. Heck, ActivityPub doesn't even have webfinger. Technically, sharedInbox doesn't even need to be on the same domain!
Both instances-as-important and webfinger are activitypub-in-practice rather than activitypub-as-written. But maybe that's immaterial. "The purpose of the fediverse is what it does"???
@gkrnours @maswan @thisismissem @mastodonmigration @baralheia Still, if I am going to sad-cassandra-complex about it, which of course I do all the time, I do think it would be completely possible to build a social network system that's even *more* flat than AP-in-practice is today, and I think some decisions along the way, while made for good reasons, ultimately make that harder.
But, as @vv reminded me the other day (about @spritely actually), "You aren't going to have control over when people start using your tools and when they do, you will always feel like you weren't quite ready for that moment."
Which is universal... not just on the fediverse, but the ATmosphere too.
I have more to say about this soon. It's been over a year since I wrote my pieces analyzing how decentralized the Fediverse vs Bluesky/the ATmosphere is, and it deserves a revisit. Ultimately, I think my core analysis was fully correct, but the ecosystems have changed.
-
@thisismissem @mastodonmigration @baralheia Great. Our main problem isn't technology, but politics... the more independent we can be from corporations, the better. I'll look into this information. Thank you!
@skarnio @mastodonmigration @baralheia yeah, and it's a very niche form of political tribalism around protocols, which in the grand scheme of things, don't really matter to every day people.
Protocols are just a means to an end user product that's simple and joyful to use.
There's interesting design choices on both sides, but at the end of the day, it's better to have two open protocols collaborating and being up against walled garden tech giants together.
Like, the repayable repository structure in AT Protocol, or the OAuth profile that they use would be s huge win to the ActivityPub ecosystem to adopt. The "apps are separate from identity and data" is also a vision in the original spirit of ActivityPub (client to server)
I'm just so sick of folks trying to divide what are otherwise two similar projects, where each project could learn a lot from esch other.
-
@gkrnours @maswan @thisismissem @mastodonmigration @baralheia Still, if I am going to sad-cassandra-complex about it, which of course I do all the time, I do think it would be completely possible to build a social network system that's even *more* flat than AP-in-practice is today, and I think some decisions along the way, while made for good reasons, ultimately make that harder.
But, as @vv reminded me the other day (about @spritely actually), "You aren't going to have control over when people start using your tools and when they do, you will always feel like you weren't quite ready for that moment."
Which is universal... not just on the fediverse, but the ATmosphere too.
I have more to say about this soon. It's been over a year since I wrote my pieces analyzing how decentralized the Fediverse vs Bluesky/the ATmosphere is, and it deserves a revisit. Ultimately, I think my core analysis was fully correct, but the ecosystems have changed.
@cwebber @maswan @thisismissem @mastodonmigration @baralheia @vv @spritely from my point of view, which is a bit naive and superficial, more flat mean more message between actor which is less efficient. Meanwhile, I think the current design could "proxy server" with little work. Instance that would provide a handle with a domain, forward message and little more. Then specialized light-weight server, easier to self host, could take advantage of that.
I need to write a PoC for that
