<JacobWeisz[m]>
If it's something you found in Rocket.Chat's control panel, it almost certainly won't work with the Sandstorm version. I don't believe it has any powerbox network code in it.
<isd>
I see that rocket.chat has IRC integration. If somebody ever updates the app, it would be really neat to get that actually working, and bridge a grain to this channel somewhere.
<ill_logic>
Does anybody use Rocket Chat on Sandstorm? It seems like something that's a cool tech demo but usefulness would be rather limited.
<ill_logic>
Maybe someone who wants to be really secluded.
<isd>
Like I said, "If somebody ever updates the app" -- I would assume that would imply interest.
<isd>
Honestly I'd rather see a sandstorm-first chat app, lighter weight but still not totally feature-bare. But... so many projects, so little time.
<isd>
TimMc was asking about chat app options not that long ago
<TimMc>
We're probably going to go with Matrix at this point.
<isd>
Probably the right call.
<JacobWeisz[m]>
ill_logic Arguably if you're using a Sandstorm server internal to an organization our Rocket.Chat app would meet the same needs businesses use Slack or Teams for. Secluded isn't a bad thing always, and it works when Slack or Teams has a global outage. ;)
<JacobWeisz[m]>
But yeah, I think chat isn't an area Sandstorm currently shines.
<TimMc>
I would *really* like the ability to remove the Sandstorm shell for certain grains, maybe via the same mechanism as "publishing".
<TimMc>
If I could expose a RocketChat grain as a fixed domain, that would solve several problems (while yes, opening up various security issues...)
<isd>
TimMc: are you actually looking to not have the grain inside the Sandstorm UI, or would it suffice to map a "well-known" domain to essentially a sharing link?
<TimMc>
It's the shell itself.
<TimMc>
Alternatively, introduce mechanisms to convey favicon changes, browser consent requests, and other things...
<TimMc>
But I feel like that list is non-terminating.
<TimMc>
(session storage...)
<isd>
Some of these are things I'd like solutions to that don't require dropping the UI.
<isd>
e.g. it really sucks that apps can't ask for access to the camera now. It means doing e.g. video chat is impossible.
<JacobWeisz[m]>
Standalone domains would also basically do what TimMc is looking for.
<JacobWeisz[m]>
With the whole "not really supported" disclaimer, of course.
<isd>
The "standalone grains" feature I don't think solves those: the iframe is still there, it's just collapsed so the user can't see it.
<JacobWeisz[m]>
True
<isd>
But it will still get in the way some of those things
<TimMc>
I wonder how much of this could be done with a script injected into the top of the page by Sandstorm.
<TimMc>
Set a watch for favicon changes, proxy the consent requests, etc.
<isd>
...but it looks like there are a bunch of places where we aren't actually doing that, nor are we doing anything that looks like an actual query of the subscription, so I'm confused.
<isd>
e.g. grainTopBar; we're doing .publish and .subscribe, but I don't see it directly used anywhere?