Eli Mallon
Eli Mallon
Allow users to bring their own S3 credentials; when segmenting we'll upload everything there for archival Could be in this format: `s3+https://ACCESS_KEY_ID:[email protected]/bucket`
``` [signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x6242ebbea18e] | -- | -- | | goroutine 396758 [running]: | | | stream.place/streamplace/pkg/director.(*StreamSession).NewSegment.(*StreamSession).Go.func12() | | | panic: runtime error: invalid memory address...
This is working including the creation UI in `/settings` with `rtmp://` and `rtmps://` URLs. It's all based on database polling at the moment, which isn't ideal but is good enough...
Example run: https://git.stream.place/streamplace/streamplace/-/pipelines/2815/test_report?job_name=test ``` 2025-09-23T19:51:40Z ERR gstreamer error error="This file is invalid and cannot be played." caller=pkg/media/bus_handler.go:38 segment_conv_test.go:185: Error Trace: /builds/streamplace/streamplace/pkg/media/segment_conv_test.go:185 /builds/streamplace/streamplace/pkg/media/leak_test.go:200 /builds/streamplace/streamplace/pkg/media/segment_conv_test.go:162 Error: An error is expected but got...
Need to have a multi-node setup (prolly with Docker?) and do stuff like change origins, start up and shut down nodes, make sure stuff still gets replicated
From the [Lexinomicon](https://github.com/bluesky-social/atproto/discussions/4245): > Because atproto accounts can be used flexibly with any application in the network, it can be ambiguous which accounts are participating in a particular app modality....
This is so we can link to the privacy policy on https://stream.place without making every node operator require our privacy policy. Prolly useful for other stuff too. I guess we'll...
Browser time being wrong has caused all sorts of unrelated issues, more recently this one but there have been others: We should look into using the server to normalize client-side...
This isn't 100% fixable — if a VPN doesn't wanna let WebRTC traffic through then it's not gonna. (It's very sniffable because it very intentionally uses the same SRTP/SIP header...