3 ms·
My main issue with the current Fediverse (i.e. ActivityPub universe) is that no one actually use the client-to-server protocol. Only applications federate with
by remram 5y ago
My main issue with the current Fediverse (i.e. ActivityPub universe) is that no one actually use the client-to-server protocol. Only applications federate with each other, exchanging a basic level of their internal representation over the server-to-server protocol, and you need accounts in each of them to go past the basic functions (text comment & retweet).
I feel like it would be much better if I could use a single identity and a single "ActivityPub server" for all my applications.
In the current situation, being able to retweet my PeerTube video from my Mastodon account has little advantage about just tweeting a link to it. Likewise, commenting on a Lemmy thread from my Mastodon account is ok but I can't really see the thread as a thread without logging into Lemmy. Watching a PeerTube video, I can post a comment using my Mastodon account but that requires 5+ click and a change of application.
I am not sure why the ecosystem went this way. The client-to-server protocol was readily available when the Fediverse was kickstarted.
- mcv 5y agoNot sure what you mean. I'm on Friendica, and I can follow, reshare and comment on posts from people on other platforms with no problem. I don't need accounts on other servers for this, though I'm sure my interaction with them is limited to whatever Friendica supports. I don't doubt you can do more if you actually get accounts on different systems, but that's a choice you have. I don't think you need to do it if you don't want to.
- remram 5y agoFollow and comment are the only things that are supported across platforms. That is what I mean by "exchanging at a basic level". To use any of the various features that makes the various applications worthwhile, you have to go create an account in that application and subscribe to people's accounts from there. When Gitea implements federated merge requests and tickets, you will be able to follow repositories from Mastodon and comment on issues from there. That's great! But to do anything else (create/assign/close issues, open/review merge requests, ...) you will have to create a separate Gitea account and use it to interact with Gitea users. This is a serious limit to "interacting with a whole diverse universe".
- zdunn 5y agoBut you can't post a video to Peertube or start a thread on Lemmy. There's a level of interoperability that was envisioned for the fediverse that we're missing right now. If you post a video, Peertube users won't see it despite being the fediverse's main video software. If you post a link with your commentary, Lemmy users won't see it despite being link sharing software. The microblogging platforms ingest most types of posts from the other activitypub softwares, but the other platforms don't ingest posts from the (micro)blogging platforms. With the client-to-server API, the other platforms would just be clients on top of your Friendica account.
- grishka 5y agoThe C2S part of ActivityPub is, to put it mildly, cumbersome. It also shifts way too much logic to the client and prevents an efficient database design. There can, theoretically, be a "dumb" AP server that implements both S2S and C2S and expects the client to do all the heavy lifting. In practice, all current ActivityPub servers are "smart". They treat the S2S protocol as more of an API, and have their own web UI with a specific user experience (Mastodon, Pleroma, and Misskey are microblogs, PeerTube is a video platform, Lemmy is a link aggregator, Smithereen is a social network, and so on). Interactions between these different experiences generally work on a best-effort basis. You can't shove Reddit into Twitter UX and expect something nice to come out, no matter how hard you try.
- remram 5y agoI'm not recommending that all server-side logic be inside of that single ActivityPub server. What I would like is to run a "dumb" ActivityPub server that would hold all my activity and federate, by receiving and sending arbitrary JSONLD documents. This would be my only identity. Then, other servers like PeerTube, Gitea, etc can talk to that server for their federating needs. When I stumble on a video post on Mastodon, I would have a link to open it in my PeerTube instance, where peer-to-peer video transmission would be implemented; but whether I retweet or reply from Mastodon or PeerTube, the same identity would be used. When I stumble on a merge request on Lemmy, I would have a link to open it in my Gitea instance, where Git repositories would be supported; but whether I upvote it from Lemmy or approve it from Gitea, the same identity would be used. This would fit the narrative of the video. > Imagine if you could share videos, events, instant messages, microblogs with the whole universe. Imagine if it didn't matter which planet you came from. > Your login on any of those services allows you to interact with a whole diverse universe.
- zdunn 5y ago> You can't shove Reddit into Twitter UX and expect something nice to come out, no matter how hard you try. Why not? it's text; you could make the same exact post on reddit and twitter (barring the length, which could be truncated in a federated context). Link aggregation is basically just microblogging with the extra constraint that the initial post has to have a link. > Smithereen is a social network What does this mean? Every other platform you mentioned are social networks. On all of these platforms, a user posts text or media posts. Displaying them in a different UI doesn't make them radically different.
- Animats 5y agoYes, the Fediverse isn't federated enough. Framatube is one of the organizations behind PeerTube. But PeerTube isn't very federated. It's just offloaded onto viewing clients. I think. Here's a video of mine supposedly on PeerTube: https://video.hardlimit.com/w/peBesyAgtzfRWS5FnDQQtn https://video.hardlimit.com/w/peBesyAgtzfRWS5FnDQQtn Well, it's really on Hardlimit, which just outsources some of the playback bandwidth. I can't, as far as I know, play that without going to Hardlimit's web site. I can't even embed it without getting Hardlimit's branding. (Getting to full screen mode on mobile is really hard because their top and bottom banners get in the way of the video controls.) I ought to be able to put that long random key into other PeerTube sites and play it, but that does not seem to be possible. This is not "federation". It's a walled garden with outsourcing. The video plays fine. I'm now using PeerTube for my technical videos, where I need streaming but the audience is people who find out about it on technical sites. The federated video crowd needs to 1) get their act together, and 2) get some major forum systems to recognize their URLs as embedded video, as those systems do for Youtube, Twitter, and often Vimeo. That would at least bring them up to where Gyazo is. The video is a pitch deck. A good one. But it's a pitch deck for something that's not fully usable yet.
- remram 5y agoYou are very misinformed. Here is your video on a random instance I found in the instance list [1]: https://peertube.ignifi.me/w/peBesyAgtzfRWS5FnDQQtn https://peertube.ignifi.me/w/peBesyAgtzfRWS5FnDQQtn [1]: https://joinpeertube.org/instances https://joinpeertube.org/instances
- crickcreek 5y agothis is why i gave up on mastadon. add that to a non-existent on-boarding experience.
- zdunn 5y ago> I am not sure why the ecosystem went this way Because when activitypub was still getting off the ground, mastodon built their own client api. A lot of excited people built apps for mastodon so pleroma, and then others, started building Masto API support so that their instances could use mastodon clients. Now the Masto API is the de facto client api. I super agree with you, using the client-to-server protocol so that we could have one account would be the best situation. I've been arguing that on the fediverse for a while, but all the developers in the space seem to think the client-to-server protocol isn't useful enough so you would have to fallback to a custom API for the missing pieces anyway so you might as well use the API everyone's already using.