Email or username:

Password:

Forgot your password?
Top-level
dansup

I would think the modular UI components would be most challenging, as you'd have to make them interoperable with each other.

Could abstract the complexity of mapping ActivityStreams verbs + compatibility to UI components and side effects with a visual drag-n-drop tool.

8 comments
dansup

If there was a standard way to list capabilities across fediverse software, you could also transform objects to ensure compatibility and limit delivery to compatible instances.

The federation.md thing is nice, but its not machine-readable. If we solved this, we could make the fediverse much more efficient!

smallcircles (Humane Tech Now)

@dansup there are various SocialHub topics on going beyond FEDERATION.md, both towards machine-readable capability discovery, and a more standardized way of documenting capabilities.

Григорий Клюшников

dansup, I've been talking about this exact thing for at least a year. Like, "I would like to know in advance whether this object supports this activity". This would also make sense to combine with privacy settings, as in, "you can send this activity but only if this actor follows you".

smallcircles (Humane Tech Now)

@dansup the standard way to discover capabilities will eventually be much needed.

But I'm interested in what comes before: the ease-of-development of entirely new application types that are not silo's afterwards, but rather building-blocks for a more task-oriented fedi.

Here thinking that AP vocab extensions represent the domain structure found by DDD and messages represent some of the events from the domain-driven design (event storming) as they travel the network. AP is wire protocol here.

GeneBean

@dansup something like this could help the entire fediverse implement consistent moderation abilities instead of every project starting from scratch.

Go Up