@Dominic I think that prioritising pub servers you follow is a good thing (and so far I have only experienced positive outcomes from it), but the way I did it was a bit hacky - probably only works for pubs you were invited to.
Merged and released as v0.0.4
This might be another --use-global-ssb problem? It seems to work fine for me.
I remember noticing the other day when the internet went down (but still connected to wifi) that nothing would play. Tried to get to the bottom of it but unfortunately the internet came back up before I could! Everything works fine when I turn wifi off, so it must be something about having a network connection available. I'm sure I could simulate it, but haven't yet gotten around to it.
Ah I see why this isn't working. Yes it is related to the global identity.
For some reason I couldn't get blobs to upload through
ssb-client, so they are getting done directly on the server. But since
--use-global-ssbdoesn't run a server it throws an error.
Need to try and figure out what's wrong with uploading blobs via the client then this can be fixed!
It should be keeping everything. But I'm using webtorrent to do the actual streaming to the audio element, so whenever you play the file webtorrent starts seeding it, which might be what you are seeing.
What version are you running? A bug caused it to depend on an internet connection to start playing (was resolving the magnet every time instead of caching the .torrent).
haha or maybe a smiley face? A green glowing orb? I agree by the way.
There are a few files in there with bad encoding. I had the ffmpeg settings wrong. They don't stream properly and you can't seek ahead. Could this have possibly been the cause?
Oh and I only just started checking the issues on git-ssb WHOOPS! I'm using patchwork so it only shows git-ssb issues after someone comments.
Built with git-ssb-web