"do one thing and do it well" #activityPub #unixPhilosophy
Conversation
Notices
-
dansup (dansup)'s status on Sunday, 03-Mar-2019 08:25:04 CET dansup
-
dansup (dansup)'s status on Sunday, 03-Mar-2019 08:25:55 CET dansup
A general ActivityPub implementation would be awesome if it ships with a UI that supports every ActivityStreams verb!
-
dansup (dansup)'s status on Sunday, 03-Mar-2019 08:29:07 CET dansup
I think the Friendica project will be the first to reach this huge milestone!
-
Jacky Alciné (jalcine)'s status on Sunday, 03-Mar-2019 09:01:41 CET Jacky Alciné
@dansup I don't know. If there's a library that could parse everything but didn't ship with a UI then we could have specialized UIs for each implementations.
-
dansup (dansup)'s status on Sunday, 03-Mar-2019 09:05:05 CET dansup
@jalcine Yeah but what if the backend couldn't handle specific features like filters or subtitles? You would need the logic in the backend because the client couldn't handle every specific feature.
-
Jacky Alciné (jalcine)'s status on Sunday, 03-Mar-2019 09:12:42 CET Jacky Alciné
@dansup I figure the backend is just storing information - decoupled from presenter logic (that way one could actually have multiple frontends but one same core)
-
dansup (dansup)'s status on Sunday, 03-Mar-2019 09:13:58 CET dansup
@jalcine What if the backend has to process something like transcode a video or handle live streaming? It can't be decoupled.
-
Jacky Alciné (jalcine)'s status on Sunday, 03-Mar-2019 09:15:06 CET Jacky Alciné
@dansup that's processing that wouldn't happen client-side (or presenter side). I'd figure something like video transcoding could be done and the proper information (bitrate, dimension, etc) could be exposed in the AP info.
I also have not yet dug deeper into how to do a soups-to-nuts implementation of AP
-