Email or username:

Password:

Forgot your password?
Top-level
marius

@dansup I think that devs should offload the supported activities on the clients, not on the services side. An activitypub server should accept whatever, and then only the clients will interact/show what they support.

As long as you think in terms of what your AP services supports, you'll end up with needless complexity.

4 comments
dansup

@mariusor Most implementations have a web client that render activities, are you saying they should support other activities (and implement C2S) that may never be exposed to the vast majority of users?

I'd say the issue isn't so much C2S vs S2S, but rather having unified UI components across all clients.

marius

@dansup I think decoupling frontends from the services is the way to go.

dansup

@mariusor That assumes the frontend can support the constraints of the backend/ActivityPub implementation.

marius

@dansup yes. That's the point. Allow clients to expose to users whatever they want to support. Everything else is ignored.

Go Up