What if...
-
What if... you had one Fedi account on a generic headless #ActivityPub server that simply hosts and federates your data... and had C2S UIs for microblogging, long form writing, media editing and sharing, link aggregation, games, fitness tracking, and so on, that all used that same Fedi account. Technically, it's a similar concept as ATProto (but no relay and app view) and Solid Pods (but no RDF).
It seems possible... if we can improve the AP C2S API/protocol sufficiently.
-
What if... you had one Fedi account on a generic headless #ActivityPub server that simply hosts and federates your data... and had C2S UIs for microblogging, long form writing, media editing and sharing, link aggregation, games, fitness tracking, and so on, that all used that same Fedi account. Technically, it's a similar concept as ATProto (but no relay and app view) and Solid Pods (but no RDF).
It seems possible... if we can improve the AP C2S API/protocol sufficiently.
@steve seems possible to me too, and is also the premise of Protosocial #ActivityPub extension.
-
What if... you had one Fedi account on a generic headless #ActivityPub server that simply hosts and federates your data... and had C2S UIs for microblogging, long form writing, media editing and sharing, link aggregation, games, fitness tracking, and so on, that all used that same Fedi account. Technically, it's a similar concept as ATProto (but no relay and app view) and Solid Pods (but no RDF).
It seems possible... if we can improve the AP C2S API/protocol sufficiently.
@steve I believe in this vision.
-
What if... you had one Fedi account on a generic headless #ActivityPub server that simply hosts and federates your data... and had C2S UIs for microblogging, long form writing, media editing and sharing, link aggregation, games, fitness tracking, and so on, that all used that same Fedi account. Technically, it's a similar concept as ATProto (but no relay and app view) and Solid Pods (but no RDF).
It seems possible... if we can improve the AP C2S API/protocol sufficiently.
@steve@social.technoetic.com it's very possible, it's not so much the protocol per se but implementation, like AP has support for groups or blogs or Videos ( Lemmy, PeerTube ) the problem is just mastodon doesn't support anything other than
Note, it is artificially limited platform -
What if... you had one Fedi account on a generic headless #ActivityPub server that simply hosts and federates your data... and had C2S UIs for microblogging, long form writing, media editing and sharing, link aggregation, games, fitness tracking, and so on, that all used that same Fedi account. Technically, it's a similar concept as ATProto (but no relay and app view) and Solid Pods (but no RDF).
It seems possible... if we can improve the AP C2S API/protocol sufficiently.
@steve This is exactly the sort of thing I'm hoping we see on the Fediverse
One thing that might need some careful design is: how to scope down the access that each of the C2S-connected apps have? A game for example doesn't need to be able to read all of my/my friends' messages, only game-related ones
I think the work Spritely's been doing could be a good building block for such a generic server
-
What if... you had one Fedi account on a generic headless #ActivityPub server that simply hosts and federates your data... and had C2S UIs for microblogging, long form writing, media editing and sharing, link aggregation, games, fitness tracking, and so on, that all used that same Fedi account. Technically, it's a similar concept as ATProto (but no relay and app view) and Solid Pods (but no RDF).
It seems possible... if we can improve the AP C2S API/protocol sufficiently.
@steve this is a reason why blue sky made a new protocol. Tu support that first day. Fedi will take 20 years to do that
-
What if... you had one Fedi account on a generic headless #ActivityPub server that simply hosts and federates your data... and had C2S UIs for microblogging, long form writing, media editing and sharing, link aggregation, games, fitness tracking, and so on, that all used that same Fedi account. Technically, it's a similar concept as ATProto (but no relay and app view) and Solid Pods (but no RDF).
It seems possible... if we can improve the AP C2S API/protocol sufficiently.
@steve If by "sufficiently improve" you mean throwing it away and replacing with a better protocol, then yes it's possible.
-
@steve this is a reason why blue sky made a new protocol. Tu support that first day. Fedi will take 20 years to do that
It depends.. since post-facto interop rules supreme, that's a possible approach to correct course.
-
@steve this is a reason why blue sky made a new protocol. Tu support that first day. Fedi will take 20 years to do that
-
What if... you had one Fedi account on a generic headless #ActivityPub server that simply hosts and federates your data... and had C2S UIs for microblogging, long form writing, media editing and sharing, link aggregation, games, fitness tracking, and so on, that all used that same Fedi account. Technically, it's a similar concept as ATProto (but no relay and app view) and Solid Pods (but no RDF).
It seems possible... if we can improve the AP C2S API/protocol sufficiently.
@steve I've often wanted to have a C2S setup. Reading https://overreacted.io/a-social-filesystem/ made me want it more
-
@steve this is a reason why blue sky made a new protocol. Tu support that first day. Fedi will take 20 years to do that
@lutindiscret @steve this is built into ActivityPub and has been since the start.
-
@steve If by "sufficiently improve" you mean throwing it away and replacing with a better protocol, then yes it's possible.
I can't wait to see what you build! Good luck.
-
I can't wait to see what you build! Good luck.
Maybe I am way over my head, but this seems like *exactly* what I am building right now and I'm not really building anything outside of ActivityPub C2S?
I mean... Yes, my current client assumes some specific profile for OAuth and the client will need a proxy to get some data remote servers (to bypass authorized fetch, or to resolve documents from transient activities), but doesn't seem to me that anything I am doing is outside of AP's scope?
-
What if... you had one Fedi account on a generic headless #ActivityPub server that simply hosts and federates your data... and had C2S UIs for microblogging, long form writing, media editing and sharing, link aggregation, games, fitness tracking, and so on, that all used that same Fedi account. Technically, it's a similar concept as ATProto (but no relay and app view) and Solid Pods (but no RDF).
It seems possible... if we can improve the AP C2S API/protocol sufficiently.
@steve I've built the server part already, that was 5 years ago. Still waiting for people with the skills to build the UIs though...
-
Maybe I am way over my head, but this seems like *exactly* what I am building right now and I'm not really building anything outside of ActivityPub C2S?
I mean... Yes, my current client assumes some specific profile for OAuth and the client will need a proxy to get some data remote servers (to bypass authorized fetch, or to resolve documents from transient activities), but doesn't seem to me that anything I am doing is outside of AP's scope?
@raphael @silverpill @steve I also think that Steve's vision is realisable with ActivityPub API, although I think adding optional features like search, server push and so on makes it easier.
-
@raphael @silverpill @steve I also think that Steve's vision is realisable with ActivityPub API, although I think adding optional features like search, server push and so on makes it easier.
Silverpill does not agree with us. I am wishing Silverpill well in their plan to rebuild with a completely different ground-up API. Silverpill is skilled and smart and very familiar with ActivityPub in great detail, so I'm sure they will come up with some interesting API architecture.
-
Silverpill does not agree with us. I am wishing Silverpill well in their plan to rebuild with a completely different ground-up API. Silverpill is skilled and smart and very familiar with ActivityPub in great detail, so I'm sure they will come up with some interesting API architecture.
@raphael @silverpill @steve I don't intend to stop working on the ActivityPub API.
There are a lot of us collaborating through the SocialCG ActivityPub API Task Force, and I expect that collaboration to continue:
GitHub - swicg/activitypub-api: ActivityPub API Task Force repository.
ActivityPub API Task Force repository. Contribute to swicg/activitypub-api development by creating an account on GitHub.
GitHub (github.com)
-
@steve I've built the server part already, that was 5 years ago. Still waiting for people with the skills to build the UIs though...
@mariusor @steve Does your server work with https://checkin.swf.pub/ ? Or https://github.com/evanp/ap ?
-
@mariusor @steve Does your server work with https://checkin.swf.pub/ ? Or https://github.com/evanp/ap ?
-
@mariusor @steve Does your server work with https://checkin.swf.pub/ ? Or https://github.com/evanp/ap ?
@evan @mariusor @steve oh neat!
Add Arrive outbox handler for check-in activities by pfefferle · Pull Request #2977 · Automattic/wordpress-activitypub
ActivityPub for WordPress. Contribute to Automattic/wordpress-activitypub development by creating an account on GitHub.
GitHub (github.com)
