Good morning Fediverse.
-
Good morning Fediverse.
I think I came across a good example, why ActivityPub C2S is bad. Consider wanting to display an actor profile. Like mine. You will probably want to display if you are already following me or not or well if you requested to follow me and I didn't react.
To do this with C2S is complicated. One can work around its limitations. However, that's homework to understand how C2S is awful. For this homework problem, please consider at least 2 clients. Second part, a client without permanent storage.
See cattle_grid#147 for how something that has processing capabilities can get around it.
-
Good morning Fediverse.
I think I came across a good example, why ActivityPub C2S is bad. Consider wanting to display an actor profile. Like mine. You will probably want to display if you are already following me or not or well if you requested to follow me and I didn't react.
To do this with C2S is complicated. One can work around its limitations. However, that's homework to understand how C2S is awful. For this homework problem, please consider at least 2 clients. Second part, a client without permanent storage.
See cattle_grid#147 for how something that has processing capabilities can get around it.
> To do this with C2S is complicated.
@helge as you don't bother to explain why you think that, I'll answer you just this: No it's not.
-
> To do this with C2S is complicated.
@helge as you don't bother to explain why you think that, I'll answer you just this: No it's not.
@mariusor @helge i don’t understand how to tell if a Follow exists or if someone is in the followers collection without storing that information *somewhere*. why would you want to do it without storage?
i find that the problem is easier to think about if you replace every instance of “you are a client” with “you are an http user agent”. you are now stateless and must access that persistent state from somewhere else, aka the server.
or you could do local-first and sync state between peers, but…
-
@mariusor @helge i don’t understand how to tell if a Follow exists or if someone is in the followers collection without storing that information *somewhere*. why would you want to do it without storage?
i find that the problem is easier to think about if you replace every instance of “you are a client” with “you are an http user agent”. you are now stateless and must access that persistent state from somewhere else, aka the server.
or you could do local-first and sync state between peers, but…
@mariusor @helge more re: the actor living on the server and state being stored on the server, imagine using proxyUrl (so that you are authenticated against your server), and your server can now inject whatever properties it wants. what’s difficult about this? what’s a “workaround”? if anything, the natural conclusion is to proxy everything through the proxyUrl endpoint if you are a client and you want to deal with state in any way, or use your actor in any way. proxyUrl is your interface.
