SceneCity - privacy-focussed live streaming and chat for the demoscene

category: general [glöplog]
Will there be VOD support with chat replay?
added on the 2022-04-19 22:05:44 by Gargaj Gargaj
VOD would be very easy to do (and will be done). Chat replay would be harder to do, and we'd have to see the implications in regards of our focus on privacy (data retention periods). But having a chat replay at least for a couple of days after a live event might be fine. Needs to be discussed.
added on the 2022-04-19 22:10:17 by scamp scamp
Also, we need more coders. The list of feature requests already is quite long - too long for just three developers.
added on the 2022-04-19 22:11:38 by scamp scamp
Is the source on Github? Where does one see the list of issues/feature requests ?
added on the 2022-04-20 12:53:05 by DaD1916 DaD1916
Bug reports and feature requests are on the ~SceneCity channel.

Right now the source code is distributed on different places (every developer used his own system), but we'll merge that into a GitLab repo soon.
added on the 2022-04-20 17:10:53 by scamp scamp
GitLab?! [sourcehut](https://sr.ht/) is far more in line, spirit-wise, I'd say.
added on the 2022-04-23 22:43:18 by Y0Gi Y0Gi
Oh dang, wrong markup.

added on the 2022-04-23 22:45:31 by Y0Gi Y0Gi
Same is true for IRC, you can /mode a passworded channel and even get the ban list when you're banned.
added on the 2022-05-11 19:39:29 by Gargaj Gargaj
If you use discord for sensitive projects you’re a moron. But I see In the Twitter thread it’s about crypto projects so that checks out.
added on the 2022-05-11 22:12:56 by okkie okkie
Nice, looks very professional. Would it be possible to join the chat room with some kind of desktop client such as Element?
added on the 2022-05-12 06:41:07 by wabe wabe
There are a couple of desktop clients mentioned here:


A couple of months ago I also started working on a native code desktop client because I had the sluggish electron crap, but not sure if I'll ever find the time to complete it...
added on the 2022-05-13 09:33:01 by scamp scamp
y0gi: Self-hosted gitlab instance, that is.
added on the 2022-05-13 09:34:17 by scamp scamp
Alright, that makes sense.
added on the 2022-05-13 22:41:18 by Y0Gi Y0Gi
This weekend we are live-streaming from Outline. Starting now at SceneCity TV
added on the 2022-05-26 23:30:20 by scamp scamp
The oauth login link says "404 Not Found: No request handler found".
added on the 2022-05-28 22:46:17 by reed reed
More like a slideshow here, but thanks for trying anyway.
added on the 2022-05-28 22:57:40 by Sir Sir
The oauth login link says "404 Not Found: No request handler found".

Seems to work now, thanks :)
added on the 2022-05-28 23:01:01 by reed reed
Sorry, fixed now.
added on the 2022-05-29 01:45:19 by scamp scamp
Scamp, FYI: Friday and Saturday afternoon the stream was totally unusable. I mean: maybe 1 second of sound/picture followed by 10-20 seconds of buffering, then goto 10 (and repeat for as many hours you want). You can probably imagine how well a dj set, or anything really, worked with that... :). I tried different browsers, different machines, different stream configurations (both bandwidth and the webrtc/hls/dash thing, whatever they are), different servers (well, those the system threw at me, but at least two different servers were shown), it was all the same. The only thing I didn't try was a different internet provider; lucky me, I had a friend in a different country (which happened to be Germany, btw) who experienced pretty much the same, though maybe a bit diluted.

Based on the above experiences, I'm willing to risk that the problem was either at Outline or at Scenecity.
added on the 2022-05-29 04:46:22 by blala blala
@blala I had the same problem but scamp found a bug. Apparently the cause is a memory leak in the streaming server. After he restarted it it was mostly OK. Hopefully fixed on the next party :)

Thanks for streaming and nice to see people using and joining SceneCity!
added on the 2022-05-29 08:30:45 by neoman neoman
For me the stream was not more or less stable than many streams via twitch in the past. But it also might be my old machine :D That being said: Thank you and keep pimping SceneCity!
First, it was nice to have a stream at all! :)
First of all: My ego demands to say that we had over 100 viewers who did NOT have problems with the stream according to the feedback.

That being said: SceneCity is a long-term project and a huge, complex beast. We got three different stream types, and 40 relay servers across the world.

Which means that if you have problems with the stream, proper debugging needs to be done so we one day are mostly bug-free.

First of all, our system is defaulting to the "Webrtc low-latency" stream type. This has an end-to-end latency of 150ms (!). It's video conferencing technology. And just as with video conferencing, this only works if your own internet connection is PERFECT. Which means using a cable. If you at home are on WiFi, it will suck. Most users that had problems were in that situation. In future we will make the safer HLS stream the default.

Those who had problems and switched to HLS said stuff was fine.

Next: A set of 5 relay servers out of 40 right now are dymically chosen based on your Geo location. So you end up with the relay server nearest to you, but that might not be the best one. In future there will be an automatic speed test in the background to find out which server you have the best and most stable speed to.

And finally: We had to bring our own Internet via a tower of four bonded LTE links, but this was setup in a rather... hackish way. This was needed as the location Internet was slow and dropping out. Which means on Thursday and Friday, our upstream stability wasn't perfect yet. On Saturday however it mostly was, with a minimal amount of our outgoing stream packets getting dropped. I could verify this by watching the stream myself.

In summary: Saying "the stream sucks for me" does not help anyone. If you have problems, we need a proper bug report. We need to know what relay you are on, what stream type you are using, if you are on the 10Mbit/s or 5MBit/s version, and you need to make sure before it's not just your own Internet connectivity sucking.

Collect this info, and report on the SceneCity channel on SceneCity, which exists exactly for this kind of bug reports. We only can improve things if we get proper bug reports and have time to investigate. Which means: You should report the problem as soon as you see it.
added on the 2022-05-29 13:46:24 by scamp scamp
Scamp: I only wrote the above comment because I was not sure that you were aware of the problem. As the stream worked much better during revision, and the problem persisted among different geographical regions, this seemed to be an issue on the streaming side.

As I explained, I tried _all available configurations_, and different hardwares/software configurations too, many times, and at least several other people, in different countries, had the exact same issue. Which was apparantly fixed by Saturday evening when you actually had 100+ viewers, and if we can believe the above comment, _it was fixed by you_, so please don't bullshit me with "we had over 100 viewers who did NOT have problems"

I don't have anything more detailed to report than "it buffered continuously between 1 seconds of playback here or there", but in any case it appears that you know exactly what was the cause.

In any case, let me finish with that I'm very glad that you are working on Scenecity, it's a great project, and sincere thanks for offering us this service! especially that it's free. But please try to communicate a tiny bit less... aggressively? defensively? whatever.
added on the 2022-05-29 16:19:29 by blala blala