Proposal for Social-Output

Is your feature request related to a problem? Please describe.
Opposite to Social-Input I not only wish to receive, I also wish to publish or react to content. So this propose is to split nextcloud/social into nextcloud/social-input and nextcloud/social-output. Social-output depend on social-input but social-input not on social-output .

Describe the solution you'd like
Social Output is the Place to show me and my thinking. Content I publish here should not be Work or Club activity relevant in first place. Any Output here do not address a to-do to a certain person. It depends on the free will of other if they see this published data.
There are two type of Content that could be created, live-streams and recorded-data.

• Live-Streams could be live TV, a Webinar, a webcam and it's may or may not a possible to live interact to it's content. Being part of it usually need a specific date and time-frame where you could focus on the content.

• Recorded-Data could be common fedivers content like, blogs, feeds, broadcasting messages and notifications. A reaction could be done independent to a time and date.

• Output could be several kind of protocols like activityPub, matrix, a blog on a website or an RSS-Feed.

• It should be possible to re-route publications to nextcloud/spreed if you wish to be able to instant react and participate on a discussion or re-route answers to Nextcloud/Mail if the reaction to the publication contains an important time independent conversation.

Describe alternatives you've considered
MS-Teams, Outlook, Twitter, Whatsapp Status, Facebook

The issue names no files, tests, or entry points. Start by clarifying the scope and architecture for splitting social-output from social-input, including the proposed live-stream, recorded-data, and protocol integrations. Done requires an agreed, implementable specification before code can be located.