@admin Any idea why now, every time I connect FastSM to this instance, it keeps saying stream connection lost? Is streaming broken for some reason? @MewProjects
@x0 @admin @MewProjects Oh na, that hhappens here as well, probably FastSM but haven't investigated.
@jonathan859 @x0 @MewProjects Nope, was on our end :)
@admin @x0 @MewProjects Huh? @admin I get thhat message as well. What was the issue for dragonscave?
@jonathan859 @x0 @MewProjects @admin Just dependency issues that weren't immediately obvious
@jonathan859 @admin @x0 @MewProjects Not sure how this account got tagged in this thread, but is there an issue we're not aware of on SomePlace.Social?
@admin @jonathan859 @x0 @MewProjects Just a coincidence that one of your members had an error that aligned with an error some of our users were experiencing for a bit. You're fine (I think) :)
@admin @admin @x0 @MewProjects X0 described an issue where the FastSM client was outputting stream connection lost. I had the same issue for a while earlier, it seems to work now, but apparently it was not a client issue, so I was just wondering if you know something on that matter. Seems to work for now though, so nothing urgent. Will let you know if it returns.
@jonathan859 @admin @x0 @MewProjects Okay, sounds good. Well, we are running the latest Glitch-Soc alpha, and there are some more updates coming down the pipe to do with collections. It is possible that part of the API is not yet complete or functional. Uncertain if the client attempts to interact with these elements, but they are very new, and not officialy part of the spec yet, so I doubt that is the issue. Best thing to do is to try multiple clients, and if a problem appears on more than one, then it is likely an instance issue, and not a client issue. We will begin an investigation if these conditions are met.