#owncast is FOSS and awesome. so why did #ATproto people build smoke signals? same reason #bluesky didn't just build off #ActivityPub I assume. something something don't mention VC etc.
Discussion
Loading...
Hello! It’s a bit of a story, but I did at first. I was pretty active in the activitypub space having contributed to Mastodon, admined an instance for several years, was active in spec discussions, and had written several apps and implementations for ideas.
and then...
(sorry I'm very skeptical about bluesky/AT. imo they are following the standard VC path. take the money and build and be awesome till the competition is basically dead and then monetize based on everybody now using your shit. until we see how they plan to make money, I think we should understand their growth in this framework.)
Looks like Bridgy didn't bridge the rest, see here: bsky.app/profile/nger... bsky.app/profile/nger...
@mackuba.eu @ngerakines.me @mackuba
I would like better data portability here but I don't understand how the PDS is much better. Doesn't it also matter who hosts your PDS? Isn't it the same as who hosts my fedi server?
@wjmaggos @mackuba.eu @ngerakines.me @mackuba
FWIW, I think the idea of a PDS like thing is a good idea, because it separates front-end development from back-end development.
The Fediverse has had an idea similar to PDS long BEFORE PDS existed — ActivityPods
But, Fediverse alternatives to ActivityPods have been proposed by others.
@reiver @mackuba.eu @ngerakines.me @mackuba
the sense I get is that there are these great ideas that everybody that cares about decentralization would like to implement, but they take time and money and agreement on how to do it. for these reasons, the Mastodon API outpaces ActivityPub (and bluesky moves even faster of course).
Retaining decentralization requires that we slow this process.
[someday a bluesky competitor will have their own API built on AT etc]