Take control over your live stream video by running it yourself. Streaming + chat out of the box.

golangvideochathlsrtmplivestreambroadcastinghacktoberfestliveowncastself-hostedstreaming-video

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: 8098304967

0.1.1

backend-refactor

btrimports

dependabot/npm_and_yarn/test/automated/browser/cypress/request-and-cypress-3.0.1

develop

gek/admin-api-disable-cors

gek/auto-complete-chat-input

gek/browser-test-errors

gek/ffmpeg-6

gek/fix-access-token-validation

gek/initial-replay-functionality

gek/ios-browser-notifications

gek/load-tests

gek/new-load-tests

gek/router-refactor

gek/test-caches

gek/transcoder-log

gek/user-repository

gek/video-test-page

l10n_localization

localization

localization_updates

renovate/cssnano-5.x

renovate/knip-3.x

renovate/nextjs-monorepo

renovate/preact-10.x

renovate/react-monorepo

renovate/regexpu-core-6.x

renovate/stylelint-15.x-lockfile

renovate/stylelint-16.x

renovate/video.js-7.x

replays-clips

replays-clips-recordings

vaapi-hardware-decoding

v0.0.1

v0.0.10

v0.0.11

v0.0.12

v0.0.13

v0.0.2

v0.0.3

v0.0.4

v0.0.5

v0.0.6

v0.0.7

v0.0.8

v0.0.9

v0.1.0

v0.1.1

v0.1.2

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '8098304967'

${ noResults }

owncast/core/chat/events

History

Ruffy 9c484efd36 Feature/oc 1316 add support for system message to single user (#1351) ... * add public func to lookup a ChatClient by its clientId * add facility to send a system message directly to a user * add clientId field to UserEvent * implement simple http endpoint to send a message to a user * let mux handle new directSystemMessageToUser endpoint * add ClientId to UserEvents across the codebase * render body of system-message to client * add clientId to Chat-Message * add tests showing how url-parsing should work * add simple rest endpoint helpers for parameter-parsing and easy routing * use newly added rest-endpoint helper to rout to Client-Messaging controller * use safe "ReadRestUrlParameter" to parse ClientId * remove empty HandleFunc in router * set Header directly to prevent built-in (platform-dependent) canonicalization to kick in * fix typo in "Parameter" message * remove debug-logging of HTTP headers in REST-helpers * convert to uint32 to prevent overruns when converting to wraptype uint later on * resolve linter-ouchies * resolve linter potential nil-deref warning * document the SendSystemMessageToClient endpoint in swaggerdoc * remove clientId assignment causing potential nil dereference in userDisabledEvent-case as the clientId isn't relevant here anyway * make findClientById private, so its not accessible outside of core/chat * remove redundant string type hint * Update PR based on linter requirements Co-authored-by: Raffael Rehberger <raffael@rtrace.io> Co-authored-by: Gabe Kangas <gabek@real-ity.com>		4 years ago
..
actionEvent.go	Expanded linting + fix warnings (#1396)	4 years ago
events.go	Feature/oc 1316 add support for system message to single user (#1351)	4 years ago
eventtype.go	Expanded linting + fix warnings (#1396)	4 years ago
nameChangeEvent.go	Expanded linting + fix warnings (#1396)	4 years ago
systemMessageEvent.go	Expanded linting + fix warnings (#1396)	4 years ago
userDisabledEvent.go	Expanded linting + fix warnings (#1396)	4 years ago
userJoinedEvent.go	Expanded linting + fix warnings (#1396)	4 years ago
userMessageEvent.go	Expanded linting + fix warnings (#1396)	4 years ago